we suggest to read the following pages before you proceed with this page
Finally, you will find the built images in platform-<platformname>/images.
Complete system images:
The complete system images are intend for:
Bootloader images:
Linux images:
Device tree blobs:
* **ls1021a-mbls1021a.dtb** : default device tree without display * **ls1021a-mbls1021a-dmb-ct21.dtb** : with parallel display (DMB S070PWS19HP-FC21) * **ls1021a-mbls1021a-dmb-ct44.dtb** : with parallel display (DMB S070SWV29HG-DC44) * **ls1021a-mbls1021a-glyn-etm0700g0edh6.dtb** : with parallel display (Glyn ETM0700G0EDH6) * **ls1021a-mbls1021a-lvds-tm070jvhg33.dtb** : with LVDS display (Tianma TM070JVHG33) * **ls1021a-mbls1021a-hdmi.dtb** : with HDMI display
Rootfs images:
Firmware images:
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=<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
To update bootloader / kernel / devicetree in a running system you have to copy the images to a 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.>
mmcdev depends on the placement of eMMC on TQMLS102xA module
Device assignment:
mmcdev 0 = SD Card (if eMMC ist not placed)
mmcdev 0 = eMMC (if eMMC ist placed)
3. Connect device via ethernet to a tftp server supplying the image
4. Provide the correct network configuration in U-Boot:
5. Provide U-Boot the file name of the desired image on the tftp server:
6. Perform Update:
The u-boot update scripts automatically implement the selection of the primary copy to boot.
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.
The bootloader environment needs to be modified to work with your tftp-server and your nfs-server.