FRDM-IMX91

Overview

The FRDM-IMX91 board is a low-cost and compact platform designed to show the most commonly used features of the i.MX 91 Applications Processor in a small and low cost package. The FRDM-IMX91 board is an entry-level development board, which helps developers to get familiar with the processor before investing a large amount of resources in more specific designs.

Hardware

  • i.MX 91 applications processor

    • The i.MX 91 Applications Processor features an Arm Cortex®-A55 core that can operate at speeds of up to 1.4 GHz.

  • RAM: 2GB LPDDR4

  • Storage:

    • SanDisk 16GB eMMC5.1

    • microSD Socket

  • Wireless:

    • Murata Type-2EL (SDIO+UART+SPI) module. It is based on NXP IW612 SoC, which supports dual-band (2.4 GHz /5 GHz) 1x1 Wi-Fi 6, Bluetooth 5.2, and 802.15.4

  • USB:

    • Two USB 2.0 Type C connectors

  • Ethernet:

    • ENET: 10/100/1000 Mbit/s RGMII Ethernet connected with external PHY YT8521

    • ENET_QoS: 10/100/1000 Mbit/s RGMII Ethernet supporting TSN connected with external PHY YT8521

  • PCIe:

    • One M.2/NGFF Key E mini card 75-pin connector

  • Connectors:

    • 40-Pin Dual Row Header

  • LEDs:

    • 1x Power status LED

    • 2x UART LED

  • Debug:

    • JTAG 20-pin connector

    • MicroUSB for UART debug

Supported Features

The frdm_imx91 board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

frdm_imx91/mimx9131 target

Type

Location

Description

Compatible

CPU

on-chip

ARM Cortex-A55 CPU1

arm,cortex-a55

CAN

on-chip

NXP FlexCAN CANFD controller11

nxp,flexcan-fd

Clock control

on-chip

i.MX CCM Rev2 (Clock Controller Module) IP node1

nxp,imx-ccm-rev2

on-chip

Generic fixed-rate clock provider4

fixed-clock

Counter

on-chip

NXP Timer/PWM Module (TPM) used as timer15

nxp,tpm-timer

DMA

on-chip

NXP MCUX EDMA controller1

nxp,mcux-edma

Ethernet

on-chip

NXP ENET1G IP Module1

nxp,enet1g

on-chip

NXP ENET MAC/L2 Device1

nxp,enet-mac

on-chip

NXP ENET MDIO Features1

nxp,enet-mdio

on-board

Motorcomm YT8521 Ethernet PHY1

motorcomm,yt8521

on-chip

NXP ENET PTP (Precision Time Protocol) Clock1

nxp,enet-ptp-clock

GPIO & Headers

on-chip

i.MX RGPIO13

nxp,imx-rgpio

on-board

NXP PCAL6408 I2C GPIO expander1

nxp,pcal6408

on-board

NXP PCAL6524 I2C GPIO expander1

nxp,pcal6524

I2C

on-chip

NXP LPI2C controller26

nxp,lpi2c

I2S

on-chip

NXP mcux SAI-I2S controller1

nxp,mcux-i2s

Input

on-board

Group of GPIO-bound input keys1

gpio-keys

Interrupt controller

on-chip

ARM Generic Interrupt Controller v31

arm,gic-v3

PHY

on-board

Simple GPIO controlled CAN transceiver1

can-transceiver-gpio

Pin control

on-chip

This compatible binding should be applied to the device’s iomuxc DTS node1

nxp,imx-iomuxc

on-chip

The node has the ‘pinctrl’ node label set in MCUX SoC’s devicetree1

nxp,imx93-pinctrl

Power management CPU operations

on-chip

Power State Coordination Interface (PSCI) version 1.11

arm,psci-1.1

SDHC

on-chip

NXP imx USDHC controller2

nxp,imx-usdhc

Serial controller

on-chip

NXP LPUART11

nxp,lpuart

Timer

on-chip

per-core ARM architected timer1

arm,armv8-timer

Watchdog

on-chip

NXP watchdog (WDOG32)11

nxp,wdog32

Devices

System Clock

This board configuration uses a system clock frequency of 24 MHz. Cortex-A55 Core runs up to 1.4 GHz.

Serial Port

This board configuration uses a single serial communication channel with the CPU’s UART1 for A55 core.

uSDHC (SD or eMMC Interface on A55)

i.MX 91 processor has three ultra secured digital host controller (uSDHC) modules for SD/eMMC interface support. On the FRDM-IMX91 board, the uSDHC2 interface of the processor connects to the MicroSD card slot (P13), and uSDHC1 interface connects to the eMMC memory (located at the SOM board). DTS overlay file “usdhc1.overlay” and “usdhc2.overlay” are provided to enable specified the uSDHC controller.

