/
Running Linux on i.MX RT1170 in 5 Minutes

Running Linux on i.MX RT1170 in 5 Minutes

1. Hardware Setup

1.1. Hardware Setup for NXP i.MX RT1170 EVK:

Prepare hardware as described below:

  1. Set the jumper J38 to position 1-2 and connect DC 5 V external power supply to J43 power jack.

  2. Connect the microUSB cable to the J11 connector on the MIMXRT1170-EVK board and the development host to provide the serial console access, which is required to run Linux (uClinux) on the i.MX RT1170. The serial console operates in U-Boot and uCLinux with the following parameters:

    • Baud rate - 115200

    • Data bits - 8

    • Stop bits - 1

    • Parity - none

  3. Connect the microUSB cable to the J20 connector on the MIMXRT1170-EVK board and the development host for SDP, which is required to install the demo image to the target board.

  4. Connect Ethernet cable to the 100M ENETor 1G ENET connector on the MIMXRT1170-EVK board.

  5. Connect LCD Panel RK055HDMIPI4MA0 to the board.

1.2. Hardware Setup for MaaXBoard-RT:

  1. Connect the USB-C cable to the J10 connector on the MaaXBoard-RT board and to the development host to provide the serial console access and power. 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. Software Setup

  1. On the development host download and install the MCUXpresso Secure Provisioning Tool provided by NXP:

  2. Download the demo image from the Emcraft web site:

     

