Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrading a StarTalk Flash

Status
Not open for further replies.

ptstechnician

Vendor
Jun 28, 2006
895
US
If I upgrade a StarTalk Flash 1.7 to 2.0, will I loose all the programming?
 
you should not as long as the flash is good
 
So, all the programming stays in the flash itself and not in the pcmcia card?
 
Does anyone know if there's a table of all the changes between versions? Our expanded Flash is running ver. 1.9.0 on our 8x24 DR5.1 I've got a 2.0.10 card here out of another Startalk Flash, and I'm wondering what's new, or if there are any valid reasons for me to upgrade?

So far the only thing I've noticed is that the CLID report is always empty, even though we have working CLID on all our trunks. Is this a flaw in v1.9.0?

~Rick
 
Well I was bored so I went ahead with the upgrade. Smooth as butter. Since I had so much fun finding the instructions, I thought I'd post it again here.

I followed the steps in Post #2 here

To perform a StarTalk Flash software upgrade:

Open the module front door.

Remove the teladapt cord(s) from the teladapt line jack(s) inside the StarTalk Flash module. Important: This step must be completed to avoid any possible loss of configuration or programming information.

Wait one minute before proceeding to the next step.
[/color blue]
I had a connection to the serial port, so I waited until I saw "!! Unable to start flashtalk,Please check port and TCM connections"

Unplug the AC power to the StarTalk Flash module.

Remove the current PCMCIA ROM card.

Insert the new PCMCIA ROM card into the slot provided on the StarTalk Flash module.

Re-insert the teladapt cord(s) into the teladapt line jack(s) inside the StarTalk Flash module.

Plug the AC power back into the StarTalk Flash module.[/color blue]

Everything came up right away. I didn't have to do any of that extra stuff in the 3rd post. All the programming and CCR trees were still in place. The only thing I've noticed is that I don't get a ton of alarm messages like I used to. And yes, it only took me 3 minutes.
Code:
Date     Time     Error Message
13/07/06 00:00:33 mbx.c: MBxClose mbCloseCabinetrc RetCode = 10752(2a00)
15/07/06 00:01:25 MsgDelete..MsgDelete of body failed: 85EB20CC.A00 RetCode = 8226(2022)
15/07/06 00:01:25 msg.c: MsgDelete RetCode = 8226(2022)
15/07/06 00:01:26 mbx.c: MBxClose mbCloseCabinetrc RetCode = 10752(2a00)
20/07/06 15:24:58 Shell 0: Idle: Unexpected event RetCode = 48(30)
29/07/06 00:07:10 MsgDelete..MsgDelete of body failed: 85SB29T'.A00 RetCode = 8226(2022)
29/07/06 00:07:10 msg.c: MsgDelete RetCode = 8226(2022)
29/07/06 00:07:11 mbx.c: MBxClose mbCloseCabinetrc RetCode = 10752(2a00)
29/07/06 00:07:12 MsgDelete..MsgDelete of body failed: 85R939#V.A00 RetCode = 8226(2022)
29/07/06 00:07:13 msg.c: MsgDelete RetCode = 8226(2022)
29/07/06 00:07:13 MsgDelete..MsgDelete of body failed: 85SA54J8.A00 RetCode = 8226(2022)
29/07/06 00:07:14 msg.c: MsgDelete RetCode = 8226(2022)
29/07/06 00:07:15 mbx.c: MBxClose mbCloseCabinetrc RetCode = 10752(2a00)
30/07/06 01:18:46 pm.c: Port OUT of service RetCode = 65535(ffff)
30/07/06 01:18:47 pm.c: Port OUT of service RetCode = 65535(ffff)
30/07/06 01:18:52 pm.c: Port OUT of service RetCode = 65535(ffff)
30/07/06 01:18:54 pm.c: Port OUT of service RetCode = 65535(ffff)
30/07/06 01:18:55 pm.c: System shutdown RetCode = 65535(ffff)
30/07/06 01:19:00 Base Alarm 00A: osRaiseException - Rebooting.
30/07/06 01:23:24 Base Alarm 000: System is now Booted and Operational.
 
Weird how it broke the link, and I can't seem to edit. Anyways, I want to give credit where credit is due. I originally found that info in thread799-675217
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top