Forum Discussion

MViss4's avatar
MViss4
Icon for New Contributor rankNew Contributor
5 years ago

Nios II Software Build Tools for Eclipse (Quartus Prime 18.1) frequently crashing

When debugging a project through the "debug" or "run" option eclipse frequently crashes. Find below 2 examples of the screens which appear when eclipse crashes. This is really annoying as you also ma...
Isaac_V_Intel's avatar
Isaac_V_Intel
Icon for Contributor rankContributor
5 years ago

Hello Mviss,


My apologize for this inconvenient tool crash. This is not common thing and few customer reported about this crash. there is no straightforward way to detect the root cause.

However, we do have some recommendations to our customers to try it out, and mostly one of those suggestions would help them:

  1. Change the workspace location.
  2. Create a new NIOS II aplciation.
  3. Clear the JAVA cache on your machine, simply go to control panel > Java > General > Temporary Internet files > Settings > Delete files.
  4. Un-install JAVA and re-install it.
  5. If all these things didnt work, then you might need a fresh installation of eclipse.

Also, is this crash come from any NIOS II application? or specific application?


Best regards,

Isaac Vazquez.


TheRealNeil's avatar
TheRealNeil
Icon for New Contributor rankNew Contributor
3 years ago

I want to add that I see this or similar error every time I debug with NIOS II Software Build tools for Eclipse.

I've generally found that the issues lies within attempting to disconnect from the target hardware. If a clean disconnect is not made (which happens often as the debugger can't make a clean break ~25% of the time) I have to perform the below steps.

When this happens I need to

  1. Close Eclipse
  2. Power off target hardware
  3. Unplug JTAG cable
  4. jtagserver.exe --stop
  5. jtagserver.exe --start
  6. Open task manager, close all instances of eclipse
  7. In task manager, close EXTRA instances of jtagserver.exe / nios2-gdb-server.exe (multiple will usually be spawned from failed debug attempts)

After this things will generally come back to a working state but not always.

Note that if I don't force close these applications from the task manager, my CPU and memory usage quickly go up to 100% each.

I have to go through these steps 10-15 times per day on a good day. At times I will spend 10-15 minutes attempting to get the debug environment back up and running.

If there is any information or follow up to this at all I would love to hear it. As it currently stands this is a very difficult tool to use, and especially unfortunate that it happens so often in debugging when things are already difficult.