Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
Last revisionBoth sides next revision
en:layerscape:tqmls10xxa:linux:yocto:deployment_yocto [2021/04/28 15:58] – created liedmannen:layerscape:tqmls10xxa:linux:yocto:deployment_yocto [2022/08/04 15:02] – external edit 127.0.0.1
Line 12: Line 12:
 </embed> </embed>
 \\   \\  
 +
 +<embed en:templates:deployment_yocto_bootstrap>
 +<label lang>en</label>
 +<label mod_arch>layerscape</label>
 +<label bsp_name>linux</label>
 +<label build_system>yocto</label>
 +<label mod_name_code>tqmls10xxa</label>
 +<label bsp_image_name>tq-image-generic-tqmls10xxa-mbls10xxa</label>
 +<label mb_name_code>mbls10xxa</label>
 +<label mb_name>MBLS10xxA</label>
 +<label mod_name>TQMLS10xxA</label>
 +<label mod_name_partition>TQMLS10xxA</label>
 +<label stk_name>STKLS10xxA</label>
 +<label eth_prime></label>
 +<label uboot_default>u-boot-esdhc-2018.07-r0.bin</label>
 +<label fdt_default>fsl-tqmls1046a-mbls10xxa.dtb</label>
 +<label kernel_default>Image</label>
 +<label update_uboot_cmd>update_uboot_mmc</label>
 +<label update_dtb_cmd>update_fdt_mmc</label>
 +<label update_kernel_cmd>update_kernel_mmc</label>
 +</embed> 
 +
 +
 +===== Updating existing firmw
 +are over ethernet new =====
 \\ \\
-===== Updating existing firmware over ethernet ===== +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 the[[en:general_information:tftp|how 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.  
-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 ====  ==== Update Process ==== 
  
-1. Setup the Starterkit to boot from QSPI, please see the [[ .:..:..:mbls10xxA:dip_switches|Starterkit dip switch page]] how to setup.\\  +1. Setup the Starterkit to boot from SD/eMMC or QSPI,  please see the [[ .:..:..:mbls10xxA:dip_switches|Starterkit dip switch page]] how to setup\\  
 2. Connect the kit to the network with TFTP server supplying the binaries via ethernet on connector<label eth_prime>ETH_PRIME</label> \\ 2. Connect the kit to the network with TFTP server supplying the binaries via ethernet on connector<label eth_prime>ETH_PRIME</label> \\
 3. Power up the system and interrupt the boot process in U-Boot\\ 3. Power up the system and interrupt the boot process in U-Boot\\
Line 28: Line 52:
 => =>
 </code> </code>
-3. Setup the ethernet interface:+4. Setup the ethernet interface:
 ++++ Set network settings manually | ++++ Set network settings manually |
  
Line 65: Line 89:
 __**Kernel**__ __**Kernel**__
  
-For Kernel update on eMMC/SD Card and QSPI NOR : <code>=> setenv kernel <filename> (e.g.: setenv kernel Image.gz)</code>+For Kernel update on eMMC/SD Card and QSPI NOR 
 +  
 +:  
 +<code>=> setenv kernel <filename> (e.g.: setenv kernel Image.gz)</code>
  
 __**Frame Manager**__ __**Frame Manager**__
Line 99: Line 126:
 </code> </code>
 \\ \\
- 
  • Last modified: 2023/11/08 13:55