• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 29 subscribers
  • Views 412 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.

LAUNCHXL2-RM57L: Defective Unit

Bjarki Bergsveinsson
Prodigy 20 points
Part Number: LAUNCHXL2-RM57L

Hello,

I was directed to post my problem here by customer service.  I think the LAUCHXL2-RM57L that I received is defective. The XDS110 Status LED lights remain off when the board is plugged in. The board is not enumerated on the USB bus on two different computers. The out-of-box demo does not work. The Code Composer Studio cannot detect the board. The other development board that I received (MSP432P401R) has the same XDS110 debug interface and everything works perfectly.  I have tried the basic troubleshooting steps such as replacing the USB cable and connecting to a different computer.  The only LED that comes on is the +5V green LED when I connect the USB cable.  Pressing any of the buttons on the board has not effect.  I have tried to use the xdsdfu command line utility, but it does not detect anything on the USB bus when the Hercules launchpad is plugged in.  The Hercules launchpad did not work from the first time that I plugged it in.  Thanks.

  • 0
    TI__Guru 65580 points

    Hi Bjarki,

    I'm sorry to hear that.  Let's just make sure it's not an issue getting power to the board.

    Do you have any booster packs plugged into the LaunchPad?   If so please remove them and see what happens.

    Also then please make sure you try plugging the LaunchPad into a host port or hub port that can provide enough power to the board.   The Hercules device does consume a lot more power than an MSP432.   So sometimes plugging into a bus powered hub (where the total current has to be shared among all downstream ports) is a problem.   Or plugging into the port on a keyboard that's really only designed to power a mouse..   These things can cause the board to not fully power up.

    (Even though the +5V LED is lit, it might be 'pulsing' because U9 is a current limiting switch,  it will shut off if the LaunchPad tries to draw more current than it negotiates for, but this may cause the power to 'cycle' rapidly).

    If it's simply an issue of providing enough power to the LaunchPad then I think you should probably keep the board you have and just use a powered hub or you can get a barrel jack that fits onto J17 and provide +5V directly to the launchpad from an external power supply (convert it to self-powered).

    But if it's not this then I would suggest returning the kit for a replacement.   It's pretty rare to hear a LaunchPad is DOA like this.  Sometimes we get a report about one being damaged but I can't remember one that was DOA.

    Thanks and Best Regards,

    (And sorry for the trouble)

    -Anthony

  • 0 in reply to Anthony F. Seely
    Prodigy 20 points
    Anthony,

    I just received a replacement unit today. The new board enumerates on the USB bus, and the out-of-box demo works. This confirms that the old board was DOA. Thanks for you help.

    Regards,
    Bjarki