• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 22 subscribers
  • Views 2832 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

How to Debug/Simulate an STM32 program from RAM in µVision4

Torsten Schoenitz

What is necessary to simulate or debug a STM32 program that is intended to run in RAM?

In µVision4 the program is located and loaded in RAM, but start debugging results in a jump to 0x00000000.
Setting the SP and PC registers manually doesn't solve the problem.
Is it necessary to define a minimal vector table that resides at 0x00000000 to make debugging possible?

Parents
  • 0 in reply to Thorsten de Buhr

    You load the program into RAM and set the PC - normally done by an init scipt. A number of Keil examples have RAM targets and a startup script for this.

    When the program starts, no interrupts are enabled, so it doesn't matter if the interrupt vector table has been remapped or not. But your code (or the startup file) must perform the remapping of the interrupt vector table before any interrupt handler is configured.

Reply
  • 0 in reply to Thorsten de Buhr

    You load the program into RAM and set the PC - normally done by an init scipt. A number of Keil examples have RAM targets and a startup script for this.

    When the program starts, no interrupts are enabled, so it doesn't matter if the interrupt vector table has been remapped or not. But your code (or the startup file) must perform the remapping of the interrupt vector table before any interrupt handler is configured.

Children
No data