Get help
If something in Chipforge doesn’t work the way you expect, check Troubleshooting first. If that doesn’t solve it, email us.
Contact support
Section titled “Contact support”Email support@chipforge.ai. To help us answer quickly, include:
-
Your Chipforge version. See Find your version.
-
Your operating system and its version.
-
Where your designs run: on this computer, or on a remote server. If you use a remote server, include its Linux distribution and the companion version on it.
-
What you did, what you expected, and what happened instead. Copy the exact text of any message Chipforge showed.
-
Your log file. See Find your logs.
Find your version
Section titled “Find your version”- In the desktop app, choose Help → About Chipforge. The version looks like
0.5.4. - In Settings → Updates, the Chipforge section shows the Installed version.
- To see the version of the companion the app runs, point at the Companion status in the top bar. It shows the version after Connected.
- On a remote server, run the companion with
-versionfrom the folder you installed it in, for example~/.local/bin/companion -version. It prints a version such asv0.3.3.
Find your logs
Section titled “Find your logs”Choose Help → Open Logs Folder, and send us the files in that folder. chipforge.log is the desktop app’s log. When the app runs its own companion, the companion’s messages are in the same file. When a log grows large, Chipforge starts it again, so send your logs soon after the problem happens.
If the app doesn’t start, open the folder yourself:
%LOCALAPPDATA%\dev.chipforge.desktop\logs~/Library/Logs/dev.chipforge.desktop~/.local/share/dev.chipforge.desktop/logsIf you set XDG_DATA_HOME, the folder is $XDG_DATA_HOME/dev.chipforge.desktop/logs.
On a remote server, the companion writes its messages to standard output. If you run it as the systemd user service described in Work on a remote EDA server, read them with:
journalctl --user -u chipforge-companion