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

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

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

  
  

• 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

2. Save environment U-boot environment (optional):

=> saveenv

3. run the following command to start the update procedure:

=> run install_firmware

• How to setup the NFS Server on your Host Computer
• How to setup the TFTP Server on your Host Computer

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.

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:

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

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

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