Loading the figure…
Stopped · Your code isn't running yet. Until you press Run, the board runs the program already on it.
Nothing printed yet. Press Run.
Not checked yet
Run your code to check it. The checks replay a fixed script on a virtual clock, so the same code always gets the same result.
Each fault really happens in the simulation. Trigger one, watch the figure, then read why.
Play the world: press, slide and turn the parts while the code runs.
Change a value here or click a chip in the code.
Each press of BTNC adds one to a binary number on the LEDs and BTNU clears it. Real buttons bounce, so the design cleans the signal up first.
iynk runs your Verilog as a behavioural model, cycle by cycle on the board clock. It does not synthesise, place or route: no timing, no LUT counts.
| Pin | Connects to | What it does |
|---|---|---|
BTNC | FPGA pin U18 (btnC) | Each press adds one |
BTNU | FPGA pin T18 (btnU) | Clears the count |
LD0 | FPGA pin U16 (led[0]) | Bit 0 of the count |
Sensors and actuators this board drives, with the real connections.