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

CCS/MSP430F5529: MSP430F Flash memory writing/reading

Florent Muret
Prodigy 470 points
Part Number: MSP430F5529
Other Parts Discussed in Thread: MSP430F5519

Tool/software: Code Composer Studio

Hi TI team,

I am currently trying to write a bunch of data on flash memory of the MSP430F5529 with code composer studio. I already manage to copy those data on the INFO A,B,C and D section, and it worked as expected because I am able to see those data with the memory browser, even after that I unpluged the board, which means those data are still in even if there is no more power supplied. 

The problem is that there is not enough places on those sections (only 128B). So I tried to do the same on the BANK A,B,C,D of the Main : code memory, flash (128KB each).

The problem is that I am still able to write my data on this section, but whenever I quit the debugging or unpluged the board, those data are erased and I am no longer able to find it with the memory browser. Is there a may to fix this ? Is those data were erased or moved somewhere else ? 

You can find here the memory organization of the MSP430F5519.

Any suggestions that might help me ? 

Thanks for helping,

Regards

  • 0
    Guru 301130 points
    Please show the writing code.

    How are you avoiding conflicts with the code?
  • 0
    TI__Mastermind 28955 points
    Hey Florent,

    We have an example for writing to BSL flash that is similar to what you are doing, found here: dev.ti.com/.../

    For further support, we'd need to look at the firmware. We also might to to segment the memory in the Linker to insure that it's not being used as program space.

    Feel free to message me if the code can't be publicably shared.

    Thanks,
    JD
  • 0 in reply to JD Crutchfield
    TI__Prodigy 470 points

    Hi all,

    I finally manage to find out what my problem was. I was writing correctly into the flash memory, nevertheless there is an option while debugging which erase all the BANK A, B,C,D flash data ( Main code memory). I had to change this option to select the range of memory that I wanted to erase, and then I was able to save the data in the Bank D.

    Thanks for your help,

    Regards,

    Florent

**Attention** This is a public forum