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 Non-responsive

Long time MCU developer, but new to the Stellaris line.  I picked up a Launchpad for cheap, thinking I could expand my knowledge a bit.  I've managed to go through several of the examples and I really like what I see.  I had even started porting some of my favorite libraries.  Part of the toolchain is this LM Flash Programmer utility, so I decided to play around with it a bit.  Well, I think I managed to brick my Launchpad.  I'm on Win7 at the moment.  Here's what happened.

Launched the LM Flash Programmer

Clicked through the tabs, noticed the ICDI Firmware Update section in the last tab.

Remembering that the ICDI firmware is what the Launchpad uses for programming and debug, I naturally thought an update would be a good thing, so...

Click.

Several messages went by, but I did notice it installed some sort of new "update" driver and I didn't see any errors.  Then when it was done, nothing.  No virtual COM port.  None of the three drivers present at all.  No characteristic ding when it's plugged in or unplugged.  Literally, there's nothing.  I tried on an XP system that had never had Launchpad plugged in and got nothing.  No ding, no driver install windows, nothing in Device Manager.  LM Flash Programmer complains that it is unable to find a target.  The update button complains that it failed to connect to the ICDI device and that it is unable to program the ICDI firmware.

I know the drivers were fine before I clicked, so let's rule out that possibility for now.  I can't see anything in Device Manager anyway.  What's left?  I read that if the ICDI firmware is lost, then the board must be returned for repair.  This gives me a bit of heartache because I modified the board to remove the exposed headers on top.  Can it be returned?  Is it worth it?

