Third-Party Add-Ons

MBa6ULX and TQMa6ULx

I2C bus TQMa6ULx
I2C4 0x08
PMIC
0x1A
Tempsensor
0x48
0x32
EEPROM (Protection Mode)
0x50
EEPROM
0x52
EEPROM
0x68
RTC
I2C bus MBa6ULx
I2C4 0x18
Audiocodec
0x19
Tempsensor
0x20
GPIO Expander
0x21
GPIO Expander
0x22
GPIO Expander
0x41
Touch Controller
0x51
EEPROM

U-Boot

Supported features
Buildsystem BSP Revision
PTXdist
Yocto
Feature BSP Revision Remarks
TQ Product Chip Interface Function 0100 0104 0106 0107 0110 0113 0115 0116 0117
TQMa6ULx i.MX6UL Ethernet RMII (10/100 Mbit/s)
TQMa6ULx i.MX6UL uSDHC eMMC / SD-Card SD card / eMMC
TQMa6ULx i.MX6UL UART1 RS232 default console
TQMa6ULx i.MX6UL I²C EEPROM
TQMa6ULx i.MX6UL SPI QSPI NOR Flash
TQMa6ULx i.MX6UL IIM / Fuse OTP Register

Supported boot devices

Boot device supported
eMMC / SD
TFTP boot
QSPI NOR

Linux

Supported Features
Buildsystem BSP Revision
PTXdist
Yocto
TQ Product Chip Interface Function 0100 0104 0106 0107 0110 0113 0115 0116 0117 Remarks
TQMa6ULx i.MX6UL ENET1 RMII
(10/100 Mbit/s)
i.MX6UL ENET2 RMII
(10/100 Mbit/s)
i.MX6UL FLEXCAN1 CAN 2.0B
i.MX6UL FLEXCAN2 CAN 2.0B
i.MX6UL GPIO 1x GPIO Supported via beep command
i.MX6UL GPMI Multiplexed with other functions
(on request), no device MBa6ULx
i.MX6UL I2C2 Not available by default / configuration resistor R451 and R455
i.MX6UL I2C4 I2C devices See supported onboard I2C devices
i.MX6UL JTAG Not tested
i.MX6UL eLCDIF Parallel LCD 24-bit interface available via X4
LVDS 24-bit available via X17
i.MX6UL MIPI CSI No device on MBa6ULx
i.MX6UL MIPI DSI No device on MBa6ULx
i.MX6UL MQS Multiplexed with other functions (on request)
i.MX6UL PWM4 Backlight Dimming
i.MX6UL QSPI Bus access
Memory access
i.MX6UL SAI1 Audiocodec
i.MX6UL TEMPMON Temperature read
i.MX6UL UART1 RS232/
USB Debug
Default console / USB debug connector selectable with S15 on MBA6ULx
i.MX6UL UART2 TTL Multiplexed with other functions (on request)
i.MX6UL UART3 TTL Not available on MBa6ULx
i.MX6UL UART4 TLL Multiplexed with other functions (on request)
i.MX6UL UART5 TLL Multiplexed with other functions (on request)
i.MX6UL UART6 RS485
i.MX6UL UART7 TLL Multiplexed with other functions (on request)
i.MX6UL UART8 TLL Multiplexed with other functions (on request)
i.MX6UL USB_Host USB2517
i.MX6UL USB_OTG1 Host
i.MX6UL USB_OTG1 OTG tested with usb serial gadget
i.MX6UL USB_OTG2 Host Only Host supported on MBa6ULx connected to USB2517 Hub [7:1]
i.MX6UL USB_OTG2 OTG
i.MX6UL uSDHC uSDHC1 SD Card
uSDHC2 eMMC
MBa6ULx TLV320AIC3204 Headphone Out/
Line Out
Line In
Microphone In On request
PCA9554BS I2C GPIO expander
PCA9554BS I2C GPIO expander
SIM Not tested / available on Connector X22 on MBa6ULx
STMPE811 resitive touch controller Connected to I2C4 on MBa6ULx
Not tested
USB2517 USB1 Host 1
USB2517 USB2 Host 2
USB2517 USB3 Host 3
USB2517 USB4 Host 4
USB2517 USB5 Host 5
USB2517 USB6 Host 6
USB2517 USB7 Host 7
SNVS Reset Reset
PMIC-Reset
Power-Down
Wake-Up

WORK IN PROGRESS

BSP Version Matrix

BSP Revision PTXdist OSELAS Toolchain Platform U-Boot Linux Kernel Qt Version
0116 2020.01.0 2019.09.1 MBa6ULx
MBa6ULxL
2016.03 + rel_imx_4.1.15_2.0.0_ga + patches 5.15.27 + patches
linux 5.15.27 + rt35
5.12.6
0115 2020.01.0 2019.09.1 MBa6ULx
MBa6ULxL
2016.03 + rel_imx_4.1.15_2.0.0_ga + patches 5.4.87 + patches
linux 5.4.87 + rt48
5.12.6
0110 2019.01 2018.12.0 MBa6ULx
MBa6ULxL
2016.03 + rel_imx_4.1.15_2.0.0_ga + patches 4.14.78 + rel_imx_4.14.78_1.0.0_ga + patches 5.6.3
0107 2019.01 2018.02.0 MBa6ULx
MBa6ULxL
2016.03 + rel_imx_4.1.15_2.0.0_ga + patches 4.14.78 + rel_imx_4.14.78_1.0.0_ga + patches 5.6.3
0106 2016.04 2014.12.2 MBa6ULx 2016.03 + rel_imx_4.1.15_2.0.0_ga + patches 4.1.15 + rel_imx_4.1.15_1.2.0_ga + patches 5.6.2
0104 2016.04 2014.12.2 MBa6ULx 2016.03 + rel_imx_4.1.15_2.0.0_ga + patches 4.1.15 + rel_imx_4.1.15_1.2.0_ga + patches 5.6.2
0100 2016.04 2014.12.2 MBa6ULx 2015.04 + rel_imx_4.1.15_1.2.0_ga + patches 4.1.15 + rel_imx_4.1.15_1.2.0_ga + patches 4.8.7

BSP / Hardware compatibility

