Forum Discussion
Any idea?
I am thinking on adding a Signaltap to discover what is happening. But which signals should be probed in this case? To get some usable information about the situation? Is there some useful internal signals to check, or just external Avalon MM?
Hello Steve,
Have you tried debugging the application using the Nios II Eclipse Debugger? Setting breakpoints after the function can help determine where the application is getting stuck. You can also use SignalTap to observe internal signals, and the Nios II plug‑in to capture the processor’s address and data activity. The external Avalon‑MM signals should be sufficient for this level of debugging. However, before relying on hardware traces, I recommend stepping through the application in the Nios II debugger to identify which specific function call is causing the issue.
Thank you,
Fawaz.