Batboard

Anyone have any idea how i ended up with a Fail 01/82 when doing a read from a XTS5000 m2
host and dsp 11??

Host R11.00.00 was notoriously buggy and was known under a variety of circumstances to corrupt the codeplug beyond any normal recovery measure. Better hope the radio is legit tagged, and send it to the depot.

There was a SRN about this a few months ago... I will try and find it....

Here is the FSB10203 Batboard Thread

Thanks for the help guys..

You can try a firmware upgrade

Rod Farva wrote:You can try a firmware upgrade

A firmware upgrade will NOT fix this. It is a problem deep in the internal codeplug. Nothing short of a trip to the depot or factory will cure it.

Are you positive? I had the same thing happen to me when I reprogrammed my radio and I up'd the firmware to ver 12 and I was able to recover it. I had to do a massive realignment though.

The fail 01/82 happened with another XTS5000 that's come across my table-just last evening actually. During a write, I removed my wireless card from my laptop and boom- the computer froze and the radio failed. It was extremely depressing. A simple re-write will fix it, at least it did for me. Hopefully, you have your codeplug up to date, unlike me...I think there is about 5 and a half months of random updates I have to go back in and re-do.

Firmware R11 bricks radios by corrupting the external codeplug, specifically the dynamic block within the external codeplug. This dynamic block in the external codeplug is NOT written when you write/program the radio with CPS. If this dynamic block of data gets corrupt, the radio reports fail 01/82 and re-writing the codeplug will not fix the problem because the dynamic block causing the 01/82 isn't written. This dynamic block of data is written by the radio's firmware only, so only special depot lab software can write this dynamic block in the external codeplug to fix this problem. Something in R11 firmware is randomly writing to the external codeplug (when it shouldn't be) causing corruption to the dynamic block.

If you are able to reprogram a codeplug into a R11.00.00 fail 01/82 and it fixed the problem, then the firmware had nothing to do with fail 01/82. However if you have R11.00.00 in a radio, get it out of there because someday it will HARD brick sooner or later just by powering up the radio.

I just had a fail 01/82 just now upon writing my xts5000. It gave me a USB/error message, and displayed "Fail 01/82" on my radios display. Luckliky I just forced in a saved old codeplug and it took it, and that was that. Worked fine after that. I'm running R16.00.01 with CPS version R16.01.00 FYI. This is the FIRST time coming across this ( or ANY ) fail message. I'm almost afraid to write to the radio again. I've been using the same CPS / Firmware for a few years now with zero issues. Time for a firmware upgrade ?

no, I think it's the shitty USB driver...it's why I only use RS-232 cables for the older stuff.

I had a radio brick with this exact issue and version. Was my first (and now only) XTL5000. There was nothing wrong with the laptop (no freeze etc) just the codeplug failed programming mid duty and bricked the radio. Being brand new I sent the sod back under warranty and it came back with version 12 (the fight about that is another story for another day). Either way I could not re-write to the radio, just constantly failed with unable to read existing codeplug error.

MTS2000des wrote:no, I think it's the shitty USB driver...it's why I only use RS-232 cables for the older stuff.

I think you hit the nail on the head. I did notice my USB port / cable acting funny when I plugged it in ( sounded like a clicking noise, turning on / off, etc. ). I'll try another port next time I plug her in. This was a cable from Jim ( N7MAQ ) and has served me well, and I even have the ribless USB cable as well ( that took FOREVER for Vista to locate a driver for ).