Embedded module TQMLS10xxA - YOCTO Linux BSP documentation

All binaries are intended for the usage on a STKLS10xxA
The symlinks point to the files of the last build

Target Machine: tqmls43a-mbls10xxa

System Image

Boot device	Symlink	File
SD Card/eMMC	tq-image-generic-tqmls1043a-mbls10xxa.wic	tq-image-generic-tqmls1043a-mbls10xxa-<build_timestamp>.rootfs.wic

Bootstream (Bootloader) Binary

Boot Device	Symlink	File
SD Card/eMMC	u-boot.bin	u-boot-esdhc-2018.07-r0.bin

Linux Kernel Binary

Symlink	File
Image	Image--5.4-r0-tqmls1043a-mbls10xxa-<build_timestamp>.bin

Devicetree Binarys

Symlink	Description
fsl-tqmls1043a-mbls10xxa.dtb	default device tree blob for TQMLS1043a on MBLS10xxA

RootFS Images

Symlink	File
tq-image-generic-tqmls1043a-mbls10xxa.ext4	tq-image-generic-tqmls1043a-mbls10xxa-<build_timestamp>.rootfs.ext4
tq-image-generic-tqmls1043a-mbls10xxa.tar.gz	tq-image-generic-tqmls1043a-mbls10xxa-<build_timestamp>.rootfs.tar.gz

Target Machine: tqmls1046a-mbls10xxa

Complete system image

Boot Device	Symlink	File
SD Card/eMMC	tq-image-generic-tqmls1046a-mbls10xxa.wic	tq-image-generic-tqmls1046a-mbls10xxa-<build_timestamp>.rootfs.wic

Bootstream (Bootloader) Binary

Boot Device	Symlink	File
SD Card/eMMC	u-boot.bin	u-boot-esdhc-2018.07-r0.bin

Linux Kernel Binary

Symlink	File
Image	Image--5.4-r0-tqmls1046a-mbls10xxa-<build_timestamp>.bin

Devicetree Binarys

Symlink	Description
fsl-tqmls1046a-mbls10xxa.dtb	default device tree blob for TQMLS1046A on MBLS10xxA

RootFS Images

Symlink	File
tq-image-generic-tqmls1046a-mbls10xxa.ext4	tq-image-generic-tqmls1046a-mbls10xxa-<build_timestamp>.rootfs.ext4
tq-image-generic-tqmls1046a-mbls10xxa.tar.gz	tq-image-generic-tqmls1046a-mbls10xxa-<build_timestamp>.rootfs.tar.gz

Target Machine: tqmls1088a-mbls10xxa

Complete system image

Boot Device	Symlink	File
SD Card/eMMC	tq-image-generic-tqmls1088a-mbls10xxa.wic	tq-image-generic-tqmls1088a-mbls10xxa-<build_timestamp>.rootfs.wic

Bootstream (Bootloader) Binary

Boot Device	Symlink	File
SD Card/eMMC	u-boot.bin	u-boot-esdhc-2018.07-r0.bin

Linux Kernel Binary

Symlink	File
Image	Image--5.4-r0-tqmls1088a-mbls10xxa-<build_timestamp>.bin

Devicetree Binarys

Symlink	Description
fsl-tqmls1088a-mbls10xxa.dtb	default device tree blob for TQMLS1088A on MBLS10xxA

RootFS Images

Symlink	File
tq-image-generic-tqmls1088a-mbls10xxa.ext4	tq-image-generic-tqmls1088a-mbls10xxa-<build_timestamp>.rootfs.ext4
tq-image-generic-tqmls1088a-mbls10xxa.tar.gz	tq-image-generic-tqmls1088a-mbls10xxa-<build_timestamp>.rootfs.tar.gz

SD / eMMC partitioning TQMLS1043A

