Thread: TI Launchpad "Bricked"?
View Single Post
  #17   Spotlight this post!  
Unread 26-01-2015, 20:28
taichichuan's Avatar
taichichuan taichichuan is offline
Software Mentor
AKA: Mike Anderson
FRC #0116 (Epsilon Delta)
Team Role: Mentor
  
Join Date: Feb 2010
Rookie Year: 2010
Location: Herndon, VA
Posts: 328
taichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud of
Send a message via AIM to taichichuan
Re: TI Launchpad "Bricked"?
Quote:
Originally Posted by wt200999 View Post
Energia and the Gamepad Tool use the same backend, so if it works in Energia, it should work in the Gamepad Tool as well. I am surprised that it did not take right away. I will see if I can replicate this and follow up, but I am glad you were able to get it working!

Were you using a VM in Linux to run the Gamepad Tool? We have seen an issue if the VM doesn't know to assign the LaunchPad to the guest OS the update can fail. When you update the debugger chip, the USB drops and reconnects, so if the VM doesn't grab it, the device doesn't finish updating.
When the gamepad tool failed, it was running in native WinDoze 7 (64-bit). The launchpad was totally hosed with no USB serial interface available. I ran Energia in Linux to recover. Then verified that both my WinDoze VM (VmWare 11) and my native WinDoze machine could reprogram. For the VM, as long as you have the VM focused when you plug the device in, it defaults to capturing any new devices.

So, it was a bit convoluted, but everything is good again. :-)

Thanks,

Mike
Reply With Quote