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.

LP-MSPM0L1306: Can't load UART SBL example (Error -614)

Part Number: LP-MSPM0L1306
Other Parts Discussed in Thread: LP-MSPM0G3507, MSPM0G3507, MSPM0L1306

Tool/software:

Hi M0 team, 

I'm attempting to use the secondary_bsl_uart example from the M0 SDK onto an MPSM0G3507 launchpad, but am encountering the following issue.

Using the following thread, I was able to change the Debugger to allow erasing of NONMAIN before writing.

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1318281/lp-mspm0l1306-bsl_spi_flash_interface-example-attempting-nonmain-write-without-erasing

However, debugging now causes a new error: 

From this point i have to factory reset the board with the following tool, which allows me to at least connect to the target.

https://dev.ti.com/gallery/view/TIMSPGC/MSPM0_Factory_Reset_Tool/ver/0.0.3/

However, repeated attempts to load through the debugger continue to fail. Any thoughts?

  • Hi, 

    1. Try to recover your device first, after factory reset, try to download a simple demo such as gpio toggle output to confirm that device is work normally.

    2. Please follow the following suggestions to do recovery.

    Addendum B - Preventing Programming Issues and Recovery

    https://dev.ti.com/tirex/explore/node?node=A__AHaph7YfvcrVy2cDlmb4sQ__MSPM0-SDK__a3PaaoK__LATEST

    Regards,

    Helic

  • Hi Helic, 

    I was able to flash the device with a GPIO toggle command and everything worked fine. Attempting to re-flash with secondary_bsl_uart still results in the same error. I was able to note this time around that the first error I get is as follows: 

    CORTEX_M0P: Error: (Error -1001 @ 0x0) Requested operation is not supported on this device. (Emulation package 12.7.0.00105) 

    Some more e2e searches reveal that this could be an issue with a support package (similar to this thread)

    However the recommended fix (updating CCS through the help > check for updates tab and rebooting) didn't update the Emulation package and did not solve this issue.

  • Hi, 

    From my side, CCS Help - About Code composer Studio - Installation Details

    My TI Emulators version is 12.7.0.00130.

    You can try update this independently by clicking Update..

    I also try these two secondary BSL demo, there is no issue.

    By the way, which device are you using? I can see LP-MSPM0L1306 and LP-MSPM0G3507 on this thread's title and text.

    Please select the right device examples from SDK:

    C:\ti\mspm0_sdk_2_01_00_03\examples\nortos\LP_MSPM0G3507\bsl

    C:\ti\mspm0_sdk_2_01_00_03\examples\nortos\LP_MSPM0L1306\bsl

    Regards,

    Helic

  • Hi Helic, 

    Sorry for the naming on the thread - I am using an MSPM0G3507 launchpad and using the example C:\ti\mspm0_sdk_2_01_00_03\examples\nortos\LP_MSPM0G3507\bsl\secondary_bsl_uart`.

    I just updated my CCS again, and my emulation package updated to 12.8.0.00189. I also re-imported the example from the SDK. However, I am still getting the same error when I attempt to flash the Secondary Bootloader example. 

    All the best, 

    Ethan Cope

  • Hi, 

    This is normal phenomenon.

    Because secondary BSL code start from 0x1000, instead of 0x0000 (default).

    For secondary BSL test, please follow the readme file.

    Regards,

    Helic