Loading Images with U-Boot - Revision history

Mgloff at 18:32, 15 April 2021

2021-04-15T18:32:15Z

Mgloff at 19:26, 15 April 2019

2019-04-15T19:26:35Z

Mgloff at 17:39, 15 April 2019

2019-04-15T17:39:17Z

Mgloff at 17:33, 15 April 2019

2019-04-15T17:33:24Z

Mgloff at 17:27, 15 April 2019

2019-04-15T17:27:27Z

Mgloff at 20:28, 17 November 2015

2015-11-17T20:28:33Z

Kyoungmeyer: One addition made. Final Draft.

2015-11-17T19:53:32Z

One addition made. Final Draft.

Mdean: Noted missing content, added Conclusion and where next, and marked for Review.

2015-11-13T23:35:10Z

Noted missing content, added Conclusion and where next, and marked for Review.

Rossi at 23:08, 13 November 2015

2015-11-13T23:08:11Z

Rossi at 23:02, 13 November 2015

2015-11-13T23:02:08Z

@@ Line 11: / Line 11: @@
 == Configuration ==
-In order to load a file using TFTP, U-Boot must be configured to access the local network. Static networking configuration or DHCP can be used on some systems (requires DHCP server). Typically, the IP address of the board and the IP address of the TFTP server are the only settings that need to be defined. The network mask and broadcast address will be determined automatically from these settings, and no default gateway setting is required if the server is on the same subnetwork as the board. Before continuing, determine a valid static network address for your local network; contact your IT department for more information on what address to use if required. The example below shows how to set the IP address of the board to 192.168.2.2 and the TFTP server IP address to 192.168.2.1:
+In order to load a file using TFTP, U-Boot must be configured to access the local network. Static networking configuration or DHCP can be used on some systems (requires DHCP server). Typically, the IP address of the board and the IP address of the TFTP server are the only settings that need to be defined. The network mask and broadcast address will be determined automatically from these settings, and no default gateway setting is required if the server is on the same subnetwork as the board. Before continuing, determine a valid static network address for your local network; contact your IT department for more information on what address to use if required. The example below shows the use of DHCP and setting the TFTP server IP address to 192.168.2.1
 {{clop}}<nowiki>U-Boot> setenv ipaddr 192.168.2.2
-U-Boot> setenv serverip 192.168.2.1
+U-Boot> setenv serverip 192.168.2.1</nowiki>{{closp}}
-U-Boot> saveenv
 Once the network settings have been configured, attempt to ping the TFTP server to test the network connection as illustrated below:

