• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 915 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.

LAUNCHXL2-RM57L: USB connection to Launchpad xl2 rm57Lx not found (anymore)

K De Coster
Intellectual 740 points
Part Number: LAUNCHXL2-RM57L


Hello,

I am working with a Launchpad XL2 RM57Lx, I was able to program it via its XDS110 usb interface. When i returned after the weekend my computer was no longer able to detect it.

If I run C:\ti\ccsv7\ccs_base\common\uscif\xds110>xdsdfu -e
The output is:

Found 0 devices.

It also does not show up in the windows device manager.

I already tried to reinstall the drivers. Both the usb port and cable work correctly (tried with RM48HDK and works fine).

When i power the board the +5V LED6 next to the ethernet port is on.

Is my board broken? How can I reconnect to it?

I am using Code Composer Studio 7 on Windows 7.

Kind regards,

Karel

  • 0
    TI__Guru 68930 points

    Karel,


    Please use a volt-meter, and place the negative terminal on one of the ground points in the corner of the board.

    Then using the positive terminal measure the voltage at:

     -  JP2,  near the USB Jack.   (it isn't populated by default, should be bare land pad with a solder bridge).   This should be ~+3.3V

     - Test point labeled +1.2V near the white label block on the top silk.   This should read ~+1.25V

    Also please let me know if the LEDs under the XDS110, LED7 and LED8 are illuminated or blinking.
    There is a table written on the top silk in small font under the LEDs explaining their meaning.  They indicate the status of the XDS110.


    To my recollection this is the first 'dead' launchpad I've heard of but we have had several HDKs reported where there was an electrical overstress condition on the MCU that shorted out the power rails and the board would grossly fail.   Especially if it is winter where you are, and the humidity is low and you're wearing nice wooly sweaters, this could be a real possibility if you don't have an ESD controlled bench.


    Of course it could be some driver problem so the other thing to do would be to use the Windows device manager and see if there board shows up as any sort of device with a driver error.   You might also want to reboot the PC if you haven't already done so, or try the kit on another PC...

  • 0 in reply to Anthony F. Seely
    Intellectual 740 points

    Thanks for your response Anthony,

    I usually work with headphones on so I only discovered now that there is a high-pitch beep being produced by the board, appears to be coming from the usb side of the board.

    Voltages:

    JP2 : 0.16 V

    JP3 : 2.5 V

    +1V2 (next to the white block and J6 and J8) : 0.97 V

    LED7 and LED8 are both off indicating not ready.

    When connecting the board nothing changes in windows device manager.

    No ESD precautions were  taken and it is winter here(Netherlands)...

    So I guess this is RIP launchpad?

  • 0 in reply to K De Coster
    TI__Guru 68930 points
    Hi Karel,

    Yes - it's *probably* RIP. It might be some sort of short circuit that you can fix though, if for example you have anything else plugged into or soldered onto the board; it would be worth a little effort maybe to undo these changes in case one of them accidentally created a short circuit.

    If it's nothing obvious like that then my next inclination would probably be look under a microscope for any problem, like wire clipping getting jammed between two pins. Then after that I might remove the MCU to see if this at least lets the voltage rails come back up. But the MCU being a BGA is difficult to remove and rework. And I think the LaunchPad fully assembled actually costs less than QTY1 of the MCU ;) so other than just undoing any modifications the rest of these steps probably don't make sense doing.

    -Anthony
  • 0 in reply to Anthony F. Seely
    Intellectual 740 points

    Hi Anthony,

    I connected the mibspi to a rm48hdk mibspi, but as soon as it didn't work anymore i disconnected it. So right now there is nothing connected to the board.

    Thanks a lot for your help :)

    Have a nice weekend,

    Kind regards,

    Karel

  • 0 in reply to K De Coster
    TI__Guru 68930 points

    Hi Karel,

    Interesting.   That might have been the issue.  There are some +12V lines near the MibSPI1 on the HDK J9 (right next to actually) and if you connected to one of these accidentally that would do the trick causing permanent damage almost immediately.  I've done this sort of thing before myself.

    -Anthony