TQMa6ULx TQMa6ULxL
Rev. 010x Rev. 030x Rev. 010x Rev. 020x
BSP Rev. 0100
BSP Rev. 01xx

BSP Version History

REV.0115

BSP

  • Activate SYSTEMD_NETWORK for systemd configs
  • Update 5.4 mainline kernel to 5.4.87-rt48
  • Update 5.4 mainline kernel to 5.4.87
  • Remove patches from u-boot imx 2016.03 and mainline 2017.11
  • Remove patches from kernel 4.19 and u-boot 2019.04
  • Remove tqma57xx config
  • Add systemd ethernet config for eth0 and eth1

U-Boot

  • Load tq u-boot from TQ-Systems github repo

Linux

  • kernel[-rt]: update to prevent eth0 link up/down problem on tqma6ul[l]2[l]

REV.0110

TQMa6ULx-BSP

  • Updated OSELAS Toolchain to 2018.12

U-Boot

  • Added support for 512MB RAM variants of TQMa6UL\[L\]x REV.030x
  • Typo fixes in output / banner / warnings
  • Add warning for CPU / config mismatch

REV.0107

TQMa6ULx-BSP

  • Added platform MBa6ULxL
  • Updated Build system to PTXdist 2019.01
  • Updated OSELAS Toolchain to 2018.02

U-Boot

  • added several bugfixes
  • fixed fdt_file environment variable definition
  • set default i2c dev to 3 (MBa6ulxl)
  • fixed typo in header include guard
  • fix build without CONFIG_DM_SPI_FLASH and CONFIG_SPI_FLASH
  • Added platform MBa6ULxL

Linux

  • Update kernel version to NXP 4.14.78
  • Set USB1 OTG dr_mode to otg
  • QSPI NOR flash uses 4byte opcodes
  • Changed default LVDS display to Tianma TM070JVHG33
  • add cpu cooling levels
  • fixed RS485 support
  • Added platform MBa6ULxL
    • display: use 24 LCD data pins
    • set USB1 OTG dr_mode to otg

REV.0106

TQMa6ULx-BSP

  • Support / fixes for TQMa6ULx with automotive grade CPU
  • e-MMC Timing fix for TQMa6ULx / TQMa6ULxL (low temperature improvement / limit clock speed)
  • Update DRAM calibration values for TQMa6ULL
  • update patches for TQMa6UL / TQMa6LL e-MMC clocking fix
  • update u-boot-imx for TQMa6ULL and TQMa6UL automotive support

U-Boot

  • fix output of i.MX6UL(L) speed grade with 696 MHz
  • added TQMa6ULL1 support

Linux

  • rewrite e-MMC clocking and tuning
  • apply e-MMC clocking changes also for LGA module

REV.0104

TQMa6ULx-BSP

  • Bugfixes in upstream packages
  • Splash if fbdev found
  • system images for QSPI
  • UBI image creation for QSPI
  • Change image names (mba6ul → mba6ulx, tqma6ul → tqma6ulx)

U-Boot

  • Support TQMa6ULx 030x / TQMa6ULxL 020x on MBa6ULx 020x
  • Dynamic default if no devicetree set
  • Optimize defconfigs
  • UBI boot support
  • Simplify env scripts
  • Optimize qspi clock
  • Optimize RAM timing
  • Update base version from NXP

Linux

  • Backport mmc sysfs fixes for OCR / DSR
  • Optimize / cleanup e-MMC / SD config
  • Improve QSPI support / Backport jedec detect for QSPI
  • Allow 4-Byte address command set for QSPI
  • MTD Partitions for MBa6UL
  • Backport fixes for EDT Touch
  • Rewrite devicetree to reuse fragments for display / TQMa6ULxL etc.
  • Support more display variants
  • Update base version from NXP

Configure the BSP for the desired hardware platform and software configuration using the correpsonding command from the following table:

Platform Configuration Command
MBa6ulx linux ¦ systemd init ¦ Qt5 tools/config-mba6ulx.qt
linux ¦ busybox init tools/config-mba6ulx.tiny
linux ¦ systemd init tools/config-mba6ulx.sd

Building the BSP:

Execute in the BSP root directory

$ ./tools/config-mba6ulx.qt
$ ./p images

or

$ ptxdist platform configs/platform-tq-tqma6ulx/mba6ulx/platformconfig
$ ptxdist select configs/platform-tq-tqma6ulx/ptxconfig.qt_bb
$ ptxdist go --git
$ ptxdist images

SD / eMMC Image

  • sector size 512 Byte
  • unpartitioned area: 4MiB (0x2000 sectors)

