Debug call stack error RRS feed

  • Question

  • Hi,

    Problem: We are using eMMC for implementing Hive and File Persistence. On reference platform first time we are seeing the FormatDisk!FormatVolume: New FAT #1 successfully written and FormatDisk!FormatVolume: New BPB successfully written messages are seen. When we reboot the system these messages are not seen. The files that are copied in first boot are seen in second boot. In the Hw that we have we are seeing the above bold text messages two time. That is for the first time OS boots and second time OS boots. From third time onward the messages are not seen and the files are seen whatever copied from second boot onward and not from first boot.

    To identify the issue when we keep a break point to find the root cause of the File Persistence Issue, the debug break point has been hit in Init function, at that instance when we see debug call stack we are seeing the below error.


     Please let me know if you had come across the same issue or how to debug the issue.

    Thanks for your time.



    Tuesday, December 11, 2012 6:42 AM