Running U-Boot

As explained in Installing U-Boot to the NXP i.MX RT1170 EVK Board , you have to install U-Boot to the SD Card of the NXP i.MX RT1170 EVK board in order to run Linux (uClinux) on the NXP i.MX RT1170 EVK board. U-Boot runs as the primary firmware from the SD Card on each power-on / reset.

U-Boot is probably the most popular firmware monitor for Linux. It is developed and maintained by DENX Software Engineering (www.denx.de). If you need detailed information on any aspects of U‑Boot operation, DENX publishes extensive U‑Boot user documentation at their web site.

U-Boot for the i.MX RT1170 microcontrollers is consisted of the two parts: SPL and TPL. SPL is installed with a 1k offset, TPL with a 128k offset in the SD card.

When SW8 switch selects the SD Card as a source boot, then the i.MX RT1170 ROM bootloader reads the SPL image at 0x400 offset from the start of the SD Card device and runs it. Then, SPL initializes SDRAM, read TPL from the SD card and runs it. TPL relocates itself to the end of the SDRAM, before the NON-Cached region, which is reserved for DMA, and is subsequently executed from there. Volatile data (stack, variables, dynamic pool) are maintained in the external SDRAM memory as well.

As soon as the NXP i.MX RT1170 EVK board is powered on or reset, the i.MX RT1170 proceeds to boot the U‑Boot firmware from the SD Card printing the following output to the serial console:

If you hit any key on the serial console before the number of seconds defined by the U-Boot bootdelay variable has elapsed, you will enter the U-Boot interactive command monitor. From the command monitor you can run U‑Boot commands to examine memory, load an image from Ethernet, boot Linux from a loaded image or perform any other action supported by U-Boot.

U-Boot makes use of the so-called environment variables to define various aspects of the target functionality. On the NXP i.MX RT1170 EVK board, the U-Boot environment is stored at offset 512k also in the SD card and is persistent across power or reset cycles. Parameters defined by the U-Boot environment variables include: target IP address, target MAC address, location in RAM where a Linux bootable image will be loaded, and many others.

To manipulate the U-Boot environment the following commands are used:

• printenv <var> - print the value of the variable <var>. Without arguments, prints all environment variables:

  => printenv addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off arch=arm baudrate=115200 board=imxrt1170-evk board_name=imxrt1170-evk bootcmd=run mmcboot bootdelay=2 cpu=armv7m ethaddr=aa:bb:cc:dd:ee:f0 fdtcontroladdr=20236c80 gatewayip=192.168.88.1 image=rootfs.uImage ipaddr=192.168.88.89 loadaddr=0x80007fc0 mmcboot=fatload mmc 0 ${loadaddr} ${image} && run addip && bootm ${loadaddr} netboot=tftp ${image} && run addip && bootm netmask=255.255.255.0 serverip=192.168.88.170 soc=imxrt stderr=serial@4007c000 stdin=serial@4007c000 stdout=serial@4007c000 vendor=freescale Environment size: 614/126972 bytes

• setenv <var> <val> - set the variable <var> to the value <val>:

  => setenv image my.rootfs.uImage =>

• saveenv - save the up-to-date U-Boot environment, possibly updated using setenv commands, into the SD Card. Running saveenv makes sure that any updates you have made to the U-Boot environment are persistent across power cycles and resets.