3. Installing Linux to NXP i.MX RT1170 EVK Board or to MaaXBoard-RT board

  1. Set up the Boot switch on the IMXRT1170-EVK board for SDP: set SW1 as 0001 and re-enable the power supply.

  2. Set up the Boot Mode Configuration Jumper (J19) on the MaaXBoard-RT board.

  3. in the 2-3 position (Serial Downloader).

  4. On the development host run the Secure Provisioning Tool. In the New Workspace window, select the MIMXRT1176 processor and click Create:

    image-20250319-100327.png

  5. For the the MaaXBoard-RT board change the boot memory configuration as shown on screenshot below. To change the boot memory configuration, click Target->Boot memory menu or press Ctrl+B:

    Screenshot_2026-02-06_13-08-11-20260206-100817.png

  6. Run the Flash Programmer tool: click Tools->Flash Programmer menu or press Ctrl+R. Answer Yes in the pooped up window:

    image-20250319-100418.png

 

  1. Click the Load button, select the imxrt1170_demo.img for the IMXRT1170-EVK board or maaxboard-rt_demo.img for the MaaXBoard-RT board from the file system and confirm Load:

    image-20250319-100457.png

  2. Make sure the Auto erase and Auto verify check-buttons are set and the click the Write button:

    image-20250319-100536.png

  3. Wait until the write operation is completed:

    image-20250319-100549.png

  4. When the writing is completed, close the MCUXpresso Secure Provisioning Tool. Then set up boot jumpers on the target board to boot from QSPI Flash / HyperFlash: set SW1 as 0010, SW2 as 0000000000 on the IMXRT1170-EVK board or set up the Boot Mode Configuration Jumper (J19) in the 1-2 position (Internal Boot) on the MaaXBoard-RT board.

  5. Use your preferable serial communication tool to connect to the target serial console (we use picocom in this demo), on the IMXRT1170-EVK board the serial console is visible as a /dev/ttyACMx device, on the MaaXBoard-RT board the serial console is visible as a /dev/ttyUSBx device:

    $ picocom -l -b 115200 /dev/ttyACM0 picocom v3.1 port is : /dev/ttyACM0 flowcontrol : none baudrate is : 115200 parity is : none databits are : 8 stopbits are : 1 escape is : C-a local echo is : no noinit is : no noreset is : no hangup is : no nolock is : yes send_cmd is : sz -vv receive_cmd is : rz -vv -E imap is : omap is : emap is : crcrlf,delbs, logfile is : none initstring : none exit_after is : not set exit is : no Type [C-a] [C-h] to see available commands Terminal ready

  6. Power cycle the board. U-Boot and then Linux should start automatically on the serial console:

    U-Boot SPL 2025.04 (Jan 22 2026 - 06:56:14 +0000) Trying to boot from NOR U-Boot 2025.04 (Jan 22 2026 - 06:56:14 +0000) Model: NXP imxrt1170-evk board DRAM: 64 MiB Core: 77 devices, 16 uclasses, devicetree: separate MMC: FSL_SDHC: 0 Loading Environment from nowhere... OK In: serial@4007c000 Out: serial@4007c000 Err: serial@4007c000 Net: eth0: ethernet@40424000 Hit any key to stop autoboot: 0 ## Booting kernel from Legacy Image at 30080000 ... Image Name: Linux-6.12.20 Image Type: ARM Linux Multi-File Image (uncompressed) Data Size: 10129762 Bytes = 9.7 MiB Load Address: 80008000 Entry Point: 80008001 Contents: Image 0: 10114088 Bytes = 9.6 MiB Image 1: 15662 Bytes = 15.3 KiB Verifying Checksum ... OK ## Flattened Device Tree from multi component Image at 30080000 Booting using the fdt at 0x30a25474 Working FDT set to 30a25474 Loading Multi-File Image to 80008000 Loading Device Tree to 8397b000, end 83981d2d ... OK Working FDT set to 8397b000 Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 6.12.20 (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 PREEMPT Wed Jan 21 14:37:53 UTC 2026 CPU: ARMv7-M [411fc272] revision 2 (ARMv7M), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache OF: fdt: Machine model: NXP IMXRT1170 EVK board earlycon: lpuart32_imxrt0 at MMIO32 0x4007c000 (options '') printk: legacy bootconsole [lpuart32_imxrt0] enabled Zone ranges: Normal [mem 0x0000000080000000-0x0000000083ffffff] Movable zone start for each node Early memory node ranges node 0: [mem 0x0000000080000000-0x0000000083afffff] node 0: [mem 0x0000000083b00000-0x0000000083ffffff] Initmem setup node 0 [mem 0x0000000080000000-0x0000000083ffffff] Reserved memory: created DMA memory pool at 0x83b00000, size 1 MiB OF: reserved mem: initialized node dmapool@83b00000, compatible id shared-dma-pool OF: reserved mem: 0x83b00000..0x83bfffff (1024 KiB) nomap non-reusable dmapool@83b00000 OF: reserved mem: 0x83c00000..0x83ffffff (4096 KiB) nomap non-reusable memory@83c00000 Kernel command line: earlycon=lpuart32_imxrt,0x4007c000 console=ttyLP0,115200 Dentry cache hash table entries: 8192 (order: 3, 32768 bytes, linear) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes, linear) Built 1 zonelists, mobility grouping on. Total pages: 16384 mem auto-init: stack:off, heap alloc:off, heap free:off SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Invalid parameters for execmem allocator, module loading will fail rcu: Preemptible hierarchical RCU implementation. rcu: RCU event tracing is enabled. rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies. NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 rcu: srcu_init: Setting srcu_struct sizes based on contention. Switching to timer-based delay loop, resolution 41ns sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=24000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) rcu: Hierarchical SRCU implementation. rcu: Max phase no-delay instances is 400. Memory: 49344K/65536K available (4121K kernel code, 229K rwdata, 1780K rodata, 3508K init, 125K bss, 15784K reserved, 0K cma-reserved) devtmpfs: initialized DMA: default coherent area is set clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns futex hash table entries: 256 (order: -1, 3072 bytes, linear) pinctrl core: initialized pinctrl subsystem NET: Registered PF_NETLINK/PF_ROUTE protocol family imxrt1170-pinctrl 400e8000.iomuxc: initialized IMX pinctrl driver imxrt1170-pinctrl 40c08000.iomuxc_lpsr: initialized IMX pinctrl driver imxrt1170-pinctrl 40c94000.iomuxc_snvs: initialized IMX pinctrl driver mxs_phy 40434000.usbphy1: supply phy-3p0 not found, using dummy regulator mxs_phy 40438000.usbphy2: supply phy-3p0 not found, using dummy regulator gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip4: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip5: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip6: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip7: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip8: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip9: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip10: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip11: Static allocation of GPIO base is deprecated, use dynamic allocation. gpio gpiochip12: Static allocation of GPIO base is deprecated, use dynamic allocation. SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb imx-lpi2c 40c34000.i2c: use pio mode i2c i2c-4: LPI2C adapter registered pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> PTP clock support registered Bluetooth: Core ver 2.22 NET: Registered PF_BLUETOOTH protocol family Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized clocksource: Switched to clocksource mxc_timer1 NET: Registered PF_INET protocol family IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear) tcp_listen_portaddr_hash hash table entries: 1024 (order: 0, 4096 bytes, linear) Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear) TCP bind hash table entries: 1024 (order: 1, 8192 bytes, linear) TCP: Hash tables configured (established 1024 bind 1024) UDP hash table entries: 256 (order: 0, 4096 bytes, linear) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear) NET: Registered PF_UNIX/PF_LOCAL protocol family RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp-with-tls transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. Bus freq driver module loaded Initialise system trusted keyrings workingset: timestamp_bits=30 max_order=14 bucket_order=0 fuse: init (API version 7.41) Key type asymmetric registered Asymmetric key parser 'x509' registered Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) io scheduler mq-deadline registered io scheduler kyber registered io scheduler bfq registered mipi_dsi_northwest 4080c000.mipi_dsi: i.MX MIPI DSI driver probed mxsfb 40804000.lcdif: Defer fb probe due to dispdrv not ready 4007c000.serial: ttyLP0 at MMIO 0x4007c010 (irq = 467, base_baud = 1500000) is a FSL_LPUART printk: legacy console [ttyLP0] enabled printk: legacy console [ttyLP0] enabled printk: legacy bootconsole [lpuart32_imxrt0] disabled printk: legacy bootconsole [lpuart32_imxrt0] disabled fec 40420000.ethernet: Invalid MAC address: 00:00:00:00:00:00 fec 40420000.ethernet: Using random MAC address: 66:3b:a8:2e:9b:f7 PPP generic driver version 2.4.2 PPP BSD Compression module registered PPP Deflate Compression module registered usbcore: registered new interface driver rt2800usb usbcore: registered new interface driver cdc_acm cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters usbcore: registered new interface driver uas usbcore: registered new interface driver usb-storage Goodix-TS 4-0014: supply AVDD28 not found, using dummy regulator Goodix-TS 4-0014: Error reading 1 bytes from 0x8140: -5 Goodix-TS 4-0014: Error reading 1 bytes from 0x8140: -5 Goodix-TS 4-0014: I2C communication failure: -5 Goodix-TS 4-0014: probe with driver Goodix-TS failed with error -5 i2c_dev: i2c /dev entries driver usbcore: registered new interface driver btusb sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper usbcore: registered new interface driver usbhid mmc0 bounce up to 128 segments into one, max segment size 65536 bytes usbhid: USB HID core driver NET: Registered PF_PACKET protocol family Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 ARMv7-M VFP coprocessor found VFP: Double precision floating points are supported mmc0: SDHCI controller on 40418000.usdhc [40418000.usdhc] using DMA Loading compiled-in X.509 certificates mipi_dsi_northwest 4080c000.mipi_dsi: MIPI DSI dispdv inited mxsfb 40804000.lcdif: registered mxc display driver mipi_dsi_northwest mxsfb 40804000.lcdif: initialized input: gpio-keys as /devices/platform/gpio-keys/input/input0 cfg80211: Loading compiled-in X.509 certificates for regulatory database Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 clk: Disabling unused clocks PM: genpd: Disabling unused power domains cfg80211: failed to load regulatory.db Freeing unused kernel image (initmem) memory: 3508K This architecture does not have kernel memory protection. Run /init as init process [56] Jan 01 00:00:02 Running in background / #

