There are plenty of example sand how-to’s on how to build a Windows CE image, download and debug it on a target:

  • Sam’s Jumpstart Kit:
    • <CD>/Vortex86DX_SPARK_WINCE600_JumpStart_Rev2.5.pdf
    • <CD>/SampleCodes/OSDesign/MyWinCE_OSDesign_Project_VDX6326.zip
    • Where the CD is the “Solution of Fault Tolerance x86 System-on-chip” as supplied with the kit
       
  • MSDN Virtual Lab: Windows Embedded CE 6.0 Platform Builder Tools
     
  • Windows CE 6 Help (Local or at MSDN) Topics:
    • For a CEPC .. A PC as a CE device, but applies to the Spark Kit:
      • How to Set Up a CEPC
        • The major hardware issue is the network card.
        • It doesn’t need a hard drive
        • You need a boot floppy, or create a USB boot floppy(Search for HP disk key)
          • Or you can set up a  bootable hard drive formatted for DOS.
    • How to Configure and Build a Run-Time Image for a CEPC
    • How to Configure and Download a Run-Time Image to a CEPC
    • How to Debug a Run-Time Image on a CEPC

Some key points:

  • Configure the system as Retail but with Kitl
    • Smaller Image
    • Quicker load
    • Kitl enables debugging of custom applications and drivers etc.
    • You need access to source code for Debug mode
      • Use if having problem with a supplied driver
      • Eg, Set a breakpoint in a mouse driver
    • If you are using a binary BSP you won’t have source and can’t debug that though
      • Try this out with CEPC or Emulator
      • Need to install Shared Source
  • Set the image RAM to that available on the system
    • Normally environment variable IMAGRAM64, IMGRAM128 etc
    • The kit has BSP has some RAM catalog options for doing this
      • I set mine to 256M as is with my kit
  • Go through the Catalog searching for things that might be useful, and removing things not wanted
    • Use search to find things (eg search for Ping)

Cheers DJ