"This device not supported" error while trying to

Xaque · Post by **Xaque** » Mon Nov 27, 2006 2:09 pm

Perhaps someone here can help me...

I have just spent all afternoon updating our fleet of CDM1550 LS+ mobiles with no problem except for the last...

After trying to program the new code plug, the radio now displays the dreaded "EEPRM CS ERROR"

Now when I try to read the radio I get "Image is corrupted. Checksum for R/W region failed."

And when I try to write the back-up code plug back into the radio I get "The Device is not supported by this application."

After searching the forum I can't seem to find an answer to my question:

What are my options? What should I try to remedy this? I do know some people have had luck forcing code plugs into radios after numerous attempts, but that does not appear to remedy this situation.

Of course, as always I would like to learn/acquire the tools to fix the problem 'in house' so any and all thoughts and suggestions are greatly appreciated!

(I'm running Windows XP with CPS 6.07.04, radio is new from moto and has firmware 5.05.17 and all equip has been working flawlessly except for this one fluke.)

Thanks for the help!

-Zack

Post by **wavetar** » Mon Nov 27, 2006 4:44 pm

The only thing which you might be able to do is try updating the firmware yet again. The latest on MOL is 5.05.19, I believe, which is newer than you indicated. Otherwise, off to the depot it probably needs to go.

Todd

Xaque · Post by **Xaque** » Mon Nov 27, 2006 5:04 pm

wavetar wrote:The only thing which you might be able to do is try updating the firmware yet again. The latest on MOL is 5.05.19, I believe, which is newer than you indicated. Otherwise, off to the depot it probably needs to go.

Todd

I have tried to give the firmware update and it did not work.

I receive another error message "The current radio has a hardware problem. Please refer to the radio repair manual for specific instructions."

I find this hard to believe as the "eeprm cs error" only occured after attempting to load a new code plug.

As far as putting the radio in boot-strap mode, I am not sure whether I have been succesful. The display constantly displays the EEPRM CS ERROR. Should there be an acknowledgment from the radio that it has entered boot-strap mode?

Sigh.

-Zack

Post by **wavetar** » Tue Nov 28, 2006 1:29 pm

One thing to try...start the firmware update with a working radio. At the point where it asks you to put the radio into bootstrap mode, swap in the bad radio. If the radio is indeed in bootstrap mode, the software should attempt to start the update. If it isn't, the software will tell you. If you cannot get it going this way, it sounds like the codeplug EEPROM is defective.

Todd

Xaque · Post by **Xaque** » Tue Nov 28, 2006 6:28 pm

Thanks, I'll try this...

...I guess what has me confused is why it wont simply let me force a new codeplug into the radio, instead of giving me the unsupported device error message.

Post by **wavetar** » Tue Nov 28, 2006 6:46 pm

Xaque wrote:Thanks, I'll try this...

...I guess what has me confused is why it wont simply let me force a new codeplug into the radio, instead of giving me the unsupported device error message.

The software isn't designed to allow "codeplug forcing" such as you can do with LAB software. It needs to get specific responses back from the radio, regarding model#, bandsplit, whatever. If it gets unexpected or garbage responses back, it doesn't know how to handle that, and gives the unsupported device error. It really all depends on where exactly the corruption resides...if it's not in an area where it affects the radios response to the software, you'll be able to write in a new codeplug & all's well. Otherwise, you're in an uphill battle. The ones I haven't been able to recover through a firmware upgrade are few & far between, but it does happen.

Todd

Xaque · Post by **Xaque** » Wed Nov 29, 2006 1:41 pm

Thanks for that explanation Todd! That makes me feel (a little) better about the situation. I'll let everyone know what my final status turns out to be.

joedisp · Post by **joedisp** » Sat Dec 30, 2006 2:04 pm

Check the radio Model is it a CDM 1250 LS or a CDM 1250

Xaque · Post by **Xaque** » Tue Jan 02, 2007 12:20 pm

joedisp wrote:Check the radio Model is it a CDM 1250 LS or a CDM 1250

They are CDM1250LS+...

...I was able to fix the EEPROM CS ERROR by writing the radio with an older version of the CPS (Well, someone else showed up and tried their machine, and they happened to be using an older version).

Terriers618 · Post by **Terriers618** » Fri Apr 13, 2007 8:08 pm

I HAD THE SAME ISSUE with a CDM1250 - using brand new version of CPS the one you were using. Had a problem, got that error, downgraded back to my older version and problem solved. any ideas why this would happen?

I want to be able to use the latest CPS unless it doesnt matter?

Jason

Post by **escomm** » Fri Apr 13, 2007 10:37 pm

Xaque wrote:
joedisp wrote:Check the radio Model is it a CDM 1250 LS or a CDM 1250
They are CDM1250LS+...

You have a radio that doesn't exist?

CDM1250LS and CDM1250LS+ are phantom models.