Hello,
Can someone determine if, in this pair of error logger entries (no others), there is evidence of more than just application memory being overwritten? This issue occurs occasionally when MpAlarmXSet is called with virtually any of the many configured alarms.
Error number 6804 appears with “mappEvIdle” as additional information, and 25314 includes the following backtrace.
Thank you.
Regards,
Michal Malek
From this information, I do not think anyone can draw a conclusion. To begin, you can deploy the IECCheck library into your project and update the mapp package to the latest version. If you’re lucky, the IECCheck library may help you identify potential bugs in your software. Additionally, updating the mapp package might resolve the issue if it has already been reported and fixed.
You can also contact the support team, providing a complete SDM system backup along with details about the versions of AR, mapp, etc., being used. The support team can check their existing bug database for any related issues.
I would just like to link to this wonderful post
Troubleshooting Page Faults - Share Info & Ideas - B&R Community
and also add that you can also get pagefaults with memset, memcpy etc. and wrong pointers to function blocks, which cannot be detected by IecCheck either.
OK, guys, thank you for your proposals. I’m a C programmer, so I need to use my own resources. The backtrace usually indicates the exact ‘problem position,’ and I was hoping that other backtrace data could help as well.
