CONSIDERATIONS
You can configure Compact 7 devices designed with different processor architectures and hardware platforms to boot from different types of storage. Depending on the selected processor and the hardware’s overall design, you need to consider the best option to deploy the OS image based on the target device’s unique hardware architecture and application scenario.
ARM, MIPS, and x86 devices each have different implementations to boot and launch Compact 7 OS. This chapter talks about different options to deploy an OS run-time image to an x86 target device, using the eBox-3310A (eBox) as a target device.
The eBox is built with an x86 processor and designed to boot from the following sources:
- Network: Boot from the network using Preboot eXecution Environment (PXE).
- Removable storage: USB flash storage.
- Fixed storage: IDE hard disk.
- Fixed storage: IDE flash storage.
- Fixed storage: Compact Flash.
Network: PXE
PXE is one of the common methods in use to boot up and launch an OS run-time image from the network. When configured to boot from the network using PXE, a Compact 7 device acquires an IP address from a DHCP server and attaches to a TFTP server to download the OS run-time image to RAM and launch the image from RAM.
Booting from the network eliminates the need to have local storage, which can help lower the component cost for the device. For an application scenario such as an information kiosk, electronic billboard, and thin-client, booting from the network can help ...
Get Professional Windows® Embedded Compact 7 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