@@ Line 1: / Line 1: @@
 {{#seo:
 |title=Loading Images with U-Boot
@@ Line 33: / Line 25: @@
 == Loading Images to RAM ==
-Files are loaded directly into RAM through TFTP. In order to load the image, you must know the physical address of the RAM device on the system. Refer to the documentation for your target board if you are unsure what value to use. The standard addresses for some common EMAC systems are shown in Table 1 below.
+Files are loaded directly into RAM through TFTP. In order to load the image, you must know the physical address of the RAM device on the system. Refer to the documentation for your target board if you are unsure what value to use. The U-Boot environment variable <code>loadaddr</code> should already be set and can be used in place of the hex addresses below. The standard addresses for some common EMAC systems are shown in Table 1 below.
 {| class="wikitable"
@@ Line 68: / Line 60: @@
 The <code>tftp</code> U-Boot command is used to transfer files to the system. The command requires two arguments: the address to load the file into and the filename of the image on the TFTP server. The example below demonstrates loading a kernel image named <code>uImage-2.6.30</code> to RAM on an SoM-9G45M.
-{{clop}}<nowiki>U-Boot> tftp 0x70000000 uImage-2.6.30
+{{clop}}<nowiki>U-Boot> tftp ${loadaddr} uImage-2.6.30
 macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
 Using macb0 device

@@ Line 89: / Line 89: @@
 In some situations, it is advantageous to execute the image directly from RAM after loading with TFTP rather than saving to flash. This is especially helpful when testing new Linux kernel images. Furthermore, the boot command can be set such that the image is automatically downloaded and executed on each boot, making testing more efficient.
-After loading a bootable image to RAM, you can execute it directly using the <code>bootm</code> command. For example, after loading the kernel image above, running <code>bootm 0x70000000</code> would boot the board using the new image without making any changes to the images stored on the flash.
+After loading a bootable image to RAM, you can execute it directly using the <code>bootm</code> command for a uImage kernel or <code>bootz</code> for a zImage kernel. For example, after loading the kernel image above, running <code>bootm 0x70000000</code> would boot the board using the new image without making any changes to the images stored on the flash.
 To update the <code>bootcmd</code> variable to download the image on each boot, simply replace the command used to load the image from flash with the TFTP download command. The following example illustrates this process on an SoM-9G45M module.

@@ Line 59: / Line 59: @@
 |-
 | SoM-3354M || 0x82000000
 |}
@@ Line 93: / Line 97: @@
 U-Boot> saveenv
 Saving Environment to dataflash...</nowiki>{{closp}}
 == Copying to Flash ==

@@ Line 132: / Line 132: @@
 U-Boot> tftp ${loadaddr} zImage
 U-Boot> sf probe;sf erase 0x100000 +${filesize};sf write ${loadaddr} 0x100000 ${filesize}
-U-Boot> set kernelsize ${filesize};saveenv</nowiki>{{closp}}
+U-Boot> setenv kernelsize ${filesize};saveenv</nowiki>{{closp}}
 Note: the "pri loadaddr" step above is not required it is just entered to make sure the variable is set.

@@ Line 1: / Line 1: @@
-{{todo|FinalDraft (12.16.13-01:25->MD-);(12.31.13-11:02->MW+);(12.31.13-11:30->KY+);(12.31.13-11:35->MG+);(03.06.14-15:30->BS-);(04.11.14-15:55->BS+)(11.06.15-12:45->MG+)(11.13.2015-13:25->MD-);(11.13.2015-16:39->ER+);(11.13.2015-17:30->MD+);(11.17.2015-13:50->KY+)|Michael Welling|project=oe 4,oe 5,mw,md,ky,mg,bs,er,FinalDraft}}
+{{todo|Complete (12.16.13-01:25->MD-);(12.31.13-11:02->MW+);(12.31.13-11:30->KY+);(12.31.13-11:35->MG+);(03.06.14-15:30->BS-);(04.11.14-15:55->BS+)(11.06.15-12:45->MG+)(11.13.2015-13:25->MD-);(11.13.2015-16:39->ER+);(11.13.2015-17:30->MD+);(11.17.2015-13:50->KY+);(11.17.2015-14:30->MG+)|Michael Welling|project=oe 4,oe 5,mw,md,ky,mg,bs,er,Complete}}
 <!-- NOTE: WE ARE STILL MISSING THE FOLLOWING CONTENT:
@@ Line 183: / Line 183: @@
 The image file can now be transferred to the board and executed as illustrated below:
-{{clo}}<nowiki>U-Boot> tftp 0x20000000 sl013-aon-30010-flash-script.img
+{{clop}}<nowiki>U-Boot> tftp 0x20000000 sl013-aon-30010-flash-script.img
 U-Boot> source 0x20000000</nowiki>{{closp}}

@@ Line 1: / Line 1: @@
-{{todo|Review (12.16.13-01:25->MD-);(12.31.13-11:02->MW+);(12.31.13-11:30->KY+);(12.31.13-11:35->MG+);(03.06.14-15:30->BS-);(04.11.14-15:55->BS+)(11.06.15-12:45->MG+)(11.13.2015-13:25->MD-);(11.13.2015-16:39->ER+);(11.13.2015-17:30->MD+)|Michael Welling|project=oe 4,oe 5,mw,md,ky,mg,bs,er,Review}}
+{{todo|FinalDraft (12.16.13-01:25->MD-);(12.31.13-11:02->MW+);(12.31.13-11:30->KY+);(12.31.13-11:35->MG+);(03.06.14-15:30->BS-);(04.11.14-15:55->BS+)(11.06.15-12:45->MG+)(11.13.2015-13:25->MD-);(11.13.2015-16:39->ER+);(11.13.2015-17:30->MD+);(11.17.2015-13:50->KY+)|Michael Welling|project=oe 4,oe 5,mw,md,ky,mg,bs,er,FinalDraft}}
 <!-- NOTE: WE ARE STILL MISSING THE FOLLOWING CONTENT:
@@ Line 177: / Line 177: @@
 Note that the script assumes that <code>mkimage</code> is installed in the user's PATH. The script should be run with the name of the existing file as the first argument and the desired output filename as the second argument:
-{{cli|./script_mkimage.sh sl013-aon-30010-flash-script sl013-aon-30010-flash-script.img}}
+{{cli|username=developer|hostname=ldc|./script_mkimage.sh sl013-aon-30010-flash-script sl013-aon-30010-flash-script.img}}
-Once an image file has been created, it can be transferred to the board and executed as illustrated below:
+Once an image file has been created, it should be copied to the TFTP server root directory, in this example <code>/srv/tftp</code> is used.
 {{clo}}<nowiki>U-Boot> tftp 0x20000000 sl013-aon-30010-flash-script.img
 U-Boot> source 0x20000000</nowiki>{{closp}}

@@ Line 1: / Line 1: @@
-{{todo|Buggy (12.16.13-01:25->MD-);(12.31.13-11:02->MW+);(12.31.13-11:30->KY+);(12.31.13-11:35->MG+);(03.06.14-15:30->BS-);(04.11.14-15:55->BS+)(11.06.15-12:45->MG+)(11.13.2015-13:25->MD-);(11.13.2015-16:39->ER+)|Michael Welling|project=oe 4,oe 5,mw,md,ky,mg,bs,er,Buggy}}
+{{todo|Review (12.16.13-01:25->MD-);(12.31.13-11:02->MW+);(12.31.13-11:30->KY+);(12.31.13-11:35->MG+);(03.06.14-15:30->BS-);(04.11.14-15:55->BS+)(11.06.15-12:45->MG+)(11.13.2015-13:25->MD-);(11.13.2015-16:39->ER+);(11.13.2015-17:30->MD+)|Michael Welling|project=oe 4,oe 5,mw,md,ky,mg,bs,er,Review}}
 {{#seo:
@@ Line 10: / Line 16: @@
 == Requirements ==
-A TFTP server must be accessible on the local network. The specific details of TFTP server setup and configuration can be found on the [[Installing TFTP server]] page. Alternatively, NFS can be used in place of TFTP but will require an NFS server.  Please contact EMAC if you need details on how to use NFS instead of TFTP to load images.
+A TFTP server must be accessible on the local network. The specific details of TFTP server setup and configuration can be found on the [[Installing TFTP server]] page. Alternatively, NFS can be used in place of TFTP but will require an NFS server.  Information on how to set up an NFS server [[Setting_up_an_NFS_File_Server | can be found here]].  Please contact EMAC if you need details on how to use NFS instead of TFTP to load images.
 == Configuration ==
@@ Line 88: / Line 94: @@
 Saving Environment to dataflash...</nowiki>{{closp}}
 {{ warning | All these hard coded addresses don't contribute much to the reader's understanding of what each address is for...  especially 0xC0042000, since it's not mentioned elsewhere, and ones that may happen to be the same number for different reasons.}}
 == Copying to Flash ==
@@ Line 179: / Line 187: @@
 U-Boot will execute all commands in the script line-by-line until the script has finished, at which point the U-boot prompt will be returned to the user.
-{{warning | Needs "Where to Go Next"}}
+<!-- /*********************************************************************************************************/ -->
 <!--[[Category:Bootloaders]]-->

@@ Line 126: / Line 126: @@
 U-Boot> set kernelsize ${filesize};saveenv</nowiki>{{closp}}
-Note: the "pri loadaddr" step about is not required it is just entered to make sure the variable is set.
+Note: the "pri loadaddr" step above is not required it is just entered to make sure the variable is set.
 == Scripting ==