Device Manager shows "Tivaware Device Firmware Upgrade" when Launchpad is connected

Hi,

   Try erase entire flash using LM Flash Programmer, and see if you still get the same results.

-kel

While the "restore mechanism" suggested is normal/customary - you may add far greater value to this user community by further reporting any/all warning/error messages emanating from your IDE.  (assumed CCS)  You must have received one/several - which led you to the device manager for further investigation - hoped for clues...

Can you recall what you last programmed - or attempted - just prior to your board's demise?  Had you tried to install or operate with a, "boot-loader?" 

Such detail may very much benefit hundreds here who have suffered similar, "board lockouts" - and too often have been unable to identify the, "real cause."

Thanks Kel. Did that. It got (displayed) Erased.

 No change in Device Manager  even after this. Do I have to program  another .bin file after "Erase" ?

Regards,

Anil

Hi cb1_mobile,

Not sure what  really triggered this. What I could remember  is, had  connected a small  DC motor to  run from 5V of this board before this problem was observed.    I have checked  all the power supplies now and they are all OK

Regards,

Anil

@ Anil,

Thanks for your feedback.  Usual suspects for such, "lockout" include: repurpose of JTAG pins (PC:0-3) or a mismatch between board's xtal & xtal param. w/in SysCtlClkSet(). 

DFU is a valid means of updating MCU firmware - our group uses IAR & no such entry appears when we attach any among a variety of Stellaris devices.

Even though your motor is small - and run from 5V - beware of inductive kickback which may over-stress the MCU.  Always safest to impose an appropriate buffer or power device between the motor and your MCU.  Unwise to employ any MCU as, "beast of burden."

Thanks. 

Yes, culprit could be inductive kickback  of Motor.

Will this problem disappear  if   I program the MCU (used as  ICDI  ) firmware ?    If yes, where do I get the  .bin file for this MCU ?

Regards,

Anil

Anil Sudhakaran said:

Will this problem disappear  if   I program the MCU (used as  ICDI  ) firmware ?    

Sorry - am neither fan nor user of ICDI as used here.   

We use IAR & JLink - find it vastly faster/superior to vendor-specific/limited offerings.  (we must choose best MCU for the application - unlikely to always result from single vendor selection - IAR accommodates many MCUs, multiple vendors, SWD, Cycle Count etc...)

OK.

Waiting for someone's help  on programming steps for  MCU used as ICDI 

Regards,

Anil

Sorry for the rather lengthy delay in responding to your question! Regardless of my silence, I've actually spent the last 3 days working on this. What looked like a simple problem actually led me to a bug in the USB boot loader used in the ICDI and also a deficiency that could make it impossible to recover the device if power was interrupted during a firmware upgrade. I've fixed both of these problems and now have enough information to help you out.

The ICDI firmware actually involves 3 parts. The device you have has a USB boot loader in ROM but the flash-based firmware image also has a USB boot loader before the main firmware image. This is due to the fact that some older ICDI devices didn't have the boot loader in ROM and, since we only use a single firmware build for all ICDIs, we need to include the flash-based boot loader too.

What you are seeing indicates that either the whole flash-based image has been deleted and the ROM-based boot loader is running OR part of the main firmware above the flash-based boot loader has been erased and the flash-based boot loader is running. Before I can tell you how to recover, therefore, I need to know which of the two boot loaders has control on the problem board. Thankfully, this is pretty straightforward to figure out.

Start LMFlash, select "Manual", "USB DFU" and the single USB device you should see listed on the Configure tab then click on the "Program" tab and let me know the address that you see in the edit field next to "Program Address Offset". If it's 0, you're running in the ROM version of the boot loader. If it's 0x1800, you're running the flash version.

Once you let me know this, I'll tell you how to proceed.

This doesn't however, address the whole question of how the firmware became corrupted in the first place. I do know that it's reasonably easy to accidentally erase if you are working on a device application including DFU functionality and you accidentally connect to the wrong DFU (the ICDI instead of the device port). I'm working on making this more difficult to do but, if you reckon you may have done this, please let me know so that I can stop worrying about something else that may be causing the ICDI to be erased. If you didn't do this, any hints you have on what may have been done to the board would be helpful. It would also be helpful to have a copy of the contents of flash on the bad board but, from earlier posts, it sounds like you've tried deleting it already so this probably doesn't exist.

Hi Dave,

Glad that you have spent lot of time analyzing  this. 

"Program Address Offset" is displayed as  0x  0.

