• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 595 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

TM4C1294NCPDT: What is this SVCall exception?

TM4C1294NCPDT: What is this SVCall exception?

mm3010
Prodigy 210 points
Part Number: TM4C1294NCPDT

Hi community, 

I am experiencing a strange behaviour. After some time the program is running in the controller, the SVcall exception raises. In the first, I was believing this was related to the swupdate.c utility, following the thread "What is this SVCall exception?". 

The project has used the TI bootloader in previous revisions and now is not used anymore. But the utility has never given troubles when not used (even if it is in the project). Now, I have removed the instructions of the swupdate utility, but the SVcall exception is still happening. 

The image refers to the core registers status:

Have you some advice to debug the code? 

Thanks to all.

  • 0
    TI__Guru 72500 points
    The SVCall exception is just the software initiated interrupt that occurs upon execution of the SVC assembly instruction. This is often used in operating systems to change into a privileged mode. To see where the SVC instruction is, set a breakpoint on your SVC vector and then look at the stack. The stack should contain the xPSR before the exception and the return address. The return address should point to the instruction following the SVC call.
  • 0 in reply to Bob Crosby
    Prodigy 210 points

    Thank you for your reply.

    I forgot to mention that I haven't an operative system.

    I have set the breakpoint on the SVC vector. But it is not hit when the exception happens, but the program goes in the FaultISR(). Actually, going deeper in the debug I've seen that the register values saved in the exception stack frame reports for xPSR a value of 0xA10C0000, so there is not an SVCall exception. Probably, the excpetion number raises a SVCall following the previous fault.

    Thank you Bob!