• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 67 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.

MSPM0G3507: Question about Secondary BSL and NVM Configuration

Zq
Prodigy 110 points

Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG

Hi there,

I am working on the secondary BSL for MSPM0G3507 to perform a firmware update.

Normally, we flash the secondary BSL first. I noticed in SysConfig that NOMAIN SWP is checked, which indicates that the BCR and BSL configurations are fixed/protected.

My question is: when flashing the application code, does this mean we do not need to configure NVM in application code, since NOMAIN is static protected? During development, should NOMAIN static write protection be enabled or not?

For the secondary BSL code, in SysConfig, the MAIN static write protection needs to be adjusted according to the exact location where I place the secondary BSL to avoid the overwrite when flashing the Application code. . Is that correct? 

Thanks,
Zq

  • 0
    TI__Expert 4590 points

    Hi Zq,

    During development we recommend not static write protecting NONMAIN. Doing so would prevent any further erase or programming operations to this region of memory through application or BSL code. 

    The secondary bootloader should be static write protected in the BCR configuration, otherwise there are chances for the device to get locked during the bootloading process.

    Best Regards,
    Brian