4. Ethernet Driver Support

  1. In the target serial console configure the eth0 or eth1 interface manually (using the ifconfig and route plugins of busybox), or start the DHCP client to apply the networking settings from a DHCP server:

    • for the eth0interface (eth0 corresponds to the i.MX RT1170 Ethernet 100M controller):

      / # udhcpc -i eth0 Micrel KSZ8081 or KSZ8091 40424000.ethernet-1:00: attached PHY driver (mii_bus:phy_addr=40424000.ethernet-1:00, irq=POLL) fec 40424000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off / # ifconfig eth0 eth0 Link encap:Ethernet HWaddr AA:BB:CC:DD:EE:F0 inet addr:192.168.1.74 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:796 (796.0 B) TX bytes:684 (684.0 B) / #

    • for the eth1interface (eth1 corresponds to the i.MX RT1170 Ethernet 1G controller):

      / # udhcpc -i eth1 RTL8211F Gigabit Ethernet 40420000.ethernet-2:00: attached PHY driver (mii_bus:phy_addr=40420000.ethernet-2:00, irq=POLL) fec 40420000.ethernet eth1: Link is Up - 100Mbps/Full - flow control rx/tx / # ifconfig eth1 eth1 Link encap:Ethernet HWaddr 3E:1F:A2:33:A9:23 inet addr:192.168.1.90 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:31 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:2 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3186 (3.1 KiB) TX bytes:1008 (1008.0 B) / #

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

    $ ping -c5 192.168.1.74 PING 192.168.1.74 (192.168.1.74) 56(84) bytes of data. 64 bytes from 192.168.1.74: icmp_seq=1 ttl=64 time=0.632 ms 64 bytes from 192.168.1.74: icmp_seq=2 ttl=64 time=0.305 ms 64 bytes from 192.168.1.74: icmp_seq=3 ttl=64 time=0.297 ms 64 bytes from 192.168.1.74: icmp_seq=4 ttl=64 time=0.288 ms 64 bytes from 192.168.1.74: icmp_seq=5 ttl=64 time=0.298 ms --- 192.168.1.74 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4112ms rtt min/avg/max/mdev = 0.288/0.364/0.632/0.134 ms $

  3. From the target board, validate that it is connected to the internet using ping:

    / # ping -c5 example.org PING example.org (93.184.215.14): 56 data bytes 64 bytes from 93.184.215.14: seq=0 ttl=57 time=122.202 ms 64 bytes from 93.184.215.14: seq=1 ttl=57 time=122.158 ms 64 bytes from 93.184.215.14: seq=2 ttl=57 time=121.991 ms 64 bytes from 93.184.215.14: seq=3 ttl=57 time=122.116 ms 64 bytes from 93.184.215.14: seq=4 ttl=57 time=122.105 ms --- example.org ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 121.991/122.114/122.202 ms / #

