===== Deployment =====

<WRAP round info 60%>
 we suggest to read the following pages before you proceed with this page\\   
  - [[<label lang>LANG</label>:<label mod_arch>MOD_ARCH</label>:<label mod_name_code>MOD_NAME_CODE</label>:<label bsp_name>BSP_NAME</label>:prepare|preparing Development Host]]
  - [[<label lang>LANG</label>:<label mod_arch>MOD_ARCH</label>:<label mod_name_code>MOD_NAME_CODE</label>:<label bsp_name>BSP_NAME</label>:build_bsp|Building BSP with PTXdist]]
  - [[<label lang>LANG</label>:<label mod_arch>MOD_ARCH</label>:<label mod_name_code>MOD_NAME_CODE</label>:<label bsp_name>BSP_NAME</label>:adapt_bsp|Customizing BSP for own Product]]
  </WRAP>
  
Finally, you will find the built images in //platform-<platformname>/images//.


{{page>en:layerscape:tqmls102xa:linux:ptxdist:ptx_images}}

==== Create SD Card with BSP Image ====

To install a new firmware use SD cards. To copy the built images on the host system to a connected card type:
<code bash>
$ 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
</code>
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:
<code bash>
[ 8197.588395]  sdf: sdf1
</code>

----

==== Updating existing firmware over ethernet ====
\\
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 [[en:general_information:tftp|How to setup TFTP Server]]


**1. Boot from eMMC or SD and stop autoboot in U-Boot**\\
<code>Hit any key to stop autoboot:  0
=></code>

**2. Set U-Boot variable //mmcdev//  according to the drive you want to write to**
<code>=> setenv mmcdev <Nr.></code>
<WRAP round important 55%>
mmcdev depends on the placement of eMMC on TQMLS102xA module\\
</WRAP>
<WRAP round info 50%>__Device assignment:__\\
//mmcdev 0// = SD Card (**if eMMC ist <wrap em>not</wrap> placed**)\\
//mmcdev 0// = eMMC (**if eMMC ist placed**)
</WRAP>

3. Connect device via ethernet to a tftp server supplying the image\\
**4. Provide the correct network configuration in U-Boot:** 
  * => setenv autoload no
  * => setenv serverip <serverip> (e.g.: setenv serverip 192.168.100.110) 
  * => setenv ipaddr <ipaddr> (e.g.: setenv ipaddr 192.168.100.111)
  * => setenv netmask <netmask> (e.g.: setenv netmask 255.255.255.0)
\\
**5. Provide U-Boot the file name of the desired image on the tftp server:** 
  * For U-Boot update on eMMC/SD Card : => setenv uboot <filename>\\
  * For U-Boot update on QSPI NOR : => setenv uboot-qspi <filename>\\
 
  * For Device Tree update on eMMC/SD Card and QSPI NOR : => setenv fdt_file <filename>\\
  
  * For Kernel update on eMMC/SD Card and QSPI NOR : => setenv zimage <filename>\\

\\
**6. Perform Update: **
  * U-Boot update on eMMC /SD Card : => run update_uboot\\
  * U-Boot update on QSPI NOR : => run update_uboot-qspi\\

  * Device Tree update on eMMC /SD Card : => run update_fdt\\
  * Device Tree update on QSPI NOR : => run update_fdt-qspi\\

  * Kernel update on eMMC /SD Card : => run update_kernel\\
  * Kernel update on QSPI NOR : => run update_kernel-qspi\\

<WRAP round info>
The u-boot update scripts automatically implement the selection of the primary copy to boot.
</WRAP>
\\
----
==== Using NFS boot ====

== Prerequisites ==

  * [[en:nfs|How to setup the NFS Server on your Host Computer]] 
  * [[en:tftp|How to setup the TFTP Server on your Host Computer]]

To boot the <label mod_name>MOD_NAME</label> from network you need a working bootloader in eMMC/SD-card or SPI-NOR (placement option on <label mod_name>MOD_NAME</label>) 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.\\


== Configuration of U-Boot Environment ==

The bootloader environment needs to be modified to work with your tftp-server and your nfs-server.

  * setenv autoload no
  * setenv serverip <serverip> (e.g.: setenv serverip 192.168.100.1)
  * setenv ipaddr <ipaddr> (e.g.: setenv ipaddr 192.168.0.10)
  * setenv netmask <netmask> (e.g.: setenv netmask 255.255.255.0)
  * setenv rootpath <rootpath> <wrap important>(NFS share has to set in /etc/exports on the Computer that runs the NFS server first)</wrap>
  * setenv fdt_file <fdt_file> (name of devicetree file to be downloaded from the tftp server)
  * setenv zimage <zimage> (name of the Linux kernel image to be downloaded from the tftp server)