One of my students,  whom I am  Training on Embedded System was using the Board when it  went to this mode. As per him , he had connected  a  small  DC motor  to the 5V power supply of this board.  Sorry, I do not have much information to provide  that can give you more hint  on what caused  this issue.

Awaiting  directions for next step.

I am based  in  Thrissur, India and  there can  be a delay of  upto  half a  day to respond to you. 

Regards,

Anil

One more information Dave,

This Board is  "Stellaris LM4F120 launch pad" ( EK-LM4F120XL) .  When we  bought  the board, it was not named as Tiva C series.

I hope there is not difference in Firmware or Hardware, except the name ?

Regards,

Anil

Dave Wilson said:

I've actually spent the last 3 days working on this. What looked like a simple problem actually led me to a bug in the USB boot loader used in the ICDI and also a deficiency that could make it impossible to recover the device if power was interrupted during a firmware upgrade. I've fixed both of these problems and now have enough information to help you out.

Such keen tech awareness & sustained, hi-level effort - deserves much applause.  Good job & thank you, Dave!  Once again - you've gone, "Very much Above & Beyond..." 

Thanks Dave.

 Programmed the .bin file that you mailed. After that Device Manager  recognizes  the board properly.   I programmed one LED toggling program and it works fine.

Thanks a lot once again Dave for your great support,

Regards,

Anil

Hi Dave,

The problem I have is the same as that of Anil.
My Board is  "Stellaris LM4F120 launch pad" ( EK-LM4F120XL)
"Program Address Offset" is displayed as 0x1800.
Can you help me?


Regards,
Vyacheslav

Your problem is slightly different in that the boot loader in flash is OK but you don't have a main code image present. Just to be absolutely sure, when you connect the board to the PC via the USB connector labeled "Debug" (not "Device") you only see 1 function in Device Manager (Device Firmware Upgrade) rather than the 3 I would expect (Device Firmware Upgrade, JTAG/SWD and virtual COM port)?

If that's the case, I'll send you an image that will let you fix the problem. The next version of LMFlash will be updated to allow this ICDI state to be diagnosed and fixed automatically via the "Upgrade ICDI Firmware" function but I'm afraid the current version doesn't handle this.

Hi Dave,

I have the same problem specified above. After connecting my TM4C123 launchpad, In the device manager , there is this : 

After installing drivers ICDI , i'm getting this in device manager

Can you please help me out ?

Hi Stephano,

    Have you made your Tiva Launchpad work before you got this "Stellaris Device Firmware Update" error at Device manager.

    Are you trying to make your Tiva Launchpad work for the first time?

- kel

Hi,

Markel

Yes on one machine ,

and no on another one.

It was working fine with my laptop, my usb cable moved a lot and after some time, it was not more recognised. I uninstalled drivers and re-installed , but i still get the same Stellaris Device Firmware Update.

I am now trying on a new PC, from fresh , installing drivers etc, and still the same result.

Thanks for help

stephano

Hi all , thanks a lot,

I fixed the problem with LMFlash.

It's my first problem in the Embedded world. I'm a newbee. :)

Thanks everyone

Stephano

@Stephano.

    Did you Erase Entire Flash Contents using LM Flash Programmer?

- kel

Hi Markel,

yes i did that. and then it worked fine.

Stephano

Hi

I have same problem.

Could you send me image?

Hello Amit,

After reading this post i fill that i have same issue with TM4C1294XL.I am unable to find "Stellaris In-Circuit Debug Interface"

instead i got "TivaWare Device Firmware Upgrade" when i connect my board.

As Dave told in post that,

when you connect the board to the PC via the USB connector labeled "Debug" (not "Device") you only see 1 function in Device Manager (Device Firmware Upgrade) rather than the 3 I would expect (Device Firmware Upgrade, JTAG/SWD and virtual COM port)?

->yes, i am connecting DEBUG USB Port and My PC Shows Device Firmware Upgrade mode only.

Also in LM Flash Programmer 1613 "Program Address Offset" is displayed as 0x1800.

The only difference is that mine device is TIVA  c-series TM4C1294XL launchpad not EK-LM4F120XL .I Guess all image for all TIVA c-series board would be same.

Why this issue occured ?

Previously it was working fine as "Stellaris In-Circuit Debug Interface" but i am looking into boot loader using dfuprog.exe.

I have given this command #dfuprog -m -f <FileName>.bin in this -m mean switch Device into DFU mode.Then after my device not working on ICDI port.

Kindly send me Image and steps to recover TM4C1294XL launchpad.

please help i am running short of time in my project.

Thanks

Viraj