Editor and terminal

The Workspace is where your files live. It is a code editor with a terminal, running in the browser. Open it with Open Workspace from any page.

Where projects are#

Each project is a folder under ~/project. Move into one before running a stage:

cd ~/project/mychip
ls -a
cat README.md

Editing files#

Open a file from the file list to edit it, or use nano or vi in the terminal. Changes are saved to your project straight away. Nothing is run until you start a stage.

Running stages from the terminal#

Every button on Overview has a command. See the Command reference.

nelix test
nelix synth
nelix build

A run started from the terminal and a run started from a button are the same thing. Both appear on Overview and on the Runs page.

The terminal on Overview#

Overview has a Terminal tab for the project you have selected, and a Log tab that shows a run while it is going. Use them for a quick command without leaving the page.

Quick checks in the terminal#

The terminal has GHDL, Icarus Verilog (iverilog, vvp), Yosys and Verilator (lint only) for quick checks:

ghdl -a rtl/counter.vhd && ghdl -e counter
iverilog -o /tmp/a.out rtl/top.sv && vvp /tmp/a.out
verilator --lint-only rtl/top.sv

These are for trying things out. The real run, with its record on Overview, is still Simulate (or nelix test). The terminal cannot build C++ with Verilator or run cocotb: use Simulate for those. An editor that is already open gets the tools the next time it starts.

Files to keep where they are#

Keep rtl/top.sv, tb/test_top.py and openlane/config.json at those paths. The lab looks for them there. See Project layout.