Sector numbers are in hexadecimal (as expected by U-Boot's mmc command), size is given in hex (=number of sectors) and dezimal (= size in byte).

Sector first Sector last Size Usage
0x000000 0x000000 0x0001 sector / 512 Byte MBR / Partition Table
0x000001 0x000001 0x0001 sector / 512 Byte free
0x000002 0x0007FF 0x07FE sectors / 1023 KiB u-boot
0x000800 0x000FFF 0x0800 sectors / 1 MiB u-boot environment
0x001000 0x001FFF 0x1000 sectors / 2 MiB free
0x002000 0x00BFFF 0xA000 sectors / 20 MiB boot / firmware (Kernel, devicetrees)
0x00C000 0x08BFFF 0x80000 sectors / 256 MiB root
0x08C000 0x10BFFF 0x80000 sectors / 256 MiB spare, unformatted

QSPI NOR

  • sector size 64k
Sector Size Usage
0x0000 … 0x0012 0x000D sectors / 832 KiB U-Boot
0x0013 … 0x0013 0x0001 sector / 64 KiB environment0
0x0014 … 0x0014 0x0001 sector / 64 KiB environment1
0x0015 … 0x0015 0x0005 sectors / 64 KiB devicetree
0x0016 … 0x0086 0x0070 sectors / 7 MiB Kernel
0x0087 … 0x0467 0x0380 sectors / 56 MiB RootFS

Create SD Card with BSP Image

To install a new firmware use SD cards. To copy the built images on the host system to a connected card type:

$ cd <BSP project>/platform-<platform_name>/images
$ sudo dd if=u-boot_<label mod_name_code>MOD_NAME_CODE</label>_hd.img of=/dev/sdf bs=1M conv=fsync #Assuming the SD card is assigned to /dev/sdf

To find out what device file the SD card has, type “dmesg” after you connect the card to see the system messages. At the bottom you'll see some “Attached scsi …” messages along with something like:

[ 8197.588395]  sdf: sdf1

Updating existing firmware over ethernet


To update bootloader / kernel / devicetree in a running system you have to copy the images in your tftp directory and upload them to the eMMC or SD Card.

Please see How to setup TFTP Server

1. Boot from eMMC or SD and stop autoboot in U-Boot

Hit any key to stop autoboot:  0
=>


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

=> setenv mmcdev <Nr.>

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

3. Connect device via ethernet to a tftp server supplying the image
4. Provide the correct network configuration in U-Boot:

  • ⇒ setenv autoload no
  • ⇒ setenv serverip <serverip> (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)


5. Provide U-Boot the file name of the desired image on the tftp server:

  • For U-Boot update: ⇒ setenv uboot <filename>
  • For Device Tree update: ⇒ setenv fdt_file <filename>
  • For Kernel update: ⇒ setenv zimage <filename>


6. Perform Update:

  • U-Boot update: ⇒ run update_uboot
  • Device Tree update: ⇒ run update_fdt
  • Kernel update: ⇒ run update_kernel

The u-boot update scripts automatically implement the selection of the primary copy to boot.



Copy Firmware from SD card to eMMC using U-Boot

  • 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 command to copy the SD card to eMMMC
Generic command
 
mmc dev 1 && mmc rescan && mmc read ${loadaddr} 0 (number of blocks)  && mmc dev 0 && mmc rescan && mmc write ${loadaddr} 0 (number of blocks)

You have to set the number of blocks according to the image size to read entire data that is stored on the SD card and write the same number of blocks to the eMMC.
Formula to calulate the number of blocks
Size of SD card image in bytes / 512. Convert the result to a hex value.
Since the data is stored in the SDRAM on the module the size of the image must not exeed the size of the SDRAM.

Example for precompiled SD card image included in BSP Rev.0100
  • Size of image-u-boot-fsl-mba6ul-hd.img in byte = 293.601.280
  • 293.601.280 / 512 = 573.440
  • 540.672 converted to hex value = h8C000
mmc dev 1 && mmc rescan && mmc read ${loadaddr} 0 0x8c000  && mmc dev 0 && mmc rescan && mmc write ${loadaddr} 0 0x8c000

Copy rootfs from SD card to eMMC

The rootfs is located in the second partition of the SD card/eMMC please see Partition Scheme

example for TQMa6ULx

dd if=/dev/mmcblk0p2 of=/dev/mmcblk1p2 bs=1M

please keep in mind to resize the eMMC rootfs partition,
if the rootfs size was changed in BSP configuration

Using NFS boot

Prerequisites

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

  • setenv autoload no
  • setenv serverip <serverip> (e.g.: setenv serverip 192.168.100.1)
  • setenv ipaddr <ipaddr> (e.g.: setenv ipaddr 192.168.0.10)
  • setenv netmask <netmask> (e.g.: setenv netmask 255.255.255.0)
  • setenv rootpath <rootpath> (NFS share 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 zimage <zimage> (name of the Linux kernel image to be downloaded from the tftp server)

TQMa6ULx serial downloader

You have to set the Starterkit to boot-mode “serial downloader”, please see MBa6ulx DIP switch settings

Starting with TQMa6ULx-BSP-REV.0104 we deliver a Linux tool to upload U-Boot into the TQMa6ULx RAM from your development host and start it.
After building the BSP the tool is located in:
…/TQMa6ULx.BSP.SW.SRC.0104/platform-MBa6ULx-FSL/packages/host-imx_usb_loader-48a85c0b84611c089cf870638fd1241619324b1d/

You have to apply the following steps before you can start to work with the tool:

  • Copy the content of folder …/TQMa6ULx.BSP.SW.SRC.0104/platform-MBa6ULx-FSL/packages/host-imx_usb_loader-48a85c0b84611c089cf870638fd1241619324b1d/usr/etc/ to /usr/etc
  • Copy the content of folder …/TQMa6ULx.BSP.SW.SRC.0104/platform-MBa6ULx-FSL/packages/host-imx_usb_loader-48a85c0b84611c089cf870638fd1241619324b1d/usr/bin/ to /bin

Usage of serial downloader tool

  1. Set Starterkit to boot-mode “serial downloader”, please see MBa6ULx DIP switch settings
  2. Connect Starterkit connector X9 (Micro USB cable provided with the Starterkit) to your host
  3. Connect Starterkit connector X15 (RS232) to your host
  4. Power up Starterkit
  5. Please check that Linux recognized a new USB device, see output of command dmesg | grep -i usb. You should see something like the following :
usb 3-2.1: Product: SE Blank 6UL
usb 3-2.1: Manufacturer: Freescale SemiConductor Inc
hid-generic 0003:15A2:007D.0007: hiddev0,hidraw1: USB HID v1.10 Device [Freescale SemiConductor Inc  SE Blank 6UL ] on usb-0000:03:00.0-2.1/input0
  1. Open a serial terminal on your host e.g. TeraTerm
  2. Open a Linux terminal and naviagate to folder “images” in the BSP dirctory
    e.g. /home/embedded/TQMa6ULx.BSP.SW.SRC.0104/platform-MBa6ULx-FSL/images
  3. Start the serial downloader imx_usb as super user with the desired U-Boot as parameter

    Keep in mind to select a U-Boot that is corresponding to your module, please see deployment

    e.g.

    embedded@ubuntu:~/workspace/TQMa6ULx.BSP.SW.SRC.0104/platform-MBa6ULx-FSL/images$ sudo imx_usb u-boot-fsl-mba6ulx-mmc.imx

Host console output after starting the serial downloader:

config file </etc/imx-loader.d/imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
config file </etc/imx-loader.d/mx6_usb_work.conf>
parse /etc/imx-loader.d/mx6_usb_work.conf
15a2:007d(mx6_qsb) bConfigurationValue =1
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot-fsl-mba6ulx-mmc.imx
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
main dcd length 1e0
sub dcd length 1dc

loading binary file(u-boot-fsl-mba6ulx-mmc.imx) to 8fbff400, skip=0, fsize=86c00 type=aa

<<<551936, 551936 bytes>>>
succeeded (status 0x88888888)
jumping to 0x8fbff400

9. Now you can see the U-Boot messages in the serial terminal programm

Next steps are:

Finally, you will find the built images in platform-<platformname>/images.

<accordion collapsed=“true”>

TQMa6ulx

System Image

Boot device File Description
SD Card/eMMC uboot-mba6ulx-hd.img bootable image for TQMaULx on MBa6ULx (usage on SD Card and eMMC)

The complete system image is intended for:

  • development system initialisation
  • deployment

QSPI NOR image without rootfs

Boot Device File Description
SD Card/eMMC uboot-mba6ulx-qspi.img bootable image for TQMaULx on MBa6ULx (usage on QSPI NOR, without rootfs)

Bootloader binaries
Not to be confused with the u-boot*.bin images, these are just intermediate images and will not be booted by the i.MX6ULx.

Boot device File Description
SD Card/eMMC u-boot-fsl-mba6ulx-mmc.imx u-boot bootloader for TQMa6ULx on MBa6ULx (usage on SD Card and eMMC)
QSPI-NOR u-boot-fsl-mba6ulx-qspi.imx u-boot bootloader for TQMa6ULx on MBa6ULx (usage on QSPI NOR)

Linux Kernel binary

File Description
linuximage Kernel (zImage)

Devicetree blobs

File Description
imx6ul-mba6ulx.dtb device tree blob for TQMa6ULx on MBa6ULx
imx6ul-mba6ulx-otg.dtb device tree blob for TQMa&ULx on MBa6ULx USB OTG activated
imx6ul-mba6ulx-lvds.dtb device tree blob for TQMa6ULx on MBa6ULx LVDS interface activated
imx6ul-mba6ulx-glyn-etm0700g0edh6.dtb device tree blob for TQMa6ULx on MBa6ULx parallel display interface activated with display timing for GLYN display ETM700G0EDH6
imx6ul-mba6ulx-dmb-ct44.dtb device tree blob for TQMa6ULx on MBa6ULx parallel display interface activated with display timing for DMB display 800×480
imx6ul-mba6ulx-dmb-ct21.dtb device tree blob for TQMa6ULx on MBa6ULx parallel display interface activated with display timing for DMB display 1024×600

firmware partition images

File Description
firmware.img firmware image contains all devicetree blobs and linux kernel image
firmware.tgz firmware image archive (for firmware image creation)

Rootfs images

File Description
root.tgz Root file system archive (for NFS etc.)
root.ext2 Root file system partition image (for system update)
root.ubi ubi partition for QSPI NOR
root.ubifs ubifs image for QSPI NOR

TQMa6ulxl

Complete system image

Boot device File Description
AD Card/eMMC uboot-mba6ulx-lga-hd.img bootable image for TQMaULxL on MBa6ULx (usage on SD Card and eMMC)

The complete system image is intended for:

  • development system initialisation
  • deployment

QSPI NOR image without rootfs

  • uboot-mba6ulx-lga-qspi.img: bootable image for TQMaULxL on MBa6ULx (usage on QSPI NOR, without rootfs)

Bootloader binaries
Not to be confused with the u-boot*.bin images, these are just intermediate images and will not be booted by the i.MX6ULx.

Boot device File Description
SD Card/eMMC u-boot-fsl-mba6ulx-lga-mmc.imx u-boot bootloader for TQMa6ULxL on MBa6ULx (usage on SD Card and eMMC)
QSPI-NOR u-boot-fsl-mba6ulx-lga-qspi.imx u-boot bootloader for TQMa6ULxL on MBa6ULx (usage on QSPI NOR)

Linux Kernel binary

File Description
linuximage Kernel (zImage)

Devicetree blobs

File Description
imx6ul-mba6ulx-lga.dtb device tree blob for TQMaULxL on MBa6ULx
imx6ul-mba6ulx-lga-otg.dtb device tree blob for TQMaULxL on MBa6ULx USB OTG activated
imx6ul-mba6ulx-lga-lvds.dtb device tree blob for TQMaULxL on MBa6ULx LVDS interface activated
imx6ul-mba6ulx-lga-glyn-etm0700g0edh6.dtb device tree blob for TQMaULxL on MBa6ULx parallel display interface activated with display timing for GLYN display ETM700G0EDH6
imx6ul-mba6ulx-lga-dmb-ct44.dtb device tree blob for TQMaULxL on MBa6ULx parallel display interface activated with display timing for DMB display 800×480
imx6ul-mba6ulx-lga-dmb-ct21.dtb device tree blob for TQMaULxL on MBa6ULx parallel display interface activated with display timing for DMB display 1024×600

firmware partition images

File Description
firmware.img firmware image contains all devicetree blobs and linux kernel image
firmware.tgz firmware image archive (for firmware image creation)

Rootfs images

File Description
root.tgz Root file system archive (for NFS etc.)
root.ext2 Root file system partition image (for system update)
root.ubi ubi partition for QSPI NOR
root.ubifs ubifs image for QSPI NOR

TQ Board Support Packages

The Board Support Packages (BSPs) usually provide source code as well as precompiled images for one or more platforms.
Please see the version matrix for details of each BSP revision.

TQMa6ULx BSP REV.0110☚ current revision
MD5SUM: A22068C4F9497229F55FF8507C5A5B15

TQMa6ULx BSP REV.0107
MD5SUM: FF2F0A18947A130EA6E93B72A61B8183

TQMa6ULx BSP REV.0106
MD5SUM: 5E44B9C8F13CFAE482FA10A41411B01D

TQMa6ULx BSP REV.0104
MD5SUM: F18039434D484420E72061B9E64E62DA

TQMa6ULx BSP Rev.0100
MD5SUM: 6C1C87DBF7724B4FBE84266CE6146C85

Build System / Toolchains

PTXdist version XXXX.YY.0 is required to compile an OSELAS Toolchain XXXX.YY.Z.
The version of PTXdist and toolchain required to build a given BSP revision is shown in the version matrix.


Build System PTXdist 2019.01

Build System PTXdist 2018.02

Build System PTXdist 2016.04

Build System PTXdist 2014.12

OSELAS Toolchain 2018.12

OSELAS Toolchain 2018.02

OSELAS Toolchain 2014.12.2

PTXdist projects for compiling OSELAS toolchains

Copy Firmware from SD card to eMMC using U-Boot on TQMa6UL

The size of eMMC/SD image exceeds TQMa6ULx RAM size so it is not possible to copy the image into the RAM.
Nevertheless copying is possible by splitting Rootfs into several parts during the process.

  • Set Starterkit to boot from SD, please see DIP Switch Settings
  • Interrupt the boot process to get to the U-Boot prompt
  • The U-Boot environment has to be expanded to copy the content from the SD Card to the eMMC therefore create the following u-boot env variables has to be created.
  • Create U-boot env variable install_firmware
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 2 7fe && mmc dev 0 && mmc write $loadaddr 2 7fe && echo U-Boot environment... && mmc dev 1 && mmc read $loadaddr 800 800 && mmc dev 0 && mmc write $loadaddr 800 800 &&  echo Firmware Partition... && mmc dev 1 && mmc read $loadaddr 2000 A000 && mmc dev 0 && mmc write $loadaddr 2000 A000 && echo Root FS... && run root_loop'
  • Create U-boot env variable root_loop
setenv root_loop 'setenv start 0xC000 && setenv r1 $rootblks16 && while itest $r1 -gt 0; do if itest $r1 -gt 0x2D000; then setenv count 2D000; 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'
  • create rootblks16 and set a value
setenv rootblks16 0x80000
  • save changes
saveenv
  • Use the new commands to copy the SD-Card image to eMMC
run install_firmware

Load / Change / Save the Device Tree under U-Boot


Devicetree can be edit with the fdt commands under U-Boot.

For testing purpose only. For bigger changes, please compile the Devicetree.
Therefore you can have a look at the following tutorial.
Tested with TQMa6ULx BSP Rev.0100

1) At first the fdt file has to be loaded from the current boot medium (mmc) into RAM.

=> run loadfdt 

2) Next step is to set the predefined U-Boot environment variable fdt_addr through the fdt addr command.

