...
For Trizeps IV & Trizeps V, Keith & Koep Seco delivers a sample eboot in the Board Support Packages (Microsoft) (.\src\bootloader\eboot) for customers who would like to use it for training purposes.
It is booted from the Keith & Koep Seco bootloader.
This article describes how to use eboot with Trizeps4 and Windows Embedded CE6. If you have a BSP prior to 2009Q1, you should take a look at the Patches & Workaround for Board-Support-Packages (RNDIS-KITL support). Other implementations of eboot work similarly (i.e. for Windows CE5 or Trizeps5).
Trizeps VI got an eboot-command built in.
...
After you have done a build of your Windows Embedded CE6 Image, a file named eboot.nb0 should be in your _FLATRELEASEDIR. If you have done some changes to the eboot-source and only want to rebuild it:
...
Too big images (typical debug images) might not load correctly, because too less RAM is left for the operating system. See How to Debug a Windows Embedded CE 6 Image for a workaround. Alternativly you may use a 128MB-RAM Trizeps-module.
...
After you have done a build of your Windows Embedded CE6 Image, a file named eboot.nb0 should be in your _FLATRELEASEDIR. If you have done some changes to the eboot-source and only want to rebuild it:
...
Changing Image Start-Offset
Unlike the Keith & Koep Seco Bootloader, the eboot sample does not support dynamic loading of the Windows Embedded CE 6 image to the end of RAM.
The RAM between RAM-adress 0 and image start-offset is used as free RAM by the operating system. The Start-Offset can be adjusted by changing the value of EXECUTABLE_PHYSICAL.
( see mt6_io.inc in .\tr4conxs\src\inc):
...
Note that the RAM-base is 0xa0000000. The default is 32MB (0x02000000). This leaves 32MB for the Windows Embedded CE image on a 64MB-module and 32MB of RAM for the operating system. Note that system may fail to boot if the offset is too big or too small. Use the method described in How to Debug a Windows Embedded CE 6 Image to reduce size of a debug image. Alternativly you may use a 128MB-RAM Trizeps-module.
...
In the Target Device Connectivity Options-dialog, verify that Use device name from bootloader is checked in the Transport Settings.