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.

MSP-GANG Programmer setting fuse bit?

Other Parts Discussed in Thread: MSP430F5342, MSP-GANG

Programming MSP430F5342 via SBW. Loading our own boot loader so mass erase not available. Boards program correctly. Then randomly, any attempt to access the target (verify, blank check, etc.) results in MCU init failure on all targets that are plugged in to the expander board.

This has happened over three different lot numbers to targets that have never been programmed before and those that have been successfully reprogrammed - including the boot loader - many times.


What could be going on here?!! Tired of buying bags of chips only to continue having these failures. Losing 25% to 35% of controllers. Thinking about tiling my office floor with them.

Is there an alternative programmer that can be used?

  • Original BSL is replaced by your boot loader? What about fuse values on 17FC (BSL area)? What other TI FET's / LP's report with connected targets? If original BSL is not erased or your boot loader is alive and have possibility to update fuse values, device can be recovered (unblown fuse).

    http://forum.43oh.com/topic/2972-sbw-msp430f550x-based-programmer/?p=44019

  • Yes, our boot loader replaces the factory default BSL.

    The17fc values in our BSL are programmed to FF FF FF FF.

    Our FET's report the MCU init fails and the security fuse is blown.

    I have been attempting to program our application firmware only (no BSL) into a blank target using the BSL. That doesn't seem to work. The MSP-GANG appears to be programming the flash but it fails the verify and when I read it back it is blank (all FFs).

    If I could get it to program or write to the target, I would have the confidence to make the device secure via the MSP-GAND PC GUI and then attempt to reset it with the erase function.

    We are adding a function to our target's monitor GUI that will read 17fc so we can tell what it is. Hopefully we can figure out how to do that. Then we should have a better idea of what is going on.

  • SOLVED!!!

    MSP-GANG occasionally does not erase the BSL section of flash. When this happens our BSL gets programmed on top of the TI BSL. The result is a locked out processor that cannot connect to the FET or any other development tool. Keep in mind, our application runs just fine because it was programmed over cleared flash.

    We added a feature to our app where we can read and write flash using our PC GUI. Reading the BSL of a bricked controller showed that the two BSLs had been ANDed together. With our new feature we cleared the BSL section and reloaded our BSL via our app.

    Going forward we are now protected from MSP-GANG malfunctions. A plus is that we can now reload our boot loader if necessary.

**Attention** This is a public forum