Most searched
Starting Logisim
Java, macOS, Windows and package-manager messages seen before the main window opens.
#Error: A JNI error has occurred, please check your installation and try again
Error: A JNI error has occurred, please check your installation and try againTerminal, or a Java error dialog. The 5.0.0 jar started with Java 8.
java.lang.UnsupportedClassVersionError: com/cburch/logisim/Main has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 52.0What it means
The 5.0.0 jar was built for Java 21 and your Java is older. The number in the message is the class file version: 52 is Java 8, 55 is Java 11, 61 is Java 17, 65 is Java 21.
| Class file version | Java |
|---|---|
| 52 | 8 |
| 55 | 11 |
| 61 | 17 |
| 65 | 21 (needed by 5.0.0) |
Fixes, most likely first
- Use the installer for your system (MSI, DMG, DEB or RPM). It bundles its own Java, so the system Java does not matter. tested by us
- Or install Java 21 and start the jar with java -jar Logisim-evolution-5.0.0-all.jar. Check with java -version first. tested by us
RelatedJava requirements and Java errorsLogisim won't open: launch troubleshootingDownload Logisim safely (all official builds)
#Error: LinkageError occurred while loading main class com.cburch.logisim.Main
Error: LinkageError occurred while loading main class com.cburch.logisim.MainTerminal. The 5.0.0 jar started with Java 17.
java.lang.UnsupportedClassVersionError: com/cburch/logisim/Main has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0What it means
The same cause as the entry above, reported by Java 17 in a different wording: the jar needs Java 21.
Fixes, most likely first
- Install Java 21, or use the installer, which bundles it. tested by us
RelatedError: A JNI error has occurred, please check your installation and try againJava requirements and Java errors
#java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper
java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapperTerminal. Classic 2.7.1 on Ubuntu with openjdk-8-jre-headless.
What it means
Java tried to load a GNOME accessibility bridge that this runtime does not include, and stopped before opening a window.
Fixes, most likely first
- Run 2.7.1 with Java 17 or 21. It starts on both (F21). tested by us
- Or start it with -Djavax.accessibility.assistive_technologies=" " in front of -jar. not tested by us
A related packaged-runtime case was fixed upstream in 5.0.0 (issue 2398). We did not test that fix.
RelatedClassic Logisim 2.7.1 todayJava requirements and Java errors
#Exception in thread "main" java.awt.HeadlessException
Exception in thread "main" java.awt.HeadlessExceptionTerminal. 5.0.0 with --test-vector or --new-file-format and no display; exit code 1.
What it means
These two options open windows, so they cannot run without a screen. The --tty mode does run headless.
Fixes, most likely first
- On a server or in CI, start a virtual display first (Xvfb) and run the same command. tested by us
- If you only need a truth table or a halt run, use --tty instead. tested by us
RelatedCommand line (tty) referenceTest Vector Builder and Checker
#Error: Invalid or corrupt jarfile …
Error: Invalid or corrupt jarfile …Terminal. Any jar.
What it means
Java could not read the file as a jar. The usual reason is an incomplete download, or a web page saved under a .jar name.
Fixes, most likely first
- Download again from the release page and compare the size and SHA-256 with the table on the download page (the 5.0.0 jar is 54,448,596 bytes). not tested by us
We have not reproduced this message with a truncated jar yet.
#macOS: “Logisim-evolution” Not Opened
“Logisim-evolution” Not OpenedmacOS 15 dialog on first launch of the app from the DMG, with buttons Done and Move to Trash. Captured on macOS 15.8.2 (Apple Silicon).
Apple could not verify “Logisim-evolution” is free of malware that may harm your Mac or compromise your privacy.A macOS dialog with a yellow warning triangle titled "Logisim-evolution" Not Opened. The text says Apple could not verify it is free of malware that may harm your Mac or compromise your privacy. The only buttons are Done and Move to Trash.
What it means
The app is ad-hoc signed and not notarized by Apple, so Gatekeeper blocks a file that carries the quarantine flag from a browser download. It is not a malware finding. The dialog has no Open button.
Fixes, most likely first
- Click Done, not Move to Trash. from Apple or Microsoft documentation, not tested by us
- Open System Settings, Privacy and Security, scroll to the message about Logisim-evolution and choose Open Anyway, then confirm with your password. from Apple or Microsoft documentation, not tested by us
- Or remove the flag in Terminal: xattr -dr com.apple.quarantine /Applications/Logisim-evolution.app (we confirmed the flag is removed, F29). tested by us
Both override paths follow Apple documentation and were not clicked through by us.
RelatedInstall Logisim on macOS (Apple Silicon and Intel)Logisim won't open: launch troubleshooting
#"Logisim-evolution" is damaged and can't be opened. You should move it to the Trash.
"Logisim-evolution" is damaged and can't be opened. You should move it to the Trash.macOS dialog after downloading the DMG on older macOS versions (community reports). Not seen on our macOS 15 runner, which shows the Not Opened dialog.
What it means
Same cause as the Not Opened dialog: the quarantine flag on an app that Apple has not notarized.
Fixes, most likely first
- Follow the fixes in the entry for the Not Opened dialog, in particular the xattr command. not tested by us
RelatedmacOS: “Logisim-evolution” Not OpenedInstall Logisim on macOS (Apple Silicon and Intel)Logisim won't open: launch troubleshooting
#“Logisim-evolution” cannot be opened because Apple cannot check it for malicious software.
“Logisim-evolution” cannot be opened because Apple cannot check it for malicious software.macOS first launch on older versions (community reports).
“Logisim-evolution” cannot be opened because the developer cannot be verified.What it means
The older wording of the same Gatekeeper block. On macOS 15 the dialog reads as the Not Opened entry above.
Fixes, most likely first
- Control-click the app and choose Open (older macOS), or use the Privacy and Security route and the xattr command from the Not Opened entry. from Apple or Microsoft documentation, not tested by us
RelatedmacOS: “Logisim-evolution” Not OpenedInstall Logisim on macOS (Apple Silicon and Intel)
#To open "Logisim" you need to install the legacy Java SE 6 runtime.
To open "Logisim" you need to install the legacy Java SE 6 runtime.macOS, classic 2.7.1 .app bundle.
What it means
The old app bundle asks for Apple's Java 6 runtime, which current macOS does not ship.
Fixes, most likely first
- Do not install Java 6. Run the 2.7.1 jar with Java 21 instead: java -jar logisim-generic-2.7.1.jar. not tested by us
Seen in community reports; we have not reproduced it.
RelatedClassic Logisim 2.7.1 todayInstall Logisim on macOS (Apple Silicon and Intel)
#Windows protected your PC
Windows protected your PCWindows SmartScreen when you run the downloaded MSI.
What it means
The MSI is not digitally signed (F25), so SmartScreen warns about an unrecognised publisher. The warning alone is not evidence of a problem.
Fixes, most likely first
- If the file came from the release page and its SHA-256 matches the download page, choose More info, then Run anyway. from Apple or Microsoft documentation, not tested by us
The exact button wording is cited, not captured by us.
RelatedInstall Logisim on WindowsDownload Logisim safely (all official builds)
#This app can't run on your PC
This app can't run on your PCWindows.
What it means
Windows says this for a file built for another processor type, or for a damaged download.
Fixes, most likely first
- Download the MSI that matches your processor (amd64 for most PCs, aarch64 for Windows on Arm). not tested by us
RelatedInstall Logisim on WindowsDownload Logisim safely (all official builds)
#Error: Cask 'logisim-evolution' has been disabled because it does not pass the macOS Gatekeeper check! It w…
Error: Cask 'logisim-evolution' has been disabled because it does not pass the macOS Gatekeeper check! It was disabled on 2026-09-01.Terminal: brew install --cask logisim-evolution. (Our CI runner prefixed the line with ::error::; that prefix is not part of the text.)
What it means
Homebrew disabled the cask because the app is not notarized. The cask was also stuck at version 4.1.0.
Fixes, most likely first
- Use the DMG from the release page and follow the macOS install guide. tested by us
#…/gtk-query-immodules-3.0: symbol lookup error: …/libgtk-3.so.0: undefined symbol: pango_font_family_get_face
…/gtk-query-immodules-3.0: symbol lookup error: …/libgtk-3.so.0: undefined symbol: pango_font_family_get_faceTerminal. Snap logisim-evolution (3.8.0, revision 4) on Ubuntu 24.04.
What it means
The Snap bundles its own GTK and prints this on start. The app still runs, and --tty gave a correct table. The bigger issue is that the Snap is 3.8.0 from March 2023.
Fixes, most likely first
- Use the .deb or the Flatpak instead, which install 5.0.0. tested by us
RelatedInstall Logisim on Linux
#PKGBUILD: line 34: unzip: command not found
PKGBUILD: line 34: unzip: command not foundTerminal: makepkg for the AUR package logisim-evolution-bin on a clean Arch system.
What it means
The PKGBUILD uses unzip without declaring it. It also declares java-runtime>=16 although 5.0.0 needs Java 21.
Fixes, most likely first
- Install unzip (sudo pacman -S unzip) and run makepkg again. The package then builds, installs and runs (F60). tested by us
- Check that the Java it picks is 21 or newer. tested by us
RelatedInstall Logisim on Linux
#xdg-mime: No writable system mimetype directory found.
xdg-mime: No writable system mimetype directory found.Terminal: dnf remove logisim-evolution with the release RPM in a minimal Fedora container.
%preun(logisim-evolution-5.0.0-1.x86_64) scriptlet failed, exit status 3What it means
The package's uninstall script could not update the MIME database. We saw it only in a minimal container where that directory does not exist. It should not appear on a normal Fedora desktop, but we have not confirmed that on a full install.
Fixes, most likely first
- Nothing to fix for a container. On a desktop, report it with your Fedora version if it appears. not tested by us
Seen in a container only.
RelatedInstall Logisim on Linux
#WARNING: Note: Java needs to be installed before using Logisim Evolution.
WARNING: Note: Java needs to be installed before using Logisim Evolution.Terminal: choco install logisim-evolution (5.0.0).
What it means
Chocolatey installs the all-in-one jar, not the MSI, so it needs Java 21. Scoop's extras bucket does the same and suggests java/openjdk.
Fixes, most likely first
- Install Java 21 first, or use winget or the MSI, which bundle Java. tested by us
RelatedInstall Logisim on WindowsJava requirements and Java errors
#Windows Defender Firewall has blocked some features of this app
Windows Defender Firewall has blocked some features of this appWindows, first launch. Wording assumed from the standard Windows prompt; not captured by us.
What it means
Users report a firewall prompt on first launch, which they trace to the update check. We did not capture it on 5.0.0.
Fixes, most likely first
- Allowing or denying network access does not stop the editor from working; the update check is the only network use we know of. not tested by us
Unconfirmed on 5.0.0.
RelatedInstall Logisim on Windows
Opening and saving files
Dialogs from loading, merging and saving a .circ file.
#Old file format -- compatibility mode
You are opening a file created with original Logisim code. You might encounter some problems in the execution, since some components evolved since then. Moreover, labels will be converted to match VHDL limitations for variable names.Dialog titled “Old file format -- compatibility mode” in 5.0.0 when the file was saved by a version before 2.7.2. The same text goes to the log in tty mode.
A dialog titled "Old file format -- compatibility mode" with a warning icon. It says: You are opening a file created with original Logisim code. You might encounter some problems in the execution, since some components evolved since then. Moreover, labels will be converted to match VHDL limitations for variable names. There is one OK button.
What it means
A warning, not an error. 5.0.0 is converting a classic-format file and will rename labels that break VHDL naming.
Fixes, most likely first
- Click OK. tested by us
- If wires stay grey and pins show 0, click an empty spot on the canvas or press Ctrl+R (Simulate, Reset Simulation). This happens after opening any file, including one saved by 5.0.0 (F45, F49). tested by us
- Keep a copy before you save. Once saved by 5.0.0 the file no longer opens in 2.7.1 (F04). tested by us
RelatedThe .circ file: open, convert, compatibility.circ Viewer and InspectorWire colours and values (E, X, U, orange)
#The built-in library FPArithmetic is not available in this version.
The built-in library FPArithmetic is not available in this version.Classic 2.7.1 dialog titled File Error when opening a file saved by 5.0.0 (first line). The second line is the 5.0.0 variant of the template, with curly quotes.
The built-in library “…” is not available in this version.A classic Logisim 2.7.1 dialog titled File Error with a red stop icon. The text starts: full-adder-v5: The built-in library FPArithmetic is not available, and continues past the edge of the box. There is one OK button.
What it means
The file uses a library that exists only in newer Logisim, and 2.7.1 does not have it.
Fixes, most likely first
- Open the file in Logisim-evolution (see the download page). tested by us
- Or ask whoever wrote it for a copy that avoids newer components. There is no safe automatic conversion back to the 2.7.1 format. tested by us
Users also report variants that name other libraries, such as HDL-IP and TCL.
RelatedDownload Logisim safely (all official builds)The .circ file: open, convert, compatibility
#Error encountered opening …: …
Error encountered opening …: …Both versions.
What it means
A wrapper. The part after the colon is the real reason, and is usually one of the other entries in this group.
Fixes, most likely first
- Read the second half of the message and look it up here. not tested by us
#XML formatting error: …
XML formatting error: …Both versions.
What it means
The file is not valid XML. A .circ file is XML, so this means it is damaged or is not a Logisim file at all.
Fixes, most likely first
- Open the file in a text editor. If it starts with an HTML tag, you saved a web page instead of the file (for example, Save link as on a GitHub file view). Download the raw file instead. not tested by us
- Check the file in the .circ viewer. not tested by us
Related.circ Viewer and InspectorThe .circ file: open, convert, compatibility
#The required library file ‘…’ is missing. Please select the file from the following dialog.
The required library file ‘…’ is missing. Please select the file from the following dialog.Dialog titled Locate ‘…’ in 5.0.0.
What it means
The project loads another .circ or .jar as a library, and that file is not where the project expects it.
Fixes, most likely first
- Select the file in the dialog that follows, and keep the project and its libraries in one folder. not tested by us
#Component not found or missing from library
component ‘…’ not foundOn load, 5.0.0.
component ‘…’ missing from library ‘…’What it means
The file uses a component this version does not have.
Fixes, most likely first
- Open the file in the version that saved it. The .circ viewer lists the version recorded in the file. not tested by us
Related.circ Viewer and InspectorThe .circ file: open, convert, compatibility
#Cannot save file
Could not save file: …Dialogs titled Cannot save file and File Not Available, 5.0.0.
You do not have permission to write to “….”What it means
Logisim could not write to the place you chose.
Fixes, most likely first
- Save to a different folder, such as one inside your home folder. not tested by us
- On macOS, a jar started by double-click may lack permission for Desktop or Documents. Run it from Terminal, or use the installer app. not tested by us
- In the Flatpak, files outside your home folder are not visible at all; save inside your home folder (F52). tested by us
RelatedInstall Logisim on LinuxInstall Logisim on macOS (Apple Silicon and Intel)
#Failed to create autosave for file: ‘…’. Will not try again for this file until after a restart.
Failed to create autosave for file: ‘…’. Will not try again for this file until after a restart.5.0.0 (autosave exists since 3.9.0).
What it means
The folder next to your file is not writable, so Logisim gave up on autosave for this file.
Fixes, most likely first
- Save manually now, and move the file to a writable folder. not tested by us
RelatedLogisim FAQ
#Components … and … exactly overlap each other. One has been moved slightly.
Components … and … exactly overlap each other. One has been moved slightly.On load, 5.0.0.
What it means
Two identical components sit at the same spot, for example in a hand-edited or merged file. Logisim moved one.
Fixes, most likely first
- Check that the moved component is wired as you expect. not tested by us
#Circular reference
The two tool messages appear in both versions; the two file messages in 5.0.0.
The file … contains within it a reference to itself.Cannot create circular reference. (The file is used by the … library.)Cannot add a subcircuit that uses this circuit, as it creates a circular reference.Cannot paste a subcircuit that uses this circuit, as it creates a circular reference.
What it means
A circuit cannot contain itself, directly or through other circuits or libraries.
Fixes, most likely first
- Break the loop: replace the inner use with a copy, or move the shared part into a third circuit that both use. not tested by us
#Circuit ‘…’ cannot be merged as the original project already contains a tool/circuit with the same name in …
Circuit ‘…’ cannot be merged as the original project already contains a tool/circuit with the same name in loaded library ‘…’Dialog titled Circuit name conflict, 5.0.0 merge or import.
What it means
The project you merge into already has a circuit or tool with that name.
Fixes, most likely first
- Rename one of the two circuits and merge again. not tested by us
#Could not open file: …
Could not open file: …Dialog titled Error During Open, 5.0.0.
What it means
The file is missing, moved or not readable.
Fixes, most likely first
- Check the path and the permissions, and try another folder. not tested by us
Simulation
Status-line messages and wire values while a circuit runs.
#Oscillation apparent
Oscillation apparentStatus line at the bottom of the canvas, both versions. Command line: halted due to detected oscillation. Test vector: oscillating.
Logisim-evolution 5.0.0 canvas with a NOT gate whose output wire loops back to its own input. The wire is red, and the output pin Q shows E.
What it means
A feedback loop never settles. In tty output a NOT gate wired to itself shows E and no text (F06).
Fixes, most likely first
- Break the loop, or add a flip-flop or latch that really stores a value. The full guide has the cases and the fix for each. tested by us
RelatedFix "Oscillation apparent"
#Incompatible widths
Incompatible widthsStatus line at the bottom of the canvas, with an orange wire; both versions.
Logisim-evolution 5.0.0 window with four test wires. Three of them are grey and their pins show 0. The fourth, from a 4-bit input to a 1-bit pin, is orange, with the words Incompatible widths at the bottom of the canvas.
What it means
Two things with different bit widths meet on one wire, for example a 4-bit bus into a 1-bit pin. The output reads U for every input (F09).
Fixes, most likely first
- Click the orange wire and the pins at its ends and make the Data Bits match, or split the bus with a splitter. tested by us
#Simulation halted by internal error
Simulation halted by internal errorCanvas, both versions.
What it means
A bug in a component or in the simulator.
Fixes, most likely first
- Save under a new name, choose Simulate, Reset Simulation, and reopen the file. If it repeats, report it upstream with the file. not tested by us
RelatedContact
#Value E (red wire)
EA red wire, or the value E on a probe or in tty output.
What it means
Two outputs drive the same wire with different values. Equal values give that value (F07).
Fixes, most likely first
- Find the second driver and remove it, or put a tri-state or a multiplexer in front of one. tested by us
#Value U (blue wire)
UA blue wire, or the value U on a pin or in tty output. Older documents write X.
What it means
Nothing drives the wire (F08). 5.0.0 shows U where older text says X.
Fixes, most likely first
- Connect an output or constant to the wire. Also check the previous entry about widths, which shows U on the output. tested by us
Editing circuits
Refusals while you place, move, name or delete things.
#Cannot modify circuit.
Cannot modify circuit.The first is the canvas status line; the second appears when you change an attribute. Identical strings in the 2.7.1 jar and the 5.0.0 source.
This circuit cannot be modified.What it means
The circuit on screen is not part of the file you have open. It belongs to a library loaded with Project, Load Library, Logisim Library, and library circuits are read-only. In the 5.0.0 source the Add, Wiring, Select and Text tools refuse when the project file does not contain the shown circuit.
Fixes, most likely first
- Open the library's own .circ file and edit it there, then reload the library. not tested by us
- Copy the circuit into your own project (5.0.0 can merge or export circuits). not tested by us
- Check the circuit list on the left: you may have double-clicked into a library subcircuit instead of your own. not tested by us
Cause confirmed from the source; not yet reproduced and photographed by us.
RelatedLibraries, merging and copying circuitsSubcircuits and custom appearance
#Conflicting component already there.
Conflicting component already there.Both versions.
What it means
You tried to place a component where an exclusive one already is.
Fixes, most likely first
- Move one of them. not tested by us
#Component cannot have negative coordinates.
Component cannot have negative coordinates.5.0.0.
What it means
The component would end up past the top or left edge.
Fixes, most likely first
- Move it right or down, or select everything and shift it first. not tested by us
#Attribute unchanged because request is invalid
Attribute unchanged because request is invalidDialog titled Value Invalid, 5.0.0.
What it means
The value you typed is not allowed for that attribute.
Fixes, most likely first
- Use a value from the list or the range the attribute accepts. not tested by us
RelatedPins, probes and constants
#The name is invalid (it must follow the rule ([a-zA-Z]+\w*)).
Dialogs in 5.0.0 when naming circuits and labelling components. The rules are stricter than in 2.7.1 because names must be valid VHDL.
The name is invalid (it must follow the rule ([a-zA-Z]+\w*)).This name is a keyword and can therefore not be used.This name is already in use in your project and can therefore not be used.Every circuit requires a name.Label is a reserved keyword and cannot be used. Please specify a different label.Label and component name may not be the same (they are case-insensitive). Please specify a label different from the component name.There exists already a component with this label! Please use unique labels in a circuit.The specified label equals a VHDL keyword. Please specify another name.The specified label equals a Verilog keyword. Please specify another name.Library must contain at least one circuit.
Logisim-evolution 5.0.0 message dialog that reads: alu1 : One component in the circuit has the same label as the component name of the newly placed component. This label has been removed! It has an info icon and one OK button.
What it means
Names and labels follow VHDL and Verilog rules so the circuit can be exported.
Fixes, most likely first
- Start with a letter, then use letters, digits and underscores only. not tested by us
- Avoid keywords such as AND, NAND or NOT, and do not give a component a label equal to its own name. not tested by us
- Keep labels unique inside one circuit. not tested by us
The label-equals-name case is the one our lab hit (F70).
RelatedSubcircuits and custom appearancePins, probes and constants
Memory images (ROM and RAM)
Loading hex images in the GUI and with –load.
#Hex file header not recognized
Hex file header not recognized5.0.0, Load Image in the GUI and --load on the command line.
What it means
The first line of the image is not a known format header. A plain list such as 0x11 0x22 is rejected and the memory stays empty.
Fixes, most likely first
- Make the first line exactly v2.0 raw, then the words in hexadecimal without 0x. tested by us
#Decoding with format 'v2.0 raw' produced 1 warnings.
Decoding with format 'v2.0 raw' produced 1 warnings.5.0.0.
Line 2: "zz" is not valid hex data.What it means
One token is not hexadecimal. That word loads as 0 and the rest load normally.
Fixes, most likely first
- Fix the token on the line named. tested by us
#No message: a value that is too wide is cut off
(no message)5.0.0.
What it means
A value wider than the memory's Data Bit Width is cut off with no warning: 100 in an 8-bit ROM becomes 00.
Fixes, most likely first
- Check widths with the memory image checker before you load. tested by us
#Image file has invalid format header
Image file has invalid format header.Classic 2.7.1 dialog titled Load Error.
Image file has some invalid contents.Image file has too much information.What it means
Classic 2.7.1 accepts only the v2.0 raw header.
Fixes, most likely first
- Use v2.0 raw as the first line. not tested by us
#Memory Image Load Error
Memory Image Load ErrorDialog title in 5.0.0 (2.7.1 uses Load Error).
What it means
A wrapper title. The body names the actual problem and matches another entry in this group.
Fixes, most likely first
- Read the body of the dialog. not tested by us
#The clipboard contents cannot be pasted into the editor.
The clipboard contents cannot be pasted into the editor.Hex editor (Edit Contents).
What it means
The pasted text is not hex words in the layout the editor expects.
Fixes, most likely first
- Paste plain hex words, or write a file and use Load Image. not tested by us
Command line
Messages from –tty, –load, –save and the other options.
#Invalid arguments for “--load”. Auguments should be <file> [label].
Invalid arguments for “--load”. Auguments should be <file> [label].5.0.0. The typo “Auguments” is in Logisim's own text.
What it means
--load takes every following argument as its own, so the .circ file has to come first.
Fixes, most likely first
- Put the circuit before the option: --tty table circuit.circ --load image.txt [label]. tested by us
RelatedCommand line (tty) referenceMemory Image Generator (ROM/RAM files)
#The “--load” option works only in conjunction with “--tty”.
The “--load” option works only in conjunction with “--tty”.First line 5.0.0, second line 2.7.1.
The "-load" option works only in conjunction with "-tty".What it means
Memory images load only in tty mode.
Fixes, most likely first
- Add a --tty format. not tested by us
RelatedCommand line (tty) reference
#No RAM/ROM was found for the “--load” labels: …
No RAM/ROM was found for the “--load” labels: …5.0.0.
What it means
The label after the file does not match any ROM or RAM.
Fixes, most likely first
- Check the label in the component's attribute table. not tested by us
RelatedCommand line (tty) referenceMemory Image Generator (ROM/RAM files)
#“--tty” requires at least one of the following: halt, speed, stats, table, tty, binary, hex, csv, tabs
“--tty” requires at least one of the following: halt, speed, stats, table, tty, binary, hex, csv, tabs5.0.0.
What it means
You gave --tty without a valid format.
Fixes, most likely first
- Add one of the formats named in the message. not tested by us
RelatedCommand line (tty) reference
#Using “--tty” requires a filename provided on command line.
Using “--tty” requires a filename provided on command line.5.0.0.
What it means
There is no .circ path on the command line.
Fixes, most likely first
- Add the path to the circuit. not tested by us
RelatedCommand line (tty) reference
#Error loading circuit file: …
Error loading circuit file: …Both versions.
What it means
The path is wrong or the file cannot be read.
Fixes, most likely first
- Check the path and permissions. not tested by us
RelatedCommand line (tty) reference
#No TTY or Keyboard component was found.
No TTY or Keyboard component was found.5.0.0.
What it means
--tty tty needs a TTY or Keyboard component in the circuit.
Fixes, most likely first
- Add one, or choose another format. not tested by us
RelatedCommand line (tty) reference
#The “--save” option works only in conjunction with “--tty”.
The “--save” option works only in conjunction with “--tty”.5.0.0.
No RAM was found for the “--save” option.What it means
As the messages say.
Fixes, most likely first
- Add --tty, and make sure the circuit contains a RAM. not tested by us
RelatedCommand line (tty) reference
#Argument for --gates option must be “ANSI” or “IEC”.
Argument for --gates option must be “ANSI” or “IEC”.5.0.0.
What it means
The value after --gates is not one of the two.
Fixes, most likely first
- Use ANSI or IEC. not tested by us
RelatedCommand line (tty) reference
#Specified locale is not supported.
Specified locale is not supported.5.0.0.
Supported locales:What it means
The language code is not in the list that follows.
Fixes, most likely first
- Use one of the codes listed. Chinese is zh. not tested by us
RelatedCommand line (tty) reference
Test vectors
Format errors and failing rows.
#Test vector does not match circuit
Dialog titled Error Loading Test Vector, 5.0.0.
Test vector in “…” does not match circuit. Details: ….Column … has no matching pinColumn … has width … but pin has width …Column … has width … but clock has width 1
What it means
A column heading does not match an input or output pin, or the width differs.
Fixes, most likely first
- Make the header names equal to the pin labels, with the same case and spacing, and match the widths. not tested by us
RelatedTest Vector Builder and CheckerTest vectors and automated testing
#Test vector could not be parsed
5.0.0.
Test vector in “…” could not be parsed. Detail: ….Test Vector header format error: bad width: …Test Vector data format error: too many valuesTest Vector data format error: not enough valuesTestVector format error: empty file
What it means
A syntax error at the line the detail names.
Fixes, most likely first
- Check the format rules and run the file through the test vector checker. not tested by us
RelatedTest Vector Builder and CheckerTest vectors and automated testing
#Error on test vector 8:
Error on test vector 8:Command line, 5.0.0.
S = 1 (expected 0)Passed: 7, Failed: 1What it means
Not a format problem: your circuit gave a different output for that row.
Fixes, most likely first
- Open the circuit, set the inputs from row 8 and compare the output with the expected value. tested by us
RelatedTest vectors and automated testingTest Vector Builder and Checker
#No message: exit code 0 on a failing test vector
(no message; exit code 0)Command line, 5.0.0.
What it means
A failing vector still exits with code 0, on every system we tried (F17).
Fixes, most likely first
- In a grader, parse the text for Failed: 0 instead of trusting the exit code. tested by us
RelatedLogisim for teachers and coursesTest Vector Builder and Checker
#Cannot show results while auto-ticking. Please stop clock first.
Cannot show results while auto-ticking. Please stop clock first.Dialog titled Auto-ticking not compatible with request, 5.0.0.
What it means
The clock is running while you ask for test-vector results.
Fixes, most likely first
- Turn off Simulate, Auto-Tick Enabled. not tested by us
#You do not have permission to read to “….”
You do not have permission to read to “….”5.0.0. “read to” is Logisim's wording.
What it means
The file is not readable by Logisim.
Fixes, most likely first
- Check the file permissions, and on macOS the privacy settings for the folder. not tested by us
Combinational Analysis
The Analyze Circuit window and the expression box.
#Analysis cannot handle more than … inputs
Analysis cannot handle more than … inputs.Dialog titled Cannot Analyze, 5.0.0.
Analysis cannot handle more than … outputs.What it means
The analyser has limits of 20 inputs and 256 outputs (AnalyzerModel).
Fixes, most likely first
- Split the circuit into parts and analyse each. not tested by us
#Computing truth table instead of expression due to Tunnel.
Computing truth table instead of expression due to Tunnel.Dialog titled Expression Not Determined, 5.0.0. The first line is the one we captured.
Circular reference detected; computing truth table instead.Conflicting outputs detected; computing truth table instead.Logisim-evolution 5.0.0 with a full adder built from gates and tunnels. A dialog titled Expression Not Determined says: Computing truth table instead of expression due to Tunnel. There is an OK button.
What it means
The circuit uses a Tunnel, feedback or conflicting outputs, so Logisim computes the truth table by simulation. The window still shows the table, the sum-of-products expressions and the Karnaugh maps from it. In our full adder, S and Cout came out right (F48).
Fixes, most likely first
- For Tunnels the message is harmless: click OK. tested by us
- If you need expressions derived from the wiring, replace the Tunnels with wires. not tested by us
Only the Tunnel variant was reproduced. The other two lines are from the source.
#Circuit oscillates.
Circuit oscillates.Analyze Circuit, 5.0.0.
Conflicting output values in circuit.What it means
The same two problems as in the simulation group, found while the analyser tries each input row.
Fixes, most likely first
- See the Oscillation apparent and E entries above. not tested by us
RelatedOscillation apparentValue E (red wire)Fix "Oscillation apparent"Wire colours and values (E, X, U, orange)
#Expression errors in the Analyze Circuit window
The expression box in the Analyze Circuit window, 5.0.0.
Unrecognized characters: ‘…’No matching closing parenthesis.No matching opening parenthesis.Operator “…” missing left operand.Operator “…” missing right operand.Unexpected apostrophe (“'”)“…” is not an input variable.Name must begin with a letter.Name duplicates existing variable.
What it means
Syntax errors in a typed expression.
Fixes, most likely first
- Check the expression against the accepted syntax. not tested by us
RelatedTruth Table and K-Map to Logisim CircuitCombinational Analysis: truth table to circuit
#Logic function(s) is/are all don’t care or not optimized. Cannot build circuit. Please provide (a) valid fu…
Logic function(s) is/are all don’t care or not optimized. Cannot build circuit. Please provide (a) valid function(s) or use the optimize button.5.0.0, Build Circuit.
What it means
Every output is don't care, or the table has not been minimised.
Fixes, most likely first
- Set at least one 0 or 1, and press Minimize first. not tested by us
RelatedCombinational Analysis: truth table to circuitTruth Table and K-Map to Logisim Circuit
FPGA and HDL
Toolchain, mapping and HDL generation.
#Required tools not found in Directory “…” !
Required tools not found in Directory “…” !5.0.0, FPGA Commander.
What it means
The Vivado or Quartus path in Preferences is wrong.
Fixes, most likely first
- Point the preference at the folder that contains the tools. not tested by us
#Workspace directory may not contain spaces!
Workspace directory may not contain spaces!5.0.0.
What it means
The workspace path has a space.
Fixes, most likely first
- Choose a path without spaces. not tested by us
#Error found in stage “…”
Error found in stage “…”5.0.0.
What it means
A toolchain step failed.
Fixes, most likely first
- Read the console output of that tool. not tested by us
Not tested on a board by us.
#Intel FPGA cable "…" was not found. Detected cables: …
Intel FPGA cable "…" was not found. Detected cables: …5.0.0, --fpga-cable.
What it means
The cable name does not match one the tool detected.
Fixes, most likely first
- Use a name from the list the message prints. not tested by us
Not tested on a board by us.
#Not all IO components have been mapped to the board "BASYS3"; please map all components to continue!
Not all IO components have been mapped to the board "BASYS3"; please map all components to continue!HDL generation, also --test-fpga … HDLONLY, which then exits with code 255. The board name varies.
What it means
HDL generation stops after the netlist and design-rule check because some pins have no board resource.
Fixes, most likely first
- Map every input and output to a board resource in the FPGA Commander, save the file, and run again. tested by us
RelatedFPGA boards: synthesize and downloadCommand line (tty) reference
#HDL generation: unsupported components, tri-state, widths, labels
5.0.0, HDL generation.
Found one or more components in your circuit that are not supported for HDL generation.Found a tri-state driver or floating output(s) for one or more components. This is not supported.Found a bit width connection problem.Found an invalid label.
What it means
The circuit contains something that cannot be turned into HDL.
Fixes, most likely first
- Replace the part, fix the width, or rename the label, then generate again. not tested by us
RelatedFPGA boards: synthesize and downloadVHDL and Verilog in Logisim-evolution
#VHDL simulation is not running. Enable it and check QuestaSim/ModelSim settings.
VHDL simulation is not running. Enable it and check QuestaSim/ModelSim settings.5.0.0.
What it means
VHDL entity simulation needs QuestaSim or ModelSim.
Fixes, most likely first
- Enable it in Preferences and set the tool path. not tested by us
#There is no current hw_target
There is no current hw_targetA Vivado message shown in the console.
What it means
Vivado cannot see a board.
Fixes, most likely first
- Check the cable driver, the USB connection and the board power. not tested by us
Not tested on a board by us.
Problems that show no message
Some failures show nothing at all. These are the ones we reproduced or that users report most.
- The jar opens in WinRAR or 7-Zip, or nothing happens. The file association points at an archive tool, or Java 21 is missing.
- A blank white window on a Linux tiling window manager. Java’s window handling does not match the window manager.
- The clock does not tick. Ticks need Simulate, Auto-Tick Enabled, or a manual tick.
- Wires stay grey and pins show 0 after opening a file. Click the canvas or press Ctrl+R (F45, F49).
- Files outside your home folder are invisible in the Flatpak. The Flatpak may only read and write your home folder (F52).
- The Snap installs the old 3.8.0. The Snap is two major versions behind (F53).
- –tty table never ends in 2.7.1. A known 2.7.1 behaviour (F05).
- ROM reads zeros with –tty table. The table is computed before the image loads (F13).
- A failing test vector returns exit code 0. Parse the text, not the exit code (F17).
- Browser downloads saved as .circ on Windows. The browser keeps a wrong extension from the download link.
Report a message we are missing
If your message is not here, send us the exact text, your Logisim version and your operating system through the contact page. If something on this page is wrong, tell us on the corrections page and we will fix it and note the change.