PSR500/PSR600: Cannot Update CPU Firmware

[robo21]

The DSP firmware updated fine from 1.3 to 1.4 however, in attempting to update the CPU firmware from 1.6 to 2.1 I get an error message: " No data from scanner (2) please retry from step 4." The test and the DSP firmware upgrade worked fine.

It's just that once I click the "upgrade" button the scanner goes into the scan mode without updating. This is bizarre. Any ideas?

And yes, I have been through the firmware sticky above. Apparently I made a mistake when I ran into a problem updating the CPU firmware I went ahead and updated the DSP. Now rather than an error message the scanner starts scanning when I click on Update. Am I now stuck with an un-updateable CPU?

Thanks.

 

[SCPD]

Wrong com port settings ..

 

[robo21]

Wrong com port settings ..

The Arc 500 software is working in downloading and uploading on Port 4. Also, I was able to update the DSP using port 4. So wouldn't that indicate that the com port setting was/is correct? Is there another com port setting besides the port # that I am not aware of? Thanks.

 

[Voyager]

Are you sure you're using the firmware for your exact model?

 

[ScannerSK]

There is a Canadian version of this scanner (PSR-500C/PSR-600C). I believe the DSP upgrade works on both versions however there are separate CPU upgrades for each version.

I would try the latest firmware version 2.3 which can be downloaded from here:
http://forums.radioreference.com/gre-scanners/314560-psr-500-600-firmware-2-3-a.html#post2401286

If this does not work, I would save your data onto your computer and then reset the scanner by holding "0" when it turns on and then press "CL". This will restore the factory DSP version and may help to restore the scanner to accept not only DSP upgrades but also CPU upgrades once again.

Its worth a try.

Shawn

 

[Swipesy]

Adding to what ScannerSK stated is this release information -

The PSR-500 and PSR-600 have two different updater EXEs. Which one you use
depends on which version of BOOT code your scanner contains. The BOOT code
version can be determined by holding down the PROG/PGM button while turning
the scanner on. The first line of the LCD should display:
uP Boot Ver:F1.x

If you have "Boot Ver" F1.4 or higher, use:
CPUUpdater_PSR500-600_U2.3_Boot1.4.EXE

Otherwise (Boot Ver less than 1.4), use:
CPUUpdater_PSR500-600_U2.3_Boot1.0.EXE

There's a third updater EXE for the Canadian PSR-500/600:
CPUUpdater_PSR500-600_U2.3_CAN.EXE.
Use this if the firmware version display is of the form: uP BootVer:Cx.y
(note the 'C' in the version).

 

[robo21]

Thank You!

Thanks guys! What a great community! I greatly appreciate the help. I went through a brain freeze, missed the instructions about having the correct boot version Swipesy, Shawn, Voyager and ScannerSK, once I had the correct loader version the procedure was smooth as silk! I can't believe I had missed that in the instructions.

A special thank you to Shawn for the link to Ver. 2.3! I thought 2.1 was the most recent. And of course you were right, by going back to the default DSP version I was able to load the new CPU firmware with no problem. BTW, reverting to the earlier DSP version didn't affect the programming of the scanner.

Thanks for being gentle Swipesy, I should have read the instructions more carefully. You guys are all a great help!

Am I correct, DSP update version 1.4 is the most recent?

And finally, as is the case with most other firmware updates, previous versions of the CPU update (i.e.1.8.1.9, 2.0, etc.,) are all rolled into the ver. 2.3?

Thanks again!

 

[Swipesy]

Robo21 you are correct that 1.4 is the most recent and that Ver2.3 contains all the CPU updates.

It is always a pleasure to help someone like you who is appreciative of the help many of us offer.

John

 

[robo21]

Robo21 you are correct that 1.4 is the most recent and that Ver2.3 contains all the CPU updates.

It is always a pleasure to help someone like you who is appreciative of the help many of us offer.

John

Hi John,

This is great! What a relief to know that everything is current and I am on the right track. Thanks again for your kind assistance and the welcoming attitude with which you provide the assistance.

Happy Holidays to you and yours!
Robin

 

[robo21]

Robo21 you are correct that 1.4 is the most recent and that Ver2.3 contains all the CPU updates.

It is always a pleasure to help someone like you who is appreciative of the help many of us offer.

