Embedded module TQMaRZG2x - YOCTO Linux BSP documentation


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

Target Machine: tqmarzg2m_aa-mbarzg2x

System Image

Boot device Symlink File
SD Card/eMMC tq-image-weston-tqmarzg2m_aa-mbarzg2x.wic tq-image-weston-tqmarzg2m_aa-mbarzg2x-<build_timestamp>.rootfs.wic

Bootstream (Bootloader) Binary

Boot Device Symlink File
SD Card/eMMC u-boot-tqmarzg2m_aa-mbarzg2x.bin u-boot-tqmarzg2m_aa-mbarzg2x-2018.09-r0.bin

Linux Kernel Binary

Symlink File
Image Image–4.19.140+git0+8e6bd492a3-r1-tqmarzg2m_aa-mbarzg2x-<build_timestamp>.bin

Devicetree Binarys

Symlink Description
r8a774a1-tqmarzg2m_aa-mbarzg2x.dtb default device tree blob for TQMaRZG2m on MBaRZg2x
r8a774a1-tqmarzg2m_aa-mbarzg2x-lvds-tm070jvhg33.dtb device tree with activated LVDS0 channel and TM070JVHG33 display timing

RootFS Images

Symlink File
tq-image-weston-tqmarzg2m_aa-mbarzg2x.ext4 tq-image-weston-tqmarzg2m_aa-mbarzg2x-<build_timestamp>.rootfs.ext4
tq-image-weston-tqmarzg2m_aa-mbarzg2x.tar.gz tq-image-weston-tqmarzg2m_aa-mbarzg2x-<build_timestamp>.rootfs.tar.gz

Target Machine: tqmarzg2m_e-mbarzg2x

System Image

Boot device Symlink File
SD Card/eMMC tq-image-weston-tqmarzg2m_e-mbarzg2x.wic tq-image-weston-tqmarzg2m_e-mbarzg2x-<build_timestamp>.rootfs.wic

Bootstream (Bootloader) Binary

Boot Device Symlink File
SD Card/eMMC u-boot-tqmarzg2m_e-mbarzg2x.bin u-boot-tqmarzg2m_e-mbarzg2x-2018.09-r0.bin

Linux Kernel Binary

Symlink File
Image Image–4.19.140+git0+8e6bd492a3-r1-tqmarzg2m_e-mbarzg2x-<build_timestamp>.bin

Devicetree Binarys

Symlink Description
r8a774a1-tqmarzg2m_e-mbarzg2x.dtb default device tree blob for TQMaRZG2m on MBaRZg2x
r8a774a1-tqmarzg2m_e-mbarzg2x-lvds-tm070jvhg33.dtb device tree with activated LVDS0 channel and TM070JVHG33 display timing

RootFS Images

Symlink File
tq-image-weston-tqmarzg2m_e-mbarzg2x.ext4 tq-image-weston-tqmarzg2m_e-mbarzg2x-<build_timestamp>.rootfs.ext4
tq-image-weston-tqmarzg2m_e-mbarzg2x.tar.gz tq-image-weston-tqmarzg2m_e-mbarzg2x-<build_timestamp>.rootfs.tar.gz

Target Machine: tqmarzg2h_c-mbarzg2x

System Image

Boot device Symlink File
SD Card/eMMC tq-image-weston-tqmarzg2h_c-mbarzg2x.wic tq-image-weston-tqmarzg2h_c-mbarzg2x-<build_timestamp>.rootfs.wic

Bootstream (Bootloader) Binary

Boot Device Symlink File
SD Card/eMMC u-boot-tqmarzg2h_c-mbarzg2x.bin u-boot-tqmarzg2h_c-mbarzg2x-2018.09-r0.bin

Linux Kernel Binary

Symlink File
Image Image–4.19.140+git0+8e6bd492a3-r1-tqmarzg2h_c-mbarzg2x-<build_timestamp>.bin

Devicetree Binarys

Symlink Description
r8a774e1-tqmarzg2h_c-mbarzg2x.dtb default device tree blob for TQMaRZG2m on MBaRZg2x
r8a774e1-tqmarzg2h_c-mbarzg2x-lvds-tm070jvhg33.dtb device tree with activated LVDS0 channel and TM070JVHG33 display timing

RootFS Images

