Running Linux on i.MX RT1050 in 5 Minutes Print

 

Hardware Setup

Prepare hardware as described below:

  1. Connect the microUSB cable to the J28 connector on the MIMXRT1050-EVK board and the development host to provide the power and serial console access, which is required to run Linux (uClinux) on the i.MX RT1050. The serial console operates in U-Boot and uCLinux with the following parameters:
    1. Baud rate - 115200
    2. Data bits - 8
    3. Stop bits - 1
    4. Parity - none
  2. Connect Ethernet cable to the J19 connector on the MIMXRT1050-EVK board.
  3. The microUSB SD Card used to boot the system on the MIMXRT1050-EVK board.
    Since U-Boot (SPL+TPL) + U-Boot environment are located at the 0x400..0x100000 range of the raw SD Card address-space, the SD Card must be partitioned properly, so that U-Boot does not overwrite the file system on the partition. The SD Card must contain at least one partition started at a at least 1MB raw offset. The partition must be FATFS-formatted. Usually, a new SD Card satisfies these requirements by default so most likely no special preparations are required unless the card has been reformatted in some other way in other projects.

Installing Linux to NXP i.MX RT1050 EVK Board

  1. Download the bootable U-Boot and Linux images from the Emcraft web site: where SPL is the U-Boot SPL prebuilt image; u-boot.img is the U-Boot TPL prebuilt image; rootfs.uImage is the prebuilt rootfs project image.
  2. Plug in the MicroSD card to the cross-development host.
  3. Find out a /dev/sdX device the system has assigned to your SD Card:
  4. $ dmesg | tail [ 456.470775] usbcore: registered new interface driver usb-storage [ 456.482079] usbcore: registered new interface driver uas [ 457.501716] scsi 3:0:0:0: Direct-Access Generic STORAGE DEVICE 0821 PQ: 0 ANSI: 6 [ 457.508132] sd 3:0:0:0: Attached scsi generic sg2 type 0 [ 457.715113] sd 3:0:0:0: [sdb] 15446016 512-byte logical blocks: (7.91 GB/7.37 GiB) [ 457.733992] sd 3:0:0:0: [sdb] Write Protect is off [ 457.733999] sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 457.753808] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 457.840489] sdb: sdb1 [ 457.840845] sd 3:0:0:0: [sdb] Attached SCSI removable disk

  5. Install U-Boot to the microSD card:
  6. $ sudo dd if=SPL of=/dev/sdX bs=1k seek=1 conv=notrunc; sync $ sudo dd if=u-boot.img of=/dev/sdX bs=1k seek=128 conv=notrunc; sync

  7. Install the rootfs project to the microSD card:
  8. $ sudo mount /dev/sdX /mnt $ cp rootfs.uImage /mnt

  9. Install U-Boot splash screen.
    Copy the splash-rt1050-series_24.bmp file to the splash.bmp file on the SD card:

    $ cp splash-rt1050-series_24.bmp /mnt/splash.bmp $ sudo umount /mnt $ sync

  10. Unplug the microSD card from the development host. Set Boot SW.7 as 1010, insert the micro SD card into the microSD slot on the target board and power the board. The system should boot up on the board:
  11. U-Boot SPL 2022.04 (Oct 25 2023 - 07:27:23 +0000) Trying to boot from MMC1 U-Boot 2022.04 (Oct 25 2023 - 07:27:23 +0000) DRAM: 32 MiB Core: 71 devices, 13 uclasses, devicetree: separate MMC: FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@40184000 Out: serial@40184000 Err: serial@40184000 Net: eth0: ethernet@402D8000 Hit any key to stop autoboot: 0 8386877 bytes read in 1490 ms (5.4 MiB/s) ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Linux-5.15.71 Image Type: ARM Linux Multi-File Image (uncompressed) Data Size: 8386813 Bytes = 8 MiB Load Address: 80008000 Entry Point: 80008001 Contents: Image 0: 8378592 Bytes = 8 MiB Image 1: 8209 Bytes = 8 KiB Verifying Checksum ... OK ## Flattened Device Tree from multi component Image at 80007FC0 Booting using the fdt at 0x808058ec Loading Multi-File Image Loading Device Tree to 81e7f000, end 81e84010 ... OK Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 5.15.71 (sasha@workbench.emcraft.com) (arm-none-eabi-gcc (GNU Arm Embedded Toolchain 10.3-2021.10) 10.3.1 20210824 (release), GNU ld (GNU Arm Embedded Toolchain 10.3-2021.10) 2.36.1.20210621) #2 Wed Oct 25 07:41:37 UTC 2023 CPU: ARMv7-M [411fc271] revision 1 (ARMv7M), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache OF: fdt: Machine model: NXP IMXRT1050-evk board …… ci_hdrc ci_hdrc.1: EHCI Host Controller ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1 mmc0: SDHCI controller on 402c0000.mmc [402c0000.mmc] using DMA ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected input: gpio-keys as /devices/platform/gpio-keys/input/input0 cfg80211: Loading compiled-in X.509 certificates for regulatory database cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 cfg80211: failed to load regulatory.db Freeing unused kernel image (initmem) memory: 3552K This architecture does not have kernel memory protection. Run /init as init process [71] Jan 01 00:00:01 Running in background / # mmc0: new high speed SDHC card at address 0007 mmcblk0: mmc0:0007 SD8GB 7.42 GiB mmcblk0: p1 Micrel KSZ8081 or KSZ8091 402d8000.ethernet-1:02: attached PHY driver (mii_bus:phy_addr=402d8000.ethernet-1:02, irq=POLL) fec 402d8000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off / #

