Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
software:linux:toradex:toradex-easy-installer [2023-07-21 09:20] Urs Grafsoftware:linux:toradex:toradex-easy-installer [2023-07-25 16:58] (aktuell) Urs Graf
Zeile 1: Zeile 1:
 ====== Toradex Easy Installer ====== ====== Toradex Easy Installer ======
  
-The Toradex Easy Installer is Toradex's recommended option for flashing images onto their modules. +The Toradex Easy Installer is Toradex's recommended option for flashing images onto their modules. The method described below loads the installer into RAM, boots from there and allows to flash a new image. We were currently not able to boot from our current image into the Toradex Easy Installer sitting on a USB stick, see [[software:linux:toradex:Toradex Easy Installer on USB]].
  
  
 ===== Getting Toradex Easy Installer ===== ===== Getting Toradex Easy Installer =====
-You need the Colibri evaluation module, see [[embedded_systems:imx6:evm|Colibri Evaluation Board from Toradex]]. Follow instructions on [[https://developer.toradex.com/easy-installer/toradex-easy-installer/loading-toradex-easy-installer|Loading Toradex Easy Installer]] to get the installer and load it via USB OTG into the RAM. First, you have to enter recovery mode, see //Using a command in the bootloader//. If there is no longer any bootloader on the board, follow instructions under //Using hardware mechanism//. Next, load the installer with [[https://developer.toradex.com/easy-installer/toradex-easy-installer/loading-toradex-easy-installer#load-toradex-easy-installer-through-the-usb-otg-interface|these instructions]]. It will now automatically boot into the Toradex Easy Installer. +You need the Colibri evaluation module, see [[embedded_systems:imx6:evm|Colibri Evaluation Board from Toradex]]. Follow instructions on [[https://developer.toradex.com/easy-installer/toradex-easy-installer/loading-toradex-easy-installer|Loading Toradex Easy Installer]] to get the installer and load it via USB OTG into the RAM. First, you have to enter recovery mode, see //Using a command in the bootloader//. If there is no longer any bootloader on the board, follow instructions under //Using hardware mechanism//. Next, load the installer with the instruction given further down on the same website unter //Load Toradex Easy Installer through the USB OTG interface//. It will now automatically boot into the Toradex Easy Installer. 
  
  
Zeile 21: Zeile 21:
 </code> </code>
  
-The following window should appear:+You can get the ip address from the Easy Installer command line with ''ip a''The following window should appear:
  
 {{:software:linux:toradex:tezi.png?400|}} {{:software:linux:toradex:tezi.png?400|}}
Zeile 27: Zeile 27:
 Now select the desired image and click install. Now select the desired image and click install.
  
-===== Booting into Toradex Easy Installer ===== 
- 
-Download the Toradex Easy Installer from the [[ https://developer.toradex.com/software/toradex-easy-installer#download-toradex-easy-installer | Toradex Wiki ]] and extract the downloaded archive onto a SD Card or USB Stick (FAT32). Insert the into the Board's SD Card slot or USB port and power it on.  
- 
-Interrupt the boot process (hit any key) to boot into uBoot. Now run ''run bootcmd_mmc1'' to boot from the SD Card or ''run bootcmd_usb0'' to boot from USB. 
- 
-Note that while Toradex recommends using the ''run distro_bootcmd'' this will boot from the modules internal flash if a bootable image is present. 
- 
-If you get an error along the lines of ''bootcmd_usb0 no found'' chances are that the board runs an older version of uboot that does not come with distroboot. In that case the bootloader can be updated by flashing a new toradex image [[ https://developer.toradex.com/knowledge-base/flashing-linux-on-imx6-modules | as described here ]]. 
- 
-Note that if Toradex's ''update.sh'' script fails with ''not space left on device'', you can try increasing the  
-''MIN_PARTITION_FREE_SIZE'' in ''update.sh'' to work around the issue. 
  
 === Images Feeds === === Images Feeds ===