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.

MSP430 program crashes with security violation

Other Parts Discussed in Thread: MSP430F5529

I'm running an application in which my MSP430 based microcontroller is resetting with SYSRSTIV value 0A or security violation. I have no idea what may be causing this reset. Is there a way to set a breakpoint in the RESET_VECTOR interrupt service routine or otherwise halt the processor before the system dies, so I can inspect the call stack for what may be causing the reset?

  • Hey Nate,

    What device are you using?

    This is an interesting question, but unfortunately, I don't believe that it's possible to breakpoint an interrupt that is going to getting a BOR. I've at least never seen an example of this.

    As you're probably aware, a security violation means your firmware somehow ran into the weeds and tried to eventually access secured memory/flash.

    Do you have the memory to increase your stack size to try and test against an overflow?

    Thanks,
    JD
  • Hey Nate,

    Here is the block diagram of the interrupt block in the MSP430F5529.  As you can see, the RST signals and Password/security violations trigger straight into the Reset circuitry.  There is no interrupt vector or ISR to breakpoint on.  

    Thanks,

    JD

  • You can breakpoint at the reset entry point, i.e. the address pointed to by the reset vector at 0xFFFE. This will be after the reset, so PC, SR, and the device registers will have been cleared to reset values.

    SP, RAM, and the General Registers will be intact, so you can look through the stack. CCS won't be much help, so you'll need some patience. I've done this quite a number of times.

    One way to find the reset entry point is to use the Hard Reset (icon in the ribbon which looks somewhat like an MCU chip).

**Attention** This is a public forum