Ethernet Driver Support

  1. Power cycle the board. While U-Boot is coming up, press any key on the serial console to enter the U-Boot command line interface:
  2. U-Boot SPL 2022.04 (Oct 25 2023 - 07:27:23 +0000) Trying to boot from MMC1 U-Boot 2022.04 (Oct 25 2023 - 07:27:23 +0000) DRAM: 32 MiB Core: 71 devices, 13 uclasses, devicetree: separate MMC: FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@40184000 Out: serial@40184000 Err: serial@40184000 Net: eth0: ethernet@402D8000 Hit any key to stop autoboot: 0

  3. From the U-Boot command line interface, reset to the default environment:
  4. => env default -a ## Resetting to default environment =>

  5. Set the ipaddr, serverip and netmask U-Boot environment variables:
  6. => setenv ipaddr 192.168.1.86 => setenv serverip 192.168.1.96 => setenv gatewayip 192.168.1.254 => setenv netmask 255.255.255.0 => saveenv Saving Environment to MMC... Writing to MMC(0)... OK =>

  7. ping the development host from the target board:
  8. => ping 192.168.88.177 Using ethernet@402D8000 device host 192.168.88.177 is alive =>

  9. Load rootfs.uImage using the U-Boot tftp command:
  10. => tftp imxrt1050/rootfs.uImage Using ethernet@402D8000 device TFTP from server 192.168.1.96; our IP address is 192.168.1.86 Filename 'imxrt1050/rootfs.uImage'. Load address: 0x80007fc0 Loading: ################################################################# ################################################################# ################################################################# ..... ################################################################# ########################################################## 215.8 KiB/s done Bytes transferred = 8386877 (7ff93d hex) =>

  11. Reset the board and let it boot up to the Linux shell:
  12. => reset resetting ... U-Boot SPL 2022.04 (Oct 25 2023 - 07:27:23 +0000) Trying to boot from MMC1 U-Boot 2022.04 (Oct 25 2023 - 07:27:23 +0000) DRAM: 32 MiB Core: 71 devices, 13 uclasses, devicetree: separate MMC: FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@40184000 Out: serial@40184000 Err: serial@40184000 Net: eth0: ethernet@402D8000 Hit any key to stop autoboot: 0 8386877 bytes read in 1492 ms (5.4 MiB/s) ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Linux-5.15.71 Image Type: ARM Linux Multi-File Image (uncompressed) Data Size: 8386813 Bytes = 8 MiB Load Address: 80008000 Entry Point: 80008001 Contents: Image 0: 8378592 Bytes = 8 MiB Image 1: 8209 Bytes = 8 KiB Verifying Checksum ... OK ## Flattened Device Tree from multi component Image at 80007FC0 Booting using the fdt at 0x808058ec Loading Multi-File Image Loading Device Tree to 81e7f000, end 81e84010 ... OK Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 5.15.71 (sasha@workbench.emcraft.com) (arm-none-eabi-gcc (GNU Arm Embedded Toolchain 10.3-2021.10) 10.3.1 20210824 (release), GNU ld (GNU Arm Embedded Toolchain 10.3-2021.10) 2.36.1.20210621) #2 Wed Oct 25 07:41:37 UTC 2023 CPU: ARMv7-M [411fc271] revision 1 (ARMv7M), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache OF: fdt: Machine model: NXP IMXRT1050-evk board ..... Run /init as init process [71] Jan 01 00:00:01 Running in background / # mmc0: new high speed SDHC card at address 0007 mmcblk0: mmc0:0007 SD8GB 7.42 GiB mmcblk0: p1 Micrel KSZ8081 or KSZ8091 402d8000.ethernet-1:02: attached PHY driver (mii_bus:phy_addr=402d8000.ethernet-1:02, irq=POLL) fec 402d8000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off / #

  13. From the development host validate that the target board is visible using ping:
  14. $ ping -c 5 192.168.1.86 PING 192.168.1.86 (192.168.1.86) 56(84) bytes of data. 64 bytes from 192.168.1.86: icmp_seq=1 ttl=64 time=8.11 ms 64 bytes from 192.168.1.86: icmp_seq=2 ttl=64 time=5.71 ms 64 bytes from 192.168.1.86: icmp_seq=3 ttl=64 time=4.99 ms 64 bytes from 192.168.1.86: icmp_seq=4 ttl=64 time=4.81 ms 64 bytes from 192.168.1.86: icmp_seq=5 ttl=64 time=5.89 ms --- 192.168.1.86 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4009ms rtt min/avg/max/mdev = 4.805/5.900/8.110/1.178 ms $

  15. From the target board, validate that the development host is visible using ping:
  16. / # ping -c 5 192.168.1.95 PING 192.168.1.95 (192.168.1.95): 56 data bytes 64 bytes from 192.168.1.95: seq=0 ttl=64 time=5.771 ms 64 bytes from 192.168.1.95: seq=1 ttl=64 time=5.132 ms 64 bytes from 192.168.1.95: seq=2 ttl=64 time=5.763 ms 64 bytes from 192.168.1.95: seq=3 ttl=64 time=5.377 ms 64 bytes from 192.168.1.95: seq=4 ttl=64 time=5.074 ms --- 192.168.1.95 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 5.074/5.423/5.771 ms / #

