• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 362 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: LP-MSPM0L1306: CCS flashing of secondary_bsl_uart fails

Zq
Prodigy 130 points

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

Hi there,


When I try to flash the secondary_bsl_uart example from CCS, flashing fails.
However, when I use UniFlash to load the same .out file, it flashes successfully. Is there any additional step or setting that I am missing to flash the secondary_bsl_uart example correctly on LP-MSPM0L1306? 

Environment:

  • Hardware: LP-MSPM0L1306 LaunchPad (on-board XDS110)

  • SDK: mspm0_sdk_2_06_00_05

Example used:
C:\ti\mspm0_sdk_2_06_00_05\examples\nortos\LP_MSPM0L1306\bsl\secondary_bsl_uart

Steps to reproduce:

  1. Import the secondary_bsl_uart example into CCS.

  2. Build the project successfully.

  3. Open Debug Configurations → erase configuration: erase MAIN und NOMAIN memory.

  4. image.png

  5. flash from CCS.
    image.png
    image.png
    here is my hardware setup:
    IMG_2546.jpeg

  • 0
    TI__Mastermind 27492 points

    Hi Ziqiang,

    Can you share the full error log that CCS outputs? Also, after it fails in CCS, can you check the memory location to see if it was unable to load the expected code into the device?

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 130 points

    Hi Diego Abad,

    Here is the full error log from the Debug Output.


    After it fails, I tried to check the memory location using UniFlash in the Memory Browser starting from address 0x1000 (for the demo code, the secondary BSL start address should be 0x1000, if I understand correctly). It looks like the flash was successful because there is data at memory address 0x1000. Here is the screenshot from the Memory Browser:

    After the failure in CCS(lastest version 20.3.1), I tried to stop or pause the flashing process, but CCS froze and I had to restart it.

    Thanks in advanceBlush 

    Best Regards,
    Ziqiang

  • 0 in reply to Zq
    TI__Mastermind 27492 points

    Hi Ziqiang,
    I talked to my team and while the code actually loads in the device and it works as intended, CCS shouldn't really be breaking as you see. I will file a ticket to fix this.

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 130 points

    Hi Diego Abad,

    Thank you for your quick reply.

    So this means the secondary BSL flashed successfully, even though CCS reported some errors, because the secondary BSL is already present in memory.

  • 0 in reply to Zq
    TI__Mastermind 27492 points

    Hi Ziqiang,
    You are correct.

    Best Regards,

    Diego Abad