XPR5550 Error #8862 during firmware upgrade

[wdatkinson]

I am attempting to upgrade the firmware in an XPR5550 model #M28QPN9KA1AN, currently running FW version #R02.00.03, Codeplug version #01.00.18, Bootloader version #2.40.00. At around 60% complete, I receive the error message, "Error #8862 Application has encountered an error. Failed to access a file in the device."

Bootloader was upgraded before the error message. It was originally at R02.00.00.

STF'ing led me to this five month old thread: http://communications.support/archive/index.php/t-7663.html

However, my situation is a bit different. I'm using CPS 11.0 Build #596, and the PMKN4016B rear accessory cable. Due to these differences and the age of the aforementioned thread, I'm starting a new one. According to the device update package I downloaded, I should be able to make this jump without issue.

I'm able to read/write the radio without issue. Any suggestions?

 

[Mars]

How many times have you tried upgrading the radio firmware? Sadly, it seems normal for it to fail multiple times before it will successfully upgrade in Windows 7. Several of us have experienced this problem.

 

[PSEhub]

See if you can use a laptop with a really clean windows install. I have a a laptop that literally only runs Windows 7, Chrome, and MotoTRBO CPS. Also make sure that in this fresh install of windows that you have the exact drivers (especially on a laptop) from the manufacturer, specifically for your model, for your USB controller (as well as everything else i.e. chipset, graphics, etc.).

I just upgraded an XPR8400 the other day with a heavily used/installed on windows install and it took 17 tries.

Also, the CPS is a RAM hog so make sure your machine has plenty of that.

Today, used the "Mototrbo only" laptop, and it worked first try just fine (upgrading an XPR8400).

I hope to trace where this falls apart more (so I don't have to have the squeaky clean laptop). I'm thinking that some other drivers I install for random peripherals interfere with flashzap.

The other mistake is when the flashzap driver doesn't initialize quick enough, and the CPS says to "reset the device and try again", let the device finish installing flashzap before you do what the CPS says. Otherwise it will never get the chance to install and you'll be in a loop.

And yes these "prerequisites" are absolutely outrageous. Motorola really needs to update/fix the flashzap driver for TRBO.

 

[wdatkinson]

@Mars - I've tried three times so far. I failed to mention that I was running Windows 7. I'll give it a few more tries....

@PSE Hub - The laptop I'm using has a clean Windows 7 install on it, only about two months old and it's only used for programming, albeit I have other CPS installed besides Mother M.

Back to the bench.....

 

[wdatkinson]

Ok, two Windows 7 machines and one Windows 8.1 machine. All fail at the exact same place, 65% with the same error message. I probably tried around ~10 times with the first machine, twice with the second and so far once with the third.

Are there issues with upgrading firmware with the rear port? Unfortunately, I do not have an XPR5500 front/mic port cable.

 

[Mars]

The rear port is actually the most reliable one.

 

[wdatkinson]

Solved!

Even though the release notes say that I should be able to make the jump, on a whim, I successfully upgraded to R02.06.33 and then was able to successfully apply R02.40.00.

Thanks everyone for the suggestions. Hopefully this will help others!

 

[N4KVE]

Are there issues with upgrading firmware with the rear port? Unfortunately, I do not have an XPR5500 front/mic port cable.

This is all I use. It's always plugged in as it also runs the speaker, & ign trigger.

 

[Mars]

This is all I use. It's always plugged in as it also runs the speaker, & ign trigger.

When I was working on a radio with D01.xx.xx firmware, I found the only cable that worked (to upgrade to R02.40.00) was the rear port. I suspect it was because the control head buffers the comms to the brick, and the CH had outdated firmware in it, too. Remember: The CH is an accessory. The best connection is directly through the brick.

Either way, I'm glad to hear the OP managed to get updated. This is excellent!

 

[escomm]

I had this same problem with an XPR7550 and XPR5550. TSO support was no help. I warrantied the radios to the depot and they built me units with the old serial number. HTH

 

[PSEhub]

Glad you got it resolved. If we ever have a large order of units that ship with buggy firmware, we'll send them right back to where they came from. It's not right for Motorola to make the upgrade process impractical, and it shows in the fact that M built new units with old serial number in escomm's case. They don't even use their own junky software, they just send new one's it seems.

 

[N4KVE]

and it shows in the fact that M built new units with old serial number in escomm's case.

Whenever a radio goes to the depot, & a new one comes back, it always has a depot ser# tag with the ser# of the original radio that was sent in. GARY