TCP/IP Stack Support

With uClinux running on the i.MX RT1050, you get the full Linux TCP/IP stack (kernel version 5.15.71). Userspace POSIX APIs are provided by the uClibc library. Key user-space networking tools and utilities are available from the multi-call busybox. Additional tools and packages, such as for instance the SSH dropbear server, can be built specifically for uClinux. All in all, you have the powerful Linux TCP/IP stack at your disposal.

  1. From the development host validate that the i.MX RT1050 is visible using ping:
  2. $ ping -c 5 192.168.1.86 PING 192.168.1.86 (192.168.1.86) 56(84) bytes of data. 64 bytes from 192.168.1.86: icmp_seq=1 ttl=64 time=8.11 ms 64 bytes from 192.168.1.86: icmp_seq=2 ttl=64 time=5.71 ms 64 bytes from 192.168.1.86: icmp_seq=3 ttl=64 time=4.99 ms 64 bytes from 192.168.1.86: icmp_seq=4 ttl=64 time=4.81 ms 64 bytes from 192.168.1.86: icmp_seq=5 ttl=64 time=5.89 ms --- 192.168.1.86 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4009ms rtt min/avg/max/mdev = 4.805/5.900/8.110/1.178 ms

  3. ping the development host from the i.MX RT1050:
  4. / # ping -c 5 192.168.1.95 PING 192.168.1.95 (192.168.1.95): 56 data bytes 64 bytes from 192.168.1.95: seq=0 ttl=64 time=5.756 ms 64 bytes from 192.168.1.95: seq=1 ttl=64 time=5.902 ms 64 bytes from 192.168.1.95: seq=2 ttl=64 time=5.505 ms 64 bytes from 192.168.1.95: seq=3 ttl=64 time=5.491 ms 64 bytes from 192.168.1.95: seq=4 ttl=64 time=4.881 ms --- 192.168.1.95 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 4.881/5.507/5.902 ms / #

  5. On the target, start the telnetd daemon to allow connections to the i.MX RT1050:
  6. / # ps | grep telnetd 101 root 864 S telnetd 103 root 864 S grep telnetd / #

  7. Connect to the target from the development host using telnet. The target is configured to accept the 123 password for root:
  8. $ telnet 192.168.1.86 Trying 192.168.1.86... Connected to 192.168.1.86. Escape character is '^]'. (none) login: root Password: / # ls bin etc httpd lib mnt root sys usr dev hello.ko init linuxrc proc sbin tmp var / # exit Connection closed by foreign host. . $

  9. The dropbear SSH daemon starts automatically on the target. Verify that dropbear allows secure connections to the target:
  10. / # ps | grep dropbear 71 root 728 S dropbear -R 108 root 864 S grep dropbear

  11. Connect to the target from the development host using ssh. The first connection takes several seconds to establish as the i.MX RT1050 runs computation-extensive key calculations. Again, enter 123 on the password prompt:
  12. $ ssh root@192.168.1.86 root@192.168.1.86's password: / # ls bin etc httpd lib mnt root sys usr dev hello.ko init linuxrc proc sbin tmp var / # exit Connection to 192.168.1.86 closed by remote host. Connection to 192.168.1.86 closed. $

  13. On the target, enable access to the Internet by configuring a default gateway. Note also that the system makes use of the public name server provided by Google:
  14. / # cat /etc/resolv.conf # This configuration makes use of the Google public DNS server. # If you would like to use something else, replace with the IP # of your DNS server nameserver 8.8.8.8 / #

  15. Use ntpd to synchronize the time on the target with the time provided by a public server:
  16. / # date Thu Jan 1 00:13:49 UTC 1970 / # ntpd -p 0.fedora.pool.ntp.org / # sleep 5 / # date Fri Oct 27 08:29:25 UTC 2023

  17. Use wget to download a file from a remote server:
  18. / # wget ftp://ftp.gnu.org/README Connecting to ftp.gnu.org (209.51.188.20:21) saving to 'README' README 100% |********************************| 2748 0:00:00 ETA 'README' saved / # / # cat README This is ftp.gnu.org, the FTP server of the the GNU project. ...

  19. Mount a directory exported by a development host over NFS:
  20. / # mount -o nolock,rsize=1024 192.168.1.99:/srv/nfs /mnt/nfs / # ls /mnt/nfs/ SimpleClass linux-dp test / # cp /bin/busybox /mnt/nfs / # cp /mnt/nfs/busybox /tmp / # md5sum /bin/busybox /tmp/busybox bb39cf3470150200a35c41bd6f78ef92 /bin/busybox bb39cf3470150200a35c41bd6f78ef92 /tmp/busybox

  21. Start the HTTP daemon:
  22. / # httpd -h /httpd/html/
    / #

  23. From a local host, open a Web browser to the i.MX RT1050 and watch the demo web page provided by the target. The i.MX RT1050 shows the current time and date as well as the list of the currently running processes:

