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

MSP430FR2355: Using IAR, always have to select Emulator/User code erase (unlocks device) before download

Vandermyer
Prodigy 60 points

Part Number: MSP430FR2355
Other Parts Discussed in Thread: MSP-EXP430FR2355

I am using IAR EW 7.21.1 with the MSP-EXP430FR2355 evaluation board, and find that I always have to select 'Emulator / User code erase (unlocks device)' before every download. If I don't then I get verification errors in the download.

Anyone have any ideas why I have to do this, and is there any way round this?

Thanks./

  • 0
    TI__Genius 10960 points

    Hi there,

    Has this problem persisted? Or is it only in certain scenes?

    Is it related to the program? You can try simple example code to see if the problem reproduces.

    Is it related to the board? You can also replace other boards and see if the problem reproduces.

    Thanks and Best Regards

    Yuhao Zhao

  • 0 in reply to Yuhao Zhao
    Prodigy 60 points

    Thanks for that response. 

    The problem was persistent, but now it seems to have 'gone away' and I must admit that I don't fully understand why. I am aware of only two changes I made:

    1) Added the line FRCTL0 = FRCTLPW | NWAITS_2; to configure 2 wait state as I am running at 24MHz (but I would assume this shiould be irrelevant for an IAR download)

    2) Had an inconsistency between the data/code model in a linked library and main application. Could this have caused erratic behaviour  to set the JTAG/SBW lock mechanism?

  • +1 in reply to Vandermyer
    TI__Genius 10960 points

    Hi Vandermyer,

    If you want, you can try to modify these two changes to compare. 

    And here is some content about NWAITS_2: 

    'Correct wait state settings must be ensured, otherwise a PUC might be generated to avoid erratic FRAM accesses.' (It can be found in Page 302 of user guide). 

    Thanks and Best Regards

    Yuhao Zhao

**Attention** This is a public forum