View Single Post
  #5   Spotlight this post!  
Unread 04-02-2010, 12:07
dyanoshak dyanoshak is offline
Registered User
AKA: David Yanoshak
FRC #2158 (ausTIN CANs)
Team Role: Mentor
 
Join Date: Dec 2007
Rookie Year: 2007
Location: Austin, TX
Posts: 189
dyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond reputedyanoshak has a reputation beyond repute
Re: New BDC-COMM Version 88

Quote:
Originally Posted by computerish View Post
Is the Recover Device feature a GUI version of the boot command or does it make furthur efforts to unbrick the jaguar?
This is a different feature than the boot command. It pushes out firmware to any Jaguar stuck in the bootloader regardless of ID. This is why it is important to recover one "bricked" Jaguar at a time. If there are more than one on the bus, you can really brick your Jaguar and the only way to recover would be use a JTAG programmer or replace the Jaguar (this might be why some teams cannot get recover to work).

The Jaguar firmware detects the hardware it is deployed on. If the firmware doesn't match the hardware, it will branch to the bootloader (no LED, so it looks bricked) and wait for an update.

-David
Reply With Quote