Support USB Host Stack Interface

  1. Attach a USB Flash device to the J9 connector. Verify that it is automatically detected and can be mounted:
  2. ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 2 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected usb 2-1: new high-speed USB device number 2 using ci_hdrc usb-storage 2-1:1.0: USB Mass Storage device detected scsi host0: usb-storage 2-1:1.0 scsi 0:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 2 sd 0:0:0:0: [sda] 8228864 512-byte logical blocks: (4.21 GB/3.92 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] No Caching mode page found sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] Attached SCSI removable disk / # mount /dev/sda1 /mnt/usbflash/ / # ls -la /mnt/usbflash/ drwxr-xr-x 3 root root 4096 Jan 1 1970 . drwxrwxrwx 8 root root 0 Oct 25 07:41 .. drwxr-xr-x 2 root root 4096 May 25 18:18 System Volume Information -rwxr-xr-x 1 root root 261 Jan 1 1980 data.log / #

  3. Unmount the USB Flash device:
  4. / # umount /mnt/usbflash/ / #

Support Loading / Unloading Kernel Modules

  1. From the Linux shell, load the demo kernel module:
  2. / # insmod hello.ko Hello, world / #

  3. Show the status of the loaded kernel modules:
  4. / # lsmod Module Size Used by Not tainted hello 576 0 / #

  5. Unload the module from the Linux kernel:
  6. / # rmmod hello Goodbye, world / #

Running Emcraft Ebike Demo

Step through the following procedure to run the Emcraft Ebike demo:

  1. From the Linux shell, type the ebike_gui_demo command to run the ebike demo:
  2. / # ebike_gui_demo

  3. Click to the padlock icon in the bottom right corner of the screen to switch to the Unlock Your Bike group.
  4. Click 4 any digits and then v. Make sure the correct PIN-code in printed out to the Linux shell terminal:
  5. / # ebike_gui_demo
    entered pin: 4 7 1 2

  6. Click to the bike icon to switch back to the Driving Information group.
  7. Press and hold the SW8 button, which resides on the opposite side of the i.MXR1050-EVK board to LCD. Make sure that the Speed, Trip, Odometer and other values are increasing on the corresponding widgets on the LCD. If release the SW8 button the Speed reading is decreasing: