BCM50R2 DSP issue

[koulioumbis]

Team hi
i have an issue with a bcm50 system that seems to be hardware fault.
i get these alarms and they are all DSP related.
anyone had the same issue?

Wed Mar 09 14:57:10 EET 2016 false 40004 warning DSP audit failed systemId=BCM;entityId=bcmm50r2;entitySubId=Msm
Wed Mar 09 14:57:04 EET 2016 false 40002 information DSP initialized systemId=BCM;entityId=bcmm50r2;entitySubId=Msm
Wed Mar 09 14:56:26 EET 2016 false 40005 critical DSP reset systemId=BCM;entityId=bcmm50r2;entitySubId=Msm
Wed Mar 09 14:56:26 EET 2016 false 40004 warning DSP audit failed systemId=BCM;entityId=bcmm50r2;entitySubId=Msm
Wed Mar 09 14:56:23 EET 2016 false 40004 warning DSP audit failed systemId=BCM;entityId=bcmm50r2;entitySubId=Msm
Wed Mar 09 14:56:20 EET 2016 false 40004 warning DSP audit failed systemId=BCM;entityId=bcmm50r2;entitySubId=Msm
Wed Mar 09 14:56:14 EET 2016 false 40002 information DSP initialized systemId=BCM;entityId=bcmm50r2;entitySubId=Msm

Thank
Nikos

 

[Firebird Scrambler]

Hello Nikos

Your BCM 50 is an old one at release 2.0. Have you replaced or reloaded the system with new 2.0 software?. It seems you might have corruption and therefore it might be more a case of it being a software problem rather than a hardware one?.


Firebird Scrambler
Nortel Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Advance knowledge on BCM support

http://www.linkedin.com/in/davidbromley

 

[ucxguy]

This indeed appears to be a hardware issue. The Msm component successfully downloads firmware to the DSP and initiates the DSP code execution, but it fails to communicate with the DSP over IP. After three failed attempts (audits), Msm resets the DSP, downloads the firmware again... Simply put, the DSP does not come up properly - and because the DSP is needed for many important tasks, software components that require DSP services cannot be started.

Changing the hard drive won't likely make any difference - based on these alarms, the software is doing what it's supposed to. The issue could be caused by the hard drive if the DSP firmware file was not read correctly - but considering all software (which is also read from the drive) appears to be working fine, the probability of that being the case is pretty small.

I am afraid you won't be able to recover the BCM50 unit, because the cause of your problem is almost certainly (99%) the DSP chip or the DSP memory on the mainboard. Well - I guess you could try to bake or freeze the mainboard (someone suggested that on some other tek-tips thread) to see if that helps, but that would be a Hail Mary pass...

 

[koulioumbis]

OK what about the DSP Chip replacement? Soldering the new chip if available maybe a good electronics lab..
the system has TDM telephony though but no GATI and GASI and no callpilot access.
Regards

Nikos