Menu

Theme

Advanced features · How-to · CHECKED ON 5.0.0

VHDL and Verilog with Logisim-evolution

Logisim VHDL and Verilog export works in 5.0.0: map every input and output to a board, then generate HDL only from the FPGA window or with the --test-fpga … HDLONLY command; without the mapping it stops with Not all IO components have been mapped. The language comes from the FPGA settings. You can also add your own VHDL as a VHDL Entity component, but we could not simulate it without an external simulator. We found no Verilog import in 5.0.0.
FOR
Students moving from schematics to HDL, and users who want their own VHDL inside a circuit
CHECKED
12 Nov 2026
Checked against Logisim-evolution 5.0.0 on 1 machines
On this page

What works in 5.0.0

Feature2.7.15.0.0
Export a circuit as VHDL2.7.1: nonot tested5.0.0: yestested (F112)
Export a circuit as Verilog2.7.1: nonot tested5.0.0: yestested (F112)
VHDL Entity component2.7.1: nonot tested5.0.0: partialplaced and saved; not simulated (F119)
Simulate a VHDL entity2.7.1: nonot tested5.0.0: partialneeds a simulator we did not have
Compile the exported files2.7.1: nonot tested5.0.0: partialVerilog elaborated and evaluated, VHDL analysed; not simulated (F128)

Export a circuit as VHDL or Verilog

You do not need a board or vendor software, but you do need to pick a board and map every pin, because the export is part of the FPGA flow.

  1. Open FPGA, Synthesize & Download…

    Choose a target board and leave the action at Generate HDL only. File, Preferences, FPGA Commander Settings holds the language setting (VHDL by default, or Verilog).

  2. Press Execute and map the pins

    A mapping window lists Unmapped Components. Select one and double-click a highlighted spot on the board picture; it moves to Mapped Components. Do this for every input and output, then press Done. The window is taller than many screens; our lab needed a very large virtual display to reach Done.

  3. Save the project

    Saving writes the map into the file as a boardmap element, so the next export can run from the command line.

The command-line form is covered on the command line page and the board list in the FPGA guide.

Where the files go and what they contain

Files are written to logisim_evolution_workspace/<project name>/<circuit name>/ in your home folder. For the full adder (VHDL):

  • ▸ vhdl/
    • ▸ circuit/
      • main_entity.vhd← ports A, B, Cin in; Cout, S out
      • main_behavior.vhd← signals and the gate instances
    • gates/← AND_GATE, OR_GATE, XOR_GATE_ONEHOT, each as entity and behavior
    • toplevel/← logisimTopLevelShell wrapper for the board
  • ucf/XilinxConstraints.ucf← pin constraints (a Xilinx board)
  • scripts/← XilinxScript.cmd, XilinxVHDLList.prj, XilinxDownload

With Verilog selected the same run writes one .v file per module under verilog/circuit, verilog/gates and verilog/toplevel. A counter driven by a Clock component adds support files for the clock and the counter.

An excerpt of the entity our full adder produced:

Terminalvhdl
ENTITY main IS
 PORT ( A    : IN  std_logic;
        B    : IN  std_logic;
        Cin  : IN  std_logic;
        Cout : OUT std_logic;
        S    : OUT std_logic );
END ENTITY main;

Download the top-level files our export wrote for the full adder: main_entity.vhd, main_behavior.vhd and the Verilog main.v. They need the gate files from the same run, and we did not compile any of them.

Add a VHDL entity to a circuit

  1. Choose Project, Add VHDL Entity…

    A prompt titled VHDL Entity Name appears. Type a name. The menu also has Import VHDL Entity….

  2. Write or import the code

    The editor opens with a template. Its ports (clock, val, max, cpt) are examples; replace the whole text. The first button above the editor opens a chooser for .vhd or .vhdl files, which is how we loaded ours.

  3. Place the entity and save

    Select the entity in the explorer and click the canvas. Save the project.

