• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 82 subscribers
  • Views 522 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.

Launchpad Died

Shayok Dutta
Prodigy 50 points

I plugged in the launchpad and when I executed the ADCSOC example program the launchpad stopped working. The LEDs slowly dimmed away so I touched the board to hit the reset button and felt that it was heated up. The following error message showed up on the CCS console:

C28xx: Error: (Error -154 @ 0x0) One of the FTDI driver functions used to write data returned bad status or an error. (Emulation package 5.1.73.0).

Another error message also showed up saying that a board was not recognized or plugged in after the LEDs dimmed away.

I made sure the voltage being passed in was under 1V and so it wasn't overloaded and the grounds were correctly in place. Is there an explanation as to why this happened? I have also tried loading the other demos or examples and the same thing happens. 

  • 0
    Guru 192875 points

    Hi Shayok,

    Unknowingly you might have shorted the terminals!

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Prodigy 50 points

    That's what I was thinking as well; however, I have ran this demo before (only difference this time was that the code was changed a little bit to meet my project needs) with the same procedure and the device wasn't damaged. I turn on the voltage source after the program is compiled and stored on to flash memory (voltage source was under 1V) and both the ground terminals are connected to ground. The incident described above happened after the program was stored into the flash memory, the voltage source was turned on, and the debugger on CCS was waiting at the start of the main function (not running). 

    Would you or anyone else be able to give me a procedural outline of what exactly to do to ensure that a device I'm working with doesn't get damaged again or if I have done anything wrong in my procedure?

    Thank you. 

  • 0
    Guru 117855 points

    Shayok Dutta said:
    I made sure the voltage being passed in was under 1V

    Might < 1V be too little to power both the MCU and any/all accessories present?

    Suspect instead that you meant the ADC signal level was < 1V.  You are silent wrt this external signal's ground - was it tied to your MCU board's ground?

    While you report < 1V - was this verified via a scope?  DVM will likely miss "peaks" and/or start-up transients - which may exceed MCU's ADC input ratings.

    And - always suspect is the powering of external device. (i.e. your analog sources)  Should the external source have been powered - and connected to your MCU - while the MCU was unpowered - that may well explain.  Best prevention here is to employ single supply - adequate to task - which simultaneously powers MCU board and any/all interconnected signals...

  • 0 in reply to cb1_mobile
    Prodigy 50 points

    I meant to say that the signal being sent to the ADC was < 1V, as you stated, and yes, I'm suer that the signal was <1 V. 

    You actually answered my question, the external power source I believe was powered and connected to the MCU while it was unpowered (a stupid mistake on my part). 

    Thank you very much for helping me discover my error and for your prevention suggestion. I appreciate it. 

  • 0 in reply to Shayok Dutta
    Guru 117855 points

    Most of us have done that (power the accessory - while main board (MCU) sits unpowered!) - haste - once again - yields waste. 

    Do not be quick to dispatch that board - may well be that only connected channel(s) so suffered - and we have seen cases where, "latch up" lasted for hours (sometimes days) and then disappeared!  (would not use such a board/chip for human implantation/space-launch - but surely proper for "most" Gov't Work...)

    Another common pitfall - separate cables/interconnects - some just for power transfer.  And - it seems - too often the power transfer cable is awol (missing) and the unpowered board/device becomes victim.

    Power is "so simple" - yet deadly when mishandled...  (thank you for neat green Verify)

  • 0 in reply to cb1_mobile
    Guru 192875 points

    Cheers guys...! (was out of town so wasn't able to revert)