Part Number: MSPM0G3519
Hello Team,
We are developing a custom bootloader for the MSPM0G3519 and have chosen the SDK's secondary_bsl_can example as the baseline implementation.
Currently, we are encountering two issues:
-
Startup Execution Failure
- The program does not reach
main(). - Execution branches to
Default_Handler()and remains in the infinite loop. - We would like assistance in reviewing our startup, linker, interrupt vector, and bootloader configuration.
- The program does not reach
-
Controller Locking After Flashing
- During programming, we select Erase MAIN and NONMAIN before flashing the bootloader image.
- Occasionally, the device becomes inaccessible and the debugger reports:
-
Error connecting to the target:Connection to MSPM0 core failed.Possible root causes:1. Debug access within NONMAIN was disabled or enabled with password.2. Peripheral misconfiguration (e.g., watchdog or clock settings).
Based on this behavior, we suspect there may be an issue with our NONMAIN memory configuration or the programming sequence.
Could you please advise on:
Proper NONMAIN configuration for custom bootloader implementations.
Recommended flashing procedure.
Recovery options for devices that become locked.
Any known considerations when modifying the
secondary_bsl_canexample.Your assistance would be greatly appreciated.
Best Regards,
Umesh