Use Linux on the NXP FRDM i.MX 93 board
Introduction
Set up the board
Set up a Linux user and connect to WiFi
Transfer files to the board
(Optional) Enable Persistent WiFi
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  2 hrs
Last updated:  13 Aug 2026
Skill level:
  Introductory
Reading time:
  2 hrs
Last updated:
  13 Aug 2026
Author:Waheed Brown, Arm
Arm IP:Cortex-A
Tags: ML Linux macOS Bash systemd picocom ConnMan OpenSSH
Author:
  • Waheed Brown, Arm
Arm IP:
Cortex-A
Tags:
ML Linux macOS Bash systemd picocom ConnMan OpenSSH

Who is this for?

This is an introductory topic for embedded developers and ML engineers who want to boot an NXP FRDM i.MX 93 board, connect over serial, enable WiFi, and transfer files for on-device development on Arm.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Boot the NXP FRDM i.MX 93 board and log in to Linux over a serial console.
  • Create a non-root Linux user with sudo access for development workflows.
  • Connect the board to WiFi using ConnMan.
  • Transfer files to the board over WiFi (scp) or USB.
  • Load the WiFi driver module on boot to enable automatic reconnection.

Prerequisites

Before starting, you will need the following:

  • An NXP FRDM i.MX 93 board.
  • A computer running Linux or macOS.
  • A USB-C cable for the board’s DBG serial connection.
  • A USB-C power supply/cable for the board’s POWER port.

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll configure an NXP FRDM i.MX 93 board for Linux development. Through a serial console, you’ll create a non-root user with sudo privileges and connect to Wi-Fi with ConnMan. Then, you’ll find the board’s IP address, transfer files with scp or USB, and optionally load the Wi-Fi driver at startup for automatic reconnection.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
Which USB-C port do I use for serial and power?
Use the DBG port for the serial connection and the POWER port for board power. Connect both ports if you need console access while powering the board.
How do I know the board has booted and I’m on the right console?
You should see Linux boot messages followed by a login prompt on the serial console. Log in as root initially to complete the bring-up steps.
How do I confirm the new user actually has sudo access?
After adding the user to the wheel group and enabling wheel in sudoers, log in as that user and run a command with sudo. If the command runs successfully, the configuration is correct.
Which IP address should I use for `scp`, and how do I find it?
Run the provided ifconfig command and look for the Wi-Fi interface, often named mlan0. Then, note its inet address. Use that IP in the scp target path.
What should I check if WiFi doesn’t reconnect after a reboot?
Load the Wi-Fi driver with the provided modprobe command so ConnMan can reconnect to the saved network. After loading, verify the interface has an IP address before continuing.
Next