[dyanoshak]

Hi all,

So far I have been unable to recreate the situation where a Jaguar gets corrupt and cannot be recovered.

Could you please post the steps that you were taking when the Jaguar would no longer accept an update?

An example of one of my successful (unsuccessful in recreating the problem) tries:

Using bdc-comm-88.exe in the GUI, one Black Jaguar connected through serial port on computer (not a usb-serial adapter).

1. Updated with Jaguar-87.bin (on purpose).
4. Update progress bar finished with no errors, but Black Jag is in LED off state.
2. Did not cycle power, tried Recover Device option (Update was grayed because there were no other Jags on the bus) with BlackJaguar-87.bin. 3.Progress bar completed and the Black Jag came back on line.

Be quite specific on what you do; when do you power-cycle the Jag, what does bdc-comm show, were you using 2CAN instead of bdc-comm, etc. Anything, no matter how insignificant, might give me some insight to what is going on.

If you could also answer these questions:

-Are you using a true serial port on your computer or are you using a usb-to-serial adapter?

-Have you "bricked" (by firmware issues) only Black Jags, Gray Jags, or both?

-Are they the only Jaguar connected when this happens?

-When updating firmware, is your 6p6c modular cable (from serial adapter to first Black Jag) running through the robot, is it isolated, long, short, etc?

I have noticed that sometimes when you get a "Cannot contact the boot loader!" error, disconnecting and reconnecting in BDC-COMM and reattempting the recover will work.

I will update with more once we can pinpoint what is going on.

-David