Skip to content

Troubleshooting

Find the message you see, or the closest symptom. Messages are shown in code as Chipforge displays them, or by their first words; … stands for a part that changes, such as a name, or for the rest of the message. If nothing here helps, contact support and include your log files.

When you sign in, Chipforge opens your default browser and waits for it to hand you back to the app. While it waits, the Sign in button in the top bar reads Signing in…. If you started from the sign-in page, its button reads Waiting for your browser… instead.

If you finished signing in but the app is still waiting, the browser tab may be stuck on the sign-in form even though it worked. To open the sign-in page in your browser again, select Signing in… in the top bar, or Open the sign-in page again on the sign-in page. On the sign-in page, you can also select Cancel sign-in and start over.

On Linux, a browser installed as a snap can refuse to hand the sign-in back to Chipforge. Sign in with a browser that wasn’t installed as a snap.

Sign-in will not be able to finish on this machine

Section titled “Sign-in will not be able to finish on this machine”

This warning appears above the sign-in button when nothing on your computer is set up to receive Chipforge’s sign-in links. That happens when Chipforge runs from an unpacked copy instead of an installed one. Install Chipforge with its installer, or on Linux with the .deb package, then start the installed copy. See Install Chipforge.

Something went wrong. This looks like a problem on our end…

Section titled “Something went wrong. This looks like a problem on our end…”

The sign-in didn’t complete. Select Didn’t work? Try again. If the message keeps coming back, contact support and include your log file.

The full message ends with Ask your Chipforge contact to add your account to an organisation. Your account isn’t a member of a Chipforge organization, or your organization’s access is paused. Ask the person who invited you, or your Chipforge contact.

Chipforge signed you out because the service no longer accepted your session. Anything you have open stays as it is. Select Sign in to continue, or Not now to sign in later.

The Companion status in the top bar shows whether the app can reach its companion: the local service that runs your EDA tools and works with your project files.

The Companion status stays on Connecting…

Section titled “The Companion status stays on Connecting…”

Chipforge is starting its companion, or reaching the one on your remote server. If the companion doesn’t start, the status changes to an error and offers Restart services. Select it. If it fails again, quit and reopen Chipforge, then contact support with your log file.

The app lost contact with its companion. Check the Companion status, and select Restart services if it offers it. If you work on a remote server, see Work on a remote EDA server.

The SSH connection to your remote server dropped. Chipforge reconnects on its own, and the Companion status shows when it’s back. Work that was already running on the server keeps running.

Connected to …, but found no Chipforge companion running as that user

Section titled “Connected to …, but found no Chipforge companion running as that user”

SSH works, but the companion isn’t running under your account on the server. Start it there, then select Detect again. See Run the companion on the server.

An SSH message such as …: Permission denied (publickey). or Host key verification failed.

Section titled “An SSH message such as …: Permission denied (publickey). or Host key verification failed.”

Chipforge shows the message that ssh printed. Chipforge can’t type a password or answer a prompt, so your SSH key must work without one, and the server’s host key must already be known. Test this from a terminal; the command must finish without asking you anything:

Terminal window
ssh -o BatchMode=yes you@eda-server true

No `ssh` program was found on this machine.

Section titled “No `ssh` program was found on this machine.”

Install an OpenSSH client, then try again.

The companion on the server is too old to accept uploads. Update the companion on the server. Downloads still work in the meantime.

This line appears under a simulator or toolchain picker when Chipforge can’t find a tool. Select it to see why each tool is missing and which setting fixes it. See Toolchains and simulators.

The project’s toolchain isn’t installed on the machine your designs run on, or Chipforge can’t find it. Install it, or set its location in Settings → Local Toolchains.

The simulator couldn’t get a licence. The message ends with the licence variables that tool reads. Set them in Settings → Local Toolchains → License variables. See Licences.

The path of your project folder contains a character that the tool can’t handle. The message names the tool, the character and a suggested place to move the project to.

A simulation stops at Module <…> not found for an AMD primitive, XPM macro or IP

Section titled “A simulation stops at Module <…> not found for an AMD primitive, XPM macro or IP”

Chipforge 0.5.4 doesn’t add the AMD simulation libraries to a simulation. A design that instantiates an AMD primitive such as MMCME2_ADV or FDRE, an XPM macro, or Vivado IP stops with this error in the Vivado simulator (xsim). Icarus Verilog shows Unknown module type instead, and Verilator Cannot find file containing module. The assistant may suggest another simulator or updating the companion; neither helps in 0.5.4.

Simulate the blocks that don’t use them in Chipforge, and simulate the parts that do in a Vivado project, which adds the libraries for you.

This chat hit its limit. Please continue in a new chat.

Section titled “This chat hit its limit. Please continue in a new chat.”

The chat has no room left. Select Continue in new chat. The new chat starts with a summary of where the work stands.

When the assistant reaches its limit of steps for one message, it ends with a short note on where it stopped. Send another message to let it carry on.

The AI service is temporarily unavailable. Please try again in a moment, or contact support if it persists.

Section titled “The AI service is temporarily unavailable. Please try again in a moment, or contact support if it persists.”

The service couldn’t get an answer from the AI model. Try again in a moment.

This organisation has reached its usage limit.

Section titled “This organisation has reached its usage limit.”

The service stopped taking the assistant’s requests for your organization. Retrying won’t help until this is resolved on Chipforge’s side, so contact your Chipforge contact.

That file type cannot be read by the current model.

Section titled “That file type cannot be read by the current model.”

Convert the file to PDF, or paste its contents into the chat as text.