Symlink File
tq-image-weston-tqmarzg2h_c-mbarzg2x.ext4 tq-image-weston-tqmarzg2h_c-mbarzg2x-<build_timestamp>.rootfs.ext4
tq-image-weston-tqmarzg2h_c-mbarzg2x.tar.gz tq-image-weston-tqmarzg2h_c-mbarzg2x-<build_timestamp>.rootfs.tar.gz

Target Machine: tqmarzg2n_b-mbarzg2x

System Image

Boot device Symlink File
SD Card/eMMC tq-image-weston-tqmarzg2n_b-mbarzg2x.wic tq-image-weston-tqmarzg2n_b-mbarzg2x-<build_timestamp>.rootfs.wic

Bootstream (Bootloader) Binary

Boot Device Symlink File
SD Card/eMMC u-boot-tqmarzg2n_b-mbarzg2x.bin u-boot-tqmarzg2n_b-mbarzg2x-2018.09-r0.bin

Linux Kernel Binary

Symlink File
Image Image–4.19.140+git0+8e6bd492a3-r1-tqmarzg2n_b-mbarzg2x-<build_timestamp>.bin

Devicetree Binarys

Symlink Description
r8a774e1-tqmarzg2n_b-mbarzg2x.dtb default device tree blob for TQMaRZG2m on MBaRZg2x
r8a774e1-tqmarzg2n_b-mbarzg2x-lvds-tm070jvhg33.dtb device tree with activated LVDS0 channel and TM070JVHG33 display timing

RootFS Images

Symlink File
tq-image-weston-tqmarzg2n_b-mbarzg2x.ext4 tq-image-weston-tqmarzg2n_b-mbarzg2x-<build_timestamp>.rootfs.ext4
tq-image-weston-tqmarzg2n_b-mbarzg2x.tar.gz tq-image-weston-tqmarzg2n_b-mbarzg2x-<build_timestamp>.rootfs.tar.gz

SD / eMMC image

Sector 1) Size 2) Contents Linux (SD-Card) Linux (eMMC) Mountpoint
0x000000 … 0x002000 0x2000 sectors / 4 MiB MBR / Partition Table unpartitioned area n/a
0x002001 … 0x022000 0x20000 sectors / 64 MiB firmware (Kernel, devicetrees) mmcblk1p1 mmcblk0p1 /boot
0x022001 … actual size depends on contents of RootFS RootFS mmcblk1p2 mmcblk0p2 /

QSPI NOR

Memory Regions Sectors 3) Size Contents Linux
0x000000000000-0x000000040000 0x04 0x00040000 / 256KB bootparam mtdblock0
0x000000040000-0x000000180000 0x14 0x00140000 / 1280KB bl2 mtdblock1
0x000000180000-0x0000001c0000 0x02 0x00040000 / 128KB cert_header_sa6 mtdblock2
0x0000001c0000-0x000000200000 0x02 0x00040000 / 128KB bl31 mtdblock3
0x000000200000-0x000000300000 0x10 0x00100000 / 1024KB tee mtdblock4
0x000000300000-0x0000003f0000 0x0F 0x000F0000 / 960KB uboot mtdblock5
0x0000003f0000-0x000000400000 0x01 0x00010000 / 64KB uboot-env mtdblock6
0x000000400000-0x000001000000 0xC0 0x00C00000 / 12288KB user mtdblock7

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-weston-tqmarzg2n_b-mbarzg2x-<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 ETH0 (X26)
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>
U-Boot Device Assignment:

mmc dev 0 = SD Card
mmc dev 1 = eMMC

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

  • For U-Boot update: ⇒ setenv uboot <filename>
    e.g. uboot.bin
  • For devicetree update: ⇒ setenv fdt_file <filename>
    e.g. fr8a774b1-tqmarzg2n_b-mbarzg2x.dtb
  • For Linux kernel update: ⇒ setenv image <filename>
    e.g. Image

6. Perform Update by running the update command:

SD Card

  • U-Boot update:
    => run update_uboot_sd
  • Device Tree update:
    => run update_fdt_sd 
  • Kernel update:
    => run update_kernel_sd

eMMC

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

1) , 2)
sector size = 512 B
3)
sector size = 64KB
  • Last modified: 2022/08/04 15:02