Environment for running local DHCOM Update - Revision history

Pzimmermann: Added explanation of some additional variables

2021-02-01T10:00:01Z

Added explanation of some additional variables

@@ Line 32: / Line 32: @@
 |-
 | do_local_update || This script increments <tt>local_update_tries</tt> by one and saves the new value. Then the update-kernel is loaded into memory. The variables <tt>src_intf</tt> and <tt>src_dev_part</tt> determine which interface, device and partition are used for this. After that the script <tt>setupdateargs</tt> (which is also used by the regular update kernel) is run. Now the update-kernel is loaded.
 |}

Pzimmermann at 07:23, 29 January 2021

2021-01-29T07:23:44Z

← Older revision		Revision as of 09:23, 29 January 2021
Line 45:		Line 45:
	== Activate Booting Update Kernel ==		== Activate Booting Update Kernel ==

	~~When~~ the update image and the update-kernel is put onto the device, you can activate the update from inside the Linux. The following example assumes that the components of the update are on the third partition of the eMMC of an i.MX6 based DHSOM-module. The eMMC on the i.MX6 has the device number 2, on other modules this can be different (like the AM335X: There the eMMC has the device number 1).		After the update image and the update-kernel is put onto the device, you can activate the update from inside the Linux. The following example assumes that the components of the update are on the third partition of the eMMC of an i.MX6 based DHSOM-module. The eMMC on the i.MX6 has the device number 2, on other modules this can be different (like the AM335X: There the eMMC has the device number 1).

	<tt>fw_setenv local_update true		<tt>fw_setenv local_update true

Pzimmermann: Revising some phrases, error correction

2021-01-29T06:45:32Z

Revising some phrases, error correction

Pzimmermann: Finished writing the draft of the documentation

2021-01-28T15:39:40Z

Finished writing the draft of the documentation

@@ Line 6: / Line 6: @@
 * A spare partition on the eMMC (NAND-flash is usually too small) where the components of the update are stored.
 * U-Boot must be built with the <tt>setexpr</tt>-command included (This command is used for arithmetic expressions).
-* The Linux on the DHSOM-System needs the fw-tools for accessing the bootloader environment.
+* The Linux on the DHSOM-System needs the fw-tools for accessing the bootloader environment. '''WARNING''': The configuration of the fw-tools must match the layout of the bootflash, else when setting the environment, the command will write to the wrong location on the flash. This may cause that the system won't work anymore.
 == Setting up the Environment ==
-Use the following commands as root (or prepend them with sudo) to set up the bootloader environment. If you are in the U-Boot console, you have to use <tt>setenv</tt> instead and after the last command you have to use <tt>saveenv</tt> to save the changed environment.
+Use the following commands as <tt>root</tt> (or prepend them with <tt>sudo</tt>) to set up the bootloader environment:
-fw_setenv local_update false
+ <tt>fw_setenv local_update false
-fw_setenv local_update_tries 0
+ fw_setenv local_update_tries 0
-fw_setenv local_update_max_tries 3
+ fw_setenv local_update_max_tries 3
-fw_setenv check_if_local_update 'if test "${local_update}" = "true" -a ${local_update_tries} -lt ${local_update_max_tries} ; then run do_local_update; fi'
+ fw_setenv check_if_local_update 'if test "${local_update}" = "true" -a ${local_update_tries} -lt ${local_update_max_tries} ; then run do_local_update; fi'
-fw_setenv do_local_update 'setexpr local_update_tries ${local_update_tries} + 1; saveenv; load ${src_intf} ${src_dev_part} ${loadaddr} zImage_${dhcom}.update; run setupdateargs; bootz ${loadaddr}'
+ fw_setenv do_local_update 'setexpr local_update_tries ${local_update_tries} + 1; saveenv; load ${src_intf} ${src_dev_part} ${loadaddr} zImage_${dhcom}.update; run setupdateargs; bootz ${loadaddr}' </tt>
 fw_setenv bootcmd 'update auto; run check_if_local_update; mmc dev ${mmcdev}; if mmc rescan; then run bootlinux; else echo Boot failed, because mmc${mmcdev} not found!;fi;

Pzimmermann: First part of the site

2021-01-25T15:28:01Z

First part of the site

New page

If you want to make a update of your DHSOM system, without using an USB-stick or a SD-card, it is possible to alter the environment of U-Boot to start a local version of the DHCOM Update Mechanism.

== Requirements ==

The DHSOM system requires the following things:
* A spare partition on the eMMC (NAND-flash is usually too small) where the components of the update are stored.
* U-Boot must be built with the <tt>setexpr</tt>-command included (This command is used for arithmetic expressions).
* The Linux on the DHSOM-System needs the fw-tools for accessing the bootloader environment.

== Setting up the Environment ==

