Kontron COMe-cP2020 - Manual (Page 98)

www.kontron.com
COMe-P2020 User Guide
98
For a one-time-only bootup, this can be accomplished with the “run” command, for example:
To make this permanent and have the board execute it automatically, it must be stored in the “bootcmd” environment vari-
able and the environment must be saved to flash.
Example:
6.5.9.2 Booting VxWorks
To boot a Wind River VxWorks image, a boot image file of the corresponding (ROM-able) VxWorks binary image and an FDT
(Flattened Device Tree) must be loaded to memory.
By default U-Boot operates on “uImage” files (boot image for U-Boot) which contain a special header and in the data por-
tion the operating system binary image. The special header defines various properties of the “uImage” file (e.g. load
address and entry point for the binary image in the data portion). Both the header and the data portion of the “uImage”
file are secured and checked against corruption by a CRC32 checksum at U-Boot load time.
All VxWorks (ROM-able) binary images will be converted to a “uImage” file at build time of the suited Wind River Workbench
projects based on the dedicated Kontron VxWorks BSP (Board Support Package). This conversion will be carried out by the
“mkImage” Kontron tool, which is automatically invoked by Wind River Workbench.
On successful build of the VxWorks binary (ROM-able) image, an additional “uImage” file containing the VxWorks (ROM-
able) binary image will be generated in the project default build folder with the following naming conventions:
Please note that the resulting “uImage” file contains all needed information for a proper U-Boot load process and start of
the contained VxWorks binary (ROM-able) image. Therefore, it is strongly recommended to utilize the corresponding “uIm-
age” file listed above when using U-Boot for booting VxWorks.
The “uImage” file and FDT are typically stored in and loaded from the SPI flash for OS.
The boot itself is initiated with the “bootm” command. To perform autobooting of a VxWorks image requires that appropri-
ate U-Boot environment variables or script(s) be defined for the boot operation to be performed. For more detailed infor-
mation with examples of boot command sequences, refer to the Kontron VxWorks BSP online documentation.
For more information on how to configure and build VxWorks images and how to utilize them e.g. for a subsequent VxWorks
boot process, please refer to the appropriate Wind River documentation.
=> run nfsboot
=>
=> setenv bootcmd 'run nandboot'
=> saveenv
=>
Table 6-9: Naming Conventions
U-BOOT “uImage” NAME VXWORKS IMAGE NAME
uImage.bootrom.bin bootrom.bin
uImage.vxWorks_rom.bin vxWorks_rom.bin
uImage.vxWorks_romCompress.bin vxWorks_romCompress.bin