• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 78 subscribers
  • Views 365 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430F5521: Soft bricked device by using BSL to program a custom ez-FET Lite.

Marcus Behel
Prodigy 20 points
Part Number: MSP430F5521

Hi,

I have been working on making a custom ez-FET lite on based on the design files released by TI and have run into a small problem. In trying to program the device (using BSL via USB) I have seemingly managed to brick the device (MSP430F5521).

I used BSL-Scripter with the script attached in the zip below trying to flash the custom BSL then the custom firmware. The BSL operations seemed to succeed, however now when I power the device no USB device is detected (I would expect to see the UART interfaces the ez-FET provides).

I assume I've managed to soft brick my device and will need a FET in order to fix what I've done, so I have two questions:

1. Is there a way I can still interface with this device (in order to put the original BSL back on it) without a FET?

2. Is flashing the ez-FET firmware (specifically the custom BSL) using BSL possible. If so what did I do wrong with my script?

Thanks in advance.

BSL-Scripter script used

ezfet_program_bsl_scripter.zip

Edit: Just to clarify the ezfet firmware and BSL in the package above are the same ones released by TI (http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430_ezFETLite/latest/index_FDS.html).

  • 0
    TI__Intellectual 2100 points

    Hi Marcus,

    "Bricking" the device is possible esp. if some security rules are violated. The MSP430F5x/6x family provides some code protection for customer code. There are several mechanisms in place that can lock the device for a good reason. From the scripter.zip I can not tell which mechanism went active since it also depends what code image has been in the device before.

    I will check in the other item and get back to you within a couple of days.

      Johann

  • 0 in reply to Johann Zipperer
    TI__Intellectual 2100 points

    Hi Marcus,

    The timestamp of your flash image dates back to May-2nd-2013. This is really old. The latest published schematics in SLAU647N is Jul 2013. I do not know where and when you downloaded your image but I am sure there are newer images. Btw. the documents SLAU647N and SLAU319AC addressing your topic got recently updated. MAR/APR 2020. Pleas have a look. Due to the current WW situation I could not find yet the current SW support filed for customer made debug tools. For right now I recommend to order a regular Board with an EZ-FET lite on it.

    have a nice day

             Johann 

**Attention** This is a public forum