Page Comparison

...

1. Connect the microUSB cable to the J28 connector on the MIMXRT1050-EVKB board or to the J1 connector on the MIMXRT1060-EVKB board and the development host to provide the power and serial console access, which is required to run Linux (uClinux) on the i.MX RT10xx. The serial console operates in U-Boot and uCLinux with the following parameters:

   • Baud rate - 115200

   • Data bits - 8

   • Stop bits - 1

   • Parity - none

2. Connect Ethernet cable to the J19 connector on the MIMXRT1050-EVKB board or to the J43 connector on the MIMXRT1060-EVKB board.

3. The microUSB SD Card used to boot the system on the MIMXRT1050/1060-EVKB 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.

...

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:

   Code Block
   U-Boot SPL 2024.04-00028-g674762029e5-dirty (Dec 11 2024 - 09:04:14 +0300) Trying to boot from MMC1 U-Boot 2024.04-00028-g674762029e5-dirty (Dec 11 2024 - 09:04:14 +0300) DRAM: 32 MiB Core: 78 devices, 17 uclasses, devicetree: separate MMC: FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@40184000 Out: serial Err: serial Net: eth0: ethernet@402d8000 Hit any key to stop autoboot: 0 =>

2. From the U-Boot command line interface, reset to the default environment:

   Code Block
   => env default -a ## Resetting to default environment =>

3. Set the ipaddr, serverip, gatewayip and netmask U-Boot environment variables:

   Code Block
   => setenv ipaddr 192.168.1.82 => setenv serverip 192.168.1.83 => setenv gatewayip 192.168.1.254 => setenv netmask 255.255.255.0 => saveenv Saving Environment to MMC... Writing to MMC(0)... OK =>

4. ping the development host from the target board:

   Code Block
   => ping 192.168.1.83 Using ethernet@402d8000 device host 192.168.1.83 is alive

5. Load rootfs.uImage using the U-Boot tftp command:

   Code Block

   => tftp imxrt1050/rootfs.uImage Using ethernet@402d8000 device TFTP from server 192.168.1.83; our IP address is 192.168.1.82 Filename 'imxrt1050/rootfs.uImage'. Load address: 0x80007fc0 Loading: ################################################################# ################################################################# ################################################################# ... ################################################################# ######################### 658.2 KiB/s done Bytes transferred = 8780437 (85fa95 hex)

6. Reset the board and let it boot up to the Linux shell:

   Code Block

   => reset resetting ... U-Boot SPL 2024.04-00028-g674762029e5-dirty (Dec 11 2024 - 09:04:14 +0300) Trying to boot from MMC1 U-Boot 2024.04-00028-g674762029e5-dirty (Dec 11 2024 - 09:04:14 +0300) DRAM: 32 MiB Core: 78 devices, 17 uclasses, devicetree: separate MMC: FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@40184000 Out: serial Err: serial Net: eth0: ethernet@402d8000 Hit any key to stop autoboot: 0 8780430 bytes read in 5996 ms (1.4 MiB/s) ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Linux-6.6.36 Image Type: ARM Linux Multi-File Image (uncompressed) Data Size: 8780366 Bytes = 8.4 MiB Load Address: 80008000 Entry Point: 80008001 Contents: Image 0: 8768576 Bytes = 8.4 MiB Image 1: 11778 Bytes = 11.5 KiB Verifying Checksum ... OK ## Flattened Device Tree from multi component Image at 80007FC0 ... / # 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 random: crng init done / #

7. From the development host validate that the target board is visible using ping:

   Code Block

   $ ping -c 5 192.168.1.82 PING 192.168.1.82 (192.168.1.82) 56(84) bytes of data. 64 bytes from 192.168.1.82: icmp_seq=1 ttl=64 time=0.826 ms 64 bytes from 192.168.1.82: icmp_seq=2 ttl=64 time=0.461 ms 64 bytes from 192.168.1.82: icmp_seq=3 ttl=64 time=0.460 ms 64 bytes from 192.168.1.82: icmp_seq=4 ttl=64 time=0.439 ms 64 bytes from 192.168.1.82: icmp_seq=5 ttl=64 time=0.444 ms --- 192.168.1.82 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4080ms rtt min/avg/max/mdev = 0.439/0.526/0.826/0.150 ms

8. From the target board, validate that the development host is visible using ping:

   Code Block

   / # ping -c 5 192.168.1.83 PING 192.168.1.83 (192.168.1.83): 56 data bytes 64 bytes from 192.168.1.83: seq=0 ttl=64 time=0.808 ms 64 bytes from 192.168.1.83: seq=1 ttl=64 time=0.649 ms 64 bytes from 192.168.1.83: seq=2 ttl=64 time=0.839 ms 64 bytes from 192.168.1.83: seq=3 ttl=64 time=0.825 ms 64 bytes from 192.168.1.83: seq=4 ttl=64 time=0.632 ms --- 192.168.1.83 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 0.632/0.750/0.839 ms

...