BootLoader - Revision history

FabienM: /* Customizing */

2015-05-13T14:30:06Z

Customizing

← Older revision		Revision as of 16:30, 13 May 2015
Line 69:		Line 69:

	===Customizing===		===Customizing===
	*U-Boot build is done by the following Makefiles:		* U-Boot build is done by the following Makefiles:
	** ''buildroot/target/u-boot/Makefile.in'' (generic part)		** ''buildroot/target/u-boot/Makefile.in'' (generic part)
	** ''buildroot/target/device/armadeus/u-boot/u-boot.mk'' (target specific part)		** ''buildroot/target/device/armadeus/u-boot/u-boot.mk'' (target specific part)

	*Configuration file (target specific) used to customize the build is:		* Configuration file (target specific) used to customize the build is:
	** ''buildroot/target/device/armadeus/apfxx/apfxx-u-boot-<version>.h''		** ''buildroot/target/device/armadeus/apfxx/apfxx-u-boot-<version>.h''

			==== Autoboot keyed ====

			To stop autoboot with special keys or special word, add following lines in the apfxx-u-boot-<version>.h file :
			* after :
			<source lang="C">
			#define CONFIG_BOOTDELAY 2
			#define CONFIG_ZERO_BOOTDELAY_CHECK
			</source>
			* add :
			<source lang="C">
			#define CONFIG_AUTOBOOT_KEYED
			#define CONFIG_AUTOBOOT_PROMPT "autoboot in %d seconds\n",bootdelay
			#define CONFIG_AUTOBOOT_STOP_STR "v"
			</source>

			The autoboot delay will be stopped if «password» given by CONFIG_AUTOBOOT_STOP_STR be entered.

	==Install or restore from scratch (board bricked)==		==Install or restore from scratch (board bricked)==

YounesC: /* Modify your environment variables */

2013-06-12T14:37:10Z

Modify your environment variables

← Older revision		Revision as of 16:37, 12 June 2013
Line 42:		Line 42:
	setenv serverip 192.168.0.2 (the IP address of your TFTP Host server to download image files)		setenv serverip 192.168.0.2 (the IP address of your TFTP Host server to download image files)
	setenv rootpath "/tftpboot/apfXX-root" (to boot Linux over NFS)		setenv rootpath "/tftpboot/apfXX-root" (to boot Linux over NFS)
			setenv consoledev ttymxc0
	</pre>		</pre>
	* You can use the '''dhcp''' command to configure these variable from your DHCP server. Probably you will have to adjust the '''serverip''' variable manually.		* You can use the '''dhcp''' command to configure these variable from your DHCP server. Probably you will have to adjust the '''serverip''' variable manually.

Jorasse: /* Advanced Linux boot */

2013-03-09T14:08:51Z

Advanced Linux boot

← Older revision		Revision as of 16:08, 9 March 2013
Line 133:		Line 133:

	* MMC/SD boot		* MMC/SD boot
	Your SD should contain a rootfs and a kernel Linux in the /boot directory. ~~See http://www.armadeus.com/wiki/index.php?title=~~MultiMediaCard#Put_your_rootfs_and_Linux_kernel_on_the_MMC.2FSD for more information.		Your SD should contain a rootfs and a kernel Linux in the /boot directory. see [[MultiMediaCard#Put_your_rootfs_and_Linux_kernel_on_the_MMC.2FSD\| Put your rootfs and Linux kernel on the MMC/SD]] for more information.

	<pre class="apf">		<pre class="apf">

Jorasse: /* Advanced Linux boot */

2013-03-09T14:04:28Z

Advanced Linux boot

← Older revision		Revision as of 16:04, 9 March 2013
Line 133:		Line 133:

	* MMC/SD boot		* MMC/SD boot
			Your SD should contain a rootfs and a kernel Linux in the /boot directory. See http://www.armadeus.com/wiki/index.php?title=MultiMediaCard#Put_your_rootfs_and_Linux_kernel_on_the_MMC.2FSD for more information.

	<pre class="apf">		<pre class="apf">
	BIOS> run mmcboot		BIOS> run mmcboot

Jorasse: /* Links */

2012-06-20T22:10:45Z

Links

← Older revision		Revision as of 00:10, 21 June 2012
Line 165:		Line 165:
	==Links==		==Links==
	* http://www.denx.de/wiki/DULG/Manual		* http://www.denx.de/wiki/DULG/Manual
			* http://git.denx.de/?p=u-boot.git;a=blob_plain;f=tools/scripts/dot.kermrc

Jorasse: /* Binaries */ update target filenames

2012-04-04T13:12:05Z

Binaries: update target filenames