I'm pretty frustrated, too bad, because it was going so well until the update.  Suggestions most welcome.

  • Can MS USBview see the board (basically does your system detect anything connected to the USB port)? If not I would just buy new one. If yes, what USB call can you see. Maybe device went into DFU-class mode and system just cannot find drivers.

  • Good thought.  I'll give that a try today and report back.  Agree, with a $5 original investment, it was a steal.  I'd just purchase a new one as a last resort.

    Ken

  • Do realize that 2 Stellaris LX4F's reside - that board.  One serves as ICDI - and the "update" you attempted was likely improper for this relatively new board - and MCU.

    Officialdom should arrive here - and advise if such code will be made available.

    The 2nd MCU on your board remains intact - you can always capture its JTAG pins - and program/debug away - via normal/customary JTAG probe. 

    Local office/FAE may be best method to gain response - should this post linger...

  • Yes, I'll definitely hold on to the board, since it still has value.  Heck, when I get another, I can use that one to program my bricked board.  The question is whether I can find a way to revive the control side of the board.  That might prove to be a good weekend challenge.

    Doing some more reading, I see that the ICDI firmware isn't "publicly available", so I bet I'm out of luck for now.  Honestly, I'm puzzled that the LM Flash Programmer tool would load an invalid firmware image.  I'm also surprised that I'm apparently the only one who's clicked the "brick my launchpad" button.  Go figure.

    Thanks for the advice guys.  I wouldn't mind hearing from the TI folks on this.

  • One would hope that - "off the bat" - Flash Programmer would interrogate target, "who are you?"  Then - and only then - (after validity check) would "update" proceed.  Oh well...

    There are many versions of ICDI (not even counting LX4 ver.) and many versions of LMI Flash Programmer - not hard to see "how/why" you suffered your fate.  

    Stronger cautions should be emplaced - in fairness it is difficult to anticipate "everything" - your failed quest to optimize a "recent release" is not especially unusual...

     

  • I still doubt that LM Flash Programmer corrupter emulator. What does usbview say?

  • Hi Ken,

    Could you please tell me which build of LM Flash Programmer you used? You can find the build number in the title bar of the LM Flash window.

    -David

  • Maciej Kucia2 said:
    I still doubt that LM Flash Programmer corrupted...

    Why such doubt?  Majority of past ICDI transactions were managed/handled by FTDI chip(s) - poster's board uses LX4F!

    Unless LM Flash Programmer "knows this" - and safely alters or halts - chance to "disturb" the existing LX4F "ICDI" program exists.

    Of course - your suggestion to further test/examine is of value - but your "doubt" - not so much...

  • Hi David.

    I'm using LM Flash Programmer Build 1381.  The green LED is illuminated, so I know it's got power.  The USB cable is plugged into the Debug port and the switch is set to debug.

    Also, by request, I loaded up USBView and found that there is no activity on the USB ports at all when it's plugged in.  Zip, zero, nada.

    Looking at the files associated with the LM Flash Programmer, I'm guessing the ICDI firmware is embedded in the LM Flash Programmer executable, so there's no easy access to the firmware (not that it was the right firmware anyway).  I guess once your Launchpad is bricked in this fashion, it's game over?

  • Ken,

    One of the windows you clicked through was this:

    LM Flash Programmer build 1381 had ICDI firmware that was for a previous version of the ICDI circuit and is incompatible with the Launchpad ICDI. Please make sure you grab the most up to date LM Flash programmer if you decide to obtain another Launchpad. With a second Launchpad you will be able to program the target MCU on the first, so all is not lost.

    -David

  • Okay, I expected as much.  Funny thing is...

    1) I've never done any TI MCU development in the past, so there was no chance of an "older version" of the LM Flash Programmer being present on my system prior to loading the Launchpad toolchain.

    2)  The LM Flash Programmer version that I do have is the one that I was directed to install by the info on the website when I installed the Launchpad toolchain, however I expect this newer version you refer to has now replaced it.

    It seems I've fallen head first into a flaw in the toolchain that existed when the Launchpad was first introduced.  Perhaps I should have thought to update all parts of the toolchain when I started back up with it.  That's fine, but it's knocked me off the rails with no way to get back on.  That's irritating.  The money is no big deal, but the time spent...that's precious.  This is the 21st century.  There's no reason to not be able to recover something like this, policy or secret firmware notwithstanding.

    Today, I'm more irritable than most days, so to be fair to TI, I'll wait until later to see "if I decide to obtain another Launchpad".

    Ken.

  • David,

    Is it possible to run ROM USB bootloader on LX4F120H? 

    How can one re-flash bricked emulator?

    Thanks,
    Maciej 

  • I apologize that the link gave you an outdated version of LM Flash. Sometimes changes to our downloads take a while to propagate through the servers. We had a warning in place but I guess it didn't convey properly that loading an older version of the firmware could break things.

    It is possible to re-flash the ICDI firmware, but it requires a working Launchpad and some creative wiring. This doesn't help you since you only have the one Launchpad.

    Let me ask around and see if there is anything else that can be done.

    Thanks for you patience,

    David

  • Thank you David.  Please provide me with any information as you see fit.  Understand though, that without a way forward it's just easier to throw it in the bottom drawer and move on.

    I have to admit that the prospect of restoring the ICDI firmware by way of another Launchpad is intriguing.  I presume the new Launchpad would be used to flash the bricked chip.  Creative wiring indeed, assuming a few lead wires would have to be soldered directly to the pins of the bricked chip.

    Standing by...

    Update:  Asking around, I managed to find another Launchpad from a colleague.  I also noticed JTAG pads for the debug chip on the bottom side of the board.  It seems I'm all set, but without proper firmware to flash I'm stuck.

  • Hi Ken,

    I sent you an email directly yesterday afternoon regarding this topic. Did you receive this?

     

    Regards,

    Dan Nakoneczny

    Texas Instruments, Inc.

    Stellaris® ARM® Cortex™-M MCUs

  • Thanks for trying to get back to me on this, Dan.  I did not receive the email.  I just checked all my spam filters and there was nothing caught up in there either.  I do, however, see notifications when folks post to this thread, so I know my profile email is correct.

    Ken.

  • Hi Ken,

    I'm going to try again, if you don't hear from me today send and email to my attention at support_lmi@ti.com.

    Regards,

    Dan

  • Hi Ken,

    I have a similar situation. Have you found any solution to this bricked launchpad?

    Any suggestions would be appreciated.

    Cheers,

    Gus