none
How to debug WinCE OS crash problem during initialization RRS feed

  • Question

  • Hello,

    I have a single board computer designed after the OMAPEVM, using the OMAP3530 and similar Flash as well as SDRAM. Copying files MLO, ebootsd.nb0, and nk.bin from the EVM project onto a SD card, I am able to boot our custom board. However, after eboot copies the OS image to SDRAM and jumps to the image launch address, the code crashes somewhere before OEMInit() is getting called and I no longer see debug messages coming out on the COM3 debug terminal. Using the same SD card on the EVM, it can go all the way to show the window screen.
    I added some code in the bootloader before the jump to the OS to dump out the first 1024 long words, starting at the launch address. The dumped data are the same between the EVM and our custom board. I also added code in the Eboot to test the SDRAM for the entire space except the Eboot portion. The test passes.

    Does anyone have any suggestions for me on how to debug this kind of problem?  Is there anyway to add code to send debug message to UART terminal before OEMInit() is called?

    I appreciate your help very much.

    Luan

    Monday, July 19, 2010 9:40 PM

Answers

  • Are you sure you've modified the config.bib to match any differences
    between your custom board and the EVM? Do you have JTAG? Are you sure
    you are dumping data from the correct address? In other words: does the
    data you are dumping match what is in the NK.BIN at the launch address?
    You can also try to set your SDRAM slower. Different board layouts can
    have an effect on the highest speed you can drive your SDRAM.
     

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.
    • Marked as answer by LuanLe Thursday, August 5, 2010 4:38 PM
    Monday, July 19, 2010 11:45 PM
    Moderator

All replies

  • Are you sure you've modified the config.bib to match any differences
    between your custom board and the EVM? Do you have JTAG? Are you sure
    you are dumping data from the correct address? In other words: does the
    data you are dumping match what is in the NK.BIN at the launch address?
    You can also try to set your SDRAM slower. Different board layouts can
    have an effect on the highest speed you can drive your SDRAM.
     

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.
    • Marked as answer by LuanLe Thursday, August 5, 2010 4:38 PM
    Monday, July 19, 2010 11:45 PM
    Moderator
  • You can read this article about Windows CE 6 startup sequence (there are also articles for older CE versions). You can add debug messages in the assembly file (startup.s). It should not be too difficult since the UART controller is started and prints debug info in Eboot (correct?).

     

    Shai

    Tuesday, July 20, 2010 4:47 AM