Bad PEC detected?

[TWISTEDAPP]

I'm trying to fire up a BCM using a 3.7 image and it doesn't matter which MSC card or PEC that I use, I get the message:

Running sequence callCheckEveryStartup
Waiting for all services to be up and running...
All services are up and running.
Bad PEC detected - isolate and replace the PEC
An environment error was detected - initialization failed
Sleeping for 600 seconds...

and of course the 3.7 stops and just repeats the cycle never getting any further. I've tried changing PEC's, MSC Cards, and even tried another drive in case it had something written to it with the first failre?

Any ideas or directions?

 

[acewarlock]

Have you gone in though the serial port and done a INI? and MSC

 

[TWISTEDAPP]

Using the serial port, I've tried doing an MSC upload, CTI2 for Canada, and it seems to complete and return me to the platform initialization menu. When it is tried, I get the bad PEC message? All these PEC's can't be bad?

 

[TWISTEDAPP]

I put one of the MSC Cards that would say bad PEC in with a 2.5 FP1 drive and the system came up fine, except I couldn't get into telephony programming. I then did an MSC upload with CTI2 and afer rebooting, everything worked fine including telephony programming. The only thing is when I try to shut it down or reboot on the system tab, I get the message box "Notified Message" (1023,255,255) and it doesn't shut down. I'm going to attempt to take it back to 3.7 by putting the other drive back in. This was a working 3.7 so I don't know why it's giving me the hard time with BAD PEC message on any of these cards?

 

[TWISTEDAPP]

I currently have the machine running with 2.5FP1 and am leaving it run to see if it clears whatever condition is causing this "Notified Message" (1023,255,255)on trying to shutdown or re-boot through unified manager. The telephony programming is accessible and all the system seems to be totally functional. Is there anyone who knows what this message code means? Is it self clearing? I am waiting to see if it clears before trying the 3.7 virgin drive upgrade again. For now I'm stuck.

 

[mrstein77]

You may have a corrupted copy of the 3.7 drive image. Suggest trying another. I had this same exact error on a 3.6 when trying the do platform init. New drive fixed it!