MSPM0G3506: Cannot Retain EEPROM Data After Reprogram

Colin Thompson

Part Number: MSPM0G3506
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

I am attempting to emulate 2kB of EEPROM Type A data in flash to store some calibration data. The data can be stored and read correctly if it is placed at address 0x00000400, after the interrupt vector table. But in order to retain this data during a reprogramming event I have placed it at the beginning of MAIN flash and shifted the interrupt vector table appropriately. However, any attempts to program the device fail with "Error -1001". What is causing this? Do I need to make changes to the linker script or startup file?

I am using CCS v12.8.1.00005, MSPM0 SDK v2.2.0.05, and SysConfig v1.21.0.

Linker File:

Flash Settings:

Error:

10 months ago

0 Yuhao Zhao 10 months ago

TI__Genius 9800 points

No the interrupt vector table should start at 0x0000

Cybersecurity Enablers in MSPM0 MCUs

0 Colin Thompson 10 months ago in reply to Yuhao Zhao

Prodigy 10 points

That's the only valid location for the interrupt vector table? It can't be changed in the BCR or BSL?

Or, at least, is there a way to erase multiple ranges of MAIN memory so I can retain the EEPROM data?

0 Yuhao Zhao 10 months ago in reply to Colin Thompson

TI__Genius 9800 points

Yes this is the only valid location.

To erase multiple ranges of MAIN memory,

For code there should be related FLASH API that can erase specified range.
For tools, you can set the erase range in IDE or other tools.

Or you can put the EEPRPM data at the end of memory.

0 Colin Thompson 10 months ago in reply to Yuhao Zhao

Prodigy 10 points

I see the "Erase MAIN memory sectors by range" option in the tools, but can I set multiple ranges, for example, 0x0000-0x0400 and 0x0800-0xFFF8?

0 Yuhao Zhao 9 months ago in reply to Colin Thompson

TI__Genius 9800 points

Sorry for late reply.

No it depends on the tools/software. For CCS you may need to erase twice.

0 Colin Thompson 9 months ago in reply to Yuhao Zhao

Prodigy 10 points

I see. It seems like programming multiple ranges at a time has been brought up before here: CCSTUDIO: Regarding the erase range specification when programming with CCS - Processors forum - Processors - TI E2E support forums

Maybe CCS will support this functionality one day.

I would have preferred to store calibration data in the front half of MAIN flash since it supports more read/write cycles, but it seems like the simplest path forward is to store the data in the last two sectors.

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0G3506: Cannot Retain EEPROM Data After Reprogram