Loading Linux Images over UART Print

 

This article explains how to load images to the target over UART in U-Boot. Keep in mind that loading via a serial port will take quite a long time (minutes per file!) due to the low speeds (limited to 115.2 Kps). That said, for embedded designs that do not provide an Ethernet port it may be the only reasonable development and software manufacturing option using U-Boot and uClinux.

Using the NXP i.MX RT1060 EVK board, you connect to the target serial console on LPUART1 available on the J45 and J46(refer to Connecting Serial Console to the NXP i.MX RT1060 EVK for details. Assuming you connect to a Linux PC host, on the Linux host the i.MX RT1060 serial console will be visible as a /dev/ttyUSBx device. The U-Boot and Linux software configures the console for 115.2 Kps operation.

There are various serial communication tools available for Linux, the most popular perhaps being kermit. kermit is a very powerful tool that can be run in interactive mode or controlled by a script. There is abundant documentation on kermit available in the Internet, if you require details.

The download procedure is based on the loadb command provided by the U-Boot command interface. loadb implements a download capability over UART using the kermit protocol and has the following synopsis:

loadb [<load_address> <baud_rate>]

If you do not specify a load address, then the value will be taken from the loadaddr environment variable. On the NXP i.MX RT1060 EVK loadaddr is set as follows, placing the download buffer into SDRAM:

=> print loadaddr
loadaddr=0x80007fc0

If you do not specify a baud rate, then the speed the console is currently running at will be used (set to a default value of 115200 on the NXP i.MX RT1060 EVK).

Once the transmission using loadb finishes, the file will be in memory at the specified load address. The loadaddr environment variable will automatically be set to the address the loadb command used. The filesize environment variable will automatically be set to the number of bytes transferred during the load operation.

Then you are free to do whatever you like with the loaded image. You can boot Linux from the image (assuming it is a Linux uImage file), copy it to some other place (for instance, on-module Flash), display the memory, etc.

To automate the download procedure, you might want to put a desired sequence of interactive steps involving interactions with the U-Boot command interface on the target and kermit on the host into a shell script. For instance, here is a sample script to download a Linux bootable image (rootfs.uImage) to SDRAM and boot Linux from it:

$ vi uartboot-imxrt1060.script
#!/usr/local/bin/kermit

set port /dev/ttyUSB0
set speed 115200
set carrier-watch off
set flow-control none
set prefixing all

echo {loading uImage}
PAUSE 1

OUTPUT loadb ${loadaddr} 115200\{13}
send rootfs.uImage
INPUT 180 {\{13}\{10}=> }
IF FAIL STOP 1 INPUT timeout

echo {running kernel}
PAUSE 1
OUTPUT run addip; bootm\{13}
c

Copy the sample Linux image (rootfs.uImage) from the Emcraft software distribution to the host directory you will be running the shell script from.

Then run the script to download the image to the target via UART and boot Linux from it:

  $ chmod a+x uartboot-imxrt1060.script $ ./uartboot-imxrt1060.script C-Kermit 9.0.302 OPEN SOURCE:, 20 Aug 2011, ubuntu [192.168.1.102] Current Directory: /mnt/work/imx Communication Device: /dev/ttyUSB0 Communication Speed: 115200 Parity: none RTT/Timeout: 01 / 03 SENDING: rootfs.uImage => ROOTFS.UIMAGE File Type: BINARY File Size: 7749634 Percent Done: 3 /- ...10...20...30...40...50...60...70...80...90..100 Estimated Time Left: 00:14:41 Transfer Rate, CPS: 8495 Window Slots: 1 of 1 Packet Type: D Packet Count: 44 Packet Length: 9024 Error Count: 0 Last Error: Last Message: X to cancel file, Z to cancel group, <CR> to resend last packet, E to send Error packet, ^C to quit immediately, ^L to refresh screen.

It will take 15+ long minutes to download the image at 115.2Kps but finally it will get to the target and Linux will boot from it:

## Total Size = 0x00764002 = 7749634 Bytes ## Start Addr = 0x80007FC0 => running kernel Connecting to /dev/ttyUSB0, speed 115200 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. ---------------------------------------------------- run addip; bootm ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Linux-4.5.0-cortexm-2.5.0 Image Type: ARM Linux Multi-File Image (uncompressed) Data Size: 7749570 Bytes = 7.4 MiB Load Address: 80008000 Entry Point: 80008001 Contents: Image 0: 7739904 Bytes = 7.4 MiB Image 1: 9654 Bytes = 9.4 KiB Verifying Checksum ... OK ## Flattened Device Tree from multi component Image at 80007FC0 Booting using the fdt at 0x80769a0c Loading Multi-File Image ... OK Loading Device Tree to 81e77000, end 81e7c5b5 ... OK Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 4.5.0-cortexm-2.5.0 ( This e-mail address is being protected from spambots. You need JavaScript enabled to view it ) (gcc version 4.7.4 20130508 (prerelease) (20170818-165657- build on build.emcraft by build) #1 Tue Oct 17 01:50:48 MSK 2017 CPU: ARMv7-M [411fc271] revision 1 (ARMv7M), cr=00000000 ... init started: BusyBox v1.24.2 (2017-10-17 01:49:35 MSK) ... / # ls bin etc lib root tmp crankdemo httpd mnt sbin usr dev init proc sys var