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

MSP430FR6972 FRAM question

Jent
Intellectual 660 points
Other Parts Discussed in Thread: MSP430FR6972

Hi ,SIr

I have a question about writting a data to FRAM.

I written a data to the address which is occupied by my code (example write 0xAA to 0x004480 ), I found that the data of the address was not 0xAA when   I re-up  electricity for MSPFR6972. I think if the address  was occupied by my code, it should not be write other data .  but I found it was written in the address by debugging. what's the reason?

As the MSP430FR6972 datasheet showing ,

I know the code memory range is 013FFFh-004400h,but how could I know the actual address range of my code ?

  • 0
    Guru 319190 points
    Check the MPU registers; the code might be write protected.

    The linker's map file shows the addresses where your code is loaded. Alternatively, look at the address of any function.
  • 0 in reply to Clemens Ladisch
    Intellectual 660 points

    thank you very much，Is "lnk430fr6972.xcl" the linker's map file ?  

    I found the code is following, the 4400h-FF7Fh is protected ,So I couldn't write the address could it?

    // ---------------------------
// Memory Protection Unit (MPU) border
//

-Z(CONST)MPU_B1

// ---------------------------
// Constant data
//

-Z(CONST)DATA16_C,DATA16_ID,TLS16_ID,DIFUNCT,CHECKSUM=4400-FF7F

// ---------------------------
// Memory Protection Unit (MPU) border
//

-Z(CONST)MPU_B2

// ---------------------------
// Intellectual Property Encapsulation (IPE)
//

-Z(CONST)IPE_B1=4400-FF7F
-Z(CODE)IPECODE16
-Z(CONST)IPEDATA16_C,IPE_B2

// ---------------------------

**Attention** This is a public forum