Use the following commands as root (or prepend them with sudo) to set up the bootloader environment. If you are in the U-Boot console, you have to use <tt>setenv</tt> instead and after the last command you have to use <tt>saveenv</tt> to save the changed environment.

fw_setenv local_update false
fw_setenv local_update_tries 0
fw_setenv local_update_max_tries 3
fw_setenv check_if_local_update 'if test "${local_update}" = "true" -a ${local_update_tries} -lt ${local_update_max_tries} ; then run do_local_update; fi'
fw_setenv do_local_update 'setexpr local_update_tries ${local_update_tries} + 1; saveenv; load ${src_intf} ${src_dev_part} ${loadaddr} zImage_${dhcom}.update; run setupdateargs; bootz ${loadaddr}'
fw_setenv bootcmd 'update auto; run check_if_local_update; mmc dev ${mmcdev}; if mmc rescan; then run bootlinux; else echo Boot failed, because mmc${mmcdev} not found!;fi;

← Older revision		Revision as of 08:45, 29 January 2021
Line 6:		Line 6:
	* A spare partition on the eMMC (NAND-flash is usually too small) where the components of the update are stored.		* A spare partition on the eMMC (NAND-flash is usually too small) where the components of the update are stored.
	* U-Boot must be built with the <tt>setexpr</tt>-command included (This command is used for arithmetic expressions).		* U-Boot must be built with the <tt>setexpr</tt>-command included (This command is used for arithmetic expressions).
	* The Linux on the DHSOM-System needs the fw-tools for accessing the bootloader environment. '''WARNING''': The configuration of the fw-tools must match the layout of the bootflash, else when setting the environment, the command ~~will~~ write to the wrong location on the flash. This may cause that the system won't work anymore.		* The Linux on the DHSOM-System needs the <tt>fw-tools</tt> for accessing the bootloader environment. '''WARNING''': The configuration of the <tt>fw-tools</tt> must match the layout of the bootflash, else when setting the environment, the command may write to the wrong location on the flash. This may cause that the system won't work anymore.

	== Setting up the Environment ==		== Setting up the Environment ==
Line 34:		Line 34:
	\|}		\|}

	You have to alter the <tt>bootcmd</tt> variable that the check is run. You have to add <tt> run check_if_local_update;</tt> after the <tt>update auto;</tt> part.		You have to alter the <tt>bootcmd</tt> variable (is always executed at startup of the module) that the check is run. You have to add <tt> run check_if_local_update;</tt> after the <tt>update auto;</tt> part.
	For a standard i.MX6-based DHSOM-module the needed command should look like this:		For a standard i.MX6-based DHSOM-module the needed command should look like this:
	<tt>fw_setenv bootcmd 'update auto; run check_if_local_update; mmc dev ${mmcdev}; if mmc rescan; then run bootlinux; else echo Boot failed, because mmc${mmcdev} not found!;fi;</tt>		<tt>fw_setenv bootcmd 'update auto; run check_if_local_update; mmc dev ${mmcdev}; if mmc rescan; then run bootlinux; else echo Boot failed, because mmc${mmcdev} not found!;fi;</tt>
Line 45:		Line 45:
	== Activate Booting Update Kernel ==		== Activate Booting Update Kernel ==

	When the update image and the update-kernel is put onto the device, you can activate the update from inside the Linux. The following example assumes that the components of the update are on the third partition of the eMMC of an i.MX6 based DHSOM-module. The eMMC on the i.MX6 has the device number 2, other modules can ~~differ here~~ (like the AM335X: There the eMMC has the device number 1).		When the update image and the update-kernel is put onto the device, you can activate the update from inside the Linux. The following example assumes that the components of the update are on the third partition of the eMMC of an i.MX6 based DHSOM-module. The eMMC on the i.MX6 has the device number 2, on other modules this can be different (like the AM335X: There the eMMC has the device number 1).

	<tt>fw_setenv local_update true		<tt>fw_setenv local_update true
Line 61:		Line 61:
	fw_setenv src_dev_part</tt>		fw_setenv src_dev_part</tt>

	If the update fails the update tried again until <tt>local_update_tries</tt> hits the number in <tt>local_update_max_tries</tt>. After that the bootloader tries to boot the system as normal. You can see that the update was aborted from inside the Linux system if the variables <tt>local_update</tt> is <tt>true</tt> and <tt>local_update_tries</tt> contains the same number as <tt>local_update_max_tries</tt>. You can use the command <tt>fw_printenv</tt> to read the content of these variables.		If the update fails the update will be tried again until <tt>local_update_tries</tt> hits the number in <tt>local_update_max_tries</tt>. After that the bootloader tries to boot the system as normal. You can see that the update was aborted from inside the Linux system if the variables <tt>local_update</tt> is <tt>true</tt> and <tt>local_update_tries</tt> contains the same number as <tt>local_update_max_tries</tt>. You can use the command <tt>fw_printenv</tt> to read the content of these variables.