John

John, is there a list somewhere of the details of all of the CPU updates since 1.6?

 

[ScannerSK]

The following PDF file lists versions 1.6 and earlier (see page 11):
https://wiki.radioreference.com/images/2/22/PSR-500_info.pdf

Version 1.7 states:

New features:

* Changed S-E GLOB "138-174 5kHz:" item to "Bandplan:", with choice
between USA and Canada

* Changed step size to 12.500kHz in 405.987500-512.000000MHz range
when the “Bandplan: Canada” option is selected in the FUNC-GLOB
menu.

* Change stepsize between 470.000000MHz and 512.000000MHz
from 12.500kHz to 6.250kHz to handle the new UHF bandplan


Fixes / Enhancements:

* Further qualify EDACS "Individual" call grants to address a
problem where the radio sometimes tunes to MDT transmissions as
radio-to-radio calls.

* Fixed EDACS "channel number" in CCDump messages

Other:

* New DSP Boot code V1.1 to handle a different Flash IC version.
There is no user-noticable performance change.

Version 1.8 states:

CPU firmware version 1.8 provides the following enhancements to your PSR-500/PSR-600 trunked scanning receiver:

Added patch support for P25, Motorola and EDACS trunking
Patched talkgroup calls are recognized and processed correctly by the scanner.

Changed CCDump type string to "EDn" if "narrow invert" is turned on
This is a minor change to the CCDump text output that identifies when the radio is monitoring an EDACS narrowband control channel and the “Invert data” option is selected.

Corrected LCD “mirror image” issue
Corrects issue where in certain rare circumstances the LCD may display data in
reverse or “mirror image” mode.

Version 2.0 states:

• Pressing the ATT key during scanning while on a CONV object causes the object to be stored to EEPROM immediately. This eliminates the possibility of the ATT status change being lost due to a Priority check.
• Changed 154-156MHz range to accommodate Marine channels
• Added duplicate checking to conventional channels created via PGM NEW CONV

Version 2.1 states:

• Fixed Marine, VHF, and UHF search frequencies

Version 2.3 states:

