Page 1 of 1
MSF - Secure/SSCB firmware issue
Posted: Fri Mar 09, 2007 10:20 am
by motorola_otaku
I have a C44CXB Digital-Capable MSF5000. The SSCB firmware is 3.15, TTRC is 4.10, and the secure board shows "3" in the RSS. I have JU1 and JU2 configured correctly and secure enabled in the codeplug, and the station takes programming just fine. It goes through the self-test, spits out the SSCB and TTRC firmware revisions, then barfs when it gets to the secure board and throws out an error code (I don't have it in front of me) that the manual says is the result of the secure and SSCB firmware being incompatible. Am I correct in assuming that the SSCB firmware needs to be upgraded for the secure board to play with it, or is there something else I can try?
I don't have the super-special test panel that reads out the MUXbits, btw, just the normal one.
MSF issue
Posted: Sun Mar 11, 2007 10:35 pm
by George
You don't need a full test set in this instance because it won't tell you anything you don't already know.
Yes, you have incompatible firmwares. There is no point in fighting it, just upgrade everything and be done with it.
Create a new station profile from the RSS and load it up and you will be ready to set levels.
The firmware you have is ancient and should be tossed. Minimum I would recommend is 5.52 in SSCB, 5.34 in the TTRC and I forget what the secure board gets, but I want to say your 4.10 should be good. I'll check my board when I get home.
There is even 5.56 available for the SSBC, but I don't know what it fixes if anything relevant.
I standardized my stations on the 5.34, 5.56 and whatever my secure boards have in them.
Make sure your RSS is 5.21.
I don't know if it was you that asked the question, but yes, there is a chart of RSS and firmware compatibility in the back of the MSF programming manual. It's like...I don't know...Appendix G. Just look in back, you will find it.
There is just no point in fighting with anything less than the newest...and the last. And yes, I am up again way beyond my bedtime because I am backing up a huge database at a customer site 75 miles from home and I finally got a new drivetrain in my car and tonight was the first trial run for the new 3.8 and transmission for the Park Ave! Okay, nobody cares, but I am tired and I don't care either....good night.
George
Re: MSF issue
Posted: Mon Mar 12, 2007 4:38 am
by motorola_otaku
George wrote:Yes, you have incompatible firmwares. There is no point in fighting it, just upgrade everything and be done with it.
Well, that's par for the course. I'm going to venture a guess and say that firmware upgrades are NLA from Motorola?
Posted: Mon Mar 12, 2007 6:26 am
by xmo
The station control [SSCB] and remote [TTRC] are still listed on MOL.
Unfortunately, the secure board firmware doesn't appear to be available.
Posted: Mon Mar 12, 2007 7:20 am
by motorola_otaku
xmo wrote:The station control [SSCB] and remote [TTRC] are still listed on MOL.
Unfortunately, the secure board firmware doesn't appear to be available.
Well, the secure board is probably okay. Got part #s for the SSCB and TTRC?
Posted: Mon Mar 12, 2007 8:15 am
by xmo
TVN6055A Software SSCB
TVN6056A Software TTRC
The prices won't even scare you.
Posted: Mon Mar 12, 2007 10:31 am
by motorola_otaku
xmo wrote:TVN6055A Software SSCB
TVN6056A Software TTRC
The prices won't even scare you.
Heh, the way you put it I was expecting something else.
Now here's the million-dollar question: does the firmware come pre-blown on ASIC chips, or do they send you a disk with the firmware on it?
Posted: Mon Mar 12, 2007 11:02 am
by xmo
Comes pre-blown into EPROM chips, ready to plug in & go.
Posted: Mon Mar 12, 2007 1:34 pm
by motorola_otaku
Well then, I think we're cooking with gas. Thanks for the help, gentlemen.

Posted: Fri Mar 16, 2007 7:58 pm
by d119
Your secure firmware may also be too old. I encountered the same problem with my station and ended up having to upgrade the secure EEPROM from another station. Read the EEPROM and programmed it into the freshly blanked one from the troubled secure board.
Cleared everything up. I was working with Version 4 secure.