I cannot do anything to my Tiva C-Series LaunchPad

Hello Phi

Did you first try to load the blink example from TivaWare installation, to see precompiled and known good examples are working?

Regards
Amit

Phi Luu said:

Most recently, I have uploaded my code in order to control my robot. The important thing here is that I uploaded code through the Debug Port

Those are important - interesting - yet rather odd - facts to present.

Untold is whether any of (your) code was ever loaded - and if any such code ever worked.   That would be most helpful.

You take pains to (importantly) note that (your) code was uploaded via the Debug Port.   (some would view that as, "Doth protest too much."  Note that you'd "not" be the first to have, "Done otherwise.")

Hundreds of posts (similar to yours) but (minus) the "important disclaimer" may be searched here - and guide users how to insure that all necessary programs which enable the PC to recognize the LPad are installed.   (at one point these must have been resident - for the resulting havoc to have visited your board)

Should Amit (or others) not quickly (further) guide - the forum search box (above) should provide hours of assistance in your behalf...

Hello cb1,
Let it more articulate. I uploaded my code to the LaunchPad with it connected to the computer exactly like the picture above.
I connected the LaunchPad to the computer like that, then I uploaded my code in. Did I connect it right? I should have connected it by "Device" USB Port located on the side of the LaunchPad, shouldn't I?
Thank you.

Your photo (key parts: Switch towards Debug and PC connected USB cable (also) to Debug) is what is recommended to achieve "program/debug."

You are silent as to:

• ever/any successful debug or programming of this board?
• you could not have loaded your (entire) robot program in one go - could you?   Did you?

If code was (just once) downloaded - how (and where) could it have been developed?

[edit] on/about 16:30 CST today poster added a 2nd photo - this one showing his "Mode Switch" favoring Device and USB cable (also attached) to Device Port of his LPad.   Was this not the (very) switch & connection point which was (importantly - we were told) not to be used for "Program & Debug?"

Hello cb1,

I used Energia to load my program to the board.
I'm from Arduino, and I only have exposed to Tiva for a month. My lacking of experience could be a problem :(
In my program, I used the following pins: PB_7, PE_5, PB_6, PB_4, PE_0, PD_0, PD_2
I did load my entire program to the Launch Pad through the USB port used for Debugging, and it had worked, once. However, I had a problem with my robot, so I plugged the LaunchPad to the computer again to change my code. And that was when I met this problem of the LaunchPad.

Hello Amit,

Thanks for responding my post. My computer didn't even connect to the LaunchPad. As usual, when I connect it to my computer, the computer always plays a sound like an USB has connected. But this time it didn't. Here is my Device manager:

i.imgur.com/HmV6Nqc.png Note that I did connect my LaunchPad to the computer, but the dialog told me to connect it (?!)

That's helpful - thank you.   So does this mean that you, "Connected a USB cable from your PC to the LPad's (top) USB port" as your first (top) photo shows?   Is this correct?

Are you stating that for one month - you loaded your program into the LPad - (just) ONE time?   Normally - I load 5 - 10 times, often far more than that in a single day.  (and that does not seem at all unusual)   One single program download - that qualifies as (highly) unusual.

How did you connect to the LPad when you, "Had a problem w/your robot?"  Can you (really) recall/remember?

You should know that there is a comprehensive User Guide for your LPad.   Mine is labeled, "SPMU296" dated Apr. 2013.   Page 14, that document, directs you to:

• Install LM Flash Programmer on your PC
• Switch the Power Select switch to the Right (Debug)
• Connect USB cable from PC to the Debug Port of your LPad
• Power Led D4 should (then) illuminate

You appear to have done all that - at least once - and (uniquely) went so far as to note those connections as "important."   (noting that was - and remains - highly unusual)

Might it have been - due to robot "resistance/non-conformity" - that you "broke" from those connections (as above) and plugged in as your (new) bottom photo shows?   Those w/more experience than I will benefit from your clear listing of past connection actions - pardon but that's (most) important...

cb1,

I did connect the LaunchPad to the computer exactly like the TOP photo.

Before uploading code that caused this problem, I had uploaded C code on the LaunchPad. That time, I only uploaded code on PORT F, and I uploaded code through the USB Port exactly like the TOP photo.
I ALWAYS initialize PORT F by the following code:
gist.github.com/.../9c3d36fb81cee3ff2a32
I hope this is not the last time I can upload my code in :(

I ALWAYS connected the LaunchPad exactly like the TOP photo. Until I met the problem, I noticed that there was another way to connect the LaunchPad to the computer (BOTTOM photo).

Feel your pain - yet I'm (far) from an LPad expert. And - at least for some time passage today, "Factory appears to have rested."

Have you no friend, fellow robot builder, robot club, friendly instructor, or hard working vendor Sales Office (right!) on the job today (Sat)- able to assist? (note that cb1 & 2 staff are "on the job" - along w/3 "captives.")

Beg, borrow or (God forbid) buy another 2 LPads - and add & change code carefully. None of the pins you mentioned seemed critical - I'm suspecting "handling" (possibly ESD if humidity has been low) or inexpensive USB cable has caused your issue...

I'm stuck now :( :( :( :( :( :(

SINCERELY THANK YOU FOR YOUR HELP!

Hello Phi,

Before "considering" the LaunchPad in a terminal state, try to remove the drivers from the device manager and USB device manager to remove all entry for the LaunchPad driver. Then re-install the drivers for the LaunchPad (use the latest from TI website).

Regards
Amit

Hello Amit,

I have already followed your instructions. I uninstalled all the entry for the LaunchPad Driver, and now they disappear forever....
I also downloaded the ICDI driver for the LaunchPad. All I have is this picture below: http://i.imgur.com/IA2AUIm.png?1

How can I install the drivers when there is no hardware displaced on Device Manager?

I think my case is like the LaunchPad is actually PLUGGED in, but it is NOT CONNECTED to the computer.

Thank you,
Phi

Hello Phi,

Does the device manager shows unknown devices or devices w/o drivers?

Regards
Amit

Hello Amit,

I tried to Scan for Hardware change many times, but it no used:

http://imgur.com/a/vGLbx

Hello Phi,

Even after a reboot?

Regards
Amit

Yes :( :( :( :(
I think I need to buy a new LaunchPad...... I'm so stupid not knowing the LaunchPad deeply enough. I'm also very impressive that people can intervene TI's LaunchPad deeply. Apparently, I have destroyed the core program of the LaunchPad :(

Hello Phi,

Last thing: Have you put the USB cable to the debug USB header and move the switch to the debug position?

Regards
Amit

Hi Amit,

Yes I did. I did it all the time connect the LaunchPad to my computer.
You can ask me as many questions as you want.

Thanks!!!

Hello Phi,

Guess, it is time to get a new LaunchPad.

One other thing, the LED as given in the first picture will always remain lit if 3.3V supply is available at the output of the LDO.

Regards
Amit

T__T

SINCERELY THANKS!

Hi Amit,

While poster (importantly) has sworn to, "not having connected to the USB Device Port while downloading a program" might you be good enough to describe:

• What is the expected result should user code be introduced to the USB Device Port - w/that being the only USB and Power inlet - and w/Switch (still) set to "Debug?"
• Same as above - but in this case w/Switch (now) set to "Device?"

My goal here is to provide - at minimum a, semi-"safe harbor" for all LPad Users - who may be unaware of the (possible) ill-effects from improper USB Port connection and/or Switch position!   From my (reread) of the User Guide - such precautions (and unwanted results) are absent (or in mice-type) thus escape ready notice...   Poster here may not emerge - the only LPad user to incur, "Emergency Situation..."

Thanks much your time, attention & expertise - as always - much appreciated...

*** And to poster: Do NOT discard or cannibalize your LPad.   Further tests & facts (may) enable recovery - perhaps not of the ICDI (top portion) but instead of the higher value, "Main MCU Section."   Such recovery is unlikely to occur in your "Emergency (Here - Now) Time-Frame yet there is hope for you to salvage something from your investment.    Note too: whenever firm/I/clients "sense" an Emergency Potential - we purchase "multiples" of raw material - knowing (even expecting) that (some) disaster will visit - and the 2nd & 3rd boards may then be pressed into service!   (if such proves "too expensive" then it is likely that the project is inappropriate - under those circumstances...)   You need to find a local club where ideas & experience can be shared - and many LPads are in residence...

Hello cb1,

I understand, what you mean.

1. With the USB connected to device and switch on debug, the LPad will not come up.
2. With the USB connected to device and switch on device, the LPad will come up and will be seen as a DFU class if the Main MCU flash is erased

We have seen in the past that for some reason (still undetermined) the ICDI MCU stops working. I am trying to determine the condition to reproduce it in the lab.

Regards
Amit

Thank you, Amit - that ICDI "loss/confusion" appears to be poster's plight. And that does not only occur here! We've seen - and squawked - at other sites/vendors - when such occurs. (this happens to be extremely high on the, "Torment of User List!)

Several vendors deal w/this by dedicating a pin (or pins) to "Boot" mode - so that (some) "Safe Recovery" becomes faster/easier. While not 100% - firm/I report that this does seem an improvement - yet costs (1 or 2) pins.

Another concern - one we've noted often enough to alarm - is the "deliberate or accidental (unseating) or removal of the USB cable" (while) some program operation is "in process." Our work-around - always (and only) power via a proper supply - and make unwanted disconnects (very) difficult!   Perhaps this is one for you to try - Amit.   (not a guaranteed "each/every" time failure - but often enough to warrant concern.)

Several of our clients - past plagued by such issues - have reported (It Works!) - yet their number & time elapsed prevents the cb1 pennant from rising to (very top) of sailboat's mast...

Hello Amit & cb1,

I think I found something on my code:
http://imgur.com/hxkg5QI

What I wanted from the statement sleep(500) was to save power, because the robot didn't always need the power to move.
Did it affect my LaunchPad? Because currently it seems like the LaunchPad is idle (which is similar to "sleep"), I reckon I had done something with sleep(500);
How to wake it up?
Thanks!
Phi

My friend - when the result of some "new/unknown" action may place you/your project into an "Emergency Situation" - can that action be wise?

Should yours (really) qualify as an "emergency" procure a 2nd (and 3rd for safety) LPad - and (importantly) maintain the connections & power switch as indicated upon your first (now top) photo.    (did we note that this connection has (some) "importance?")