Installing Linux Images to Flash Print


This note explains how to install a bootable Linux image to the NOR Flash on the STM32F7 System-On-Module (SOM). Having installed a Linux image to the Flash, you would be able to boot Linux on the target automatically on any power up or reset cycle. This is the mode of operation that is typically used for deployed production units.

It should be noted that all STM32F7 SOMs come with a default Linux image preloaded to the Flash. This is the same networking.uImage that is included in the Emcraft software distribution (refer to STM32F7 System-On-Module Release Materials). Clearly, as you proceed to develop your Linux applications against your specific requirements, you will need a way to install an updated Linux image to the target for deployment. This note explains how to do that.

The example below refers to networking.uImage. This image is included as a prebuilt binary in the software distribution so you can always use it to revert to the factory default software, should you decide to do that for some reason. For instance, you may want to do that in order to validate an I/O interface supported by the networking project. As mentioned above though, the process below will work for any uImage you build using the Emcraft software distribution.

Before you proceed to install an uImage to the NOR Flash, it probably makes sense to verify that what you have is indeed a bootable Linux image. You can do that by loading the image to the target from the network using the run netboot command (refer to Loading Linux Images via Ethernet and TFTP). It is important to understand that the same uImage that you load via TFTP can be loaded from the Flash as well. It doesn't make sense to install an uImage to the Flash unless you have validated the image by loading it via Ethernet and TFTP.

The U-Boot command sequence required to install a uImage to the NOR Flash is defined for you by the U-Boot environment variable called update. Here is how update is defined in U-Boot by default:

STM32F7-SOM> print update
update=tftp ${image};prot off ${flashaddr} +${filesize};era ${flashaddr} +${filesize};cp.b ${loadaddr} ${flashaddr} ${filesize};setenv kernelsize ${filesize};setenv filesize; setenv fileaddr;saveenv
STM32F7-SOM>

You will notice that the first command in update is a tftpboot command to download an image from the network via Ethernet and TFTP. Please refer to Loading Linux Images via Ethernet and TFTP for detailed information on how to set up your target and the development host for loading images from TFTP. Following tftp, there is a sequence of commands that erase those Flash sections where the Linux image will be installed to and then copy the image to the Flash.

Here is a snapshot showing how update is used to install networking.uImage to the Flash:

STM32F7-SOM> setenv image vlad/networking.uImage
STM32F7-SOM> saveenv
...
STM32F7-SOM> run update
Auto-negotiation...completed.
STM32_MAC: link UP (100/Half)
Using STM32_MAC device
TFTP from server 172.17.0.1; our IP address is 172.17.4.211
Filename 'vlad/networking.uImage'.
Load address: 0xc0007fc0
Loading: #################################################################### #########################################################################
done
Bytes transferred = 2114160 (204270 hex)
................. done
Un-Protected 17 sectors

................. done
Erased 17 sectors
Copy to Flash... done
Saving Environment to Flash...
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors
STM32F7-SOM>

Having installed an image to the Flash, just hit the Reset button on the baseboard to boot the newly installed image from Flash:

U-Boot 2010.03-linux-cortexm-1.13.0 (Feb 17 2015 - 13:58:38)

CPU  : STM32F7 (Cortex-M7)
...
## Booting kernel from Legacy Image at c0007fc0 ...
Image Name:   Linux-2.6.33-arm1
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    2114096 Bytes =  2 MB
Load Address: c0008000
Entry Point:  c0008001
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.33-arm1 (vlad@ocean.emcraft.com) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-189) ) #108 Tue Feb 17 13:21:29 +0400 2015
...
init started: BusyBox v1.17.0 (2015-02-17 12:21:05 +0400)
~ # ls
bin    dev    etc    httpd  init   mnt    proc   root   sys usr    var

~ #

On deployed units, you will probably want to optimize the boot time by setting the U-Boot bootdelay variable to 0. Please refer to Running U-Boot for detailed information on how to do that.