DHCOM Flash Update - Revision history

Lzenz: /* Step by Step */

2017-08-21T09:24:09Z

Step by Step

← Older revision		Revision as of 11:24, 21 August 2017
Line 14:		Line 14:
	If you received an ''Update Image'' follow these steps to flash it to your target:		If you received an ''Update Image'' follow these steps to flash it to your target:
	[[File:Update_stick_v1.PNG\|thumb\|right\|200px\|Files on the update media]]		[[File:Update_stick_v1.PNG\|thumb\|right\|200px\|Files on the update media]]
	# untar or unzip (or just copy of not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick		# untar or unzip (or just copy if not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick
	#* see picture on the right for an example how your update media should look after this step		#* see picture on the right for an example how your update media should look after this step
	# plug your usb stick into the USB Host port of the target		# plug your usb stick into the USB Host port of the target
Line 24:		Line 24:
	# remove the usb stick		# remove the usb stick
	# done		# done

	== Pitfalls ==		== Pitfalls ==
	# Bootloader U-Boot does not recognice all types of usb sticks. FAT32 und MSDOS master boot record is required.		# Bootloader U-Boot does not recognice all types of usb sticks. FAT32 und MSDOS master boot record is required.

Lzenz: /* User Manual */

2017-08-21T07:57:29Z

User Manual

← Older revision		Revision as of 09:57, 21 August 2017
Line 11:		Line 11:

	= User Manual =		= User Manual =
			== Step by Step ==
	If you received an ''Update Image'' follow these steps to flash it to your target:		If you received an ''Update Image'' follow these steps to flash it to your target:
	[[File:Update_stick_v1.PNG\|thumb\|right\|200px\|Files on the update media]]		[[File:Update_stick_v1.PNG\|thumb\|right\|200px\|Files on the update media]]
Line 23:		Line 24:
	# remove the usb stick		# remove the usb stick
	# done		# done
			== Pitfalls ==
			# Bootloader U-Boot does not recognice all types of usb sticks. FAT32 und MSDOS master boot record is required.
			# ''Update Image'' is written to a subdirectory on the usb stick. This is not supported.

	= Modes =		= Modes =

Lzenz: /* User Manual */

2017-08-21T07:52:11Z

User Manual

← Older revision		Revision as of 09:52, 21 August 2017
Line 12:		Line 12:
	= User Manual =		= User Manual =
	If you received an ''Update Image'' follow these steps to flash it to your target:		If you received an ''Update Image'' follow these steps to flash it to your target:
			[[File:Update_stick_v1.PNG\|thumb\|right\|200px\|Files on the update media]]
	# untar or unzip (or just copy of not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick		# untar or unzip (or just copy of not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick
			#* see picture on the right for an example how your update media should look after this step
	# plug your usb stick into the USB Host port of the target		# plug your usb stick into the USB Host port of the target
	# switch on the power supply		# switch on the power supply
	# wait until the update has completed		# wait until the update has completed
	## progress can be followed at serial console		#* progress can be followed at serial console
	## or on the LCD Display (if you have any)		#* or on the LCD Display (if you have any)
	# switch off the power supply		# switch off the power supply
	# remove the usb stick		# remove the usb stick

Lzenz: /* User Manual */

2017-08-21T07:47:45Z

User Manual

← Older revision		Revision as of 09:47, 21 August 2017
Line 11:		Line 11:

	= User Manual =		= User Manual =
			If you received an ''Update Image'' follow these steps to flash it to your target:
			# untar or unzip (or just copy of not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick
			# plug your usb stick into the USB Host port of the target
			# switch on the power supply
			# wait until the update has completed
			## progress can be followed at serial console
			## or on the LCD Display (if you have any)
			# switch off the power supply
			# remove the usb stick
			# done

	= Modes =		= Modes =

Lzenz at 07:35, 21 August 2017

2017-08-21T07:35:15Z

