System Images
Boot Device | Symlink | File |
---|---|---|
SD Card/eMMC | tq-image-weston-debug-tqma8mpxl-mba8mpxl.wic | tq-image-weston-debug-tqma8mpxl-mba8mpxl-<build_timestamp>.rootfs.wic |
Bootloader Binaries
Boot Device | File |
---|---|
SD/eMMC | imx-boot-tqma8mpxl-mba8mpxl-sd.bin-flash_spl_uboot |
QSPI NOR | imx-boot-tqma8mpxl-mba8mpxl-sd.bin-flash_evk_flexspi |
Linux Kernel Image
Symlink | File |
---|---|
Image | Image–5.10.109+git0+5357caa1bc-r0-tqma8mpxl-mba8mpxl-<build_timestamp>.bin |
Devicetree Blobs
Symlink | Description |
---|---|
imx8mp-tqma8mpql-mba8mpxl.dtb | Default |
imx8mp-tqma8mpql-mba8mpxl-hdmi.dtb | Default with HDMI interface activated |
imx8mp-tqma8mpql-mba8mpxl-lvds-tm070jvhg33.dtb | Default with LVDS interface activated |
imx8mp-tqma8mpql-mba8mpxl-hdmi-ov9281.dtb | Default with CSI monocrome Camera and HDMI activated |
imx8mp-tqma8mpql-mba8mpxl-hdmi-imx327.dtb | Default with CSI color Camera and HDMI activated |
imx8mp-tqma8mpql-mba8mpxl-rpmsg.dtb | Default with RPMSG support |
Rootfs images
Symlink | File |
---|---|
tq-image-weston-debug-tqma8mpxl-mba8mpxl.ext4 | tq-image-weston-debug-tqma8mpxl-mba8mpxl-<build_timestamp>.rootfs.ext4 |
tq-image-weston-debug-tqma8mpxl-mba8mpxl.tar.gz | tq-image-weston-debug-tqma8mpxl-mba8mpxl-<build_timestamp>.rootfs.tar.gz |
Sector 1) | Size 2) | Contents | Linux (SD-Card) | Linux (eMMC) | Mountpoint |
---|---|---|---|---|---|
0x000000 … 0x000000 | 0x0001 sector / 512 B | MBR / Partition Table | unpartitioned area | n/a | |
0x000001 … 0x00003F | 0x003F sectors / 32256 B | none | |||
0x000040 … 0x001FFF | 0x1FC0 sectors / 4064 kiB | bootstream (U-Boot) | |||
0x002000 … 0x003FFF | 0x2000 sectors / 4 MiB | U-Boot environment | |||
0x004000 … 0x023FFF | 0x20000 sectors / 64 MiB | firmware (Kernel, devicetrees) | mmcblk1p1 | mmcblk0p1 | /boot |
0x024000 … | 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-weston-tqma8mpxl-2gb-mba8mpxl-<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:
$ dmesg | tail -n 15
$ 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 ETH1 (X18)
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 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 :
6. Perform Update by running the update command:
=> run update_uboot_mmc
=> run update_fdt_mmc
=> run update_kernel_mmc
1. Run the following commands in the Uboot shell to create update script:
setenv root_loop 'setenv start 24000 && setenv r1 $rootblks16 && while itest $r1 -gt 0; do if itest $r1 -gt 0x100000; then setenv count 0x100000; else setenv count $r1; fi && mmc dev 1 && mmc read $loadaddr $start $count && mmc dev 0 && mmc write $loadaddr $start $count && setexpr start $start + $count && setexpr r1 $r1 - $count; done; setenv r1; setenv start; setenv count'
setenv install_firmware 'echo MBR... && mmc dev 1 && mmc read $loadaddr 0 1 && mmc dev 0 && mmc write $loadaddr 0 1 && echo U-Boot... && mmc dev 1 && mmc read $loadaddr 40 1FC0 && mmc dev 0 && mmc write $loadaddr 40 1FC0 && echo U-Boot environment... && mmc dev 1 && mmc read $loadaddr 2000 2000 && mmc dev 0 && mmc write $loadaddr 2000 2000 && echo Firmware Partition... && mmc dev 1 && mmc read $loadaddr 4000 20000 && mmc dev 0 && mmc write $loadaddr 4000 20000 && echo Root FS... && run root_loop'
To calculate the value of rootblks16 devide the size of the image in byte by 512 and convert the result into a hex value.
627 * 1024 * 1024 = 657457152
657457152 / 512 = 1284096
1284096 = 139800HEX
setenv rootblks16 0x139800
2. Save environment U-boot environment (optional):
=> saveenv
3. run the following command to start the update procedure:
=> run install_firmware
To boot the TQMa8MPxL from network you need a working bootloader in eMMC/SD-card or SPI-NOR (placement option on TQMa8MPxL ) 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.
The bootloader environment needs to be modified to work with your tftp-server and your nfs-server.
1. Prepare network interface:
Set network settings using DHCP
2. set the Uboot variables for TFTP and NFS:
3. Run the uboot script to boot from nfs:
=> run netboot
The UUU (Universal Update Utility is an open source programm provided by NXP, it is the successor of NXP's MFG Tools, intended to download and execute code on i.MX SoC family via the Serial Download Protocol (SDP).
Documentation, source code and prebuild releases are available via the NXP mfgtools github repository.
1. Download the latest release from Universal Update Utility repository or build it from source
2. TQMa8MPxL BSP built following the BSP quickstart instructions.
A prebuild UUU release version can be downloaded from the UUU git repository.
The Universal Update Utility (UUU) tool can be compiled manually. The build instructions for Linux, Windows are available in the UUU documentation:
A U-Boot binary with the U-Boot configuration mfgtool is required to use the UUU. This particular U-Boot will be built during the TQMa8MPxL Yocto BSP build process and is located in the build directory deploy folder named imx-boot-tqma8mpxl-mba8mpxl-mfgtool.bin-flash_spl_uboot.
For the sake of siplicity, copy the following components to a new folder e.g. in your home directory:
The following commands are executed in the folder containing the tool and the binaries.
After connecting the kit, it should be automatically detected when it is in serial downloader mode. Run the following command to list all detected devices:
uuu -lsusb
To load the U-boot binary into the RAM and start it from there use the command below:
uuu <u-boot binary>
Example for the STKa8MPxL:
uuu imx-boot-tqma8mpxl-mba8mpxl-mfgtool.bin-flash_spl_uboot
Use the following command to program a U-Boot binary into the eMMC.
uuu -b emmc <u-boot binary>
Example for the STKa8MPxL:
uuu -b emmc imx-boot-tqma8mpxl-mba8mpxl-mfgtool.bin-flash_spl_uboot
Follow the command below to load the mfgtool U-Boot and write an image onto the TQMa8MPxL eMMC afterwards.
uuu -b emmc_all <u-boot binary> <wic-image>
Example for the STKa8MPxL:
uuu -b emmc_all imx-boot-tqma8mpxl-mba8mpxl-mfgtool.bin-flash_spl_uboot.bin tq-image-weston-debug-tqma8mpxl-mba8mpxl.rootfs.wic
Use a custom workflow:
For a custom workflow uuu commands can be listed in a cmdlist file. The following example shows how to program a wic image to eMMC user area, without writing the bootstream to the eMMC boot partition.
Example cmdlist file on STKa8MPxL:
For the sake of simplicity, create the cmdlist file in the same location as the uuu executable. For example uuu.tqma8mpxl
uuu_version 1.5.4 SDPS: delay 500 SDPS: @ boot -f @BOOTSTREAM@ SDPS: delay 1000 FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: ucmd mmc dev ${emmc_dev} FB: @ flash -raw2sparse all @WICIMAGE@ FB: done
Example command for the STKa8MPxL using custom cmdlist:
uuu -e BOOTSTREAM=<bootstream for uuu> -e WICIMAGE=<wic image for eMMC> uuu.tqma8mpxl
uuu -e BOOTSTREAM=imx-boot-tqma8mpxl-mba8mpxl-mfgtool.bin-flash_spl_uboot -e WICIMAGE=tq-image-weston-debug-tqma8mpxl-mba8mpxl.rootfs.wic uuu.tqma8mpxl