• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 30 subscribers
  • Views 434 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.

Original question:

MSPM0G3507: MSPM0G3507 BSL issues

MSPM0G3507: secondary_BSL

Pakho
Prodigy 175 points
Part Number: MSPM0G3507

Tool/software:

Hi Team,

I have tried BSL demo with LP-MSPM0G3507.
I built BSL and APP. Did I need to merge 2 txt together then load image, or load image as snapshot.

  • 0
    TI__Mastermind 39650 points

    Both will work, if the memory are not conflict.

  • 0 in reply to Gary Gao
    Prodigy 175 points

    Can you share how to merge two TXT files? I am trying to perform OTA from the host MCU. A file should make the whole process simpler.

  • 0
    Prodigy 175 points

    Another thing, I loaded both secondary BSL and invoke demo app images.

    The snapshot shows that I am using host MCU to update MSPM0G3507. I am succeed to update by default BSL but secondary BSL not.

    The log mentions Mass Erase failed.

  • 0 in reply to Pakho
    Prodigy 175 points

    The error is 0xF1. What does this mean?

  • 0 in reply to Pakho
    TI__Mastermind 39650 points

    It will be very simple here is a demo, 

    Here are two firmwares

    Fullscreen demo_firmware_v1.txt Download 
    @41c00100
01 00 00 00 16 02 15 02 01 03 02 03 A8 12 FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 48 00 16 F4 7D 0F 
q
    Fullscreen demo_firmware_v2.txt Download 
    @41c00000
01 00 00 00 BB AA BB AA BB AA 66 55 FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF BB AA
BB AA BB AA FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF 31 92 D3 EB
q

    This the combine version

    Fullscreen demo_firmware_v3.txt Download 
    @41c00000
01 00 00 00 BB AA BB AA BB AA 66 55 FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF BB AA
BB AA BB AA FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF 31 92 D3 EB
@41c00100
01 00 00 00 16 02 15 02 01 03 02 03 A8 12 FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 48 00 16 F4 7D 0F
q

  • 0 in reply to Pakho
    TI__Mastermind 39650 points

    0xF1 means program failed, make sure your firmware are 8 bytes aligned. You can check it.

  • 0 in reply to Gary Gao
    Prodigy 175 points

    I checked the sent data. The length is 0x5D. Data length is 0x58. It is 8 bytes aligned.

  • 0 in reply to Pakho
    TI__Mastermind 39650 points

    Sorry for the late response. I saw that you have send factory reset before write this packet, Have you try to wait sometime before program data and wait the device be erased? By the way, recommend to write non-main flash data first, if it update failed before write non-main flash data, the non-main flash will be all 0xFF and the device will be locked forever when do a reset or power cycle.