DHCOM Update Mechanism - Revision history

Christoph: /* Commandline Mode */

2020-03-03T12:01:59Z

Commandline Mode

← Older revision		Revision as of 14:01, 3 March 2020
Line 61:		Line 61:
	\|valign="top"\| <tt>bootloader</tt> \|\| update the bootloader		\|valign="top"\| <tt>bootloader</tt> \|\| update the bootloader
	:Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.		:Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.
	Default file name = u-boot.imx/u-boot-with-spl.imx (i.MX6) / u-boot.img (AM335x)		Default file name = u-boot.imx (i.MX6) / u-boot-with-spl.imx (i.MX6 \| i.MX6ULL) / u-boot.img (AM335x)
	\|-		\|-
	\|\| <tt>script</tt> \|\| bootloader executes the provided bootloader script e.g. to customize bootloader environment variables		\|\| <tt>script</tt> \|\| bootloader executes the provided bootloader script e.g. to customize bootloader environment variables

Christoph: /* Commandline Mode */

2020-03-03T12:00:25Z

Commandline Mode

← Older revision		Revision as of 14:00, 3 March 2020
Line 61:		Line 61:
	\|valign="top"\| <tt>bootloader</tt> \|\| update the bootloader		\|valign="top"\| <tt>bootloader</tt> \|\| update the bootloader
	:Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.		:Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.
	Default file name = u-boot.imx (i.MX6) / u-boot.img (AM335x)		Default file name = u-boot.imx/u-boot-with-spl.imx (i.MX6) / u-boot.img (AM335x)
	\|-		\|-
	\|\| <tt>script</tt> \|\| bootloader executes the provided bootloader script e.g. to customize bootloader environment variables		\|\| <tt>script</tt> \|\| bootloader executes the provided bootloader script e.g. to customize bootloader environment variables

Christoph: /* Flowchart of the Update Process */

2020-02-24T13:28:19Z

Flowchart of the Update Process

← Older revision		Revision as of 15:28, 24 February 2020
Line 179:		Line 179:
	= Flowchart of the Update Process =		= Flowchart of the Update Process =

	:[[Image:Flash Update Overview.png\|~~1020px~~]]		:[[Image:Flash Update Overview.png\|1750px]]

Christoph: /* Example */

2020-02-24T13:25:49Z

Example

← Older revision		Revision as of 15:25, 24 February 2020
Line 131:		Line 131:

	'''Notes:'''		'''Notes:'''
	:*It is necessary to use UNIX End Of Line conversion!!!		:*<font color="#C90646">It is necessary to use UNIX End Of Line conversion!!!</font>
	:*The order of the bitmap-filenames in the section <code>display</code> tells the system when to display which bitmap.		:*The order of the bitmap-filenames in the section <code>display</code> tells the system when to display which bitmap.
	:*If you use "refresh" command, please ensure that settings bin update is listed in DHupdate.ini file before "refresh" command.		:*If you use "refresh" command, please ensure that settings bin update is listed in DHupdate.ini file before "refresh" command.

Christoph: /* Syntax */

2020-02-24T13:24:57Z

Syntax

← Older revision		Revision as of 15:24, 24 February 2020
Line 77:		Line 77:
	The DHupdate.ini file is a ASCII text file, which controls the update mechanism.		The DHupdate.ini file is a ASCII text file, which controls the update mechanism.
	== Syntax ==		== Syntax ==
	:[[Image:DHupdate_file_layout.png\|~~700px~~]]		:[[Image:DHupdate_file_layout.png\|800px]]

	:The <type> parameter could be specified as follows:		:The <type> parameter could be specified as follows:
Line 111:		Line 111:
	: Note: If you update the DHCOM settings, it is possible to use the new settings for the update progress notifications on the display, by inserting the "refresh" command to the [update] section. The bootloader loads the new settings and calls the '''update kernel''' with the new parameters.		: Note: If you update the DHCOM settings, it is possible to use the new settings for the update progress notifications on the display, by inserting the "refresh" command to the [update] section. The bootloader loads the new settings and calls the '''update kernel''' with the new parameters.
	\|}		\|}

	== Example ==		== Example ==
	##DHCOMupdate##		##DHCOMupdate##

Christoph: /* Downloads */

2020-02-24T13:22:26Z

Downloads

