CCSTUDIO-THEIA: Segger Jlink looses connection after MSPM0C1104 resets

Part Number: CCSTUDIO-THEIA
Other Parts Discussed in Thread: MSPM0C1104, MSPM0C1106

I've worked with NXP and ST Micros, and when a micro performs a reset function, the debuggers maintain connection and the system can be paused to inspect variables.   
For MSPM0C1104, the segger jlink loose connection and can not attach to the micro.  Is there a setting for this, or is this just a quirk of this micro?

  • Hello,

    What exact CCS version are you using? I tried using CCS 21.0.1 with my J-Link Ultra connected to my MSPM0C1106 LaunchPad. I added some code to my example which will cause the M0 to reset. When the reset happens, I will be halted in the reset handler. CCS is still connected to by device and I can continue execution.

    What is the behavior you see? The debugger disconnects? Is there any error message?

    Thanks

    ki

  • i'm using 20.5.0.28_1.11.0 Theia.  Im issuing a cpu/por reset.  Debugger looses connection.  The image has a custom boot and application, with BCR set to "All open" with swd enabled.

  • I also tried with 20.5.0 and still have not seen any issue. It could be something specific to the application or device. I will bring this thread to the attention of the device experts for further suggestions.

  • Hello Thomas,

    If you trigger CPU reset, it won't cause disconnection and agree with Ki, it will go to reset handler, on theory. But if you trigger POR reset, it will cause disconnection, POR reset will cause MCU completely restart.  CPU reset and POR reset are not the same level. And could you please help to explain what is your meaning of "customer boot"?

    BR,

    Janz Bai

  • "Custom" boot, is a bootloader we wrote, not the TI bootloader.   The application writes to a no init RAM section, does a reset, bootloader checks the RAM to see if it should stay in boot or run application.    I wanted POR so it properly resets peripherals that are write once after POR, but this may not be an issue.  I tried both POR and CPU reset, and both seemed to disconnect.   I'll dig a bit more, just difficult to debug the bootloader/application when it looses connection.