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.

MSPM0G3519: MSPM0G3519 Custom Bootloader Issues – Startup Execution and NONMAIN Configuration

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:

  1. 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.
  2. 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_can example.

      Your assistance would be greatly appreciated.

      Best Regards,
      Umesh