COM iMX6 Bootloader U-Boot - Revision history

Christoph: /* Downloads */

2020-05-11T07:07:12Z

Downloads

← Older revision		Revision as of 09:07, 11 May 2020
Line 12:		Line 12:

	== Downloads ==		== Downloads ==
	Please have a look at the[[~~COM_iMX6~~-D2#Download binaries/images\| i.MX6 Download binaries/images]] section.		Please have a look at the[[DHCOM iMX6-D2#Download binaries/images\| i.MX6 Download binaries/images]] section.

	== Enter Bootloader Console ==		== Enter Bootloader Console ==

Christoph: /* Building U-Boot (Version 2015.10 and older) */

2020-03-17T17:13:20Z

Building U-Boot (Version 2015.10 and older)

← Older revision		Revision as of 19:13, 17 March 2020
Line 635:		Line 635:
	Your new <tt>u-boot-with-spl.imx</tt> file is available in <tt>u-boot-imx6qdl/</tt>		Your new <tt>u-boot-with-spl.imx</tt> file is available in <tt>u-boot-imx6qdl/</tt>

	== Building U-Boot (~~Version 2015~~.10 ~~and older~~) ==		== Building U-Boot (based on v2015.10) ==
	=== Prepare Build Environment ===		=== Prepare Build Environment ===
	{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|		{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|
Line 648:		Line 648:
	3. <tt># ''git clone [https://github.com/dh-electronics/u-boot-imx6qdl.git https://github.com/dh-electronics/u-boot-imx6qdl.git]''</tt><br/>		3. <tt># ''git clone [https://github.com/dh-electronics/u-boot-imx6qdl.git https://github.com/dh-electronics/u-boot-imx6qdl.git]''</tt><br/>
	4. <tt># ''cd u-boot-imx6qdl''</tt><br/>		4. <tt># ''cd u-boot-imx6qdl''</tt><br/>
	5. <tt># ''git checkout dev/~~legacy/2018~~.~~05_dhcom~~''</tt>		5. <tt># ''git checkout dev/2015.10_dhcom''</tt>
	\|}		\|}

Line 654:		Line 654:
	{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|		{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|
	\|		\|
	6. <tt># ''~~make ARCH=arm CROSS_COMPILE=/opt/gcc-linaro-6.3.1-2017~~.~~05-x86_64_arm-linux-gnueabihf~~/~~bin/arm-linux-gnueabihf- dh_imx6_defconfig~~''</tt>~~<br/>~~		6. <tt># ''./uboot_make [q_d dl s s_1g]''</tt> # add argument 'dl' to build for Duallite (if unsure contact DH electronics)<br/>
	~~7. <tt>~~# ''~~make ARCH=arm CROSS_COMPILE=/opt/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- all''~~</tt>
	\|}		\|}
	Your new <tt>u-boot~~-with-spl~~.imx</tt> file is available in <tt>u-boot-imx6qdl/</tt>		* Your new <tt>u-boot.imx</tt> file is available in <tt>u-boot-imx6qdl/</tt>
			* If your build does fail please check content of uboot_make and adjust PATH.

Christoph at 16:57, 17 March 2020

2020-03-17T16:57:40Z

@@ Line 612: / Line 612: @@
 == Building U-Boot  ==
 === Prepare Build Environment ===
 {| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" |

Christoph: /* Building U-Boot */

2020-03-17T13:08:32Z

Building U-Boot

← Older revision		Revision as of 15:08, 17 March 2020
Line 613:		Line 613:
	== Building U-Boot ==		== Building U-Boot ==
	=== Prepare Build Environment ===		=== Prepare Build Environment ===
	* Download and start the Virtual Machine ~~based on Debian 8 (see [[COM_iMX6-D2#Downloads\| i.MX6 Downloads~~]])		{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|
	* Install Denx ELDK 5.4 to /opt (Available at [ftp://ftp.denx.de/pub/eldk/5.4/iso/ ftp://ftp.denx.de/pub/eldk/5.4/iso/]: we use eldk-5.4-armv7a.iso)		\|
			1. Download and start the [[Virtual Machine for Application Development]]
			\|}

	=== Get Sources ===		=== Get Sources ===
	{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|		{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|
	\|		\|
	1. Start a terminal on Linux<br/>		2. Start a terminal on Linux<br/>
	2. <tt># ''git clone [https://github.com/dh-electronics/u-boot-imx6qdl.git https://github.com/dh-electronics/u-boot-imx6qdl.git]''</tt><br/>		3. <tt># ''git clone [https://github.com/dh-electronics/u-boot-imx6qdl.git https://github.com/dh-electronics/u-boot-imx6qdl.git]''</tt><br/>
	3. <tt># ''cd u-boot-imx6qdl''</tt><br/>		4. <tt># ''cd u-boot-imx6qdl''</tt><br/>
	4. <tt># ''git checkout ~~release~~/~~v1.0.0~~.6'' ~~# checkout latest/required branch or tag~~</tt>		5. <tt># ''git checkout dev/legacy/2018.05_dhcom''</tt>
	\|}		\|}

	=== Start Build===		=== Start Build===
	{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|		{\| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" \|
	\|		\|
	6. <tt># ''./~~uboot_make [q_d dl s s_1g]~~''</tt> # ~~add argument~~ 'dl' ~~to build for Duallite (if unsure contact DH electronics)~~<br/>		6. <tt># ''make ARCH=arm CROSS_COMPILE=/opt/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- dh_imx6_defconfig''</tt><br/>
			7. <tt># ''make ARCH=arm CROSS_COMPILE=/opt/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- all''</tt>
	\|}		\|}
	* Your new <tt>u-boot.imx</tt> file is available in <tt>u-boot-imx6qdl/</tt>		Your new <tt>u-boot-with-spl.imx</tt> file is available in <tt>u-boot-imx6qdl/</tt>
	* If your build does fail please check content of uboot_make and adjust PATH.
	~~'''''Attention: Risk of bricking the Device!!'''''~~

Christoph: /* Display and Hardware settings */

2020-03-17T12:46:18Z

Display and Hardware settings

← Older revision		Revision as of 14:46, 17 March 2020
Line 569:		Line 569:
	:The DHCOM settings are used to setup display and special hardware parameters. For detailed description please have a look at [[DHCOM Settings\|'''How to create a settings.bin file''']].		:The DHCOM settings are used to setup display and special hardware parameters. For detailed description please have a look at [[DHCOM Settings\|'''How to create a settings.bin file''']].
	:The DHCOM settings file and the splash bitmap are loaded via the env variables "'''load_settings_bin'''" and "'''load_splash'''" during startup from boot partition. The default content of these env variables is:		:The DHCOM settings file and the splash bitmap are loaded via the env variables "'''load_settings_bin'''" and "'''load_splash'''" during startup from boot partition. The default content of these env variables is:
	settings_bin_file=~~default_settings~~.bin		settings_bin_file=settings.bin
	splash_file=splash.bmp		splash_file=splash.bmp
	load_settings_bin=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${settings_bin_file}		load_settings_bin=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${settings_bin_file}

Christoph: /* How to do Updates */

2020-03-17T12:42:17Z

How to do Updates

← Older revision		Revision as of 14:42, 17 March 2020
Line 563:		Line 563:

	==How to do Updates==		==How to do Updates==
	[[DHCOM Update Mechanism \|~~How to do Updates~~]]		[[DHCOM Update Mechanism\|DHCOM Update Mechanism]]

	== Display and Hardware settings ==		== Display and Hardware settings ==

Christoph: /* eMMC as USB Mass Storage */

2020-03-16T17:46:16Z

eMMC as USB Mass Storage

← Older revision		Revision as of 19:46, 16 March 2020
Line 542:		Line 542:
	:The uLinuxEnv.txt file should have unix line ending. Also make sure that there is an empty line at the end of the file.		:The uLinuxEnv.txt file should have unix line ending. Also make sure that there is an empty line at the end of the file.

	=== ~~eMMC as~~ USB Mass Storage ===		=== USB Mass Storage ===
	:'''Example: Write an image to the eMMC using the "ums" command:'''		:'''Use device as USB Mass Storage'''

			:{\| class="wikitable"
			\|''<code>ums <USB_controller> <devtype> <dev[:part]></code>''
			\|}

			:'''Example: Write an image on PDK2 to the eMMC using the "ums" command:'''
	:1. Connect the USB OTG on the PDK2 with a suitable cable to a computer running Debian Linux		:1. Connect the USB OTG on the PDK2 with a suitable cable to a computer running Debian Linux
	:2. Go to the U-Boot console on the module		:2. Go to the U-Boot console on the module

Christoph: /* Environment */

2020-03-16T17:32:39Z

Environment

← Older revision		Revision as of 19:32, 16 March 2020
Line 523:		Line 523:
	\|}		\|}

	:'''Revert to default ENV'''		:'''Revert to default ENV (all)'''

	:{\| class="wikitable"		:{\| class="wikitable"

Christoph: /* Environment */

2020-03-16T17:29:12Z

Environment

← Older revision		Revision as of 19:29, 16 March 2020
Line 451:		Line 451:
	:'''Show ENV variables'''		:'''Show ENV variables'''

	:{\| class="wikitable"		:{\| class="wikitable" style="float:left; margin-right:1em"
			\|-
	\|''<code>env print</code>''		\|''<code>env print</code>''
	\|}		\|}
			{\| style="float:left; margin-right:1em; margin-top:1em"
			\|-
			\|or
			\|}
			{\| class="wikitable" style="float:left; margin-right:1em"
			\|-
			\|''<code>printenv</code>''
			\|}




	bootdelay=0		bootdelay=0
Line 467:		Line 479:
	:'''Set ENV variables'''		:'''Set ENV variables'''

	:{\| class="wikitable"		:{\| class="wikitable" style="float:left; margin-right:1em"
			\|-
	\|''<code>env set <ENV name> <ENV value></code>''		\|''<code>env set <ENV name> <ENV value></code>''
	\|}		\|}
			{\| style="float:left; margin-right:1em; margin-top:1em"
			\|-
			\|or
			\|}
			{\| class="wikitable" style="float:left; margin-right:1em"
			\|-
			\|''<code>setenv <ENV name> <ENV value></code>''
			\|}




	:Example: <code>env set ipaddr 192.168.55.2</code>		:Example: <code>env set ipaddr 192.168.55.2</code>

	:Note: If you need to edit "bootcmd" it is necessary to insert ";" between the unique commands. ~~You can enter ";" at~~ the ~~command line with "\;"~~.		:Note: If you need to edit "bootcmd" it is necessary to insert <code>;</code> between the unique commands. Put the whole sequence in quotation marks <code>'...'</code>.

	:'''Save ENV variables'''		:'''Save ENV variables'''

	:{\| class="wikitable"		:{\| class="wikitable" style="float:left; margin-right:1em"
			\|-
	\|''<code>env save</code>''		\|''<code>env save</code>''
			\|}
			{\| style="float:left; margin-right:1em; margin-top:1em"
			\|-
			\|or
			\|}
			{\| class="wikitable" style="float:left; margin-right:1em"
			\|-
			\|''<code>saveenv</code>''
	\|}		\|}




	:'''Delete ENV variable'''		:'''Delete ENV variable'''
Line 499:		Line 536:

	:Example:		:Example:
	: <code>~~fatload~~ mmc 0 0x10000000 ~~uEnv~~.txt</code>		: <code>load mmc 0 0x10000000 uLinuxEnv.txt</code>
	: <code>env import -t 0x10000000 $filesize</code>		: <code>env import -t 0x10000000 $filesize</code>

	:Important:		:Important:
	:The ~~uEnv~~.txt file should ~~be in~~ unix ~~format~~. Also make sure that there is an empty line at the end of the file.		:The uLinuxEnv.txt file should have unix line ending. Also make sure that there is an empty line at the end of the file.

	~~bootargs=console=ttyO0,115200n8 root=/dev/mmcblk0p2 mem=128M rootwait~~
	~~bootcmd=mmc rescan; fatload mmc 0 0x82000000 uImage; bootm 0x82000000~~
	~~uenvcmd=boot~~

	=== eMMC as USB Mass Storage ===		=== eMMC as USB Mass Storage ===

Christoph: /* I2C */

2020-03-13T16:16:46Z

I2C

← Older revision		Revision as of 18:16, 13 March 2020
Line 402:		Line 402:

	=== I2C ===		=== I2C ===
			:'''Set current I2C bus'''

			:{\| class="wikitable"
			\|''<code>i2c dev <I2C bus></code>''
			\|}

			:Example: <code>i2c dev 0</code>

			:Description: Set current I2C bus to 0.

			Valid buses on i.MX6:
			0 = DHCOM I2C port 1
			1 = DHCOM I2C port 2
			2 = i.MX6 OnBoard I2C port

	:'''List available devices'''		:'''List available devices'''
Line 409:		Line 423:
	\|}		\|}

	~~Valid devices~~:		:Description: Test for and show device(s) on the I2C bus.
	~~0 = DHCOM~~ I2C ~~port 1~~
	~~1 = DHCOM I2C port 2~~		Valid chip addresses: 32 50 51 52 53 58 59
	~~2 = i.MX6 OnBoard I2C port~~

	:'''Read'''		:'''Read'''