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: Unable to add "Configuration NVM" to sysconfig on MSPM0L1306-WQFN-16(RTR)

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

Tool/software:

I'm trying to add "Configuration NVM" to sysconfig on an existing MSPM0L1306 WQDN-16(RTR)  project. However, the UI warns me of exceptions when I click the Add button. In order to discard any error on my current sysconfig or project, I've generated a new fresh empty project for my device but, unfortunately, the same error message is shown as soon as I try to add here the "Configuration NVM" option in sysconfig. 

These are the steps I follow to replicate the error:

  • Create a new empty project for MSPM0L1306 using "No RTOS" and "CCS - TI Arm Clang". This will create a project targeting MSPM0L1306-VQFN-32(RHB)

  • Open empty.syscfg and change the device package to WQFN-16(RTR)

  • Try adding Configuration NVM

  • An error message is shown

Some other things I've tried:

  1. If I switch back to package VFQN-32 (RHB), I can add "configuration NVM" without any problem.
  2. If I add "configuration NVM" when package is VQFN-32 (RHB), switching once more to WQFN-16(RTR) results in the same error.

I'm working with Code Composer version 20.2.0.12, Sysconfig  version 1.24.0 and MSPM0 SDK  version 2.5.0.05.

  • Hi Aritz,

    I looked into this issue and found this E2E post. Seems like it is a known issue and is prioritized to be fixed as soon as possible. In the meantime, please check the post and see if any of the suggestions resolve your issue for now.

    Best,

    Owen

  • Hi Owen. Thanks for your answer! I'll keep an eye for new software releases. In the meantime I think I can work with two projects: one targeting my package that implements my firmware, and a second one targeting the VQFN-32(RHB) only with the configuration NVM. Using hex tools I can extract the NONMAIN configuration generated by the second one and then update my target's firmware using BSL.

  • Hi Aritz,

    I just wanted to follow up and let you know that the issue should be resolved in the next SDK release. If you still encounter the issue after the next SDK release, please reach out!

    Best,

    Owen