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.

MSP430F5359: MSP430F5359 BSL issue

Part Number: MSP430F5359

Dear TI experts,

We would like to know if there is any way to recover the bootloader which is preloaded on MSP430F5359?  The reason that I am asking this is because we accidentally corrupted bootloader flash area during mass programming of the devices.  The default bootloader which shipped with the device is mandatory for after market service, where it will be used for firmware upgrade. Thus, we really hope to get help from you. Thank you.

Best regards,

Peter     

  • Hi Hoi,

    I am looking into this and will provide more info as soon as I can.

    Thanks,

    Mitch

  • It may depend on where the BSL memory was corrupted.

    If you are able to use MSP Flasher to connect to an F5359 that you have not yet flashed, you could try reading out the contents of 0x1000 - 0x17ff, which is where the BSL is stored.  If that is successful, you would have a HEX file containing the known good BSL code, which you could then flash to the parts that have been corrupted  (you would have to first unlock BSL, then erase the BSL segments, then write the good copy to the segments).

    I don't know if that would work, but it might be worth a try.  One problem is that I believe the JTAG fuse for these parts is actually located within the BSL segments.  If the corruption took place in that area, Flasher may not work.  So the first step might be to see if you can read the BSL segments of a corrupted chip.  If you can, then it should be possible to write correct code there as well.

  • Hi Hoi,

    George's suggestion on reading out the BSL memory from a "fresh" device could work. You will need to first clear the SYSBSLPE bit in the SYSBSLC register:

    Are you trying to also fix the BSL in the corrupted devices? Or do you just need a reliable BSL image moving forward?

    Thanks,

    Mitch

**Attention** This is a public forum