An update to the PSR-500 and PSR-600 has been released. This version addresses the EDACS ESK detection problem discovered while monitoring the Denver Public Safety system (it may occur on other systems but, to my knowledge, it's only been reported on this one).

Shawn

 

[robo21]

The following PDF file lists versions 1.6 and earlier (see page 11):
https://wiki.radioreference.com/images/2/22/PSR-500_info.pdf

Version 1.7 states:

New features:

* Changed S-E GLOB "138-174 5kHz:" item to "Bandplan:", with choice
between USA and Canada

* Changed step size to 12.500kHz in 405.987500-512.000000MHz range
when the “Bandplan: Canada” option is selected in the FUNC-GLOB
menu.

* Change stepsize between 470.000000MHz and 512.000000MHz
from 12.500kHz to 6.250kHz to handle the new UHF bandplan


Fixes / Enhancements:

* Further qualify EDACS "Individual" call grants to address a
problem where the radio sometimes tunes to MDT transmissions as
radio-to-radio calls.

* Fixed EDACS "channel number" in CCDump messages

Other:

* New DSP Boot code V1.1 to handle a different Flash IC version.
There is no user-noticable performance change.

Version 1.8 states:

CPU firmware version 1.8 provides the following enhancements to your PSR-500/PSR-600 trunked scanning receiver:

Added patch support for P25, Motorola and EDACS trunking
Patched talkgroup calls are recognized and processed correctly by the scanner.

Changed CCDump type string to "EDn" if "narrow invert" is turned on
This is a minor change to the CCDump text output that identifies when the radio is monitoring an EDACS narrowband control channel and the “Invert data” option is selected.

Corrected LCD “mirror image” issue
Corrects issue where in certain rare circumstances the LCD may display data in
reverse or “mirror image” mode.

Version 2.0 states:

• Pressing the ATT key during scanning while on a CONV object causes the object to be stored to EEPROM immediately. This eliminates the possibility of the ATT status change being lost due to a Priority check.
• Changed 154-156MHz range to accommodate Marine channels
• Added duplicate checking to conventional channels created via PGM NEW CONV

Version 2.1 states:

• Fixed Marine, VHF, and UHF search frequencies

Version 2.3 states:

An update to the PSR-500 and PSR-600 has been released. This version addresses the EDACS ESK detection problem discovered while monitoring the Denver Public Safety system (it may occur on other systems but, to my knowledge, it's only been reported on this one).

Shawn

Wow, this is awesome. Thank you very much Shawn. This is exactly what I was looking for but was hard to find.

I am amazed that updates continue to roll out on the PSR-500 & PSR-600. After doing a little research I see that even though GRE no longer builds scanners, they continue to offer support and warranty service for their radios.

 

[Swipesy]

Unfortunately Robin you have probably seen the last of GRE updates and certainly no warranty since GRE is out of business. The last update to the PSR500/600 was done out of the kindness of Don Starr who provided the bug fix with permission from Whistler.

John

 

[robo21]

Unfortunately Robin you have probably seen the last of GRE updates and certainly no warranty since GRE is out of business. The last update to the PSR500/600 was done out of the kindness of Don Starr who provided the bug fix with permission from Whistler.

John

Thanks for the info John. I sold my mint condition - like new, GRE PSR-500 about 45 days ago. Funny thing, a business associate of mine happened to hear my scanner in the background of a telephone call one day. He went nuts and fired off the following: "Wow, your scanner is awesome, the audio quality is amazing. I want it! How much will you sell it to me for?" "Can you get Beverly Hills, LAPD, & LASO on it for me today?" "I will send a courier today to pick it up!"

So I loaded it up with the frequencies he wanted and he sent the courier, he paid $400. With that I was able to purchase a brand new Pro-651 and a used Pro-106 and I had $60 left over from the sale which I used to buy cases for my new Radio Shack scanners. He's happy and I am happy. He even gave me the GRE programming cable as he will want me to program the scanner for him in the future, if necessary.

I have been helping him and also a buddy who lives out of state keep their GRE scanners up to date.

I am also concerned about updates on the Whistler built, Pro-651. I don't imagine there will be anything forthcoming on the GRE built 106.

 

[Mojaveflyer]

PSR-500 / 600 Updates

After finding this thread I was able to update both my PSR-500 & 600 last night. It took several tries for both of the radios but got it eventually.

I wanted to say thanks to the folks on this forum for all of the information provided here.

 

[robo21]

Does anyone know if there is a 2.3 CPU update for the Radio Shack Pro-106? Interestingly, my Pro-651 has a CPU version of 2.8.

 

[Spitfire8520]

Interestingly, my Pro-651 has a CPU version of 2.8.

The CPU firmware development between the Pro-106 and Pro-651 is independent due some "under the hood" changes. I would avoid comparing firmware between the two models as they are not compatible.

 

[robo21]

The CPU firmware development between the Pro-106 and Pro-651 is independent due some "under the hood" changes. I would avoid comparing firmware between the two models as they are not compatible.

Interesting! I have been mistakenly thinking that these radios (PSR-500, Pro-106, & Pro-651) were all exactly the same except for firmware and cosmetics. My understanding was that GRE built the 500 & 106 and Whistler built the 651 using the same schematic and parts as GRE. Of course I realize that the firmware is NOT cross compatible among the 3 units and that some have actually bricked their radios when trying to update with the wrong firmware.

I am very curious about the specific "under the hood" variations.

 

[fxdscon]

Interesting! I have been mistakenly thinking that these radios (PSR-500, Pro-106, & Pro-651) were all exactly the same except for firmware and cosmetics. My understanding was that GRE built the 500 & 106 and Whistler built the 651 using the same schematic and parts as GRE. Of course I realize that the firmware is NOT cross compatible among the 3 units and that some have actually bricked their radios when trying to update with the wrong firmware.

I am very curious about the specific "under the hood" variations.

It has been posted previously by DonS (the person writing the firmware) that the newer firmware in the Whistler versions of those scanners addresses the newer versions of some of the EOL components used in the older scanners. There is no difference in features or functionality.

 

[robo21]

It has been posted previously by DonS (the person writing the firmware) that the newer firmware in the Whistler versions of those scanners addresses the newer versions of some of the EOL components used in the older scanners. There is no difference in features or functionality.

Excellent! So what do you guys think, will there be any future updates on the 651 since it is still in production?