This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Single stepping with ARM Realview Debug

Note: This was originally posted on 22nd September 2012 at http://forums.arm.com

Hi,

I am working on ARM Versatile Express Cortex A9x4 (Quad core) board. I am using RealView ICE and Realview Debugger. Application was built with command line tools from Mentor Graphics which utilizes Nucleus SMP kernel GNU tool chain. Current build configuration uses two cores only. I wanted to navigate through a critical step of source for individual core (one core should be stopped while stepping through the other is being performed). To accomplish this, I have disabled synchronization of step option in synchronization control (snapshot attached)  . The application runs successfully as long as no break-point is enabled. Whenever I enable a break point, the application halts there and does not perform single stepping. Even if I disable break-points later in that session , it still remains there unless and until I reset the cores and disconnect and re-connect them.

Can anyone suggest some solution?

I have gone through the documentation of Realview Debug. Unfortunately, it covers too little in multicore domain. If anyone has link to such any document, please share it with me.

Regards,

Ejaz
Parents
  • Note: This was originally posted on 25th September 2012 at http://forums.arm.com

    The message "Warning: No stack/heap or top_of_memory defined - setting top_of_memory to 0x00080000 " means that RVD doesn't know what to tell the image if it asks (via semihosting) what the stack/heap boundaries are.  If your image doesn't ask then the warning doesn't matter.  Alternatively you can websearch the message and find the explanation of how to set the values in the RVD user guide.
Reply
  • Note: This was originally posted on 25th September 2012 at http://forums.arm.com

    The message "Warning: No stack/heap or top_of_memory defined - setting top_of_memory to 0x00080000 " means that RVD doesn't know what to tell the image if it asks (via semihosting) what the stack/heap boundaries are.  If your image doesn't ask then the warning doesn't matter.  Alternatively you can websearch the message and find the explanation of how to set the values in the RVD user guide.
Children
No data