Currently it rely on U-boot or Linux to boot Zephyr, so Zephyr need to use different uSDHC controller from U-boot or Linux to avoid resource conflict. For example, if FRDM-IMX91 board boots from SD Card which uses uSDHC2, Zephyr can use MMC which uses uSDHC1 for testing:

# From the root of the zephyr repository
west build -b frdm_imx91/mimx9131 tests/subsys/sd/mmc -- -DEXTRA_DTC_OVERLAY_FILE=usdhc1.overlay

And if FRDM-IMX91 board boots from MMC which uses uSDHC1, Zephyr can use SD Card which uses uSDHC2 for testing:

# From the root of the zephyr repository
west build -b frdm_imx91/mimx9131 tests/subsys/sd/sdmmc -- -DEXTRA_DTC_OVERLAY_FILE=usdhc2.overlay

User Button

The user buttons K2 is connected to onboard GPIO expander PCAL6524, use the following command to test user buttons:

# From the root of the zephyr repository
west build -b frdm_imx91/mimx9131 samples/basic/button

Run the app, press and release K2 button, then the following log could be found on Zephyr console: .. code-block:: console

* Booting Zephyr OS build v4.3.0-6943-gc384779e39ac * Press the button Button 11 pressed at 3058829772 Button 11 released at 3064215344

Programming and Debugging

The frdm_imx91 board supports the runners and associated west commands listed below.

flash debug attach rtt debugserver reset
jlink ✅ (default) ✅ (default)

There are multiple methods to program and debug Zephyr

Option 1. Boot Zephyr by Using U-Boot Command

U-Boot “go” command is used to load and kick Zephyr to Cortex-A55 Core.

Stop the board at U-Boot command line, then need to download Zephyr binary image into DDR memory, it can use tftp:

tftp 0x80000000 zephyr.bin

Or copy the Zephyr image zephyr.bin to SD card and plug the card into the board, for example if copy the image to the FAT partition of the SD card, use the following U-Boot command to load the image into DDR memory (assuming the SD card is dev 1, fat partition ID is 1, they could be changed based on actual partitions):

fatload mmc 1:1 0x80000000 zephyr.bin;

Then use U-Boot to load and kick zephyr.bin to Cortex-A55 Core:

dcache off; icache flush; go 0x80000000

Use this configuration to run basic Zephyr applications and kernel tests, for example, with the Basic Synchronization sample:

# From the root of the zephyr repository
west build -b frdm_imx91/mimx9131 samples/synchronization

This will build an image with the synchronization sample app, boot it and display the following console output:

*** Booting Zephyr OS build v4.2.0-4272-g1cbd317fd85e ***
thread_a: Hello World from cpu 0 on frdm_imx91!
thread_b: Hello World from cpu 0 on frdm_imx91!
thread_a: Hello World from cpu 0 on frdm_imx91!
thread_b: Hello World from cpu 0 on frdm_imx91!

Option 3. Boot Zephyr by Using SPSDK Runner

SPSDK runner leverages SPSDK tools (https://spsdk.readthedocs.io), it builds an bootable flash image flash.bin which includes all necessary firmware components. Using west flash command will download the boot image flash.bin to DDR memory, SD card or eMMC flash. By using flash.bin, as no U-Boot image is available, so TF-A will boot up Zephyr on the Cortex-A55 Core directly.

In order to use SPSDK runner, it requires fetching binary blobs, which can be achieved by running the following command:

west blobs fetch hal_nxp

Note

It is recommended running the command above after west update.

SPSDK runner is enabled by configure item CONFIG_BOARD_NXP_SPSDK_IMAGE, currently it is not enabled by default for FRDM-IMX91 board, so use this configuration to enable it, for example, with the Basic Synchronization sample:

# From the root of the zephyr repository
west build -b frdm_imx91/mimx9131 samples/synchronization -- -DCONFIG_BOARD_NXP_SPSDK_IMAGE=y

If CONFIG_BOARD_NXP_SPSDK_IMAGE is available and enabled for the board variant, flash.bin will be built automatically. The programming could be through below commands. Before that, onboard switch SW1[3:0] should be configured to 0b0001 for USB download mode to boot, and USB1 and DBG ports should be connected to Linux host PC. There are 2 serial ports enumerated (115200 8n1), the first port will be used for Cortex-A55 Zephyr’s Console. (The flasher is spsdk which already installed via scripts/requirements.txt. On Linux host, USB device permission should be configured per Installation Guide of https://spsdk.readthedocs.io)

# load and run without programming. for next flashing, need to reset the board firstly
$ west flash -r spsdk

# program to SD card, then set SW1[3:0]=0b0011 to reboot from SD
$ west flash -r spsdk --bootdevice sd

# program to emmc card, then set SW1[3:0]=0b0010 to reboot from EMMC
$ west flash -r spsdk --bootdevice=emmc

Then the Zephyr log will be displayed in the first serial port’s console.

Support Resources for Zephyr