GUI form vs JSON

Your LibreLane configuration can be edited two ways — a guided form or raw JSON. They're two views of the same config.json, and they stay in sync, so you can switch whenever it suits the task.

Two views, one config#

There's only ever one config behind the scenes. Edit a field in the form and the JSON updates; edit the JSON and the form reflects it. You're never maintaining two copies.

Form and JSON in sync

Interactive demo · coming soon

Change a value in either view; the other follows.

The guided form#

The form lays out the common settings with labels and sensible inputs — design name, Verilog files, clock port and period, PDK. It's the safest way to make a change when you're not sure of the exact key name or value format.

Raw JSON#

The JSON view gives you the full config directly. Reach for it when you want to set something the form doesn't surface, paste a config in wholesale, or work quickly because you already know LibreLane.

Which to use#

Form to learn, JSON to move fast

  • New to LibreLane, or touching a key field? Use the form.
  • Comfortable with the config, or setting an advanced option? Use the JSON.
For what the individual fields mean, see Key parameters.