• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 79 subscribers
  • Views 391 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.

MSP430F5659: Hardware BSL External Invocation does not work reliably

Randy Holmberg
Prodigy 40 points

Part Number: MSP430F5659

I have an application for the MSP430F5659 that does not seem to invoke BSL mode on most of the boards I have tested. I have followed the BSL entry sequence shown in figure 1-2 of section 1.3.1.1 of the SLAU319AF. One board enumerates itself to our host system as a USB HID device which is good. Two other boards tested come up in our application mode and do not invoke BSL mode under the same conditions. I found an errata, USB11 published in the SLAZ493AA, that indicates seems to indicate that external entry into BSL mode basically does not work. Please provide any more information available on this issue.

  • 0
    TI__Guru 56685 points

    Hellos Randy,

    Please follow the errata workarounds provided in the USB11 errata as this device is affected by it. The workarounds state either invoke BSL via application, while ensuring VCORE level 2 or 3 before jumping.  OR, update the BSL to a newer version provided by the CUSTOM BSL download package, found here: https://www.ti.com/tool/MSPBSL 

  • 0 in reply to Jace H
    Prodigy 40 points

    The errata says it applies to the REV A Die, but not REV B. If I am not able to communicate with the device at all, is there any way I can tell whether I have DIE REV A or B - is there a package marking / date code that would tell me???

  • 0 in reply to Randy Holmberg
    TI__Guru 56685 points

    Hello Randy,

    Please see the device marking sections of the errata sheet. It describes how to ascertain the different revisions of the device by the marking on the device package. 

  • 0 in reply to Jace H
    Prodigy 40 points

    The Die Revision marked on the package is "B". Please let me know if you can think of any other reason why we are not able to invoke the BSL for our application.

  • 0 in reply to Randy Holmberg
    TI__Guru 56685 points

    Randy,

    If that's the case then it could be that BSL has been erased from the BSL memory, or your BSL invoke procedure is not robust. You should do the following debug steps...

    1. Review your BSL invoke procedure.Insure hte PUR is high before and through reset of the device. This could be done via RST pin or hold PUR high and apply power to device. 
    2. Uee JTAG to confirm BSL memory is valid. As further debug, you should go ahead and flash the device with the updated USB BSL image mentioned earlier.  

**Attention** This is a public forum