← Older revision		Revision as of 09:35, 21 August 2017
Line 8:		Line 8:
	# Display adaptor EEPROM		# Display adaptor EEPROM

	If you are working with DHCOM AM335x or DHCOM i.MX6 please have a look at [[DHCOM_Update_Mechanism\|DHCOM Update Mechanism]].		If you are working with DHCOM AM335x or DHCOM i.MX6 please have a look at [[DHCOM_Update_Mechanism\|DHCOM Update Mechanism]].

	= ~~Overview~~ =		= User Manual =
	~~:[[Image:Flash Update Overview.png\|1020px]]~~

	= Modes =		= Modes =
	== ~~Automatically Update~~ ==		== Automatic Mode ==
	:Is called after the start of the bootloader if the environment variable '''bootcmd''' contains '''update auto'''. The functionality tries to update the flash content '''via the DHupdate.ini file''' (Please have a look at [[DHCOM Flash Update#DHupdate.ini file\|DHupdate.ini file]]). The update mechanism is searching for the update files on the specified storage devices. The update devices must be defined at the settings block (Please have a look at [[DHCOM Settings\|DHCOM settings]]). With the DHupdate.ini file you have the possibility to run more then one updates, e.g. OS image and settings block.		:Is called after the start of the bootloader if the environment variable '''bootcmd''' contains '''update auto'''. The functionality tries to update the flash content '''via the DHupdate.ini file''' (Please have a look at [[DHCOM Flash Update#DHupdate.ini file\|DHupdate.ini file]]). The update mechanism is searching for the update files on the specified storage devices. The update devices must be defined at the settings block (Please have a look at [[DHCOM Settings\|DHCOM settings]]). With the DHupdate.ini file you have the possibility to run more then one updates, e.g. OS image and settings block.

	== ~~Command line Update~~ ==		== Commandline Mode ==
	#Instruction: "update"		#Instruction: "update"
	#:The functionality tries to update the flash content '''via the 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'''. 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.
Line 74:		Line 73:
	::5 LED blinking interval = Specified file not valid (e.g. linux *.env file)		::5 LED blinking interval = Specified file not valid (e.g. linux *.env file)
	::6 LED blinking interval = Image file size is to large		::6 LED blinking interval = Image file size is to large

			= Overview - Flow Chart =
			:[[Image:Flash Update Overview.png\|1020px]]

Lzenz at 14:19, 22 March 2016

2016-03-22T14:19:05Z

← Older revision		Revision as of 16:19, 22 March 2016
Line 7:		Line 7:
	# WinCE image		# WinCE image
	# Display adaptor EEPROM		# Display adaptor EEPROM

			If you are working with DHCOM AM335x or DHCOM i.MX6 please have a look at [[DHCOM_Update_Mechanism\|DHCOM Update Mechanism]].

	= Overview =		= Overview =

Ageisreiter: /* Command line Update */

2014-07-14T13:52:09Z

Command line Update

Ageisreiter: /* Command line Update */

2014-07-14T13:49:46Z

Command line Update

Lzenz: /* Command line Update */

2012-09-27T05:38:47Z

Command line Update

← Older revision		Revision as of 07:38, 27 September 2012
Line 24:		Line 24:
	#::* linux = Linux image update + ENV update		#::* linux = Linux image update + ENV update
	#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.		#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
	#::* rootfs = Create or replace the linux root-filesystem which is stored in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the <code>reset</code> command) in the DHupdate.ini file. For further Details: [DHCOM Update: Linux Root Filesystem\|DHCOM Update: Linux Root Filesystem]		#::* rootfs = Create or replace the linux root-filesystem which is stored in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the <code>reset</code> command) in the DHupdate.ini file. For further Details: [[DHCOM Update: Linux Root Filesystem\|DHCOM Update: Linux Root Filesystem]]
	#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.		#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.
	#::* bootloader = Bootloader update		#::* bootloader = Bootloader update

Lzenz: /* Command line Update */

2012-09-27T05:38:07Z

Command line Update

← Older revision		Revision as of 07:38, 27 September 2012
Line 24:		Line 24:
	#::* linux = Linux image update + ENV update		#::* linux = Linux image update + ENV update
	#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.		#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
	#::* rootfs = Create or replace the root-filesystem in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the reset command) in the DHupdate.ini file.		#::* rootfs = Create or replace the linux root-filesystem which is stored in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the <code>reset</code> command) in the DHupdate.ini file. For further Details: [DHCOM Update: Linux Root Filesystem\|DHCOM Update: Linux Root Filesystem]
	#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.		#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.
	#::* bootloader = Bootloader update		#::* bootloader = Bootloader update

← Older revision		Revision as of 15:52, 14 July 2014
Line 21:		Line 21:
	#: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 <type> parameter you have to specify the update type.
	#:The <type> parameter could be specified as follows:		#:The <type> parameter could be specified as follows:
	#::* wince = WinCE image update + ENV update ~~(Not supported from i.MX6)~~		#::* wince = WinCE image update + ENV update
	#::* linux = Linux image update + ENV update		#::* linux = Linux image update + ENV update
	#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.		#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
Line 34:		Line 34:
	#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.		#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.
	#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.		#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.
	~~#::* script = run bootloader script file (Only supported from i.MX6)~~
	#:The [filename] parameter could be used to specify a non default filename. The default filenames are:		#:The [filename] parameter could be used to specify a non default filename. The default filenames are:
	#::* wince = default file names nk.gz or nk.bin		#::* wince = default file names nk.gz or nk.bin
Line 44:		Line 43:
	#::* eeprom = default file name eeprom.bin		#::* eeprom = default file name eeprom.bin
	#::* reset = no file to specify		#::* reset = no file to specify
	~~#::* script = default file name script.bin~~

	= DHupdate.ini file =		= DHupdate.ini file =

← Older revision		Revision as of 15:49, 14 July 2014
Line 21:		Line 21:
	#: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 <type> parameter you have to specify the update type.
	#:The <type> parameter could be specified as follows:		#:The <type> parameter could be specified as follows:
	#::* wince = WinCE image update + ENV update		#::* wince = WinCE image update + ENV update (Not supported from i.MX6)
	#::* linux = Linux image update + ENV update		#::* linux = Linux image update + ENV update
	#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.		#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
Line 34:		Line 34:
	#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.		#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.
	#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.		#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.
			#::* script = run bootloader script file (Only supported from i.MX6)
	#:The [filename] parameter could be used to specify a non default filename. The default filenames are:		#:The [filename] parameter could be used to specify a non default filename. The default filenames are:
	#::* wince = default file names nk.gz or nk.bin		#::* wince = default file names nk.gz or nk.bin
Line 43:		Line 44:
	#::* eeprom = default file name eeprom.bin		#::* eeprom = default file name eeprom.bin
	#::* reset = no file to specify		#::* reset = no file to specify
			#::* script = default file name script.bin

	= DHupdate.ini file =		= DHupdate.ini file =