Deployment Yocto

Deployment Yocto

BSP Binaries

All binaries are intended for the usage on a <label stk_name>STK_NAME</label>
The symlinks point to the files of the last build

Yocto Partitions

Create SD Card with BSP Image

The Image can be simply written to the SD Card by using the dd shell command in Linux:

$ cd <path to your image>
$ sudo dd if=<label bsp_image_name>BSP_IMAGE_NAME</label>-<build Timestamp>.rootfs.wic of=/dev/sdc bs=1M conv=fsync #Assuming the SD card is assigned to /dev/sdc

The image must be written to the RAW device of the SD Card (e.g. /dev/sdc) and not into a partition (e.g. /dev/sdc1) !

To identify the SD card in Linux the shell command dmesg can be used:

Open a new terminal
Execute the following command without plugged SD Card
```
 $ dmesg | tail -n 15
```
Insert SD Card and wait a few seconds
Run the command from step two again

$ dmesg | tail -n 15 
 #plug in SD Card into the reader
$ dmesg | tail -n 15

Updating existing firmware over ethernet

A good approach to update the firmare components U-Boot,Linux kernel and devicetree in a running system it to load them from a tftp server.
This process requires a running TFTP server, please see the following page how to setup TFTP Server. After setting up the TFTP server, the binaries to be updated must be copied into the TFTP directory.

Update Process

1. Setup the Starterkit to boot from eMMC or SD
2. Connect the kit to the network with TFTP server supplying the binaries via ethernet on connector ETH_PRIME
3. Power up the system and interrupt the boot process in U-Boot

Hit any key to stop autoboot:  0
=>

3. Setup the ethernet interface:

Set network settings manually

Set network settings using DHCP

4. Set U-Boot variable mmcdev according to the drive you want to write to.

=> setenv mmcdev <device_number>

5. Set the file name of the binary to update in U-Boot :

For U-Boot update: ⇒ setenv uboot <filename>
e.g. UBOOT_DEFAULT
For devicetree update: ⇒ setenv fdt_file <filename>
e.g. FDT_DEFAULT
For Linux kernel update: ⇒ setenv image <filename>
e.g. KERNEL_DEFAULT

6. Perform Update by running the update command:

U-Boot update:

=> run <label update_uboot_cmd>UPDATE_UBOOT_CMD</label>

Device Tree update:

=> run <label update_dtb_cmd>UPDATE_FDT_CMD</label>

Kernel update:

=> run <label update_kernel_cmd>UPDATE_KERNEL_CMD</label>

The variables can be saved with the command saveenv to keep the values permanently.

Copy Firmware from SD card to eMMC using U-Boot

Write Image to SD card (use dd command under Linux or Win32diskImager under Windows)

The image on the SD card must not be booted, otherwise the initial run once services have already been started.

Set Starterkit to boot from SD, please see DIP Switch Settings
Interrupt the boot process to get to the U-Boot prompt
Use the following commands to copy the SD card to eMMMC

The following commands are based on the default eMMC/SD image partitioning.

2. Save environment U-boot environment (optional):

=> saveenv

3. run the following command to start the update procedure:

=> run install_firmware

Using NFS boot

Prerequisites

To boot the <label mod_name>ModuleName</label> from network you need a working bootloader in eMMC/SD-card or SPI-NOR (placement option on <label mod_name>ModuleName</label> ) which is able to get the kernel image over tftp and to provide the kernel with commandline settings for NFS. The dtb-file and kernel image have to be provided via tftp and the rootfs via nfs.

Configuration of U-Boot Environment

The bootloader environment needs to be modified to work with your tftp-server and your nfs-server.

1. Prepare network interface: