Greetings,
If I leave the FVP idle for around 1 hour and come back to it, I find that it freezes and have to stop the simulation and re-run it again. What is the possible reason for this and is there a way to stop that from happening? Thank you for your help and support!
Best regards,
Mohannad Ismail
Thank you for your reply.
Sure I apologize. I'll give you the details I can and let me know if you need something else more specific.
There aren't any error messages when it freezes. There are cases when I am running an application like gdbserver and it freezes and other times I am not, but mostly it is when I am not. In the Fast Models window, the counter for the instructions on Cluster0 is still increasing, so maybe it's not completely frozen, but I can't type anything in the terminal nor can I even SSH to it. I don't see any other visible indications or error messages.
There is also another issue that happens sometimes when starting the FVP. On FVP terminal_1, I get a constant stream of "ignoring interrupt" messages and it never boots completely. This doesn't happen very often but happened several times. Any insight on this also would be helpful.
Any help on these two issues is appreciated. Let me know if you want something else that I can look for. Thank you for your help!
thanks for the additional info. regarding the "freeze" issue, could you try the following? start the FVP with the CADI server running, (CADI is the Debug API in Fast Models that enables the connection of debuggers such as Arm DS to the model). To start CADI add "-RS" to the command line when you start the FVP and run as usual. When the FVP "freezes" you can run the debugger and connect to the model, From there you can examine the run state of the model, etc.
Do you have access to Arm DS, or another debug solution that you can use?
I currently am using gdbserver for debugging the programs. I think that the debugger would require a license for me to use it, am I right? I am not sure if it's possible to use gdbserver to do what you are asking. Which debug solution would you suggest?