• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 80 subscribers
  • Views 2812 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.

MSP430F5528: BSL not working

Keith Nicholas
Mastermind 48310 points
Part Number: MSP430F5528


Hello,

My customer cannot get the BSL to work on the most recent version of the MSP430F5528; older parts work just fine.  Please see below.

I’m having a problem getting the latest revision MSP430F5528 to load code over USB using the internal bootstrap loader (BSL).  My problem only occurs with Rev K parts.  Earlier revision Rev H parts work perfectly.

With the Rev K part installed on my board I boot the processor into BSL mode by pulling PUR to VUSB and connecting the USB cable.  Two HID devices show up in Device Manager as expected.  I then try loading the code using “MSP430 USB Firmware Upgrade Example v1.3.1” and get this result:

Starting

Password Sent Successfully

Sending RAM BSL v00.07.08.38

Done RAM BSL v00.07.08.38

Failed to read data from RAM BSL

Unsuccessful in starting the BSL. Restarting.

Password Sent Successfully

Sending RAM BSL v00.07.08.38

Done RAM BSL v00.07.08.38

Failed to read data from RAM BSL

I have also tried using the Python firmware upgrader found in the latest version of the USB developers package (MSP430USBDevelopersPackage_5_10_00_17), but it hangs as well.

The device errata sheet says that there are BSL issues (BSL6 and BSL7) with Rev H parts but Rev K shows no issues.

When I read out the TLV information from the two  parts I get the following:

Rev K: HW revision: 19h, FW revision 12h

Rev H: HW revision: 17h, FW revision 12h

The two parts indicate the same FW revision, but when I examine the bytes starting at location 0x1000 (first setting SYSBSLPE to zero) they are completely different:

 

                RevK      RevH

0x1000  3C05      3C34

0x1002  3C41      3C08

0x1004  3FFF       3FFF

0x1006  3FFF       3FFF

0x1008  0800       3FFF

I have tried this with multiple parts and they behave identically. 

Why doesn’t this just work as it did with the older parts? 

Why did the firmware change with no indication in the TLV?

How do I fix this?

Thank you,

Keith N.
AFA OH/wPA

  • 0
    TI__Expert 6760 points
    Hi Keith,

    I am trying to get hold of Rev K device but in the meantime, can you tell me what version of BSL is loaded in the Rev K device that you have. It will be bytes 8 thru 11 starting at address @1000. It should be something like this: 00 08 88 39.

    The Python Firmware upgrader tool and the MSP430 USB Firmware Upgrade example tools download RAM_BSL along with application firmware. Are you downloading one of the example Firmwares like Blink_LED? Or is the firmware you are downloading a custom application?

    Maybe you can try downloading BSL again to the Rev K device and then use one of the tools to download RAM_BSL along with the application. Downloading BSL again should wipe out RAM_BSL area. You can get the latest BSL and RAM_BSL files from here:
    http://www.ti.com/tool/mspbsl

    Regards,
    Arthi Bhat
  • 0 in reply to Arthi Bhat1
    TI__Expert 6760 points

    Hi Keith,

    I just wanted to know if this is still an issue for you or if you have resolved it?  At my end I have no issues dowloading firmware using either Python Firmware upgrader tool or the Visual Studio based tool on Rev K devices. 

    Regards,

    Arthi Bhat

  • 0 in reply to Arthi Bhat1
    TI__Mastermind 48310 points
    Hello Arthi,

    The BSL-Scripter tool on the page you referenced works with the Rev K part; no further action is needed. You can close this request.

    FYI, the BSL version is 00 08 88 39, both custom application and Blink_LED failed the same way.

    Thanks for your help.
    Regards,
    Keith N.
  • 0 in reply to Keith Nicholas
    Prodigy 60 points
    Hi All,

    I face the same problem with our MSP430F5528 as descripted in the initial posting.
    (It works well with the 5529 Launchpad).

    Unfortunately the BSL-Scripter tool does not work too on my Windows 7 desktop. Message "APPCRASHED" each time i entered a demo script txt -file.

    Regards,

    Christian
  • 0 in reply to Christian Reinhold
    TI__Expert 6760 points

    Hi Christian,

    I notice that you stated that BSL download works fine on the 5529 launchpad but does not work with the MSP430F5528.   Is the MSP430F5528 in TI's MSP-TS430RGC64USB EVM board or is it in a custom board?   When you first connect the board to the Windows 7 do you see the VID/PID  2047/0200?  Is the MSP430F5528 Rev K?  What BSL scripter command are you using to download BSL?   Are you able to download RAM_BSL using the Python Firmware downloader tool?

    Regards,

    Arthi  

  • 0 in reply to Arthi Bhat1
    Prodigy 60 points
    Hi Arthi,

    i) My Msp430 is in a custom board.
    ii) BSL started correctly showing VID/PID 2047/0200
    iii) Revision ???

    With the Firmware Upgrade Example 1.3.1 Mass erase succeds, but when loadin RAM_BSL it fails.

    Regards,

    Christian
  • 0 in reply to Christian Reinhold
    TI__Expert 6760 points
    Is it possible to verify your custom board USB schematic with the schematic for the TI's MSP-TS430RGC64USB EVM board? I have my Rev K MSP430F5528 device in the TS430RGC64USB board and I am able to download BSL with no issue. You can also use the hardware layout in Figure 8 of SLAA457A document to verify your board's schematic.

    Regards,
    Arthi Bhat

**Attention** This is a public forum