Embedded module TQMLX2160A - YOCTO Linux BSP documentation


Deployment Yocto

  1. All binaries are intended for the usage on a STKLX2160A
  2. The symlinks point to the files of the last build

Target Machine: tqmlx2160a-mblx2160a

System Image

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

Bootstream (Bootloader) Binary

Boot Device Symlink File
SD Card/eMMC u-boot.bin u-boot-tfa-2019.04-r0.bin

Linux Kernel Binary

Symlink File
Image Image--5.4-r0-tqmlx2160a-mblx2160a-<build_timestamp>.bin

Devicetree Binarys

Symlink Description
fsl-lx2160a-mblx2160a.dtb default device tree blob for TQMLX2160A on MBLX2160A

RootFS Images

Symlink File
tq-image-generic-tqmlx2160a-mblx2160a.ext4 tq-image-generic-tqmlx2160a-mblx2160a-<build_timestamp>.rootfs.ext4
tq-image-generic-tqmlx2160a-mblx2160a.tar.gz tq-image-generic-tqmlx2160a-mblx2160a-<build_timestamp>.rootfs.tar.gz
tq-image-generic-tqmlx2160a-mblx2160a.ubi tq-image-generic-tqmlx2160a-mblx2160a-<build_timestamp>.rootfs.ubi
tq-image-generic-tqmlx2160a-mblx2160a.ubifs tq-image-generic-tqmlx2160a-mblx2160a-<build_timestamp>.rootfs.ubifs

SD / eMMC partitioning

Sector1) Size2) 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 0x1000 sector / 2 MiB U-Boot
0x001801 … 0x004000 0x2800 sector / 5 MiB U-Boot environment
0x004001 … 0x008000 0x4000 sector / 8 MiB ddr-fw
0x008001 … 0x018000 0x10000 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-tqmlx2160a-mblx2160a-<build Timestamp>.rootfs.wic of=/dev/sdc bs=1M conv=fsync #Assuming the SD card is assigned to /dev/sdc

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

  1. Open a new terminal
  2. Execute the following command without plugged SD Card
     $ dmesg | tail -n 15
  3. Insert SD Card and wait a few seconds
  4. 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 depends on SERDES configuration
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-tfa-2019.04-r0.bin
  • For devicetree update: ⇒ setenv fdt_file <filename>
    e.g. fsl-lx2160a-mblx2160a–5.4-r0-tqmlx2160a-mblx2160a-<build_timestamp>.dtb
  • For Linux kernel update: ⇒ setenv image <filename>
    e.g. Image–5.4-r0-tqmlx2160a-mblx2160a-<build_timestamp>.bin

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

1) , 2)
sector size = 512 B

Octal SPI NOR

Memory Range Usage
0x000000000000-0x000000100000 RCW-PBL
0x000000100000-0x000000300000 U-Boot
0x000000500000-0x000000600000 U-Boot-Env
0x000000800000-0x000000a00000 DDR-PHY
0x000000a00000-0x000000d00000 DPAA2-MC
0x000000d00000-0x000000e00000 DPAA2-DPL
0x000000e00000-0x000000f00000 DPAA2-DPC
0x000000f00000-0x000001000000 Linux-DTB
0x000001000000-0x000003000000 Kernel
0x000003000000-0x000008000000 RootFS UBI

SD Card

Size Uasage
0x0001 sectors 512 Byte MBR /Partition Table
0x0007 sectors 3584 Byte Free
0x1000 / RCW-PBL
U-Boot
DDR-PHY
Boot Partition
RootFS ext4
  • Last modified: 2022/08/04 15:02