=> fdt addr $fdt_addr 

3) Afterwards the size of the fdt has to be increased (to the next 4K divider) in order to have some space for modifications. This is simply done by entering:

=> fdt resize 

4) List device in the tree you want to change to have a look at the default settings.

Example

5) To modify a value of a propertie use the fdt set command.

=> fdt set <path> <property> <value> 

Example

6) Optional: If you want to save your modified Devicetree back to mmc you'll have to run the following command:

=> fatwrite mmc $mmcdev:$firmwarepart $fdt_addr $fdt_file <totalsize> 

You can find out <totalsize> of the modified fdt by entering the command fdt header

Otherwise you can boot your module with the changed Devicetree right after the modification.



TQMa6ULx BSP Rev.0104

Affects TQMa6ULx Camera Sensor Interface
Issue When CSI is configured in Linux devicetree and the CSI is bound by the Linux driver, the system does not boot properly
Effect System does not boot properly
Solution / Workaround The issue can be fixed by removing the pinmux entries of the PMIC in Linux devicetree

BSP Version Matrix

BSP Revision meta-tq release Yocto Project / Poky Release Target machine1) U-Boot Linux Kernel
0116 hardknott 3.3.3 - Hardknott tqma6ulx-mba6ulx
tqma6ulx-512mb-mba6ulx
tqma6ulx-lga-mba6ulx
tqma6ullx-mba6ulx
tqma6ullx-512mb-mba6ulx
tqma6ullx-lga-mba6ulx
tqma6ulx-lga-mba6ulxl
2016.03 (NXP imx-rel_imx_4.1.15_2.0.0_ga) 5.15.27
0113 zeus 3.0.3 - Zeus tqma6ulx-mba6ulx
tqma6ulx-512mb-mba6ulx
tqma6ulx-lga-mba6ulx
tqma6ullx-mba6ulx
tqma6ullx-512mb-mba6ulx
tqma6ullx-lga-mba6ulx
tqma6ulx-lga-mba6ulxl
2016.03 (NXP imx-rel_imx_4.1.15_2.0.0_ga) 5.4.23
5.4.23 + rt23
v2019.04-lf-5.4.y-1.0.0
0110 warrior 2.7 - Warrior tqma6ulx-mba6ulx
tqma6ulx-512mb-mba6ulx
tqma6ulx-lga-mba6ulx
tqma6ullx-mba6ulx
tqma6ullx-512mb-mba6ulx
tqma6ullx-lga-mba6ulx
2016.03 (NXP imx-rel_imx_4.1.15_2.0.0_ga) NXP 4.14.78 rel_imx_4.14.78_1.0.0_ga
0107 warrior 2.7 - Warrior tqma6ulx-mba6ulx
tqma6ulx-lga-mba6ulx
tqma6ullx-mba6ulx
2016.03 (NXP imx-rel_imx_4.1.15_2.0.0_ga) NXP 4.14.78 rel_imx_4.14.78_1.0.0_ga
0106 pyro 2.3.3 - Pyro tqma6ulx-mba6ulx
tqma6ulx-lga-mba6ulx
tqma6ullx-mba6ulx
2016.03 (NXP imx-rel_imx_4.1.15_2.0.0_ga) rel_imx_4.1.15_2.0.0_ga
0104 pyro 2.3.3 - Pyro tqma6ulx-mba6ulx 2016.03 (NXP imx-rel_imx_4.1.15_2.0.0_ga) rel_imx_4.1.15_2.0.0_ga
0105 pyro 2.3.3 - Pyro tqma6ulx-mba6ulx
tqma6ulx-lga-mba6ulx
tqma6ullx-mba6ulx
2016.03 (NXP imx-rel_imx_4.1.15_2.0.0_ga) rel_imx_4.1.15_2.0.0_ga

