Embedded module en tqmarzg2x TQMaRZG2x arm linux yocto YOCTO Linux \\ ===== BSP Binaries ===== - All binaries are intended for the usage on a STKaRZG2x - The symlinks point to the files of the last build {{section>en:arm:tqmarzg2x:data#yocto_images&noheader}} ===== Yocto Partitions ===== {{section>.:..:..:..:partitions#tqmarzg2x&noheader}} ---- ===== Create SD Card with BSP Image ===== The Image can be simply written to the SD Card by using the dd shell command in Linux: $ cd $ sudo dd if=tq-image-weston-tqmarzg2n_b-mbarzg2x-.rootfs.wic of=/dev/sdc bs=1M conv=fsync #Assuming the SD card is assigned to /dev/sdc The image must be written to the RAW device of the SD Card (e.g. /dev/sdc) and not into a partition (e.g. /dev/sdc1) ! To identify the SD card in Linux the shell command dmesg can be used: - Open a new terminal - Execute the following command without plugged SD Card $ dmesg | tail -n 15 - Insert SD Card and wait a few seconds - Run the command from step two again $ dmesg | tail -n 15 #plug in SD Card into the reader $ dmesg | tail -n 15 \\ ---- ===== Updating existing firmware over ethernet ===== \\ 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 [[en:general_information:tftp|how to setup TFTP Server]]. After setting up the TFTP server, the binaries to be updated must be copied into the TFTP directory. ==== Update Process ==== 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 ETH0 (X26) \\ 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 | Provide the correct network configuration in U-Boot: * => setenv autoload no * => setenv serverip (IP address of your TFTP server e.g.: setenv serverip 192.168.100.110) * => setenv ipaddr (e.g.: setenv ipaddr 192.168.100.111) * => setenv netmask (e.g.: setenv netmask 255.255.255.0) ++++ ++++ Set network settings using DHCP | If a DHCP server is available in the network, the interface can be configured by the server: * => setenv autoload no * => setenv serverip (IP address of your TFTP server e.g.: setenv serverip 192.168.100.110) * => dhcp (get IP from server) ++++ \\ 4. Set U-Boot variable **mmcdev** according to the drive you want to write to. => setenv mmcdev {{section>.:..:..:data#device_assignment&noheader}} 5. Set the file name of the binary to update in U-Boot : * For U-Boot update: => setenv uboot \\ e.g. uboot.bin * For devicetree update: => setenv fdt_file \\ e.g. fr8a774b1-tqmarzg2n_b-mbarzg2x.dtb * For Linux kernel update: => setenv image \\ e.g. Image 6. Perform Update by running the update command: **SD Card** * U-Boot update: => run update_uboot_sd * Device Tree update:=> run update_fdt_sd * Kernel update:=> run update_kernel_sd **eMMC** * U-Boot update: => run update_uboot_mmc * Device Tree update:=> run update_fdt_mmc * Kernel update:=> run update_kernel_mmc The variables can be saved with the command **saveenv** to keep the values permanently.