Astro Saber I Firmware Upgrade

[akardam]

Fail 02/90 indicates a general DSP failure. This combined with the firmware upgrade scenario and the lack of any DSP revision in service mode suggests that there was a problem during the firmware upgrade, either to completely erase the DSP ROM in prep for new firmware, or an incomplete new DSP firmware write. Either of those conditions would generally indicate a bad DSP ROM itself. You can try flashing the radio again, but I doubt it will come back.

[RADIO43]

Alot of info here....

Link- http://batboard.batlabs.com/viewtopic.php?f=4&t=84203

[jmr061]

Probably used the wron upgrade file. What is the cvn #?

Jason

[akardam]

I think if the file had the wrong type of DSP (and all the newer CVN's at least contain code for both generation DSP chips), it would have thrown an error, but I'm not sure... something about a hardware mismatch?

[RADIO43]

I had the same problem when I did an upgrade of an older firmware version..... Use CVN6251N and a different Flashkey and it should fix this error. Thank you again to n7maq for his help when I had this problem...

njradionut.... Open up the attached link on my previous post and you will see I had the same problem....

[RADIO43]

Just use a different Flashkey from the original one, that you used the first time you tried to flash the radios....

[jmr061]

The refresh flashkey has nothing to do with it. Thats a generic key to allow an upgrade. That is all a refresh key does.

Jason

[RADIO43]

In this situation the Flashkey did matter....

I ran into the same problem as njradionut, as I mentioned in the linked post.

I tried to flash my Astro Sabers that had old firmware in them with CVN6236 which was XTS3000 / Astro Sabers with newer firmware in them specific. I had used the same .cvn file many of times on Astro Sabers but never on a Astro Saber that had as old of Firmware in them as these. When I did it developed the same symptoms as njradionuts radios.

Now, after posting it on the board, I received some great knowledge from n7maq who advised me of the right .cvn (CVN6251) to use. I then went to reflash these radios (with same same refresh flashkey I used before) with this .cvn and I got an message advising me that the radio had already been flashed using this refresh flashkey.

Well, after trying over and over again with that flashkey, I decieded to get more help and was advised to try a diffrent refresh flashkey.....

After using a different refresh flashkey... BOOM, it upgrades perfect....

Hope that explains what I meant better....

[akardam]

The Astro platform does not, as far as I know, track which flashkey was used on the radio last. I have had the CPS tell me that the radio has already been upgraded with the current version. In my testing it seemed that it would trip on not only the major version number (07.xx.xx) but also the minor revision number (xx.71.xx), even if it was one or two revisions off. This was all a while back so take it for what it's worth. If this is still true, it may mean that the OP might not be able to reflash his radio even with the correct CVN and a different flashkey.

FYI, the CVN6236 part you reference is 1meg Astro Saber firmware for analog DSP's. It should work with both A or M (version 2 or 1, respectively) DSP chips. CVN6251 is the same, except for digital DSP's, I and N (v2 and v1). Other than the host rom size, I don't think there's any limitation on how new or old an Astro Saber needs to be in order to use these CVN's.

[RADIO43]

akardam,

You are correct, the message was that the radio was already upgraded with the current version, not a flashkey message. It has been a few months, so I forgot that. The work around that I was advised to use for this was to use a different refresh flashkey. Once I did... Boom, the AS took the CVN6251 upgrade and corrected the issue.

sorry for confusion there

radio43

[akardam]

Each CVN should have a revision suffix, e.g. CVN1234A, where A is the revision. What were the full CVN and revision numbers you used?

[RADIO43]

First .cvn I used was CVN6236L...

The .cvn that fixed it was CVN6251N....