Kontron COMe-bP5020 Manual de usuario Pagina 63

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 71
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 62
www.kontron.com
63
User Guide
COMe-bP5020
The VxWorks FDT binary blob is also provided with the Kontron VxWorks BSP. This binary blob is only a basic FDT framework. The
previously mentioned U-Boot fdt-commands are required to prepare and add module specific information to the FDT in RAM
which is later retrieved by the VxWorks ELF image from the FDT.
The most common way to load VxWorks ELF images and VxWorks FDT’s during development is by transferring them using TFTP
over the Ethernet interface. For a finalized application the VxWorks ELF image and VxWorks FDT blob are typically stored in and
loaded from the SPI flash for OS.
The boot itself is initiated with the "bootelf" command. To perform autobooting of a VxWorks image requires that appropriate
U-Boot environment variables or script(s) be defined for the boot operation to be performed. For more detailed information
with examples to boot command sequences, please refer to the Kontron VxWorks BSP online documentation
For more information on how to setup, configure and build VxWorks images and how to utilize them e.g. for a subsequent Vx-
Works boot process, please refer to the appropriate Wind River VxWorks documentation.
6.6 Getting Help
U-Boot was configured with support for longhelp. This means that online help is available for every command while working
with the system. To access the online help, enter “?” or “help” at the console prompt. This will show an overview over all avail-
able commands. To get specific help, enter “? <command/command group” or “help <command/command group”.
For example to get help on the “saves” command enter “? saves”.
To get help on the mmc command group enter “? mmc”.
6.7 Update
The environment contains two scripts which allow an update of various components, e.g. U-Boot, bootrom for VxWorks, data
in EEPROMs, etc.
The script “update” checks for a U-Boot script “update” in the directory “update_d0c81” in the first partition of the SD card
with “ext2” or “fat” filesystem. If unsuccessful, the check continues with the first NAND chip, volume “boot”, and again U-Boot
searches in the subdirectory “update_d0c81” for the script “update”. If the script “update” is found, it is loaded to memory
and executed.
So, to actually execute an update, e.g. an SD card should be prepared with a directory “update_d0c81” on the first partition.
Kontron provides an update e.g. for U-Boot as a compressed archive (zip, tar.bz2, tar.gz) which must be unpacked in the di-
rectory “update”.
=> ? saves
saves - save S-Record file over serial line
Usage:
saves [ off ] [size] [ baud ]
- save S-Record file over serial line with offset 'off', size 'size' and
baudrate 'baud'
=>
=> ? mmc
mmc - MMC sub system
Usage:
mmc read <device num> addr blk# cnt
mmc write <device num> addr blk# cnt
mmc rescan <device num>
mmc part <device num> - lists available partition on mmc
mmc list - lists available devices
=>
Vista de pagina 62
1 2 ... 58 59 60 61 62 63 64 65 66 67 68 69 70 71

Comentarios a estos manuales

Sin comentarios