|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Bricked Grey Jag
I recovered a bricked grey Jag today by using a black Jag, RS-232 Adapter and the the BDC-COMM application.
It was recovered over the CAN port. I didn't think it would work at first, but I had the Black Jag configured for Board #7, chained up the bricked grey Jag, and used the recover option in BDC-COMM using the grey Jag firmware. It breathed life back into our grey Jag. Afterwards, I updated the firmware on the black Jag, making sure it was the only device on the chain, and explicitly using the black Jag firmware. |
|
#2
|
|||
|
|||
|
Re: Bricked Grey Jag
I can see that working. Unbricking the gray one but then bricking the black one. Remove the gray one then unbrick the black one.
I just don't like the idea of bricking a working controller for a non-working one. I popped the cover off earlier to find a set of vias labeled JTAG but don't know how they are wired. |
|
#3
|
||||
|
||||
|
Re: Bricked Grey Jag
Quote:
But I AM happy to say that we got through it unscathed. Just note that I did not at any time cut power to black Jag. I just disconnected the grey Jag, and moved the termination on to the black - then immediately updated the firmware on the black Jag to the proper one. Good luck! P.S. By bricked, I'm assuming that when you power it on, you simply get no response on the status LED, and cannot enumerate it on the CAN - this was the same behaviour we had, and it came as a result of a failed firmware update. |
|
#4
|
|||
|
|||
|
Re: Bricked Grey Jag
Quote:
Also there are solder-less jtag headers with spring loaded pins |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|