Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:layerscape:tqmls10xxa:linux:yocto:deployment_yocto [2020/07/15 14:43] – Externe Bearbeitung 127.0.0.1 | en:layerscape:tqmls10xxa:linux:yocto:deployment_yocto [2023/11/08 13:55] (current) – removed work in progress liedmann | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | <WRAP round important> | + | <embed en: |
- | <embed en: | + | |
<label product_type> | <label product_type> | ||
<label lang> | <label lang> | ||
Line 12: | Line 11: | ||
</ | </ | ||
\\ | \\ | ||
+ | |||
+ | <embed en: | ||
+ | <label lang> | ||
+ | <label mod_arch> | ||
+ | <label bsp_name> | ||
+ | <label build_system> | ||
+ | <label mod_name_code> | ||
+ | <label bsp_image_name> | ||
+ | <label mb_name_code> | ||
+ | <label mb_name> | ||
+ | <label mod_name> | ||
+ | <label mod_name_partition> | ||
+ | <label stk_name> | ||
+ | <label eth_prime></ | ||
+ | <label uboot_default> | ||
+ | <label fdt_default> | ||
+ | <label kernel_default> | ||
+ | <label update_uboot_cmd> | ||
+ | <label update_dtb_cmd> | ||
+ | <label update_kernel_cmd> | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Updating existing firmw | ||
+ | are over ethernet new ===== | ||
+ | \\ | ||
+ | A good approach to update the firmare components U-Boot, | ||
+ | After setting up the TFTP server, the binaries that should be updated must be copied into the TFTP directory of your TFTP Server. | ||
+ | |||
+ | |||
+ | |||
+ | ==== Update Process ==== | ||
+ | |||
+ | 1. Setup the Starterkit to boot from SD/eMMC or QSPI, please see the [[ .: | ||
+ | 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: | ||
+ | => | ||
+ | </ | ||
+ | 4. Setup the ethernet interface: | ||
+ | ++++ Set network settings manually | | ||
+ | |||
+ | Provide the correct network configuration in U-Boot: | ||
+ | < | ||
+ | => setenv autoload no | ||
+ | => setenv serverip < | ||
+ | => setenv ipaddr < | ||
+ | => setenv netmask < | ||
+ | </ | ||
+ | ++++ | ||
+ | |||
+ | ++++ 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 < | ||
+ | => 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 : < | ||
+ | | ||
+ | __**QSPI NOR**__ | ||
+ | |||
+ | For U-Boot update on QSPI NOR : < | ||
+ | |||
+ | __**Devicetree**__ | ||
+ | |||
+ | For Device Tree update on eMMC/SD Card and QSPI NOR : < | ||
+ | |||
+ | __**Kernel**__ | ||
+ | |||
+ | For Kernel update on eMMC/SD Card and QSPI NOR | ||
+ | |||
+ | : | ||
+ | < | ||
+ | |||
+ | __**Frame Manager**__ | ||
+ | |||
+ | For Frame Manager Microcode on eMMC/SD Card and QSPI NOR : < | ||
+ | |||
+ | |||
+ | \\ | ||
+ | **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 | ||
+ | </ | ||
\\ | \\ |