• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 178 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.

LP-MSPM0L2228: Problem while flashing

Mahesh Bhat
Prodigy 10 points

Part Number: LP-MSPM0L2228
Other Parts Discussed in Thread: MSPM0L2228, UNIFLASH

I am using MSPM0L2228 Launchpad. Facing below issue after loading hex file. Checked the suggested steps mentioned in the log but unable to resolve the error. Any idea on how to fix it .?

image.png

 

  • 0
    TI__Mastermind 23392 points

    Hi Mahesh,
    Does the .hex file modifies NONMAIN or changes the functionality of the SWD lines? One thing you can try to do is a manual factory reset to clean the device's storage/memory to factory.

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 10 points

    Hi Diego,
    I am not modifying the NONMAIN region. Tried factory reset as well but didn't work out.
    Any hints on "Device diagnostic read = 0x00000007" ?

  • 0 in reply to Mahesh Bhat
    TI__Mastermind 23392 points

    Hi Mahesh,
    The diagnostic read indicates the device is bricked. It may be a hardware or software brick. Can you try the following steps for the hardware reset?:
    1. Disconnect the LaunchPad from power
    2. Open a Uniflash session for the device (Check both device and debugger, or select the launchpad image)
    3. Press and hold the NRST button (S3).
    4. Connect the LaunchPad to power while continuing to hold the NRST button
    5. Click on the "Settings & Utilities" tab and click on/Issue a manual Factory Reset DSSM command
    6. Release the NRST button when the console prompts you to press the NRST button

    If the device doesn't unlock after these steps, it's completely bricked and can't be recovered. This could be caused by a bad example project that accidentally modified the NONMAIN memory, or by hardware damage to the device. If the previous doesn't work, can you share the following:
    1. The hex file you loaded (or hopefully the full project (the main.c and .syscfg)

    2. Your launchpadhardware setup 

    Best Regards,

    Diego Abad

**Attention** This is a public forum