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.
Each press of KEY0 adds one to a binary number on the LEDs. A tap on KEY1 does nothing; holding it for a second clears the count.
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 |
|---|---|---|
KEY0 | U14 → PIN_B8 (KEY[0]) | Each press adds one |
KEY1 | U14 → PIN_A7 (KEY[1]) | Hold for a second to clear |
LEDR0 | PIN_A8 (LEDR[0]) | Bit 0 of the count |
Sensors and actuators this board drives, with the real connections.