5. TCP/IP Stack Support

With uClinux running on the i.MX RT1170, you get the full Linux TCP/IP stack TCP/IP stack (kernel version 6.1.22). 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 RT1170 is visible using ping:

    $ ping -c5 192.168.1.74 PING 192.168.1.74 (192.168.1.74) 56(84) bytes of data. 64 bytes from 192.168.1.74: icmp_seq=1 ttl=64 time=0.320 ms 64 bytes from 192.168.1.74: icmp_seq=2 ttl=64 time=0.274 ms 64 bytes from 192.168.1.74: icmp_seq=3 ttl=64 time=0.269 ms 64 bytes from 192.168.1.74: icmp_seq=4 ttl=64 time=0.278 ms 64 bytes from 192.168.1.74: icmp_seq=5 ttl=64 time=0.277 ms --- 192.168.1.74 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4109ms rtt min/avg/max/mdev = 0.269/0.283/0.320/0.018 ms

  2. ping the development host from the i.MX RT1170:

    / # ping -c5 192.168.1.64 PING 192.168.1.64 (192.168.1.64): 56 data bytes 64 bytes from 192.168.1.64: seq=0 ttl=64 time=0.510 ms 64 bytes from 192.168.1.64: seq=1 ttl=64 time=0.407 ms 64 bytes from 192.168.1.64: seq=2 ttl=64 time=0.394 ms 64 bytes from 192.168.1.64: seq=3 ttl=64 time=0.402 ms 64 bytes from 192.168.1.64: seq=4 ttl=64 time=0.404 ms --- 192.168.1.64 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 0.394/0.423/0.510 ms / #

  3. On the target, start the telnetd daemon to allow connections to the i.MX RT1170:

    / # telnetd / # ps | grep telnet 90 root 864 S telnetd 92 root 864 S grep telnet / #

  4. Connect to the target from the development host using telnet. The target is configured to accept the 123 password for root:

    $ telnet 192.168.1.74 Trying 192.168.1.74... Connected to 192.168.1.74. Escape character is '^]'. (none) login: root Password: / # / # ls bin hello.ko lib proc sys var dev httpd linuxrc root tmp etc init mnt sbin usr / # exit Connection closed by foreign host. $

  5. The dropbear SSH daemon starts automatically on the target. Verify that dropbear allows secure connections to the target:

    / # ps | grep dropbear 70 root 416 S dropbear -R 98 root 388 S grep dropbear

  6. Connect to the target from the development host using ssh. The first connection takes several seconds to establish as the i.MX RT1170 runs computation-extensive key calculations. Again, enter 123 on the password prompt:

    $ ssh root@192.168.1.74 The authenticity of host '192.168.1.74 (192.168.1.74)' can't be established. ED25519 key fingerprint is SHA256:/5yRBM3MvDHN7Lu4Sd1zDNpKp3c/G34RSH0qdQubRTI. This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '192.168.1.74' (ED25519) to the list of known hosts. root@192.168.1.74's password: / # ls bin hello.ko lib proc sys var dev httpd linuxrc root tmp etc init mnt sbin usr / # exit Connection to 192.168.1.74 closed. $

  7. Use ntpd to synchronize the time on the target with the time provided by a public server:

    / # date Thu Jan 1 00:11:00 UTC 1970 / # ntpd -p 0.fedora.pool.ntp.org / # sleep 5 / # date Fri Sep 1 10:07:58 UTC 2023 / #

  8. Use wget to download a file from a remote server:

    / # 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. ...

  9. Start the HTTP daemon:

    / # httpd -h /httpd/html/ / #

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

    image-20250319-100704.png

  11. Mount a directory exported by a development host over NFS:

    / # 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

