• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 77 subscribers
  • Views 953 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 Overwrites InfoB Memory Segment!?

Justin Reina
Intellectual 695 points
Other Parts Discussed in Thread: MSP430F2132

Hello All,

 While programming the MSP430F2132 with CCSv4, I am using the InfoB memory Segment to store initial calibration values after each device is asembled for the first time (mostly timing info, and a unique ID). My calibration routine works fine and I have confirmed the data gets into FLASH correctly with my MSP430-FETUIF JTAG interface. Power-cycling the device shows that infoB still retains the same info.

However when I try to deploy the actual firmware to the device, Code Composer sets the InfoB segments to all 0xFFs!!! I thought the Information Memory was off limits to the compiler?I can't find any discussion of this anywhere, or any mention of it in the app notes (SLAU132D,SLAU132C, Family User's Guide).

 

How do I configure CCS to not overwrite my InfoB section?? I can't find any compiler options when diving into the project configuration either.

 

Thanks,

 Justin Reina

**Attention** This is a public forum