recovery for a brick'd tan jag?

[grambo]

I just bricked two of our old (tan/grey) jaguars trying to update them... I was able to update two black jags without issue, so I got brave and went on to the tan ones. I bricked the first one, second jag went fine, and the third bricked. Each time I had only a serial cable into the black jag and a single tan jag in the CAN network. I'm looking at the "getting started guide" for the black jag and I'm realizing that my terminator on the black jag is about 3" or 4" away from where they are prescribing (stated as part of the serial cable), so I'll fix that before trying anything else.

I tried holding down the 'user' button on the tan jags at power-up to try and recover them, but it didn't seem to work. Is there a certain length of time to hold the button for, or a different method for recovering a bricked tan jag?
Thanks in advance.
-Jonathan

[Mark McLeod]

Did you use the Recover option in BDC-COMM?
Here's one story thread by someone who recovered a Gray Jag.

[grambo]

I'll have to give Mr. Lim's sequence a shot. That's what I was tempted to try this evening, but the BDC-COMM isn't explicit about what that "recovery" action does - if it's intended for recovering a grey jag via a black jag, or just what's at the end of the serial cable. I'll let you know how it goes tomorrow.
Thanks for the link.
-Jonathan

[WizenedEE]

Originally Posted by Mark McLeod

Did you use the Recover option in BDC-COMM?
Here's one story thread by someone who recovered a Gray Jag.

I recovered two bricked black jags (bricked by the 2CAN web interface) with BDC com, just by doing the normal upload firmware thing. Perhaps you could try that first?

Also, what were you saying about the terminator being too far away? Does the cable length matter?

[jhersh]

Originally Posted by grambo

I'll have to give Mr. Lim's sequence a shot. That's what I was tempted to try this evening, but the BDC-COMM isn't explicit about what that "recovery" action does - if it's intended for recovering a grey jag via a black jag, or just what's at the end of the serial cable. I'll let you know how it goes tomorrow.
Thanks for the link.
-Jonathan

It's for black or gray jags... just make sure there is only one bricked Jaguar on the bus when attempting recovery!

[ratdude747]

make sure you use the correct firmware file... the one not for black is what you want.

[grambo]

We're all set!

new cables with the terminators in the correct locations, turned off the milling machine and a couple other power tools from the 1940's and we're back in action. The two bricked jags appeared to need a power cycle with the reset button pressed and then the "recovery" via BDC-COMM worked fine. Thanx!

[4molo]

Bricked a gray jag during firmware upgrade. Went through the process to get it back and got my LED back. But When I connect up a black jag as bridge and the gray jag, then start up BDC Comm, it only recognizes the black jag on the CAN. I've got no board ID for the gray jag so I can reassign. I attempt to run recover device using the gray jag firmware with the black jag as bridge to the gray jag when BDC Comm only recognizes the black jag, but that ended up bricking the black jag (which I was able to recover when I took the gray off the CAN). I tried changing the board ID of the black jag to see if there was a ID conflict, but still only recognized the black jag. I'm connecting via a USB-to-Serial-to-RJ12 bridge cable and had no problems updating 2 black jags and 1 gray jag before this. So the question is how do I get a board ID back on the gray jag?

[ratdude747]

are you sure your cabling is ok?

try setting a new ID to the jag. some of the gray jags have no ID and need to be set (assign button +paperclip in user button).

[4molo]

Originally Posted by ratdude747

are you sure your cabling is ok?

try setting a new ID to the jag. some of the gray jags have no ID and need to be set (assign button +paperclip in user button).

Cabling/terminator all check good. 3 jags on CAN all (2 black, 1 gray) check good via BDC Comm. Tried a couple times to assign, but can't select the board ID of the gray because it doesn't show up. Just see the black jag acting as serial bridge in BDC Comm, solid amber LED. The gray jag shows a blinking yellow which means it's not communicating. However think I should be able to see the board ID in the drop down.

[kamocat]

How was this gray Jag bricked?
Did you accidentally give it Black Jag firmware?

[4molo]

Originally, it bricked when loading the gray jag firmware...no LED. Recovered using Mr Lim's sequence...LED flashing amber. Disconnected gray from CAN (terminated Black Jag), then reimaged the Black Jag acting as serial bridge with the Black Jag firmware. Powered down both. Reconnected CAN (terminated Gray Jag). Powered up to assign number to Gray, but only the Black Jag enumerated...no board ID showing for Gray Jag.

[Mr. Lim]

Did you assign a board ID to the Black Jag other that #1? By default, after recovering, your Jags will all reset to Board ID #1, and so you may have both the Black and Grey Jags enumerating to Board #1, causing a conflict.

[4molo]

Black Jag was assigned 11. BDC Comm just doesn't show another board ID even though the Gray is properly connected and terminated. Changed assignment on Black Jag to 21 just to be sure there wasn't a conflict and tried again, but BDC Comm still not showing another board ID on the CAN.

[ratdude747]

did you try resetting the ID on the tan jag? sometimes the tans act as if they do not have an id until you give it one.