BSP version history

REV.0117

BSP

  • Update to Yocto Kirkstone

Linux

REV.0116

BSP

  • Add machine configs with 512 MB RAM
  • Add missing information in documentation
  • Add bbappend for mesa to support TQMa6U[L]x[L] with mainline kernel
  • Support different list of device tree files, depending on the virtual/kernel provider
  • Add firmware ath10k as MACHINE_EXTRA_RRECOMEND

Linux

  • linux 5.15 support based on linux-stable 5.15.y
  • merge all mainline stable fixes up to v5.15.27 (CVE-2022-0847 “Dirty Pipe Vulnerability”)
  • linux-tq-5.4 is deprecated for all TQMa6UL[L]x modules (LGA variants as well)
  • Fixed:
    • GPIO wakeup
    • Audio configuration on TQMa6UL[L]x
    • QSPI driver bug causing frequent corruptions of filesystems on SPI-NOR flash
    • USB support with parallel LCD device tree on MBa6ULxL

REV.0113

BSP

  • Update to Linux Kernel 5.4
  • Added kernel linux-tq 5.4
  • Added kernel linux-rt-tq 5.4
  • Added kernel linux-imx-tq 5.4

Linux

  • Changed kernel configuration to use the better supported mainline graphics stack

REV.0110

U-Boot

  • Added support for 512MB RAM variants of TQMa6UL\[L\]x REV.030x
  • Typo fixes in output / banner / warnings
  • Add warning for CPU / config mismatch