← Older revision		Revision as of 15:12, 4 April 2012
Line 64:		Line 64:
	===Binaries===		===Binaries===
	Compiled binary files will be put in the ''buildroot/output/images/'' subdirectory:		Compiled binary files will be put in the ''buildroot/output/images/'' subdirectory:
	* '''~~apfxx~~-u-boot.bin''' is a binary image file ~~that~~ can be downloaded and flashed from U-Boot itself (see below)		* '''apf9328-u-boot.bin''' is a binary image file for the apf9328that can be downloaded and flashed from U-Boot itself (see below)
			* (Armadeus 5.0) image filenames are respectively for each board '''apf27-u-boot-nand.bin''' '''apf51-u-boot-nand.bin''' '''apf28-u-boot.sb'''

	===Customizing===		===Customizing===

Jorasse at 15:54, 1 April 2012

2012-04-01T15:54:42Z

← Older revision		Revision as of 17:54, 1 April 2012
Line 28:		Line 28:

	Device 0: NAND 256MiB 1,8V 16-bit, sector size 128 KiB		Device 0: NAND 256MiB 1,8V 16-bit, sector size 128 KiB
	~~</pre>~~

	~~<pre class="apf">~~
	~~BIOS> i2c probe~~
	~~Valid chip addresses: 38 39 3F 50 51 52 53 54 55 56 57 7F~~
	~~Excluded chip addresses:~~
	</pre>		</pre>

Line 47:		Line 41:
	setenv ipaddr 192.168.0.10		setenv ipaddr 192.168.0.10
	setenv serverip 192.168.0.2 (the IP address of your TFTP Host server to download image files)		setenv serverip 192.168.0.2 (the IP address of your TFTP Host server to download image files)
	setenv rootpath "/tftpboot/~~apf9328~~-root" (to boot Linux over NFS)		setenv rootpath "/tftpboot/apfXX-root" (to boot Linux over NFS)
	</pre>		</pre>
	* You can use the '''dhcp''' command to configure these variable from your DHCP server. Probably you will have to adjust the '''serverip''' variable manually.		* You can use the '''dhcp''' command to configure these variable from your DHCP server. Probably you will have to adjust the '''serverip''' variable manually.
Line 65:		Line 59:
	Build process is now part of the Armadeus automated build (see [[Toolchain \| Install Armadeus software]]). To only build U-Boot you can launch:		Build process is now part of the Armadeus automated build (see [[Toolchain \| Install Armadeus software]]). To only build U-Boot you can launch:
	<pre class="host">		<pre class="host">
	$ make u-~~boot-clean~~		$ make uboot-rebuild
	~~$ make u-boot~~
	</pre>		</pre>

	===Binaries===		===Binaries===
	Compiled binary files will be put in the ''buildroot/~~binaries~~/~~apfxx~~/'' subdirectory:		Compiled binary files will be put in the ''buildroot/output/images/'' subdirectory:
	* '''apfxx-u-boot.bin''' is a binary image file that can be downloaded and flashed from U-Boot itself (see below)		* '''apfxx-u-boot.bin''' is a binary image file that can be downloaded and flashed from U-Boot itself (see below)
	* '''apf9328-u-boot-brec''' is a boostrap record file compatible with the [[BootStrap \| Freescale bootstrap]] inside the i.MXL (only when compiling for [[APF9328]]).

	===Customizing===		===Customizing===
Line 80:		Line 72:

	*Configuration file (target specific) used to customize the build is:		*Configuration file (target specific) used to customize the build is:
	** ''buildroot/target/device/armadeus/apfxx/apfxx.h''		** ''buildroot/target/device/armadeus/apfxx/apfxx-u-boot-<version>.h''

	==Install or restore from scratch (board bricked)==		==Install or restore from scratch (board bricked)==
