F53xx SYSRSTIV - Security Violation

Rick Nardone

Other Parts Discussed in Thread: MSP430F5324

I was wondering what can cause the "security violation" reset reason on the MSP430F5324. The SYSRSTIV value is 0x0a (10 decimal). The user's guide doesn't seem to have much detail at all.
Some quick forum searches indicate it may be related to accessing BSL memory when its protection bit is set, or other "protected" memory locations. This may be indicative of a stack overflow or RAM corruption causing out-of-bounds pointer access.

If you have a definitive list of all the things that can cause this particular reset reason, that would be helpful.

Best,

Rick Nardone

over 13 years ago

0 Priya Thanigai over 13 years ago

TI__Mastermind 26380 points

Rick,

To my knowledge the only cause for this flag to be set is access to protected areas such as boot code and protected BSL. They can try disabling the BSLPE bit (sysbslc register) to see if this still occurs.

We have seen this happen in case of illegal accesses (perhaps to peripheral area?) for example when a pointer overflows and points to "0x0000".

A careful check of the code before the violation occurs should narrow down the cause.

I will check with systems to see if there are any other causes.

Regards,

Priya

0 Rick Nardone over 13 years ago in reply to Priya Thanigai

TI__Genius 10405 points

Hi Priya,

Thanks for your response!

Best,

Rick

0 Priya Thanigai over 13 years ago in reply to Rick Nardone

TI__Mastermind 26380 points

Rick,

To reconfirm only access to proetcted BSL or bootcode would cause a security violation.

An access to peripheral space (or any memory gaps) would result in a VMAIFG (vacant memory access IFG).

-Priya

0 Rick Nardone over 13 years ago in reply to Priya Thanigai

TI__Genius 10405 points

Thanks again for the confirmation.

Best,

Rick

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

F53xx SYSRSTIV - Security Violation