REV.0107

BSP

  • Added platform MBa6ULxL

U-Boot

  • added several bugfixes
  • fixed fdt_file environment variable definition
  • set default i2c dev to 3 (MBa6ulxl)
  • fixed typo in header include guard
  • fix build without CONFIG_DM_SPI_FLASH and CONFIG_SPI_FLASH
  • Added platform MBa6ULxL

Linux

  • Update kernel version to NXP 4.14.78
  • Set USB1 OTG dr_mode to otg
  • QSPI NOR flash uses 4byte opcodes
  • Changed default LVDS display to Tianma TM070JVHG33
  • add cpu cooling levels
  • fixed RS485 support
  • Added platform MBa6ULxL
    • display: use 24 LCD data pins
    • set USB1 OTG dr_mode to otg

REV.0106

BSP

  • Support / fixes for TQMa6ULx with automotive grade CPU
  • e-MMC Timing fix for TQMa6ULx / TQMa6ULxL (low temperature improvement / limit clock speed)
  • Update DRAM calibration values for TQMa6ULL
  • update patches for TQMa6UL / TQMa6LL e-MMC clocking fix
  • update u-boot-imx for TQMa6ULL and TQMa6UL automotive support

U-Boot

  • fix output of i.MX6UL(L) speed grade with 696 MHz
  • added TQMa6ULL1 support

Linux

  • rewrite e-MMC clocking and tuning
  • apply e-MMC clocking changes also for LGA module

REV.0104

BSP

  • Change image names (mba6ul → mba6ulx, tqma6ul → tqma6ulx)

U-Boot

  • Support TQMa6ULx 030x / TQMa6ULxL 020x on MBa6ULx 020x
  • Dynamic default if no devicetree set
  • Optimize defconfigs
  • UBI boot support
  • Simplify env scripts
  • Optimize qspi clock
  • Optimize RAM timing
  • Update base version from NXP

Linux

  • Backport mmc sysfs fixes for OCR / DSR
  • Optimize / cleanup e-MMC / SD config
  • Improve QSPI support / Backport jedec detect for QSPI
  • Allow 4-Byte address command set for QSPI
  • MTD Partitions for MBa6UL
  • Backport fixes for EDT Touch
  • Rewrite devicetree to reuse fragments for display / TQMa6ULxL etc.
  • Support more display variants
  • Update base version from NXP

BSP Revision 0113

Target Machine: tqma6ulx-mba6ulx

System Image
SD Card/eMMC
Symlink File
tq-image-weston-tqma6ulx-mba6ulx.rootfs.wic tq-image-weston-tqma6ulx-mba6ulx-<build_timestamp>.rootfs.wic
Bootloader Binary
SD Card/eMMC
Symlink File
u-boot-tqma6ulx-mba6ulx.imx-sd u-boot-sd-2016.03-r0.imx
QSPI
Symlink File
u-boot-tqma6ulx-mba6ulx.imx-qspi u-boot-qspi-2016.03-r0.imx
Linux Kernel Binary
Symlink File
zImage
zImage-tqma6ulx-mba6ulx.bin
zImage–5.4-r0-tqma6ulx-mba6ulx-<build_timestamp>.bin
Devicetree Binarys
Symlink Description
imx6ul-mba6ulx.dtb
imx6ul-mba6ulx-tqma6ulx-mba6ulx.dtb
device tree blob for TQMa6ULx on MBa6ULx
imx6ul-mba6ulx-lvds.dtb
imx6ul-mba6ulx-lvds-tqma6ulx-mba6ulx.dtb
device tree blob for LVDS Display
imx6ul-mba6ulx-dmb-ct21.dtb
imx6ul-mba6ulx-dmb-ct21-tqma6ulx-mba6ulx.dtb
device tree blob for Display CT21
imx6ul-mba6ulx-dmb-ct44.dtb
imx6ul-mba6ulx-dmb-ct44-tqma6ulx-mba6ulx.dtb
device tree blob for Display CT44
imx6ul-mba6ulx-glyn-etm0700g0edh6.dt
imx6ul-mba6ulx-glyn-etm0700g0edh6-tqma6ulx-mba6ulx.dtb
device tree bolb for glyn Display
RootFS Images
Symlink File
tq-image-weston-tqma6ullx-mba6ulx.ext4 tq-image-weston-tqma6ulx-mba6ulx-<build_timestamp>.rootfs.ext4
tq-image-weston-tqma6ullx-mba6ulx.tar.gz tq-image-weston-tqma6ulx-mba6ulx-<build_timestamp>.rootfs.tar.gz

Target Machine: tqma6ulx-512mb-mba6ulx