Line 93:		Line 85:
	There are 2 steps to update U-Boot:		There are 2 steps to update U-Boot:
	*1] Load the new U-Boot code in RAM (You can use the following commands to download U-boot):		*1] Load the new U-Boot code in RAM (You can use the following commands to download U-boot):
	**With ethernet and a [[Connection_with_U-Boot_on_Linux#TFTP_server \|TFTP server]]: <pre class="apf">BIOS> ~~tftpboot ${loadaddr} apfxx-u-boot.bin~~</pre>		**With ethernet and a [[Connection_with_U-Boot_on_Linux#TFTP_server \|TFTP server]]: <pre class="apf">BIOS>run download_uboot</pre>
	**With ethernet and a [[Network_Configuration \| NFS server]]: <pre class="apf">BIOS> nfs ${loadaddr} ${serverip}:/~~nfs_path_to_buildroot~~/apfxx-u-boot.bin</pre>		**With ethernet and a [[Network_Configuration \| NFS server]]: <pre class="apf">BIOS> nfs ${loadaddr} ${serverip}:/tftpboot/apfxx-u-boot.bin</pre>
	**With the kermit and a serial line:		**With the kermit and a serial line:
	<pre class="apf">		<pre class="apf">
Line 113:		Line 105:
	The command "boot" is the common way to run Linux from flash memory.		The command "boot" is the common way to run Linux from flash memory.
	This command is equivalent to the macro:		This command is equivalent to the macro:
			- on the APF9328 board
	<pre class="apf">		<pre class="apf">
	BIOS> run jffsboot		BIOS> run jffsboot
			</pre>
			- on the other APF board
			<pre class="apf">
			BIOS> run ubifsboot
	</pre>		</pre>

Line 121:		Line 118:
	BIOS> printenv bootcmd		BIOS> printenv bootcmd
	bootcmd=run jffsboot		bootcmd=run jffsboot
			or
			bootcmd=run ubifsboot
	</pre>		</pre>
	U-Boot also supports the commands to boot from the network or a SD/MMC card.		U-Boot also supports the commands to boot from the network or a SD/MMC card.
Line 130:		Line 129:
	This command boots Linux rootfs from a NFS server. Change the U-Boot variables ''serverip'' and ''rootpath'' to fit with your host PC.		This command boots Linux rootfs from a NFS server. Change the U-Boot variables ''serverip'' and ''rootpath'' to fit with your host PC.
	serverip=192.168.0.2		serverip=192.168.0.2
	rootpath="/tftpboot/~~apf9328~~-root"		rootpath="/tftpboot/apfXX-root"

	* MMC/SD boot		* MMC/SD boot
Line 136:		Line 135:
	BIOS> run mmcboot		BIOS> run mmcboot
	</pre>		</pre>
	~~This command boots Linux rootfs from an sd/mmc memory card. Adapt the variables: ''mmcroot'' and ''mmcrootfstype'' to your card's boot partition type.~~
	~~mmcroot=/dev/mmcblk0p1~~
	~~mmcrootfstype=ext2~~

	~~==Customize the flash memory organization==~~
	~~TBD~~
	== Installing Target software from U-Boot ==		== Installing Target software from U-Boot ==

JulienB: /* Introduction */

2009-10-29T10:03:30Z

Introduction

← Older revision		Revision as of 12:03, 29 October 2009
Line 2:		Line 2:

	This page describe the U-Boot usage/installation in the Armadeus context.		This page describe the U-Boot usage/installation in the Armadeus context.

			==Some (informational) commands==
			<pre class="apf">
			BIOS> printenv
			</pre>

			<pre class="apf">
			BIOS> bdinfo
			arch_number = 0x000006A2
			env_t = 0x00000000
			boot_params = 0xA0000100
			DRAM bank = 0x00000000
			-> start = 0xA0000000
			-> size = 0x04000000
			DRAM bank = 0x00000001
			-> start = 0xB0000000
			-> size = 0x04000000
			ethaddr = 00:1E:AC:00:10:54
			ip_addr = 192.168.1.10
			baudrate = 115200 bps
			</pre>

			<pre class="apf">
			BIOS> nand info

			Device 0: NAND 256MiB 1,8V 16-bit, sector size 128 KiB
			</pre>

			<pre class="apf">
			BIOS> i2c probe
			Valid chip addresses: 38 39 3F 50 51 52 53 54 55 56 57 7F
			Excluded chip addresses:
			</pre>

	==Modify your environment variables==		==Modify your environment variables==

JulienB: /* Introduction */

2009-10-29T09:50:33Z

Introduction

← Older revision		Revision as of 11:50, 29 October 2009
Line 1:		Line 1:
	==Introduction==		==Introduction==

	This page describe the U-Boot installation~~/usage~~ in the Armadeus context.		This page describe the U-Boot usage/installation in the Armadeus context.

	==Modify your environment variables==		==Modify your environment variables==

JulienB: move build part

2009-10-29T09:50:08Z

move build part

@@ Line 2: / Line 2: @@
 This page describe the U-Boot installation/usage in the Armadeus context.
 ==Build U-Boot==
@@ Line 28: / Line 54: @@
 In that case the ''uboot_recover'' python script is used to flash a new U-Boot version; this tool is located in the ''armadeus/software/uboot_recover/'' folder of the Armadeus project tree.<br>
 Take a look a the ''INSTALL'' file the first time you want to use the recover tool.<br>
-Remark: the serial port must support a baud rate of 57600 bps per second.<br>
+Remark: the serial port must support a baud rate of 57600 bps per second.
 ==Update U-Boot==