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.

MSPM0L1306: Using different derivatives for software validation and production

Part Number: MSPM0L1306
Other Parts Discussed in Thread: MSPM0L1304,

we currently use the MSPM0L1306 derivative with 64KB Flash memory and 4KB of SRAM for our firmware development, testing and validation, because of availability. In the series production the MSPM0L1304 with 16KB Flash memory and 2KB of SRAM will be used. We now have concerns, because all the validation happend on another derivative with more Flash and SRAM.

The firmware is way smaller than the 16kB available on the MSP0L1304. So it would definitely fit. Are there any concern when using software on a MSP0L1304 build with settings for MSPM0L1306?

Is there a possibility to lock the unused memory areas on the current MSP0L1306 and limit them to the size of the MSP0L1304, i.e. to use only 16K FLASH and correspondingly less RAM?
Then our software validation would basically run under series conditions.

  • Hi Maximilian,

    You are fine using and validating on the MSPM0L1306.  Not sure which tools you are using, but I'll assume CCS.  When you are ready to start programming/debugging with MSPM0L1304, all you have to do is change the device in the project settings.  That will automatically pull in the appropriate linker script for the MSPM0L1304 and limits you to the 16KB FLASH.

    Now, while you are still working with the MSPM0L1306, you can manually modify the linker script to limit the memory to 16KB.

    Here is screen shot of MSPM0L1306.  Just modify the length = 0x00004000