1) 11-Dec-2009
2) 1 Day
3) MC3090
4) BSP35 5) 2031970 Hi all,
Metro Germany has issues with our MC3090 and their .NET application when using SD Cards. The app ends sometimes with a fatal application error. They did a lot of tests, did contact Microsoft, but now they need the Microsoft Windows CE Error Reporting on our MC3090. Microsoft states: Its not possible to install the Error reporting per CAB file. It needs to be implemented in the Platform Builder to add it to the kernel. Also OEM Adaption Layer (OAL) is some code needed to initialise and specify how much memory should be reserved for the dump etc. My question. Is there something we advice for them to have an error dump from their application? Do we know any tool we could recommend to accomplish that? Thanks a lot for your help! Best Regards,
5 Replies
Just to clarify a couple of items: - Application support and diagnostics is generally not enough to get an ECSG involved or even Motorola involved but this is more of a guideline in practice. - This could be an ECSG effort but would need to go through the enagement process. This process has a potential of the request being rejected but we will try to help if we can. - We do have diagnostics for CE but most if not all of our current CE products do not support DR.Watson or retail message logging. This means the tools w do have may be limited to the system level and not provide much help to the application developer. - WIth that said, we can customize an OS to support more comprehensive debugging but this would need to be a one and not used beyond diagnostics. Simple fact is that it will not be supported. - Outside of enaging ECSG, you may also want to consider opening a GRIP to get these extra debug features into CE so it can be supported. You can also try the normal support route but the application needs to be minimal and point to an API somewhere. Hope this helps, Gene
Thanks Gene, this is the kind of info we needed.
What I understand is Error reporting is disabled in release images for our CE based devices. Build environment changes will have to be done in the Platform’s Kernel sources to accommodate memory for the kdumps generated also changes to SYSGEN components is required to arrive at the customized image which can be used for Diagnostics ONLY. Regards, Mahesh
Mahesh, thanks for your clarification. Anyway we still need a clue about how can we help this customer. They want to troubleshoot their application by themselves to see why it crashes in our terminals and we don't include the error reporting in our images. Could this be a candidate for a ECSG work? Also, I have find the CaptureDump tool on the ECRT compass site and have seen that it supports some CE terminals but not MC3090. Can this tool be useful somehow for the customer? Thanks for help! Best Regards,
Samuel/Milan, ECSG welcomes you to submit the opportunity for engagement. Click on the the ECSG-Enagement Form link from the ECSG compass home page ( http://compass.mot.com/go/ECSG-Home) and submit the completed form. Once the form has been submitted send and email to ECSGTeam@motorola.com. As Mahesh reported, enabling Dr. Watson/kdump reports in CE builds requires a custom image. Once ECSG is engaged we can determine if this is an appropriate step and proceed accordingly.