• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 553 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.

MSP430f6659 - "Security violation" reset when loading the project through the debugger (IAR)

noa graf
Prodigy 30 points

Other Parts Discussed in Thread: MSP430F6659

Hallo,

I am using the IAR IDE to write a project for MSP430f6659.

When I download my program using the IAR debugger, I receive a security violation while burning. This means that when I load the program with the debugger, the reset vector indicates that there was a security violation reset.

This happens only if I start a debug sessiong when my program is already running on the board.

If another program is running on the board, this does not happen.

If I load my program without the debugger (BOR), this does not happen.

and my program runs just fine - no resets (only when loading with the debugger).

Any ideas?

thanks

  • 0
    Guru 25210 points

    I have seen similar "flakiness" with my IAR setup since moving from XP to Win-7, but with an F5309 device. The debugger works just fine with my F2618 and F5438 projects, but the F5309 would halt at 0x0000 within seconds of running under debugger (works fine without debugger).

    I am not sure if it has something to do with using LPMx modes or not.

    I know this doesn't answer your question, but you are not alone! I use the MSP-FET430UIF pod with IAR.

  • 0 in reply to Brian Boorman
    Prodigy 30 points

    Hey Brian,

    I also experienced exactly what you describe, on the f5419a. It was solved by installing the latest patch of the IAR (5.6.6). They also list it as a bug fix in the release notes. The FET must be updated accordingly (this also doesn't work smoothly, I also stopped using the latest version of FET-pro-lite, since they do not agree on the latest version of the FET driver).

    thanks :)

  • 0 in reply to noa graf
    Guru 25210 points

    Unfortunately I am "stuck" with 5.50 at the moment (due to our corporate license), the most recent patches for that version didn't fix my problem, even with the latest FET firmware. And you are correct, the Elpro tool doesn't support that.

    On the 5309 project, I ended up debugging my problem with printf's on the serial console since it was application level problem and not low-level driver issue.

**Attention** This is a public forum