• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 78 subscribers
  • Views 421 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

security violation in release mode in msp430bt5190

sarang bagade
Prodigy 10 points
Other Parts Discussed in Thread: MSP430BT5190

      I am a firmware developer.I am working on Bluetopia stack and using MSP430BT5190. I also using IAR workbench. 

The main problem is the controller resets after 2-3 seconds when the controller is in the release mode.But when it is in the debug mode it works normally without reset.

I then checked the SYSRSTIV register to see the cause of error.I found its security violation(the value is 0x0A).

I then searched the cause of security violation on forums.I found that its because of the access to BSL area or any protected area.But I havent changed the SYSBSLC register.So it has the default value and BSL code area is not protected.

So I still dont know what is the cause of the reset.So tell me about this.

Also the main problem is why it resets only during the release mode but not in the debug mode.  

I searched a lot but no one has such a problem.

  • 0
    Guru 227245 points

    Unless you wrote (or included) code that is conditionally compiled, the only difference between debug mode and release mode is that in release mode, more compiler optimizations are active. This may affect application timing (especially if the timing is implicit or rather coincidental, and not done using a timer)
    If this makes a difference, then your code Is faulty, making assumptions that contradict the assumptions the compiler code optimizer makes. (Be assured, that the compiler is usually right and the coder is wrong, assuming things that are not covered by the C language standard)

    To see what happens, a closer look at your code is required.

**Attention** This is a public forum