← Older revision		Revision as of 15:22, 24 February 2020
Line 42:		Line 42:

	= Downloads =		= Downloads =
	For the ~~Update Kernel~~ please have a look at the [[COM_iMX6-D2#Downloads\| i.MX6 Downloads]], [[COM_iMX6ULL-D2#Downloads\| i.MX6ULL Downloads]] or [[COM_AM335-D2#Downloads\| AM335x Downloads]] section.		For the "'''''update kernel'''''" please have a look at the [[COM_iMX6-D2#Downloads\| i.MX6 Downloads]], [[COM_iMX6ULL-D2#Downloads\| i.MX6ULL Downloads]] or [[COM_AM335-D2#Downloads\| AM335x Downloads]] section.

	= Execution Modes =		= Execution Modes =

Christoph: /* Downloads */

2020-02-24T13:21:22Z

Downloads

← Older revision		Revision as of 15:21, 24 February 2020
Line 42:		Line 42:

	= Downloads =		= Downloads =
	~~Please~~ have a look at the [[COM_iMX6-D2#Downloads\| i.MX6 Downloads]], [[COM_iMX6ULL-D2#Downloads\| i.MX6ULL Downloads]] or [[COM_AM335-D2#Downloads\| AM335x Downloads]] section.		For the Update Kernel please have a look at the [[COM_iMX6-D2#Downloads\| i.MX6 Downloads]], [[COM_iMX6ULL-D2#Downloads\| i.MX6ULL Downloads]] or [[COM_AM335-D2#Downloads\| AM335x Downloads]] section.

	= Execution Modes =		= Execution Modes =

Christoph: /* Commandline Mode */

2020-02-24T13:20:52Z

Commandline Mode

← Older revision		Revision as of 15:20, 24 February 2020
Line 70:		Line 70:
	\|-		\|-
	\|\| <tt>reset</tt> \|\| reboot system after a successful update. A reset can only be the last item in a DHupdate.ini file.		\|\| <tt>reset</tt> \|\| reboot system after a successful update. A reset can only be the last item in a DHupdate.ini file.
	:Warning: ~~risk~~ of a infinite update loop.		<font color="#C90646">Warning: Risk of a infinite update loop.</font>
	\|-		\|-
	\|}		\|}

Christoph: /* Commandline Mode */

2020-02-24T13:18:43Z

Commandline Mode

← Older revision		Revision as of 15:18, 24 February 2020
Line 52:		Line 52:
	*:The functionality tries to update the flash content via the [[#DHupdate.ini file\|'''DHupdate.ini file''']]. In contrast to Automatically Update (which you can start with "'''update auto'''") the update mechanism is searching on every available storage device for the update files.		*:The functionality tries to update the flash content via the [[#DHupdate.ini file\|'''DHupdate.ini file''']]. In contrast to Automatically Update (which you can start with "'''update auto'''") the update mechanism is searching on every available storage device for the update files.
	*Instruction: "'''update <command> [filename]'''"		*Instruction: "'''update <command> [filename]'''"
	*:The functionality '''doesn't use the DHupdate.ini file'''. It allows only one update and the update mechanism is searching on every available storage device for the update files. With the <~~type~~> parameter you have to specify the update type.		*:The functionality '''doesn't use the DHupdate.ini file'''. It allows only one update and the update mechanism is searching on every available storage device for the update files. With the <command> parameter you have to specify the update type. If no [filename] is passed, the default file name will be used.
	::The following <command> parameters are possible from command line:		::The following <command> parameters are possible from command line:
	:::{\| class="wikitable" \| style="width: 50%; color: #000000; background: #f3f3f3;" valign="top" \|		:::{\| class="wikitable" \| style="width: 50%; color: #000000; background: #f3f3f3;" valign="top" \|
Line 61:		Line 61:
	\|valign="top"\| <tt>bootloader</tt> \|\| update the bootloader		\|valign="top"\| <tt>bootloader</tt> \|\| update the bootloader
	:Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.		:Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.
			Default file name = u-boot.imx (i.MX6) / u-boot.img (AM335x)
	\|-		\|-
	\|\| <tt>script</tt> \|\| bootloader executes the provided bootloader script e.g. to customize bootloader environment variables		\|\| <tt>script</tt> \|\| bootloader executes the provided bootloader script e.g. to customize bootloader environment variables
			default file name = script.bin
	\|-		\|-
	\|\| <tt>eeprom</tt> \|\| update the display timings stored in the display adapter EEPROM		\|\| <tt>eeprom</tt> \|\| update the display timings stored in the display adapter EEPROM
			default file name = eeprom.bin
	\|-		\|-
	\|\| <tt>reset</tt> \|\| reboot system after a successful update. A reset can only be the last item in a DHupdate.ini file.		\|\| <tt>reset</tt> \|\| reboot system after a successful update. A reset can only be the last item in a DHupdate.ini file.
	:Warning: risk of a infinite update loop.		:Warning: risk of a infinite update loop.
	\|-
	\|}

	~~::The [filename] parameter could be used to specify a non default filename. The default filenames are:~~
	~~:::{\| class="wikitable" \| style="width: 40%; color: #000000; background: #f3f3f3;" valign="top" \|~~
	\|-
	~~\| style="background: #076b8d;" \| '''''command'''''~~
	~~\| style="background: #076b8d;" \| '''''default filename'''''~~
	\|-
	~~\|\| <tt>bootloader</tt> \|\| default file name is u-boot.imx (i.MX6) / u-boot.img (AM335x)~~
	\|-
	~~\|\| <tt>script</tt> \|\| default file name is script.bin~~
	\|-
	~~\|\| <tt>eeprom</tt> \|\| default file name is eeprom.bin~~
	\|-
	~~\|\| <tt>reset</tt> \|\| no file to specify~~
	\|-		\|-
	\|}		\|}

Christoph: /* Downloads */

2020-02-24T13:09:12Z

Downloads

← Older revision		Revision as of 15:09, 24 February 2020
Line 42:		Line 42:

	= Downloads =		= Downloads =
	Please have a look at the[[COM_iMX6-D2#Downloads\| i.MX6 Downloads]] or [[COM_AM335-D2#Downloads\| AM335x Downloads]] section.		Please have a look at the [[COM_iMX6-D2#Downloads\| i.MX6 Downloads]], [[COM_iMX6ULL-D2#Downloads\| i.MX6ULL Downloads]] or [[COM_AM335-D2#Downloads\| AM335x Downloads]] section.

	= Execution Modes =		= Execution Modes =