What you need
Supported boards
The 5.0.0 jar contains these 31 board definitions (F51). The resources are what Logisim itself listed when we ran --test-fpga with HDLONLY on a full adder for each board (F109). Each run reached the same stop (exit code 255) because nothing was mapped. No row means a board was programmed: we have none. The command line uses the same names (command line).
| ALCHITRY_AU_IO | 6 buttons, 3 dip switches, 32 LEDs, 1 7-segment (scanning) | Reached the mapping stop |
|---|---|---|
| ARROW_SOCKIT | 8 buttons, 4 LEDs | Reached the mapping stop |
| BASYS2 | 34 pins, 12 buttons, 16 LEDs | Reached the mapping stop |
| BASYS3 | 51 pins, 21 buttons, 28 LEDs | Reached the mapping stop |
| BEMICRO_SDK | 4 buttons, 8 LEDs | Reached the mapping stop |
| CYCLOARDUINO | 28 pins, 11 buttons, 10 LEDs | Reached the mapping stop |
| CYCLONE_V_GX_STARTER | 2 pins, 13 buttons, 18 LEDs, 4 7-segment | Reached the mapping stop |
| DE0_CV | 5 port i/o, 15 buttons, 10 LEDs, 6 7-segment | Reached the mapping stop |
| DIGILENT_CMOD_A7_15T | 54 port i/o, 2 buttons, 1 rgb leds, 2 LEDs | Reached the mapping stop |
| DIGILENT_SPARTAN_3E_STARTER | 2 pins, 9 buttons, 8 LEDs | Reached the mapping stop |
| EPM2525_CONSOLE | 5 pins, 10 buttons, 16 LEDs | Reached the mapping stop |
| EPM2525_FULL | 2 port i/o, 14 pins, 1 buttons | Reached the mapping stop |
| FPGA4U | 20 buttons, 100 LEDs | Reached the mapping stop |
| GECKO4LED | 6 buttons, 3 rgb leds, 1 dip switches, 64 LEDs, 3 7-segment | Reached the mapping stop |
| GECKO4_EDUCATION | 1 led arrays, 77 pins, 10 buttons, 2 dip switches, 4 7-segment | Reached the mapping stop |
| GECKO4_EDUCATION_EPFL_EDITION | 1 led arrays, 80 pins, 8 buttons, 2 dip switches, 2 LEDs, 4 7-segment | Reached the mapping stop |
| GECKO5_EDUCATION | 1 led arrays, 16 pins, 11 buttons, 1 dip switches, 1 7-segment (scanning) | Reached the mapping stop |
| LEGUAN | 1 led arrays, 40 pins, 12 buttons, 2 dip switches, 4 7-segment | Reached the mapping stop |
| MAX1000-8k-BOARD | 15 pins, 8 LEDs | Reached the mapping stop |
| MAX_V_80P_25P | 3 port i/o, 6 pins, 12 buttons, 1 rgb leds, 1 dip switches, 8 LEDs, 1 7-segment | Reached the mapping stop |
| MAX_V_CONSOLE | 2 port i/o, 6 pins, 21 buttons, 1 rgb leds, 1 dip switches, 24 LEDs, 1 7-segment | Reached the mapping stop |
| MICROLABTLE | 3 buttons, 8 LEDs | Reached the mapping stop |
| REPTAR_SPARTAN_6 | 1 local bus, 1 port i/o, 7 pins, 9 buttons, 1 dip switches, 8 LEDs, 3 7-segment | Reached the mapping stop |
| ROBOTCYCLONEFPGA | 16 pins, 11 buttons, 10 LEDs | Reached the mapping stop |
| SLO_MAX7000S | 82 pins, 23 buttons, 28 LEDs | Reached the mapping stop |
| TERASIC_DE0 | 1 port i/o, 14 buttons, 10 LEDs, 4 7-segment | Reached the mapping stop |
| TERASIC_DE0_NANO | 2 buttons, 8 LEDs | Reached the mapping stop |
| TERASIC_DE10_LITE | 1 led arrays, 7 port i/o, 19 pins, 2 buttons, 1 dip switches, 6 7-segment | Reached the mapping stop |
| TERASIC_DE10_NANO | 6 buttons, 8 LEDs | Reached the mapping stop |
| TERASIC_DE1_SOC | 2 port i/o, 6 7-segment (no dp), 14 buttons, 10 LEDs | Reached the mapping stop |
| ZYBO | 58 pins, 8 buttons, 4 LEDs | Reached the mapping stop |
No boards match.
The Synthesize & Download window
The FPGA menu has two items: FPGA Board Editor and Synthesize & Download…. The second opens this window (F109):
The Synthesize and Download window: Clock settings with Frequency 1.0 Hz and Divider value 1, Annotation method with an Annotate button, Action method with Toplevel main, the action Generate HDL only and an Execute button, a Target board list showing BASYS2 with its picture blurred, a Settings button, a button Select Xilinx's software and a progress bar reading Idle.
It has clock settings (frequency and a divider value), an annotation method, an action method with the top-level circuit, a target board, a button to choose the vendor software, and a progress bar with Infos, Warnings, Errors and Console tabs. With no vendor software chosen, the action list had one entry: Generate HDL only.
Settings
File, Preferences, FPGA Commander Settings holds the workspace location, the language used for generated HDL (VHDL by default), the list of external boards and the colours:
The FPGA Commander Settings tab of Preferences: Workspace location, Hardware description language VHDL, Use upper case for VHDL keywords ticked, an empty External FPGA Board list with Add a board and Remove selected board, two DRC suppress checkboxes, and colour settings for the board editor and board map.
That tab has no field for a Vivado or Quartus folder. In the Synthesize window the board’s vendor software is chosen with the button below the board picture (it read “Select Xilinx’s software” for a Xilinx board). We did not press it, so we do not know what it asks for.
Prepare and map your design
Prepare the circuit
Pins become the board’s switches and LEDs. Label them, as in the pins guide.
Check: Inputs and outputs are labelled; a top-level circuit exists.
Open FPGA, Synthesize & Download…
Pick the target board and the top-level circuit. The annotation method labels components that have no label or an invalid one.
Check: The window above opens.
Press Execute
On our unmapped full adder, Execute built the netlist, ran the design rule check, listed the board’s resources and opened a window with the unmapped components /A#0, /B#0, /Cin#0, /Cout#0 and /S#0.
Check: The mapping window opens when anything is unmapped.
Map and save
The window has Load Map, Save Map, Cancel and Done buttons. We did not map components, because the window is wider than our test screen. Save the project afterwards so the mapping is stored.
Check: The mapped list holds every component; the file is saved.
The mapping window opened by Execute: a list Unmapped Components with /A#0, /B#0, /Cin#0, /Cout#0 and /S#0, an empty list Mapped Components and buttons on the right. Behind it the Synthesize window is greyed out and the Infos tab lists the netlist steps. The board picture is blurred.
Common errors
Not all IO components have been mapped to the board “BASYS3”; please map all components to continue! | Map every input and output and save the file. From the command line this exits with 255. | Tested (F51) |
There is no current hw_target | Reported by users of Vivado with a Basys 3: the programming cable or its driver is not seen. Check the cable, the driver and the vendor tool's hardware manager. | Community report, not reproduced |
| VHDL compile errors in Quartus Prime | Reported on the project's issue tracker. We did not run Quartus, so we cannot say whether 5.0.0 still shows them. | Community report, not reproduced |
| RAM or buses behave differently on hardware | Reported as upstream issues. Check on a small design first. | Community report, not reproduced |
No rows match.
Add your own board
The FPGA Board Editor is in the FPGA menu, and Preferences, FPGA Commander Settings has an External FPGA Board list with Add a board and Remove selected board (F109). We did not open the editor, so we give no steps. See the project’s documentation on adding a board.
Generate HDL only (no board needed)
This is the part we tested. Choose Generate HDL only in the window, or run:
java -jar logisim-evolution-5.0.0-all.jar --test-fpga full-adder.circ main BASYS3 HDLONLY
Output: Building netlist for sheet “main”
Output: Circuit “main” has 8 nets and 0 buses.
Output: Circuit “main” passed DRC check.
Output: The Board BASYS3 has:
Output: 51 Pin(s)
Output: 21 Button(s)
Output: 28 Led(s)
Output: Not all IO components have been mapped to the board “BASYS3”; please map all components to continue!
exit: 255
A board must be chosen and every input and output mapped and saved first (F51). We did not run it on a mapped file, so we do not say where the HDL files are written. See VHDL and Verilog and the command line.
Limits
We did not test which components export to HDL, simulation against hardware differences, macOS or any vendor tool. We hold no board photos and show none: the board picture in our screenshots is blurred.