--- Quote Start ---
This seems un-scientific ... I tried to re-produce the result seen before lunch with the automation folks and was not able to reproduce the result. ie no red MAX_EROR LED.
--- Quote End ---
The un-scientific term is that you have a Heisen-bug, i.e., a bug that disappears when observed :)
--- Quote Start ---
Does that mean the Cyclone card was in some state that when the nios2-terminal was connected and the card power cycled caused the MAX_ERROR LED to come on ...
--- Quote End ---
Its hard to say until you can duplicate the error systemically on your board, and then on another. Only then do you know you're not dealing with a mildly damaged board.
--- Quote Start ---
Just 1/2 an hour ago I saw another Cyclone card locked up with the MAX_ERROR LED stuck on and in that case the NIOS Eclipse GUI was active not a NIOS Command terminal ... so I agree I need to work some more to get to root cause ... all I can say was that ... whatever I did in my office environment ... I got to a matching behavior as seen in an automation environment.
Let me gather some more info on this and modify the status to .... "trending to solved ....."
--- Quote End ---
If you could determine whether the JTAG chain is still valid when the error occurs, that would be a useful piece of information :)
Good luck!
Cheers,
Dave
Honored Contributor