Sector¹⁾	Size²⁾	Contents	Linux (SD-Card)	Linux (eMMC)	Mountpoint
`0x000000 … 0x000000`	`0x0001` sector / 512 B	MBR / Partition Table	unpartitioned area		n/a
`0x000001 … 0x000007`	`0x0007` sector / 3584 B	none
`0x000008 … 0x001800`	`0x17F8` sector / 3068 kiB	U-Boot
`0x001801 … 0x004800`	`0x3000` sector / 6 MiB	U-Boot environment
`0x004801 … 0x008000`	`0x3800` sector / 7 MiB	fman-ucode
`0x008001 … 0x018000`	`0x10000` sector / 32 MiB	firmware (Kernel, devicetrees)	mmcblk1p1	mmcblk0p1	/boot
`0x018001 …`	actual size depends on contents of RootFS	rootFS	mmcblk1p2	mmcblk0p2	/

SD / eMMC partitioning TQMLS1046A

Sector³⁾	Size⁴⁾	Contents	Linux (SD-Card)	Linux (eMMC)	Mountpoint
`0x000000 … 0x000000`	`0x0001` sector / 512 B	MBR / Partition Table	unpartitioned area		n/a
`0x000001 … 0x000007`	`0x0007` sector / 3584 B	none
`0x000008 … 0x001800`	`0x17F8` sector / 3068 kiB	U-Boot
`0x001801 … 0x004800`	`0x3000` sector / 6 MiB	U-Boot environment
`0x004801 … 0x008000`	`0x3800` sector / 7 MiB	fman-ucode
`0x008001 … 0x018000`	`0x10000` sector / 32 MiB	firmware (Kernel, devicetrees)	mmcblk1p1	mmcblk0p1	/boot
`0x018001 …`	actual size depends on contents of RootFS	rootFS	mmcblk1p2	mmcblk0p2	/

SD / eMMC partitioning TQMLS1088A

Sector⁵⁾	Size⁶⁾	Contents	Linux (SD-Card)	Linux (eMMC)	Mountpoint
`0x000000 … 0x000000`	`0x0001` sector / 512 B	MBR / Partition Table	unpartitioned area		n/a
`0x000001 … 0x000007`	`0x0007` sector / 3584 B	none
`0x000008 … 0x000800`	`0x07F8` sector / 1020 kiB	rcw-pbi
`0x000801 … 0x001800`	`0x0100` sector / 2 MiB	U-Boot
`0x001801 … 0x005000`	`0x3800` sector / 7 MiB	U-Boot environment
`0x005001 … 0x006800`	`0x1800` sector / 3 MiB	mc-app
`0x006801 … 0x007000`	`0x0800` sector / 1 MiB	mc-dp1
`0x007001 … 0x008000`	`0x0100` sector / 2 MiB	mc-dpc
`0x008001 … 0x018000`	`0x1000` sector / 32 MiB	firmware (Kernel, devicetrees)	mmcblk1p1	mmcblk0p1	/boot
`0x018001 …`	actual size depends on contents of RootFS	rootFS	mmcblk1p2	mmcblk0p2	/

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=tq-image-generic-tqmls10xxa-mbls10xxa-<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

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.

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
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>

Device assignment:
mmcdev 0 = eMMC
mmcdev 1 = SD Card

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

For U-Boot update: ⇒ setenv uboot <filename>
e.g. u-boot-esdhc-2018.07-r0.bin
For devicetree update: ⇒ setenv fdt_file <filename>
e.g. fsl-tqmls1046a-mbls10xxa.dtb
For Linux kernel update: ⇒ setenv image <filename>
e.g. Image

6. Perform Update by running the update command:

U-Boot update:
```
=> run update_uboot_mmc
```
Device Tree update:
```
=> run update_fdt_mmc
```
Kernel update:
```
=> run update_kernel_mmc
```

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

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

Prerequisites

To boot the TQMLS10xxA from network you need a working bootloader in eMMC/SD-card or SPI-NOR (placement option on TQMLS10xxA ) 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:

Set network settings manually

Set network settings using DHCP

2. set the Uboot variables for TFTP and NFS:

setenv rootpath <rootpath> (NFS directory has to set in /etc/exports on the Computer that runs the NFS server first)
setenv fdt_file <fdt_file> (name of devicetree file to be downloaded from the tftp server)
setenv image <image> (name of the Linux kernel image to be downloaded from the tftp server)

3. Run the uboot script to boot from nfs:

uboot command to start netboot

=> run netboot

¹⁾ , ²⁾ , ³⁾ , ⁴⁾ , ⁵⁾ , ⁶⁾

sector size = 512 B

===== Updating existing firmw are over ethernet new

A good approach to update the firmare components U-Boot,Linux kernel and devicetree in a running system is to load them from a TFTP server. Therefore a running TFTP server is required in your network environment, please see thehow to setup TFTP Server page how to setup on your development host. After setting up the TFTP server, the binaries that should be updated must be copied into the TFTP directory of your TFTP Server.

1. Setup the Starterkit to boot from SD/eMMC or QSPI, please see the Starterkit dip switch page how to setup
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
=>

4. Setup the ethernet interface:

Set network settings manually

Provide the correct network configuration in U-Boot:

=> setenv autoload no
=> setenv serverip <serverip>  (IP address of your TFTP server e.g.: setenv serverip 192.168.100.110) 
=> setenv ipaddr <ipaddr>      (e.g.: setenv ipaddr 192.168.100.111)
=> setenv netmask <netmask>    (e.g.: setenv netmask 255.255.255.0)

Set network settings using DHCP

If a DHCP server is available in the network, the interface can be configured by the server:

=> setenv autoload no
=> setenv serverip <serverip>   (IP address of your TFTP server e.g.: setenv serverip 192.168.100.110)
=> dhcp (get IP from server)

5. Set U-Boot environment variables according to the image file name stored on the tftp server:

eMMc/SD Card

For U-Boot update on eMMC/SD Card :

=> setenv uboot_mmc <filename> (e.g.: setenv uboot_mmc u-boot-with-spl-pbl.bin)

QSPI NOR

For U-Boot update on QSPI NOR :

=> setenv uboot_qspi <filename> (e.g.: setenv uboot_spi_file fip_uboot.bin)

Devicetree

For Device Tree update on eMMC/SD Card and QSPI NOR :

=> setenv fdt_file <filename> (e.g.: setenv fdt_file fsl-tqmls1043a-mbls10xxa.dtb)

Kernel

For Kernel update on eMMC/SD Card and QSPI NOR

:

=> setenv kernel <filename> (e.g.: setenv kernel Image.gz)

Frame Manager

For Frame Manager Microcode on eMMC/SD Card and QSPI NOR :

=> setenv fmucode <filename> (e.g.: setenv fmucode  fsl_fman_ucode_ls1043_r1.1_106_4_18.bin)

6. Perform Update:

U-Boot

eMMC /SD Card :   => run update_uboot_mmc
QSPI NOR :        => run update_uboot_qspi

Devicetree

eMMC /SD Card :   => run update_fdt_mmc
QSPI NOR :        => run update_fdt_qspi

Kernel

eMMC /SD Card :   => run update_kernel_mmc
QSPI NOR :        => run update_kernel_qspi

Frame Manager

eMMC /SD Card :   => run update_fmucode_mmc
QSPI NOR :        => run update_fmucode_qspi

Embedded module TQMLS10xxA - YOCTO Linux BSP documentation

Deployment Yocto

BSP Binaries

Target Machine: tqmls43a-mbls10xxa

Target Machine: tqmls1046a-mbls10xxa

Target Machine: tqmls1088a-mbls10xxa

Yocto Partitions

SD / eMMC partitioning TQMLS1043A

SD / eMMC partitioning TQMLS1046A

SD / eMMC partitioning TQMLS1088A

Create SD Card with BSP Image

Updating existing firmware over ethernet

Update Process

Copy Firmware from SD card to eMMC using U-Boot

Using NFS boot

Prerequisites

Configuration of U-Boot Environment

uboot command to start netboot

Update Process