6. Support USB Host Stack Interface

  1. Attach a USB Flash device to the USB1 or USB2 connector. Verify that it is automatically detected and can be mounted:

    ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected usb 1-1: new high-speed USB device number 2 using ci_hdrc usb-storage 1-1:1.0: USB Mass Storage device detected scsi host0: usb-storage 1-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 00:00 . drwxrwxrwx 8 root root 0 Jun 22 2023 .. drwxr-xr-x 2 root root 4096 May 25 2023 System Volume Information -rwxr-xr-x 1 root root 319 Jan 1 1980 data.log / #

  2. Unmount the USB Flash device:

    / # umount /mnt/usbflash/ / #

7. Support Loading / Unloading Kernel Modules

  1. From the Linux shell, load the demo kernel module:

    / # insmod hello.ko Hello, world / #

  2. Show the status of the loaded kernel modules:

    / # lsmod Module Size Used by Not tainted hello 576 0 / #

  3. Unload the module from the Linux kernel:

    / # rmmod hello Goodbye, world / #

8. Running GUI Demo

NOTE: At the current release of the BSP, this functionality is supported only for the NXP EVK board.

Step through the following procedure to run the GUI demo, LVGL widgets example:

  1. From the Linux shell, use sysfs interface to turn on LCD back-light:

    / # echo 0 > /sys/class/backlight/backlight/bl_power

  2. From the Linux shell, type the widgets_gui_demo command to run the widgets demo:

    / # widgets_gui_demo

  3. Make sure the demo appears on the LCD:

    image-20250319-100737.png

  4. Use touch panel to validate various GUI controls provided by the demo:

    image-20250319-100759.png