System Image
SD Card/eMMC
Symlink File
tq-image-weston-tqma6ulx-512mb-mba6ulx.rootfs.wic tq-image-weston-tqma6ulx-512mb-mba6ulx-<build_timestamp>.rootfs.wic
Bootloader Binary
SD Card/eMMC
Symlink File
u-boot-tqma6ulx-512mb-mba6ulx.imx-sd u-boot-sd-2016.03-r0.imx
QSPI
Symlink File
u-boot-tqma6ulx-512mb-mba6ulx.imx-qspi u-boot-qspi-2016.03-r0.imx
Linux Kernel Binary
Symlink File
zImage
zImage-tqma6ulx-512mb-mba6ulx.bin
zImage–5.4-r0-tqma6ulx-512mb-mba6ulx-<build_timestamp>.bin
Devicetree Binarys
Symlink Description
imx6ul-mba6ulx.dtb
imx6ul-mba6ulx-tqma6ulx-mba6ulx.dtb
device tree blob for TQMa6ULx on MBa6ULx
imx6ul-mba6ulx-lvds.dtb
imx6ul-mba6ulx-lvds-tqma6ulx-512mb-mba6ulx.dtb
device tree blob for LVDS Display
imx6ul-mba6ulx-dmb-ct21.dtb
imx6ul-mba6ulx-dmb-ct21-tqma6ulx-512mb-mba6ulx.dtb
device tree blob for Display CT21
imx6ul-mba6ulx-dmb-ct44.dtb
imx6ul-mba6ulx-dmb-ct44-tqma6ulx-512mb-mba6ulx.dtb
device tree blob for Display CT44
imx6ul-mba6ulx-glyn-etm0700g0edh6.dt
imx6ul-mba6ulx-glyn-etm0700g0edh6-tqma6ulx-mba6ulx.dtb
device tree bolb for glyn Display
RootFS Images
Symlink File
tq-image-weston-tqma6ulx-512mb-mba6ulx.ext4 tq-image-weston-tqma6ulx-512mb-mba6ulx-<build_timestamp>.rootfs.ext4
tq-image-weston-tqma6ulx-512mb-mba6ulx.tar.gz tq-image-weston-tqma6ulx-512mb-mba6ulx-<build_timestamp>.rootfs.tar.gz

Target Machine: tqma6ulx-lga-mba6ulx

System Image
SD Card/eMMC
Symlink File
tq-image-weston-tqma6ulx-lga-mba6ulx.rootfs.wic tq-image-weston-tqma6ulx-lga-mba6ulx-<build_timestamp>.rootfs.wic
Bootloader Binary
SD Card/eMMC
Symlink File
u-boot-tqma6ulx-lga-mba6ulx.imx-sd u-boot-sd-2016.03-r0.imx
QSPI
Symlink File
u-boot-tqma6ulx-lga-mba6ulx.imx-qspi u-boot-qspi-2016.03-r0.imx
Linux Kernel Binary
Symlink File
zImage
zImage-tqma6ulx-lga-mba6ulx.bin
zImage–5.4-r0-tqma6ulx-lga-mba6ulx-<build_timestamp>.bin
Devicetree Binarys
Symlink Description
imx6ul-lga-mba6ulx.dtb
imx6ul-lga-mba6ulx-tqma6ulx-lga-mba6ulx.dtb
device tree blob for TQMa6ULx on MBa6ULx
imx6ul-lga-mba6ulx-lvds.dtb
imx6ul-lga-mba6ulx-lvds-tqma6ulx-lga-mba6ulx.dtb
device tree blob for LVDS Display
imx6ul-lga-mba6ulx-dmb-ct21.dtb
imx6ul-lga-mba6ulx-dmb-ct21-tqma6ulx-lga-mba6ulx.dtb
device tree blob for Display CT21
imx6ul-lga-mba6ulx-dmb-ct44.dtb
imx6ul-lga-mba6ulx-dmb-ct44-tqma6ulx-lga-mba6ulx.dtb
device tree blob for Display CT44
imx6ul-lga-mba6ulx-glyn-etm0700g0edh6.dt
imx6ul-lga-mba6ulx-glyn-etm0700g0edh6-tqma6ulx-lga-mba6ulx.dtb
device tree bolb for glyn Display
RootFS Images
Symlink File
tq-image-weston-tqma6ulx-lga-mba6ulx.ext4 tq-image-weston-tqma6ulx-lga-mba6ulx-<build_timestamp>.rootfs.ext4
tq-image-weston-tqma6ulx-lga-mba6ulx.tar.gz tq-image-weston-tqma6ulx-lga-mba6ulx-<build_timestamp>.rootfs.tar.gz

Target Machine: tqma6ullx-mba6ulx

System Image
SD Card/eMMC
Symlink File
tq-image-weston-tqma6ullx-mba6ulx.rootfs.wic tq-image-weston-tqma6ullx-mba6ulx-<build_timestamp>.rootfs.wic
Bootloader Binary
SD Card/eMMC
Symlink File
u-boot-tqma6ullx-mba6ulx.imx-sd u-boot-sd-2016.03-r0.imx
QSPI
Symlink File
u-boot-tqma6ullx-mba6ulx.imx-qspi u-boot-qspi-2016.03-r0.imx
Linux Kernel Binary
Symlink File
zImage
zImage-tqma6ullx-mba6ulx.bin
zImage–5.4-r0-tqma6ullx-mba6ulx-<build_timestamp>.bin
Devicetree Binarys
Symlink Description
imx6ull-mba6ulx.dtb
imx6ull-mba6ulx-tqma6ulx-mba6ulx.dtb
device tree blob for TQMa6ULx on MBa6ULx
imx6ull-mba6ulx-lvds.dtb
imx6ull-mba6ulx-lvds-tqma6ulx-mba6ulx.dtb
device tree blob for LVDS Display
imx6ull-mba6ulx-dmb-ct21.dtb
imx6ull-mba6ulx-dmb-ct21-tqma6ulx-mba6ulx.dtb
device tree blob for Display CT21
imx6ull-mba6ulx-dmb-ct44.dtb
imx6ull-mba6ulx-dmb-ct44-tqma6ulx-mba6ulx.dtb
device tree blob for Display CT44
imx6ull-mba6ulx-glyn-etm0700g0edh6.dt
imx6ull-mba6ulx-glyn-etm0700g0edh6-tqma6ulx-mba6ulx.dtb
device tree bolb for glyn Display
RootFS Images
Symlink File
tq-image-weston-tqma6ullx-mba6ulx.ext4 tq-image-weston-tqma6ullx-mba6ulx-<build_timestamp>.rootfs.ext4
tq-image-weston-tqma6ullx-mba6ulx.tar.gz tq-image-weston-tqma6ullx-mba6ulx-<build_timestamp>.rootfs.tar.gz

