we suggest to read the following pages before you proceed with this page
Finally, you will find the built images in platform-<platformname>/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=@mod_name_code@_hd.img of=/dev/sdf bs=1M conv=fsync #Assuming the SD card is assigned to /dev/sdf
You have to use the raw device of the SD card not a partition!
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
Starting with BSP REV.0110 a firmware partition that contains all device tree blobs and the linux kernel image has been introduced.
To change the devicetree you can select it from the firmware partition.
1. Boot from eMMC or SD and stop autoboot in U-Boot
Hit any key to stop autoboot: 0 =>
2. To determine the mmc device that is currently selected run the mmc dev command.
mmcdev 0 = eMMC mmcdev 1 = SD Card
3. The firmware partition is formated with vfat. To list all files in the partition U-Boot provides the fatls coammnd.
=> fatls <interface> <dev:part>
5. The U-Boot variable fdt_file is used to select the the device tree that should be loaded by U-Boot. Please set this variable according to the file you want to use.
=> setenv fdt_file <filename> => saveenv
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.>
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:
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.
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.0109
The rootfs is located in the second partition of the SD card/eMMC please see Partition Scheme
example for TQMa6Q
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
You have to set the Starterkit to boot-mode “serial downloader”, please see MBa6x DIP switch settings
We recommend to use Ubuntu 14.04 64bit for the imx-usb tool
Starting with TQMa6x-BSP-REV.0109 we deliver a Linux tool to upload U-Boot into the TQMa6X RAM from your development host and start it.
After building the BSP the tool is located under
…/TQMa6x-BSP-REV.0109/platform-MBa6x/packages/h-imx_usb_loader-master
You have to apply the following steps before you can start to work with the tool:
usb 1-1: Manufacturer: Freescale SemiConductor Inc hid-generic 0003:15A2:0054.0002: hiddev0,hidraw1: USB HID v1.10 Device [Freescale SemiConductor Inc SE Blank ARIK] on usb-0000:02:03.0-1/input0
Keep in mind to select a U-Boot that is corresponding to your module, please see deployment
e.g.
embedded@ubuntu:~/workspace/TQMa6x-BSP-REV.0109/platform-MBa6x/images$ sudo imx_usb u-boot-TQMa6Q_MBa6x.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=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:0054(mx6_qsb) bConfigurationValue =1 Interface 0 claimed HAB security state: development mode (0x56787856) == work item filename u-boot-TQMa6Q_MBa6x.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 308 sub dcd length 304 loading binary file(u-boot-TQMa6Q_MBa6x.imx) to 4fbff400, skip=0, fsize=5cc00 type=aa <<<379904, 379904 bytes>>> succeeded (status 0x88888888) jumping to 0x4fbff400
Next steps are: