After the ""TinyKern"" image boot finishes, from the Target menu, select Target Control. The Windows CE Command Prompt window will appear. Type “gi proc” at the command prompt. This command will display all current running process on the device. If ""‘nk.exe’"" and ""‘Shell.exe’"" show up in the command window, it means the image is running in the device. You can also select Break All from Debug menu, the image should enter debug break mode. If the Break All command is not enabled in your PB, type 's loaddbg' in the command prompt window to load the debugger. Try to set a break point and step over your code. Note: when you set the break point, make sure the break point is not in ISR or somewhere that could break the kitl.

To make sure the new ""TinyKern"" image is indeed working and stable, the BSP has to pass several CETK OAL tests. Those tests are OAL Cache Tests, OAL Interrupt Tests, OAL Ioctl Tests, OAL Kitl Tests, and OAL Timer Tests. Other CETK tests are not needed for ""TinyKern"" image, since ""TinyKern"" image doesn’t support other drivers. For more information on how to run CETK tests, see MSDN document Windows Embedded CE Test Kit

After OAL tests passed, you can use the Windows Embedded CE Stress tool to verify this ""TinyKern"" image is stable after prolonged use. The CE Stress test can help you identify whether a functional unit leaks memory, crashes, hangs, or fails to function after extended continuous operation. In addition, the CE Stress test verifies that functional units of a run-time image interact appropriately with one another in arbitrary combinations. For more information, see Running Stress, and MSDN document Windows Embedded CE Stress Tool

---

Go up to BSP Bringup
Go up to Big Book of BSP

Thank you for contributing to this BSP Wiki. To ensure your comments and concerns receive proper exposure, include bspwiki""@""microsoft"".""com when providing feedback or topical suggestions.

---