Target Machine: tqma6ullx-512mb-mba6ulx

System Image
SD Card/eMMC
Symlink File
tq-image-weston-tqma6ullx-512mb-mba6ulx.rootfs.wic tq-image-weston-tqma6ullx-512mb-mba6ulx-<build_timestamp>.rootfs.wic
Bootloader Binary
SD Card/eMMC
Symlink File
u-boot-tqma6ullx-512mb-mba6ulx.imx-sd u-boot-sd-2016.03-r0.imx
QSPI
Symlink File
u-boot-tqma6ullx-512mb-mba6ulx.imx-qspi u-boot-qspi-2016.03-r0.imx
Linux Kernel Binary
Symlink File
zImage
zImage-tqma6ullx-512mb-mba6ulx.bin
zImage–5.4-r0-tqma6ullx-512mb-mba6ulx-<build_timestamp>.bin
Devicetree Binarys
Symlink Description
imx6ull-mba6ulx.dtb
imx6ull-mba6ulx-tqma6ullx-mba6ulx.dtb
device tree blob for TQMa6ULx on MBa6ULx
imx6ull-mba6ulx-lvds.dtb
imx6ull-mba6ulx-lvds-tqma6ullx-512mb-mba6ulx.dtb
device tree blob for LVDS Display
imx6ull-mba6ulx-dmb-ct21.dtb
imx6ull-mba6ulx-dmb-ct21-tqma6ullx-512mb-mba6ulx.dtb
device tree blob for Display CT21
imx6ull-mba6ulx-dmb-ct44.dtb
imx6ull-mba6ulx-dmb-ct44-tqma6ullx-512mb-mba6ulx.dtb
device tree blob for Display CT44
imx6ull-mba6ulx-glyn-etm0700g0edh6.dt
imx6ull-mba6ulx-glyn-etm0700g0edh6-tqma6ullx-mba6ulx.dtb
device tree bolb for glyn Display
RootFS Images
Symlink File
tq-image-weston-tqma6ullx-512mb-mba6ulx.ext4 tq-image-weston-tqma6ullx-512mb-mba6ulx-<build_timestamp>.rootfs.ext4
tq-image-weston-tqma6ullx-512mb-mba6ulx.tar.gz tq-image-weston-tqma6ullx-512mb-mba6ulx-<build_timestamp>.rootfs.tar.gz

Target Machine: tqma6ullx-lga-mba6ulx

System Image
SD Card/eMMC
Symlink File
tq-image-weston-tqma6ullx-lga-mba6ulx.rootfs.wic tq-image-weston-tqma6ullx-lga-mba6ulx-<build_timestamp>.rootfs.wic
Bootloader Binary
SD Card/eMMC
Symlink File
u-boot-tqma6ulx-lga-mba6ullx.imx-sd u-boot-sd-2016.03-r0.imx
QSPI
Symlink File
u-boot-tqma6ulx-lga-mba6ullx.imx-qspi u-boot-qspi-2016.03-r0.imx
Linux Kernel Binary
Symlink File
zImage
zImage-tqma6ullx-lga-mba6ulx.bin
zImage–5.4-r0-tqma6ullx-lga-mba6ulx-<build_timestamp>.bin
Devicetree Binarys
Symlink Description
imx6ull-lga-mba6ulx.dtb
imx6ull-lga-mba6ulx-tqma6ullx-lga-mba6ulx.dtb
device tree blob for TQMa6ULx on MBa6ULx
imx6ull-lga-mba6ulx-lvds.dtb
imx6ull-lga-mba6ulx-lvds-tqma6ullx-lga-mba6ulx.dtb
device tree blob for LVDS Display
imx6ull-lga-mba6ulx-dmb-ct21.dtb
imx6ull-lga-mba6ulx-dmb-ct21-tqma6ullx-lga-mba6ulx.dtb
device tree blob for Display CT21
imx6ull-lga-mba6ulx-dmb-ct44.dtb
imx6ull-lga-mba6ulx-dmb-ct44-tqma6ullx-lga-mba6ulx.dtb
device tree blob for Display CT44
imx6ull-lga-mba6ulx-glyn-etm0700g0edh6.dt
imx6ull-lga-mba6ulx-glyn-etm0700g0edh6-tqma6ullx-lga-mba6ulx.dtb
device tree bolb for glyn Display
RootFS Images
Symlink File
tq-image-weston-tqma6ullx-lga-mba6ulx.ext4 tq-image-weston-tqma6ullx-lga-mba6ulx-<build_timestamp>.rootfs.ext4
tq-image-weston-tqma6ullx-lga-mba6ulx.tar.gz tq-image-weston-tqma6ullx-lga-mba6ulx-<build_timestamp>.rootfs.tar.gz

Device assignment

mmcdev 0 = eMMC
mmcdev 1 = SD Card

Yocto specific command Update eMMC

1. Run the following commands in the Uboot shell to create update script:

 
setenv root_loop 'setenv start 12000 && setenv r1 $rootblks16 && while itest $r1 -gt 0; do if itest $r1 -gt 0x50000; then setenv count 0x50000; 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 1 1FFF && mmc dev 0 && mmc write $loadaddr 1 1FFF && echo Firmware Partition... && mmc dev 1 && mmc read $loadaddr 2000 10000 && mmc dev 0 && mmc write $loadaddr 2000 10000  && echo Root FS... && run root_loop'

2. Create the environment variable rootblks16 and set the value accordingly to the size of the RootFS in this case 323MB.

To calculate the value of rootblks16 devide the size of the image in byte by 512 and convert the result into a hex value.

323 * 1024 * 1024 = 338690048
338690048 / 512 = 661504
661504= A1800HEX

setenv rootblks16 0xA1800

uboot command to start netboot

=> run netboot

Supported features


Supported boot devices


1)
i.e. value for MACHINE variable