LAB lab-lnx · Linux lab5.0.02026-11-12
Project, Add VHDL Entity asks for the entity name first.lab-lnx-le500-vhdl-name-01
A prompt titled VHDL Entity Name with an empty text field and OK and Cancel buttons.
LAB lab-lnx · Linux lab5.0.02026-11-12

The VHDL editor in Logisim-evolution 5.0.0 showing a 2-input XOR entity with ports a, b and y, and the explorer with the entity xor2.

The editor after importing our xor2 file. The three buttons above the text import, export and validate.lab-lnx-le500-vhdl-editor-02
The VHDL editor showing a 2-input XOR entity with ports a, b and y, next to the explorer.

Our entity is a 2-input XOR; download the source as xor2.vhd.

Simulation needs an external program

The Simulate menu has VHDL Simulation Enabled and Restart VHDL simulator.

LAB lab-lnx · Linux lab5.0.02026-11-12
The Simulate menu has two VHDL items. Enabled is unticked by default.lab-lnx-le500-vhdl-simulate-menu-01
The Simulate menu with the items VHDL Simulation Enabled and Restart VHDL simulator after Reset Simulation.

Ticking the first item opened a folder chooser. We had no simulator, so we cancelled it.

LAB lab-lnx · Linux lab5.0.02026-11-12
Ticking VHDL Simulation Enabled opens a folder chooser.lab-lnx-le500-vhdl-questa-folder-01
A folder chooser with the field Folder name set to the home directory and Select and Cancel buttons.

Afterwards the canvas showed a red message that VHDL simulation is not running and asks you to enable it and check the simulator setup (the rest of the text is cut off in the pane). A VHDL simulator log panel appeared and stayed empty, and the entity’s output stayed undefined.

LAB lab-lnx · Linux lab5.0.02026-11-12
Without a simulator, the canvas says VHDL simulation is not running and the log stays empty.lab-lnx-le500-vhdl-simulator-log-01
A circuit with an xor2 entity block, the red message VHDL simulation is not running and an empty VHDL simulator log panel.

We did not point the chooser at Questa or ModelSim, so we do not know how a working simulator behaves.

Using the exported HDL elsewhere

We checked the exported files with two free tools (F128). The Verilog of the full adder was elaborated in Yosys and all eight input rows gave the expected sum and carry; the 4-bit counter synthesised without errors. The VHDL of the full adder, the counter and an XOR gate was analysed with vhdl_lang and gave no errors; the counter reported four warnings for signals that are declared and never used. This is static analysis, not simulation, and we did not run Vivado, Quartus, GHDL or Icarus, so we make no claim about them.

A “Logisim to Verilog converter”

No separate converter is needed. The export above is the way, after you map the pins.

Verilog import

We found no Verilog import in 5.0.0. Upstream describes one on its development branch; we will test it when it is released. See what is new in 5.0 and releases.

The FPGA guide covers boards and the mapping window; the .circ file page shows where the map and the VHDL are stored; and the error messages list has the mapping stop.

Frequently asked questions

Can Logisim export Verilog?

Yes. In our test the same mapped circuit gave VHDL files by default and Verilog files after the language preference was set to Verilog (F112).

Can I use VHDL code inside a Logisim circuit?

Yes: Project, Add VHDL Entity… creates an entity you can place in a circuit. We placed and saved one (F119).

Do I need ModelSim or Questa?

To simulate a VHDL entity, apparently yes: without it we got the message VHDL simulation is not running and the entity output stayed undefined. Exporting HDL needs no simulator.

Can Logisim import Verilog?

We found no Verilog import in 5.0.0. Upstream notes one on its development branch, which we have not tested.

Can classic Logisim 2.7.1 export HDL?

We did not test 2.7.1. Our component data lists no HDL generation for it.

Sources

  1. HDL export and VHDL entity tests on Logisim-evolution 5.0.0, logisim.dev lab data: test-data/lab21-2026-11-12-hdl/
  2. FPGA window and boards, logisim.dev lab data: test-data/FINDINGS.md F51, F109

Try: , , ,