LXE HX2 E-EQ-HX2RG-B Benutzerhandbuch
Installed Software
79
E-EQ-HX2RG-B
HX2 Reference Guide
Software Backup
Application programs and data that are normally RAM resident are backed up via ActiveSync, as
well as being stored on the internal SD card. The operating system is on internal SD card and does
not need backup. Registry configuration is backed up to internal SD card automatically using the
hive registry setup from CE 5.0. Registry backup occurs on every Suspend, WARMBOOT.EXE,
every 20 minutes and every 10 registry changes.
well as being stored on the internal SD card. The operating system is on internal SD card and does
not need backup. Registry configuration is backed up to internal SD card automatically using the
hive registry setup from CE 5.0. Registry backup occurs on every Suspend, WARMBOOT.EXE,
every 20 minutes and every 10 registry changes.
Version Control
Version numbers are applied to the boot loader and the OS image independently. The version
information stored consists of the LXE build number, plus the date and time of compile (in lieu of
a build number). These version numbers are stored in non-volatile storage, where the user cannot
inadvertently modify them. A control panel and API is provided so the user can reference the
version numbers for support purposes.
information stored consists of the LXE build number, plus the date and time of compile (in lieu of
a build number). These version numbers are stored in non-volatile storage, where the user cannot
inadvertently modify them. A control panel and API is provided so the user can reference the
version numbers for support purposes.
The HX2 has a unique 128-bit ID code as required by the CE 5.0 specification. This ID number is
generated by the boot loader. This ID code is available in the control panel, and via a Win32
standard API.
generated by the boot loader. This ID code is available in the control panel, and via a Win32
standard API.
In addition, an API is provided to return a standard LXE copyright string, so that applications may
reference this to be sure they are running on an LXE mobile device for licensing purposes.
reference this to be sure they are running on an LXE mobile device for licensing purposes.
See Accessories for the LXE HX2 SDK Kit part number.
Boot Loader
The HX2 supports a proprietary boot loader. It is the responsibility of the boot loader to:
• Initialize all system hardware
• Load code into internal FPGA device(s)
• Load the OS image from SD card to DRAM
• Initiate OS startup
• Handle wakeup from system suspend, loading saved state
• Handle copying a new boot loader from SD card to internal flash
• Load code into internal FPGA device(s)
• Load the OS image from SD card to DRAM
• Initiate OS startup
• Handle wakeup from system suspend, loading saved state
• Handle copying a new boot loader from SD card to internal flash
The HX2 reloads the OS every time during warm boot or cold boot. In Warm Boot (i.e., the user
executes a Warm Boot) the OS and the CAB files are reloaded from the internal SD card and the
preserved registry is also reloaded. Anything else (user data), which was not preserved in the
registry, is lost. During Cold Boot (i.e., user executes a Cold Boot utility) the system behavior is
identical to Warm Boot with the addition that the registry is reloaded with factory defaults.
executes a Warm Boot) the OS and the CAB files are reloaded from the internal SD card and the
preserved registry is also reloaded. Anything else (user data), which was not preserved in the
registry, is lost. During Cold Boot (i.e., user executes a Cold Boot utility) the system behavior is
identical to Warm Boot with the addition that the registry is reloaded with factory defaults.
The SD card holds user applications and CAB files. The SD card is mapped to the System folder
in the Windows CE file system.
in the Windows CE file system.