BDC-COM reports "Unable to contact boot loader" when trying to update firmware

[Dragonslayerend]

I get a report of this:

How do I fix this? I have all correct cables 6p6c and correctly assembled DB9 connector. I found someone with a problem like this but it was from 2010, was there a patch for this if so please help me I'm stuck.

[linuxboy]

It has been a while since I've seen that error, just to note, it looks like you posted just a thumb and not the full image. If memory serves, try flashing the firmware in recovery mode (WARNING, HERE BE DRAGONS), which will contact it at some lower level I think, and upload the firmware that way. Recovery is in one of the menus. Normally it is used for an otherwise nonfunctional jag, if something goes wrong in this process, you can brick the jag, so make sure not to unplug it, and I'm not responsible if anything bad happens.

Good luck,
Oliver

[Dragonslayerend]

Haha okay I'll see what happens thanks, all 4 jags are doing this though could all of them have this problem?

[Cecil]

Also, make sure you have given the Jaguars unique ID numbers before flashing their firmware. If more than one Jaguar has the same ID, it will give the same error, if I remember correctly.

[Dragonslayerend]

I can't even set ID

[cbf]

We're having the same problem.

Was there a resolution to this issue?

[Phalanx]

I've run across this a few times. What has always worked for me, (if it wasn't truly bricked) was to use a USB to Serial on my laptop, with the DB9 connector built as documented, a 6 wire can cable, and ONE and ONLY one Jaguar attached and terminated.

I was then able to perform a recover device. But you can only have one JAGUAR on the bus for it to work.

[graham.robots]

We are having the same problem, but we have been only using one jaguar at a time in the first place... any other solutions?
Thanks in advance,
Team 4024

[Dragonslayerend]

What happened was for some weird reason it was the DB-9 connector. I fixed the problem after making another one and using the new one instead. Though I still don't understand how it happened. It got even more confusing after I tried the old DB-9 connector that gave me problems again and then it miraculously worked! Physiscs is confusing but you should try out with a new DB-9 connector, or might as well just make a custom cable that plugs straight into a serial port.

[Levansic]

Two of our new Jaguars have this problem. Never got the LED to light on either one. Students labeled them, and put them in an anti-static bag to deal with them later.

Now is later. We thought it may be excess conformal coating, which was a visible translucent film on the power terminals, but scraping them had no effect. The power pins for the encoder give 5V, but still no LED, or boot loader. Time to get RMA's.

These were in the last batch of Jaguars we bought this year, after our robot was outfit. The initial discovery was made when we tried to flash with the 107 firmware, to prepare for competition. Luckily, we had no failures of any Jaguars, and had a few spares that were working.

-- Len

[DavisDad]

We were updating a VEX Black Jag firmware with bdc-com and PC crashed. The Jag LED was dead. We researched this a tried all suggestions to restore communication. Contacted VEX and determined we needed to send back to VEX to fix. We sent the "bricked" unit back w/ RMA and the repaired unit was quickly returned. The only cost was shipping to VEX.

Two thumbs up for their customer support.