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.

MSP430F6659: MSP430 programming difficulty in production

Part Number: MSP430F6659
Other Parts Discussed in Thread: MSP-FET

Hi,

In one of our product, we are using MSP4306659 microcontroller. The design is proven and this product is working well more than 2 years. Currently we are facing an issue, we use two firmware for production. We use firmware 1, which is only used to check board peripherals relays, DAC, LCD, LEDs etc, Once this stage is passed we use firmware 2, which is the final one. In few board we found that after loading firmware 1 when we try to load firmware 2, programming fails, error appears. This happened in 6 out of 100 boards. What could be the issue. We are using MSP-FET – MSP430 Flash Emulation Tool and FET-Pro-430-LITE application for programming.

  • Welcome to the E2E Forums,

    What is the error you are seeing?  Are you getting any feedback in the terminal?  

    Are you using the standard cable that comes with the MSP-FET or a custom cable of some sort?  

    How is the board powered?  Externally or from the MSP-FET it self?  

    Thanks,

    JD

  • Please see image attached for error.

    We are using standard usb cable comes with MSP-FET. It works on other boards. Board is powered by external DC source.

  • What happens when you try to reprogram the boards again?  Does it work or does it continue to fail?   

    How many MSP-FETs are you seeing this on?  Is it just one or many?  

    I'm guessing that it's some sort of communication error with the JTAG.  Either due to noise, small power variations, cable integrity, etc.  Sometimes some MCUs are slightly more sensitive than others.  Trying to figure out if there is any sort of pattern here and if you can just re-program again and continue with production of if the boards are just not working at all. 

    Thanks,

    JD  

  • When we try to reprogram, it continue to fail and displays above error while programming. We tried the same with 3nos. MSP-FET but no improvement.

    Programming is successful only after soldering a new microcontroller. We tried with multiple power supplies but no improvement.

  • Hey Amit,

    Sorry for the delay, reviewing older threads.  Were you able to figure this out?  Are you still seeing failures?  

    If the MCU has to be replaced, it sounds like somehow the JTAG fuse has been blown on the devices.  If this has happened unintentionally, then the devices are probably not recoverable.  Looking at the datasheet, it looks like the JTAG security lock key is at addresses 0x17FC - 0x17FF.  Is your program 1, overwriting this section?  

    Last year I had an investigation with a customer where they had an ageing production programming setup and started have JTAG communication failures that ended up locking some devices if it happened while programming critical sections.  

    Thanks,

    JD

  • "If the MCU has to be replaced, it sounds like somehow the JTAG fuse has been blown on the devices.  If this has happened unintentionally, then the devices are probably not recoverable.  Looking at the datasheet, it looks like the JTAG security lock key is at addresses 0x17FC - 0x17FF.  Is your program 1, overwriting this section?"

    If factory HID BSL is untouched (and BSL segments are locked by default) than device can be mass erased by HID BSL. Also, SBW / JTAG can be unlocked by HID BSL.

**Attention** This is a public forum