FRDM-IMX91 Board User Manual

Rev. 3.0 — 22 April 2025

Document Information

>
Information Content
Keywords i.MX 91, FRDM-IMX91, UM12262
Abstract The FRDM i.MX 91 development board (FRDM-IMX91 board) is a low-cost platform designed to show the most commonly used features of the i.MX 91 applications processor in a small and low-cost package.

1 FRDM-IMX91 overview

The FRDM i.MX 91 development board (FRDM-IMX91 board) is a low-cost 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.

This document includes system setup and configurations, and provides detailed information on the overall design and usage of the FRDM board from a hardware system perspective.

1.1 Block diagram

The FRDM-IMX91 block diagram is shown in Figure 1.

Figure 1. FRDM-IMX91 block diagram

1.2 Board features

Table 1 lists the features of FRDM-IMX91.

>
Board feature Target processor feature used Description
Applications processor The i.MX 91 applications processor features a single Arm Cortex-A55 core speeding up to 1.4 GHz. Note: For more detail on the i.MX 91 processor, see the i.MX 91 Applications Processor Reference Manual.
USB interface USB2.0 high-speed host and device controller • x1 USB 2.0 Type C connector
• x1 USB 2.0 Type A connector
DRAM memory DRAM controller and PHY 1 GB LPDDR4 (Nanya NT6AN512M16AV-J1)
Mass storage USDHC • 8 GB eMMC5.1 (FEMDRM008G-58A39)
• MicroSD card connector (SD3.0 supported)
Boot configuration • Default boot mode is single boot from the eMMC device
• Board also supports SD card boot
Display interface Parallel display Parallel display support
Ethernet interface Two ENET controllers • 10/100/1000 Mbit/s RGMII Ethernet with one RJ45 connector (P3) supporting TSN and connected with external PHY, YT8521
• 10/100/1000 Mbit/s RGMII Ethernet with one RJ45 connector (P4) connected with external PHY, YT8521
I/O expanders CAN, I2C/I3C, analog-to-digital converter (ADC) One 10-pin 2x5 2.54 mm connector P12 provides:
• One high-speed CAN transceiver TJA1051GT/3 connection
• 3-pin header for I2C/I3C expansion
• Two-channel ADC support
Tri-radio module SDIO, UART, SPI, SAI U-blox MAYA-W476-00B module supporting Wi-Fi 6, Bluetooth Low Energy 5.4, and 802.15.4
M.2 interface USB, SDIO, SAI, UART, I2C, and GPIO One M.2/NGFF Key E mini card 75-pin connector, P8, supporting USB, SDIO, SAI, UART, I2C, and Vendor-defined SPI interfaces
Note: By default, these signals are connected with the onboard tri-radio module, however, to use this M.2 slot, you must rework resistors (see Table 15).
Audio MQS MQS support
Debug interface • USB2.0 Type-C connector (P16) with USB-to-UART device, CH342F. CH342F provides two COM ports:
– First COM port is used for Cortex A55 system debug
– Second COM port is reserved
• Serial wire debug (SWD), P14
EXPI One 2x20-pin EXPI for I2S, UART, I2C, and GPIO expansion
Power • One USB 2.0 Type-C connector for power delivery only
• PCA9451AHNY PMIC
• Discrete DCDC/LDO
PCB FRDM-IMX91: 105 mm x 65 mm, 10-layer
Orderable part number FRDM-IMX91

1.3 Board kit contents

Table 2 lists the items included in the FRDM-IMX91 board kit.

>
Item description Quantity
FRDM-IMX91 board 1
USB 2.0 Type-C Male to Type-A Male assembly cable 2
FRDM-IMX91 Quick Start Guide 1

1.4 Board pictures

Figure 2 shows the top-side view of the FRDM-IMX91 board.

Figure 2. FRDM-IMX91 top-side view

Figure 3 shows the connectors available on the top side of the FRDM-IMX91 board.

Figure 3. FRDM-IMX91 connectors

Figure 4 shows the onboard switches, buttons, and LEDs available on the FRDM-IMX91 board.

Figure 4. FRDM-IMX91 onboard switches, buttons, and LEDs

Figure 5 shows the bottom-side view, and also highlights the connectors available at the bottom side of the FRDM-IMX91 board.

Figure 5. FRDM-IMX91 bottom-side view

1.5 Connectors

See Figure 3 and Figure 5 for connectors position on the board. Table 3 describes the FRDM-IMX91 board connectors.

>
Part identifier Connector type Description Reference section
P1, P2, P16 USB 2.0 Type C USB connector Section 2.16.2
P3, P4 RJ45 jack Ethernet connectors Section 2.14
P9 (DNP) U.FL connector RF antenna connector Section 2.11
P10 (DNP) U.FL connector RF antenna connector Section 2.11
P8 75-pin connector M.2 socket KEY-E Section 2.10
P11 2x20-pin connector EXPI Section 2.15
P12 2x5-pin connector I/O connector Section 2.4
P13 MicroSD push-push connector MicroSD 3.0 Section 2.8
P14 1x3-pin 2.54 mm connector SWD connector Section 2.16.1
P15 3.5 mm headphone jack MQS connector Section 2.6
P17 USB 2.0 Type A USB connector Section 2.13
P18 JST SH 2P RTC battery connector For detail, see the board schematic

1.6 Push buttons

Figure 4 shows the push buttons available on the board.

Table 4 describes the push buttons available on FRDM-IMX91.

>
Part identifier Switch name Description
K1 Power button The i.MX 91 applications processor supports the use of a button input signal to request main SoC power state changes (that is, ON or OFF) from the PMIC. The ON/OFF button is connected to the ONOFF pin of the i.MX 91 processor.
  • In the ON state: If the ON/OFF button is held longer than the debounce time, the power off interrupt is generated.
  • If the button is held longer than the defined max timeout (approx. 5 s), the state will transit from ON to OFF, and send PMIC_ON_REQ signal to turn off the powers of PMIC.
In the OFF state: If the ON/OFF button is held longer than the OFF-to-ON time, the state will transit from OFF to ON, and send PMIC_ON_REQ signal to turn on the powers of PMIC.
K2 User button The User button is kept for customized use cases.
K3 Reset / User button By default, K3 is connected with SYS_nRST and used as a reset function. To use K3 as a customized function, remove the R3061 resistor and install the R2612 resistor.

1.7 DIP switch

The following DIP switches are used on the FRDM-IMX91 board:

  • 4-bit DIP switch – SW1
  • 2-bit DIP switch – SW3
  • 1-bit DIP switch – SW4

If a DIP switch pin is:

  • OFF – pin value is 0
  • ON – pin value is 1

The following list describes the description and configuration of the DIP switches available on the board.

SW1 – Provides control for boot mode configuration. For detail, see Section 2.5.

SW3 - Provides control for enabling or disabling the CAN interface signals, CAN_TXD (GPIO_IO25) and CAN_RXD (GPIO_IO27), on the board.

>
Switch Signal Description
SW3[1] CAN_TXD (GPIO_IO25) ON (default setting): Enables CAN_TXD signal
OFF: Disables CAN_TXD signal
SW3[2] CAN_RXD (GPIO_IO27) ON (default setting): Enables CAN_RXD signal
OFF: Disables CAN_RXD signal

SW4 – Provides control for enabling or disabling the CAN split termination RC filter.

>
Switch Signal Description
SW4[1] ON (default setting): Enables RC termination filter (62 Ω + 56 pF) and configures CAN bus for normal operation.
OFF: Disables RC termination filter for test mode.

1.8 LEDs

The FRDM-IMX91 board has light-emitting diodes (LEDs) to monitor system functions, such as power-on and board faults. The information collected from LEDs can be used for debugging purposes.

Figure 4 shows the LEDs available on the board.

Table 7 describes the FRDM-IMX91 LEDs.

>
Part identifier LED color LED name Description (When LED is ON)
D601 Red PWR LED Indicates 3.3 V power-on status. When 3.3 V is available on board, the D601 LED turns ON.
LED1 Red / Green / Blue RGB_LED User application LEDs. Each of these LEDs can be controlled through a user application.
• Red LED connects to target MPU pin GPIO_IO13
• Green LED connects to target MPU pin GPIO_IO04
• Blue LED connects to target MPU pin GPIO_IO12
D613 GREEN LED_GREEN D613 ON – WLAN status indicator. When ON, indicates that the WLAN connection is established.
D614 ORANGE LED_ORANGE D614 ON – Bluetooth status indicator. When ON, indicates that the Bluetooth connection is established.

2 FRDM-IMX91 functional description

This chapter describes the features and functions of the FRDM-IMX91 board.

Note: For details of the i.MX 91 MPU features, see i.MX 91 Applications Processor Reference Manual.

The chapter is divided into the following sections:

2.1 Processor

The i.MX 91 applications processor includes single Arm Cortex-A55 processors with speeds up to 1.4 GHz. Robust control networks are possible via the CAN-FD interface. Also, dual 1 Gbit/s Ethernet controllers, one supporting time sensitive networking (TSN), drive gateway applications with low latency.

The i.MX 91 is useful for applications such as:

  • Smart home
  • Building control
  • Contactless HMI
  • Commercial
  • Healthcare
  • Industrial

Each processor provides a 16-bit LPDDR4 memory interface and other interfaces for connecting peripherals, such as WLAN, Bluetooth, USB2.0, uSDHC, Ethernet, CAN, and multisensors.

For more detailed information about the processor, see the i.MX 91 data sheet and i.MX 91 Applications Processor Reference Manual at https://www.nxp.com/imx91.

2.2 Power supply

The primary power supply to the FRDM-IMX91 board is VBUS_IN (12 V - 20 V) through USB Type-C PD connector (P1).

Three DC buck switching regulators are used:

  • MP8759GD (U702) switches VBUS_IN supply to SYS_5V (5 V) power supply, which is input power supply for PCA9451AHNY PMIC (U701) and other devices on board.
  • MP2147GD (U726) switches VDD_5V supply to VPCIe_3V3 (3.3 V / 4 A) for M.2 / NGFF module (P8).
  • MP1605C (U730) switches VPCIe_3V3 supply to VEXT_1V8 (3.3 V / 500 mA) for onboard tri-radio module MAYA-W476-00B (U731).

Figure 6 shows the FRDM-IMX91 power supply block diagram.

Figure 6. FRDM-IMX91 power supply

Table 8 describes different power sources available on the board.

>
Part identifier designator Manufacturing part number Part manufacturer Power supply Specifications Description
U702 MP8759GD Monolithic Power Systems Inc. DCDC_5V / VSYS_5V 5 V at 8 A Supplies power to:
• PMIC PCA9451AHNY (U701)
• NX20P3483UK USB PD and Type-C switches (U710)
• DC buck MP2147GD (U726) for VPCIe 3V3
• Load switch SGM2526 (U733) for VRPI_5V
• Load switch SGM2526 (U742) for VBUS_USB2_5V
• Input supply for switch-mode converter MP1605C (U730)
Supply for onboard tri-radio module u-blox MAYA-W476-00B (U731)
U726 MP2147GD Monolithic Power Systems Inc. VPChia 3V3 3.3 V at 3 A
U730 MP1605C Monolithic Power Systems Inc. VEXT_1V8 1.8 V at 500 mA Supplies power to onboard tri-radio u-blox MAYA-W476-00B module
U701 PCA9451AHNY NXP Semiconductors BUCK2: LPD4/x_VDDQ_0V6
BUCK1/3: VDD_SOC_0V8[1][2]
BUCK4: VDD 3V3
BUCK5: VDD_1V8
BUCK6: LPD4/x_VDD2_1V1
LDO1: NVCC_BBSM_1V8
LDO4: VDD_ANA_0P8
LDO5: NVCC_SD_3V3
Load switch: VSD_3V3
• 0.6 V at 2000 mA
• VOL (V): 0.85
Typ VOL (V): Dynamic voltage scaling (DVS)
Note: Refer to SoC data sheet.
3.3 V at 3000 mA
1.8 V at 2000 mA
1.1 V at 2000 mA
1.8 V at 10 mA
0.8 V at 200 mA
1.8 V/3.3 V
3.3 V
Supplies power to VDDQ_DDR power supply for CPU DRAM PHY I/O (LPDDR4)
VDD_SOC, power supply for SoC logic and Arm core
Supplies power to:
• NVCC_GPIO, power supply for GPIO when it is in 3.3 V mode
• VDD_USB_3P3 pin for USB PHY power
• eMMC 5.1 device
• MicroSD
• EEPROM
• Ethernet ports (P3 and P4)
• I2C IO expander PCAL6524HEAZ (U725, I2C address: 0x22)
Power source for:
• ENET1_DVDD3 and ENET1_AVDD3 supplies
Supplies to:
• LPD4/x VDD1
• eMMC 5.1 device
• VDD_ANA_1P8, analog core supply voltage
• NVCC_WAKEUP, digital I/O supply
Supplies to:
• VDD2_DDR, DDR PHY supply voltage
NVCC BBSM I/O supply
Analog core supply voltage
MicroSD card
MicroSD card
U703 FDS4435 (Power Trench MOSFET) SG MICRO CORP VDD_5V 5 V / 2.5 A Supplies to:
• 10-pin dual-row header (P12)
• CAN transceiver through CAN_VDD_5V
• RGB LED
Power source for:
• VPCIe_3V3
• VRPI_5V
• VBUS_USB2_5V
U732 SGM2525 (Load switch) SG MICRO CORP VRPI_3V3 3.3 V at 2.5 A 2x20-pin EXPI connector (P11)
U733 SGM2525 (Load switch) SG MICRO CORP VRPI_5V 5 V at 2.5 A 2x20-pin EXPI connector (P11)
U737 TLV76033DBZR (Voltage regulator) Texas Instruments VCC_3V3 DEBUG 3.3 V Supplies to 4-bit voltage-level translator used for USB-to-dual UART debug interface
U742 SGM2526 (Load switch) SG MICRO CORP VBUS_USB2_5V 5V / 2.5 A Supplies to USB2.0 Type-A Host

For further details on the power sequence needed by the i.MX 91, see section "Power sequence" in the i.MX 91 Reference Manual.

2.3 Clocks

FRDM-IMX91 provides all the clocks required for the processor and peripheral interfaces. Table 9 summarizes the specifications of each clock and the component that provides it.

>
Part identifier Clock generator Clock Specifications Destination
Y401 Crystal oscillator XTALI_24M / XTALO_24M Frequency: 24 MHz Target processor
QZ401 Crystal oscillator XTALI_32K / XTALO_32K Frequency: 32.768 kHz NVCC_BBSM block of target processor
QZ701 Crystal oscillator XIN_32K / XOUT_32K Frequency: 32.768 kHz PCA9451AHNY PMIC
Y402 Crystal oscillator PHY1_XTAL_I / PHY1_XTAL_O Frequency: 25 MHz Ethernet RMII PHY1
Y403 Crystal oscillator PHY2_XTAL_I / PHY2_XTAL_O Frequency: 25 MHz Ethernet RMII PHY2

2.4 I2C interface

The i.MX 91 processor supports a low-power inter-integrated circuit (I2C) module that supports an efficient interface to an I2C-bus as a master. The I2C provides a method of communication between a number of devices available on the FRDM-IMX91 board.

One 10-pin 2x5 2.54 mm connector P12 is provided on the board to support I2C, CAN, and ADC connections. The developers can use the port for some specific application development.

Table 10 explains the I2C, CAN, and ADC header, P12, pinout.

>
Pin Signal name Description
1 VDD_3V3 3.3 V power supply
2 VDD_5V 5 V power supply
3 ADC_INO ADC input channel 0
4 ADC_IN1 ADC input channel 1
5 I3C_INT I2C/I3C interrupt signal
6 GND Ground
7 I3C_SCL I2C/I3C SCL signal
8 CAN_H CAN transceiver high signal
9 I3C_SDA I2C/I3C SDA signal
10 CAN_L CAN transceiver low signal

Table 11 describes the I2C devices and their I2C addresses (7-bit) on the board.

>
Part identifier Device I2C address (7-bit) Port Speed Voltage Description
U748 PCAL6408AHK 0x20 (0b'0100000x) MX-I2C1 1 MHz Fm+ 3.3 V I/O expander for IRQ / OUTPUT
U701 PCA9451AHNY 0x25 (0b'0100101x) MX-I2C2 1 MHz Fm+ 3.3 V PMIC
U725 PCAL6524HEAZ 0x22 (0b'01000[10]x) MX-I2C2 1 MHz Fm+ 3.3 V IO expander for IRQ/ OUTPUT
U10 FT24C256A 0x50 (0b'1010000x) MX-I2C2 1 MHz Fm+ 3.3 V EEPROM
U705 PTN5110NHQZ 0x52 (0b'10100[10]x) MX-I2C3 1 MHz Fm+ 3.3 V USB Type-C Power Delivery PHY
U712 PTN5110NHQZ 0x50 (0b'10100[00]x) MX-I2C3 1 MHz Fm+ 3.3 V USB Type-C Power Delivery PHY
U710 NX20P3483UK 0x71 (0b'11100[01]x) MX-I2C3 1 MHz Fm+ 3.3 V USB load switch
U740 PCF2131 0x 53 (0b'110101[0]x) MX-I2C3 400 kHz Fm 3.3 V External RTC

2.5 Boot mode and boot device configuration

The i.MX 91 processor offers multiple boot configurations, selectable by SW1 on the FRDM-IMX91 board. In addition, the i.MX 91 can download a program image from a USB connection when configured in serial download mode. The four dedicated BOOT MODE pins are used to select the various boot modes.

Figure 7 shows the boot mode selection switch.

Figure 7. Boot mode selection switch

Table 12 describes the SW1 values used in different boot modes.

>
SW1 [3:0] BOOT_MODE[3:0] Boot core Boot device
0001 0001 Cortex-A55 Serial downloader (USB)
0010 0010 uSDHC1 8-bit eMMC 5.1
0011 0011 uSDHC2 4-bit SD3.0

On the FRDM-IMX91 board, the default boot mode is from the eMMC device. The other boot device is the microSD connector. Set SW1[3:0] as 0010 to choose uSDHC1 (eMMC) as boot device, set 0011 to choose uSDHC2 (SD), and set 0001 to enter USB serial download.

Note: For more information about the boot modes and boot device configuration, see chapter "System Boot" in the i.MX 91 Applications Processor Reference Manual.

Figure 8 shows the connection of SW1 and i.MX 91 boot mode signals.

Figure 8. Boot configuration schematic

2.6 PDM interface

The pulse density modulated (PDM) microphone interface of the processor provides PDM/MQS support on the FRDM-IMX91, and it connects to a 3.5 mm audio jack (P15).

>
Part identifier Manufacturing part number Description
P15 PJ 3536X 3.5 mm audio jack for onboard MQS analog input / output

2.7 LPDDR4 DRAM memory

The FRDM-IMX91 board features one 512 M × 16 (1 channel ×16 I/O × 1 rank) LPDDR4 SDRAM chip (NT6AN512M16AV-J1) for a total of 1 GB of RAM memory. The LPDDR4 DRAM memory is connected to the i.MX 91 DRAM controller.

The ZQ calibration resistors (R209 and R2941) used by the LPDDR4 chip are 240 Ω 1% to LPD4/x_VDDQ and the ZQ calibration resistor DRAM_ZQ used at i.MX 91 SoC side is 120 Ω 1% to GND.

In the physical layout, the LPDDR4 chip is placed at the top side of the board. The data traces are not necessarily connected to the LPDDR4 chips in sequential order. Instead, the data traces are connected as best determined by the layout and other critical traces for the ease of routing.

2.8 SD card interface

The target processor has three ultra secured digital host controller (uSDHC) modules for SD/eMMC interface support. The uSDHC2 interface of the i.MX 91 processor connects to the MicroSD card slot (P13) on the FRDM-IMX91 board. This connector supports one 4-bit SD3.0 MicroSD card. To select it as the boot device of the board, see Section 2.5.

2.9 eMMC memory

The eMMC memory (at the SOM board) is connected to the uSDHC1 interface of the i.MX 91 processor, which can support eMMC 5.1 devices. It is the default boot device of the board. Table 12 describes the boot settings.

Table 14 describes the eMMC memory device that is supported by the uSDHC1 interface.

>
Part identifier Part number Configuration FBGA Manufacturer Memory size
U501 FEMDRM008G-58A39 64 Gb x1 TFBGA-153 FORESEE 8 GB

2.10 M.2 interface

The FRDM-IMX91 board supports the M.2/NGFF Key E mini card 75-pin connector, P8. The M.2 mini card connector supports USB, SDIO, SAI, UART, I2C, and GPIO connection. By default, these signals are connected with the onboard tri-radio MAYA-W476-00B module, however, to use this M.2 slot, the following resistors must be reworked.

>
Resistors DNP Resistors install
R2808, R2809, R2812, R2819, R2820, R2821
R3023, R3024, R2958, R3028
R2854, R2855
R3038, R2870, R2871
R2788, R2791, R2792, R2794
R2796, R2798, R2800, R2802
R2797, R2799, R2801, R2805
R2832, R2834, R2836, R2838
R2824, R2825, R2826, R2827, R2828, R2829
R2960, R2860
R2851, R2853
R3037, R2866, R2867
R2789, R2790, R2793, R2795
R2833, R2835, R2837, R2839

The M.2 connector can be used for Wi-Fi / Bluetooth card, IEEE 802.15.4 Radio, or 3G / 4G cards.

Table 16 describes the pinout of the M.2 mini card connector (P8).

>
Pin number M.2 mini card connector pin Connection details
2, 4, 72, 74 3V3_1, 3V3_2, 3V3_3, 3V3_4 Connected to VPCIe_3V3 power supply
6 LED1 Connected to M.2 Green LED, D613
8 I2S_SCK Connected to SAI1_TXC processor pin if R2788 is populated
10 I2S_WS Connected to SAI1_TXFS processor pin if R2791 is populated
12 I2S_SD_IN Connected to SAI1_RXD processor pin if R2794 is populated
14 I2S_SD_OUT Connected to SAI1_TXD processor pin if R2792 is populated
16 LED2 Connected to M.2 Orange LED, D614
20 UART_WAKE M2_UART_nWAKE input for I/O expander (PCAL6524HEAZ, P0_3, I2C address: 0x22) if R2853 is populated
22 UART_RXD Connected to UART5_RXD if R2835 is populated
32 UART_TXD Connected to UART5_TXD if R2833 is populated
34 UART_CTS Connected to UART5_CTSI if R2839 is populated
36 UART_RTS Connected to UART5_RTSO if R2837 is populated
38 VEN_DEF1 Connected to SPI3_MOSI if R2790 is populated
40 VEN_DEF2 Connected to SPI3_MISO if R2795 is populated
42 VEN_DEF3 Connected to SPI3_CLK if R2793 is populated
50 SUSCLK Connected to PMIC_32K_OUT, generated by PCA9451AHNY PMIC
52 PERSTO M2_nRST input for I/O expander (PCAL6524HEAZ, P2_2, I2C address: 0x22)
54 W_DISABLE2 M2 nDIS2 input for I/O expander (PCAL6524HEAZ, P2_3, I2C address: 0x22) if R2867 is populated
56 W_DISABLE1 M2 nDIS1 input for I/O expander (PCAL6524HEAZ, P2_4, I2C address: 0x22) if R2866 is populated
58 I2C_DATA Connected to SDAL pin of PCA9451AHNY PMIC
60 I2C_CLK Connected to SCLL pin of PCA9451AHNY PMIC
62 ALERT M2_nALERT input for I/O expander (PCAL6524HEAZ, P1_2, I2C address: 0x22) if R2860 is populated
3 USB_D+ Connected to USB2_D_P processor pin if R2806 is populated
5 USB_D- Connected to USB2_D_N if R2807 is populated
9 SDIO_CLK Connected to the SD3_CLK processor pin and processor interface SDHC3 if R2824 is populated
11 SDIO_CMD Connected to the SD3_CMD processor pin and processor interface SDHC3 if R2825 is populated
13 SDIO_DATA0 Connected to the SD3_DATA0 processor pin and processor interface SDHC3 if R2826 is populated
15 SDIO_DATA1 Connected to the SD3_DATA1 processor pin and processor interface SDHC3 if R2827 is populated
17 SDIO_DATA2 Connected to the SD3_DATA2 processor pin and processor interface SDHC3 if R2828 is populated
19 SDIO_DATA3 Connected to the SD3_DATA3 processor pin and processor interface SDHC3 if R2829 is populated
21 SDIO_WAKE Connected to the CCM_CLK01 processor pin of NVCC_WAKEUP module if R2851 is populated
23 SDIO_RST SD3_nRST output from I/O expander (PCAL6524HEAZ, P1_4, I2C address: 0x22) if R3037 is populated
55 PEWAKEO PCIE_WAKE input for I/O expander (PCAL6524HEAZ, P0_2, I2C address: 0x22) if R2868 is populated

For further details about i.MX 91 interfaces, see i.MX 91 Applications Processor Reference Manual.

2.11 Tri-radio module interface

The FRDM-IMX91 board features a Tri-radio (Wi-Fi 6, Bluetooth Low Energy 5.4, and 802.15.4) module based on the NXP IW612 that interfaces with the SD2, UART5, SAI1, and SPI3 controller of the target processor.

>
Part identifier Manufacturing part number Description
U731 MAYA-W476-00B (u-blox) Host-based Wi-Fi 6, Bluetooth Low Energy 5.4, and 802.15.4 modules for IoT applications

The two antenna pins (RF_ANT0 and RF_ANT1) of the module connects to U.FL connectors P9 and P10 (DNP by default). The module is supplied with VPCIe_3V3, VEXT_1V8, and VDD_1V8.

The MAYA-W476-00B module and M.2 connector share several interface lines on the FRDM-IMX91 board. Zero-ohm resistors enable signal selection between these components.

SD3 interface

The SD3 interface lines are shared between the MAYA-W476-00B module and the M.2 connector. Zero-ohm resistors select either the MAYA-W476-00B module (default setting) or the M.2 connector.

UART5 interface

Similarly, the UART5 interface lines are shared between the MAYA-W476-00B module and the M.2 connector. Zero-ohm resistors select either the MAYA-W476-00B module (default setting) or the M.2 connector.

SAI1 interface

The SAI1 interface lines are shared between the MAYA-W476-00B module and the M.2 connector. Zero-ohm resistors select either the MAYA-W476-00B module (default setting) or the M.2 connector for 1.8 V translated signals, generated using the 74AVC4T3144 bidirectional voltage translator (U728).

SPI3 interface

The SPI3 signals (CLK, MOSI, MISO, and CS0) are multiplexed with GPIO_IO[08, 09, 10, 11] signals, respectively. These SPI3 signals are shared between the MAYA-W476-00B module and the M.2 connector. Zero-ohm resistors select either the MAYA-W476-00B module (default setting) or the M.2 connector for 1.8 V translated signals, generated using the 74AVC4T3144 bidirectional voltage translator (U729).

2.12 CAN interface

The i.MX 91 processor supports a controller area network (CAN) module that is a communication controller implementing the CAN protocol according to the CAN with flexible data rate (CAN FD) protocol and the CAN 2.0B protocol specification. The processor supports two CAN FD controllers.

On the FRDM-IMX91 board, one of the controllers is connected to the high-speed CAN transceiver TJA1051T/3. The high-speed CAN transceiver drives CAN signals between the target processor and a 10-pin 2x5 2.54 mm header (P12) to its physical two-wire CAN bus.

The CAN_TXD and CAN_RXD signals are multiplexed on GPIO_IO25 and GPIO_IO27, respectively. On the board, a 2-bit DIP switch (SW3) is used to control the CAN signals. For SW3 detail, see Section 1.7. The CAN_STBY signal from the IO expander PCAL6524HEAZ (U725, P2_7, I2C address: 22) enables / disables CAN standby mode.

The CAN interface circuit includes the split termination RC filter (62Ω + 56pF) for noise rejection and signal integrity. The switch SW4 is provided for enabling/disabling the RC filter. For SW4 detail, see Section 1.7.

The HS-CAN transceiver and header are described in Table 18.

>
Part identifier Manufacturing part number Description
U741 TJA1051T/3 High-speed CAN transceiver. Provides an interface between a CAN protocol controller and the physical two-wire CAN bus.
P12 Not applicable 10-pin 2x5 2.54 mm connector (P12). It is connected to the CAN bus and allows external connection with the bus.
Note: Table 10 explains pinout for the 10-pin 2x5 2.54 mm connector P12.
Note: For details about TJA1051, see TJA1051 data sheet at nxp.com.

2.13 USB interface

The i.MX 91 applications processor features two USB 2.0 controllers, with two integrated USB PHYs. On the FRDM-IMX91 board, one is used for the USB2.0 Type-C Port (P2) and the other is used for USB2.0 Type-A Port (P17).

Table 19 describes the USB ports available on the board.

>
Part identifier USB port type Description
P2 USB2.0 Type-C Connects to full-speed USB host and device controller (USB 1) of target processor.
It can operate as a device or host. The USBC_VBUS signal controls the VBUS drive for the USB port.
P17 USB2.0 Type-A Connects to full-speed USB host and device controller (USB 2) of target processor. It can operate as a device or host. The USB2_VBUS signal controls the VBUS drive for the USB port.
The USB2_DP and USB2_DN signals from the USB2 controller of the target processor connect to USB2 Type A port (P17) by default. These signals can be connected to M.2 card connecter (P6) by solder/DNP R2803, R2804, R2806, R2807.
P1 USB Type-C PD It is used for power only. It does not support USB data transfer. It is the only power supply port therefore it must always be supplied for system power.
P16 USB Type-C It is used for system debug purpose. For detail, see the system debug section.

2.14 Ethernet

The i.MX 91 processor supports two Gigabit Ethernet controllers (capable of simultaneous operation) with support for Energy-Efficient Ethernet (EEE), Ethernet AVB, and IEEE 1588.

The Ethernet subsystem of the board is provided by the Motorcomm YT8521SH-CA Ethernet transceivers (U713, U716) which support RGMII and connect to RJ45 connectors (P3, P4). The Ethernet transceivers (or PHYs) receive standard RGMII Ethernet signals from i.MX 91. The RJ45 connectors integrate Magnetic transformer inside, so they can be directly connected to Ethernet transceivers (or PHYs).

Each Ethernet port has a unique MAC address, which is fused into i.MX 91. The Ethernet connectors are labeled clearly on the board.

2.15 EXPI connector

One 2x20-pin EXPI connector (P11) is provided on the FRDM-IMX91 board to support I2S, UART, I2C, and GPIO connections. The header can be used to access various pins or to plug in accessory cards, such as the LCD display TM050RDH03-41, 8MIC-RPI-MX8 card, and MX93AUD-HAT.

The connector is shown in Figure 3.

>
Pin number Net name Pin number Net name
1 VRPI_3V3 2 VRPI_5V
3 GPIO_I002 4 VRPi_5V
5 GPIO_1003 6 GND
7 GPIO_I004 8 GPIO_IO14
9 GND 10 GPIO_IO15
11 GPIO_IO17 12 GPIO_IO18
13 GPIO_IO27 14 GND
15 GPIO_IO22 16 GPIO_IO23
17 VRPI_3V3 18 GPIO_IO24
19 GPIO_IO10 20 GND
21 GPIO_I009 22 GPIO_IO25
23 GPIO_IO11 24 GPIO_I008
25 GND 26 GPIO_I007
27 GPIO_1000 28 GPIO_I001
29 GPIO_I005 30 GND
31 GPIO_1006 32 GPIO_IO12
33 GPIO_IO13 34 GND
35 GPIO_IO19 36 GPIO_IO16
37 GPIO_IO26 38 GPIO_IO20
39 GND 40 GPIO_IO21

2.16 Debug interface

The FRDM-IMX91 board features two independent debug interfaces.

  • Serial wire debug (SWD) header (Section 2.16.1)
  • USB-to-dual UART debug port (Section 2.16.2)

2.16.1 SWD interface

The i.MX 91 applications processor has two serial wire debug (SWD) signals on dedicated pins, and those signals are directly connected to the standard 3-pin 2.54 mm connector P14. The two SWD signals used by the processor are:

  • SWCLK (serial wire clock)
  • SWDIO (serial wire data input / output)

The SWD connector P14 is shown in Figure 3.

2.16.2 USB debug interface

The i.MX 91 applications processor has six independent UART ports (UART1 – UART6). On the FRDM-IMX91 board, UART1 is used for Cortex-A55 core. A single chip USB to dual UART is used for the debug purpose. The part number is CH342F. You can download the driver from WCH Website.

After installing the CH342F driver, the PC / USB host enumerates two COM ports connected to the P16 connector through a USB cable:

  • COM Port 1: Cortex-A55 system debugging
  • COM Port 2: Reserved

You can use the following terminal tools for debugging purposes:

  • Putty
  • Tera Term
  • Xshell
  • Minicom>=2.9

To debug under Linux, make sure CH342F Linux driver is installed.

Table 21 describes the required settings.

>
Terminal setting parameters
Data rate 115,200 Baud
Data bits 8
Parity None
Stop bits 1

The USB debug connector P16 is shown in Figure 3.

2.17 Board errata

No board errata.

3 Working with accessories

This section describes how a connection can be established between with the FRDM-IMX91 board and compatible accessory boards.

3.1 5-inch Tianma LCD

TM050RDH03-41 is a 5" TFT LCD display with 800x480 resolution. This industrial-grade display uses an RGB interface without a touch panel. This display module connects to the FRDM-IMX91 through the EXPI 2x20-pin connector (P11).

3.1.1 Connection between Tianma panel and adapter board

Figure 11 shows the FPC connection between the 5-inch Tianma LCD panel and adapter board. Insert the FPC connector with the conductive side up (stiffener side down).

Figure 11. FPC connection between 5-inch Tianma LCD panel and adapter board

3.1.2 Connection between adapter board and FRDM-IMX91

Plug 5" Tianma LCD to FRDM-IMX91 through the EXPI 2x20-pin connector (P11) as shown in Figure 12.

Figure 12. 5-inch Tianma LCD connection with FRDM-IMX91 through 2x20-pin EXPI connector

3.1.3 Software configuration update

The following steps specify how to replace the default dtb with the custom dtb (imx91-11x11-frdm-tianma-wvga-panel.dtb) that supports Tianma LCD.

  1. Stop at U-Boot
  2. Use the below commands to replace the default dtb:
$setenv fdtfile imx91-11x11-frdm-tianma-wvga-panel.dtb
$saveenv
$boot

3.2 Other accessory boards

There are other accessory boards also that can work with FRDM-IMX91 through EXPI 2x20-pin interface, such as 8MIC-RPI-MX8 and MX93AUD-HAT. To use any such board, check the schematic and layout to determine the direction of the connection between FRDM-IMX91 and the accessory board in advance. Also, choose the right dtb file in the U-Boot stage.

3.2.1 Software configuration update

  • To use the MX93AUD-HAT and 8MIC-RPI-MX8 boards together or use the MX93AUD-HAT board alone, run the following commands at U-Boot to replace the default dtb:
$setenv fdtfile imx91-11x11-frdm-aud-hat.dtb
$saveenv
$boot
  • To use the 8MIC-RPI-MX8 board alone, run the following commands at U-Boot to replace the default dtb:
$setenv fdtfile imx91-11x11-frdm-8mic.dtb
$saveenv
$boot

4 PCB information

The FRDM-IMX91 is made with standard 10-layer technology. The material is FR-4, and the PCB stack-up information is described in Table 22.

>
Layer Description Copper (mil) Generic Er Dielectric thickness (mil)
1 TOP 0.7+Plating 1.3 2.61
Dielectric
2 GND02 1.4
Dielectric
3 ART03 1.4
Dielectric
4 PWR04 1.4
Dielectric
5 PWR05 1.4
Dielectric
6 ART06 1.4
Dielectric
7 GND07 1.4
Dielectric
8 ART08 1.4
Dielectric
9 GND09 1.4
Dielectric
10 BOTTOM 0.7+Plating 1.3 2.61

Finished: 1.6 mm
Designed: 71.304 mil
Material: FR-4

5 European Union regulatory compliance

Table 23 is provided as per Article 10.8 of the Radio Equipment Directive 2014/53/EU.

(a) Frequency bands in which the equipment operates.

(b) The maximum RF power transmitted.

>
Part number RF technology (a) Frequency range (b) Maximum transmitted power
FRDM-IMX91 Bluetooth Low Energy 5.4 2402 MHz - 2480 MHz 13 dBm
IEEE 802.15.4 2405 MHz - 2480 MHz 13 dBm
Wi-Fi IEEE 802.11b/g/n/ax 2400 MHz - 2500 MHz 16 dBm
Wi-Fi IEEE 802.11a/n/ac/ax 4900 MHz - 5895 MHz 18 dBm

EUROPEAN DECLARATION OF CONFORMITY (Simplified DoC per Article 10.9 of the Radio Equipment Directive 2014/53/EU)

This apparatus, namely FRDM-IMX91 Freedom Development Platform, conforms to the Radio Equipment Directive 2014/53/EU. The full EU Declaration of Conformity for this apparatus can be found at the NXP website: FRDM-IMX91.

6 Acronyms

Table 24 lists and explains the acronyms and abbreviations used in this document.

>
Term Description
BGA Ball grid array
CAN Controller area network
DNP Do not populate
DRAM Dynamic random access memory
DSI Display serial interface
eMMC Embedded multimedia card
ENET Ethernet transceiver
EXPI Expansion interface
FD Flexible data rate
GPIO General-purpose input/output
HS High-speed
I2C Inter-integrated circuit
I2S Inter-IC sound
I3C Improved inter-integrated circuit
LDO Low dropout regulator
LED Light-emitting diode
MISO Master input slave output
MOSI Master output slave input
MQS Medium quality sound
NGFF Next-generation form factor
PCB Printed circuit board
PDM Pulse-density modulation
PMIC Power management-integrated circuit
PWM Pulse width modulation
RGMII Reduced gigabit media independent interface
SAI Serial audio interface
SDIO Secure digital I/O
SPI Serial peripheral interface
SWD Serial wire debug
TSN Time-sensitive networking
UART Universal asynchronous receiver/transmitter
USB Universal serial bus
USDHC Ultra secured digital host controller

7 Related documentation

Table 25 lists and explains the additional documents and resources that you can refer to for more information on the FRDM-IMX91 board. Some of the documents listed below may be available only under a nondisclosure agreement (NDA). To request access to these documents, contact your local field applications engineer (FAE) or sales representative.

>
Document Description Link / how to access
i.MX 91 Applications Processor Reference Manual Intended for system software and hardware developers and application programmers who want to develop products with i.MX 91 MPU IMX91RM
i.MX 91 Industrial Application Processors Data Sheet Provides information about electrical characteristics, hardware design considerations, and ordering information IMX91IEC
i.MX 91 Hardware Design Guide This document aims to help hardware engineers design and to test their i.MX 91 processor-based designs. It provides information about board layout recommendations and design checklists to ensure first-pass success and avoidance of board bring-up problems. UG10147

8 Note about the source code in the document

The example code shown in this document has the following copyright and BSD-3-Clause license:

Copyright 2025 NXP Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

9 Revision history

Table 26 summarizes the revisions to this document.

>
Document ID Release date Description
UM12262 v.3.0 22 April 2025 Updated link in Section 5
UM12262 v.2.0 5 March 2025 Updated Section 5
UM12262 v.1.0 25 February 2025 Initial public release

Legal information

Definitions

Draft - A draft status on a document indicates that the content is still under internal review and subject to formal approval, which may result in modifications or additions. NXP Semiconductors does not give any representations or warranties as to the accuracy or completeness of information included in a draft version of a document and shall have no liability for the consequences of use of such information.

Disclaimers

Limited warranty and liability - Information in this document is believed to be accurate and reliable. However, NXP Semiconductors does not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information and shall have no liability for the consequences of use of such information. NXP Semiconductors takes no responsibility for the content in this document if provided by an information source outside of NXP Semiconductors.

In no event shall NXP Semiconductors be liable for any indirect, incidental, punitive, special or consequential damages (including - without limitation - lost profits, lost savings, business interruption, costs related to the removal or replacement of any products or rework charges) whether or not such damages are based on tort (including negligence), warranty, breach of contract or any other legal theory.

Notwithstanding any damages that customer might incur for any reason whatsoever, NXP Semiconductors' aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms and conditions of commercial sale of NXP Semiconductors.

Right to make changes - NXP Semiconductors reserves the right to make changes to information published in this document, including without limitation specifications and product descriptions, at any time and without notice. This document supersedes and replaces all information supplied prior to the publication hereof.

Suitability for use NXP Semiconductors products are not designed, authorized or warranted to be suitable for use in life support, life-critical or safety-critical systems or equipment, nor in applications where failure or malfunction of an NXP Semiconductors product can reasonably be expected to result in personal injury, death or severe property or environmental damage. NXP Semiconductors and its suppliers accept no liability for inclusion and/or use of NXP Semiconductors products in such equipment or applications and therefore such inclusion and/or use is at the customer's own risk.

Applications - Applications that are described herein for any of these products are for illustrative purposes only. NXP Semiconductors makes no representation or warranty that such applications will be suitable for the specified use without further testing or modification.

Customers are responsible for the design and operation of their applications and products using NXP Semiconductors products, and NXP Semiconductors accepts no liability for any assistance with applications or customer product design. It is customer's sole responsibility to determine whether the NXP Semiconductors product is suitable and fit for the customer's applications and products planned, as well as for the planned application and use of customer's third party customer(s). Customers should provide appropriate design and operating safeguards to minimize the risks associated with their applications and products.

NXP Semiconductors does not accept any liability related to any default, damage, costs or problem which is based on any weakness or default in the customer's applications or products, or the application or use by customer's third party customer(s). Customer is responsible for doing all necessary testing for the customer's applications and products using NXP Semiconductors products in order to avoid a default of the applications and the products or of the application or use by customer's third party customer(s). NXP does not accept any liability in this respect.

Terms and conditions of commercial sale NXP Semiconductors products are sold subject to the general terms and conditions of commercial sale, as published at https://www.nxp.com/profile/terms, unless otherwise agreed in a valid written individual agreement. In case an individual agreement is concluded only the terms and conditions of the respective agreement shall apply. NXP Semiconductors hereby expressly objects to applying the customer's general terms and conditions with regard to the purchase of NXP Semiconductors products by customer.

Export control - This document as well as the item(s) described herein may be subject to export control regulations. Export might require a prior authorization from competent authorities.

Suitability for use in non-automotive qualified products - Unless this document expressly states that this specific NXP Semiconductors product is automotive qualified, the product is not suitable for automotive use. It is neither qualified nor tested in accordance with automotive testing or application requirements. NXP Semiconductors accepts no liability for inclusion and/or use of non-automotive qualified products in automotive equipment or applications.

In the event that customer uses the product for design-in and use in automotive applications to automotive specifications and standards, customer (a) shall use the product without NXP Semiconductors' warranty of the product for such automotive applications, use and specifications, and (b) whenever customer uses the product for automotive applications beyond NXP Semiconductors' specifications such use shall be solely at customer's own risk, and (c) customer fully indemnifies NXP Semiconductors for any liability, damages or failed product claims resulting from customer design and use of the product for automotive applications beyond NXP Semiconductors' standard warranty and NXP Semiconductors' product specifications.

Evaluation products This evaluation product is intended solely for technically qualified professionals, specifically for use in research and development environments to facilitate evaluation purposes. It is not a finished product, nor is it intended to be a part of a finished product. Any software or software tools provided with an evaluation product are subject to the applicable license terms that accompany such software or software tools. This evaluation product is provided on an "as is" and "with all faults" basis for evaluation purposes only and is not to be used for product qualification or production. If you choose to use these evaluation products, you do so at your risk and hereby agree to release, defend and indemnify NXP (and all of its affiliates) for any claims or damages resulting from your use. NXP, its affiliates and their suppliers expressly disclaim all warranties, whether express, implied or statutory, including but not limited to the implied warranties of non-infringement, merchantability and fitness for a particular purpose. The entire risk as to the quality, or arising out of the use or performance, of this evaluation product remains with user.

In no event shall NXP, its affiliates or their suppliers be liable to user for any special, indirect, consequential, punitive or incidental damages (including without limitation damages for loss of business, business interruption, loss of use, loss of data or information, and the like) arising out the use of or inability to use the evaluation product, whether or not based on tort (including negligence), strict liability, breach of contract, breach of warranty or any other theory, even if advised of the possibility of such damages.

Notwithstanding any damages that user might incur for any reason whatsoever (including without limitation, all damages referenced above and all direct or general damages), the entire liability of NXP, its affiliates and their suppliers and user's exclusive remedy for all of the foregoing shall be limited to actual damages incurred by user based on reasonable reliance up to the greater of the amount actually paid by user for the evaluation product or five dollars (US$5.00). The foregoing limitations, exclusions and disclaimers shall apply to the maximum extent permitted by applicable law, even if any remedy fails of its essential purpose and shall not apply in case of willful misconduct.

HTML publications An HTML version, if available, of this document is provided as a courtesy. Definitive information is contained in the applicable document in PDF format. If there is a discrepancy between the HTML document and the PDF document, the PDF document has priority.

Translations - A non-English (translated) version of a document, including the legal information in that document, is for reference only. The English version shall prevail in case of any discrepancy between the translated and English versions.

Security Customer understands that all NXP products may be subject to unidentified vulnerabilities or may support established security standards or specifications with known limitations. Customer is responsible for the design and operation of its applications and products throughout their lifecycles to reduce the effect of these vulnerabilities on customer's applications and products. Customer's responsibility also extends to other open and/or proprietary technologies supported by NXP products for use in customer's applications. NXP accepts no liability for any vulnerability. Customer should regularly check security updates from NXP and follow up appropriately. Customer shall select products with security features that best meet rules, regulations, and standards of the intended application and make the ultimate design decisions regarding its products and is solely responsible for compliance with all legal, regulatory, and security related requirements concerning its products, regardless of any information or support that may be provided by NXP.

NXP has a Product Security Incident Response Team (PSIRT) (reachable at PSIRT@nxp.com) that manages the investigation, reporting, and solution release to security vulnerabilities of NXP products.

NXP B.V. - NXP B.V. is not an operating company and it does not distribute or sell products.

Trademarks

Notice: All referenced brands, product names, service names, and trademarks are the property of their respective owners.

NXP - wordmark and logo are trademarks of NXP B.V.

AMBA, Arm, Arm7, Arm7TDMI, Arm9, Arm11, Artisan, big.LITTLE, Cordio, CoreLink, CoreSight, Cortex, DesignStart, DynamIQ, Jazelle, Keil, Mali, Mbed, Mbed Enabled, NEON, POP, RealView, SecurCore, Socrates, Thumb, TrustZone, ULINK, ULINK2, ULINK-ME, ULINK-PLUS, ULINKpro, µVision, Versatile are trademarks and/or registered trademarks of Arm Limited (or its subsidiaries or affiliates) in the US and/or elsewhere. The related technology may be protected by any or all of patents, copyrights, designs and trade secrets. All rights reserved.

Bluetooth - the Bluetooth wordmark and logos are registered trademarks owned by Bluetooth SIG, Inc. and any use of such marks by NXP Semiconductors is under license.

Models: i.MX 91, FRDM-IMX91, UM12262, UM12262 Development Board, UM12262, Development Board, Board

File Info : application/pdf, 34 Pages, 4.06MB

PDF preview unavailable. Download the PDF instead.

p1197002-UM12262

References

Apache FOP Version 2.8

Related Documents

Preview NXP FRDM Development Platforms for Seamless Prototyping and Rapid Development
Explore NXP's FRDM (Freedom) Development Platforms, offering a flexible and scalable hardware design for a wide range of edge applications. Discover MCUs and i.MX Application Processors, software tools, expansion boards, and application code for AI/ML, security, IoT, and more. Get started with rapid prototyping and development.
Preview Getting Started with IW610 Module on FRDM i.MX 91 Development Board Running Linux OS
This guide provides comprehensive instructions for setting up the IW610 module on the FRDM i.MX 91 development board with Linux OS. Learn how to configure Wi-Fi, Bluetooth LE, and 802.15.4, transfer software files, and bring up essential network functionalities.
Preview i.MX Linux User's Guide: Build and Install the i.MX Linux OS BSP
A comprehensive guide for building and installing the i.MX Linux OS Board Support Package (BSP) on i.MX platforms. This document covers essential steps, special i.MX features, and provides detailed instructions for various i.MX hardware configurations.
Preview NXP i.MX Linux User's Guide: Build, Install, and Utilize i.MX Linux OS BSP
Comprehensive guide for developers on building and installing the i.MX Linux OS Board Support Package (BSP). Covers i.MX platform features, bootloader configuration, kernel, device trees, and system setup for embedded Linux development.
Preview NXP i.MX Linux Release Notes LF5.15.71_2.2.2
NXP i.MX Linux Release Notes LF5.15.71_2.2.2 provides comprehensive details on the latest embedded Linux distribution for NXP's i.MX processors. It covers supported features, new additions, known issues, and multimedia specifications for i.MX 6, 7, 8, and 9 series.
Preview FRDM-RW612 Board User Manual
This user manual provides a comprehensive guide to the NXP FRDM-RW612 board, a low-cost design and evaluation board based on the RW612 MCU. It details the board's overview, functional description, power supplies, clocks, interfaces (USB, Ethernet, I2C, SPI), memory, headers, RF front-end, MCU-Link debug probe, and operating conditions. The manual also includes information on supported debug scenarios, MCU-Link host driver installation, firmware updates, and related documentation.
Preview How to Understand and Use TRDC in i.MX Devices
This application note explains how to understand and use the Trusted Resource Domain Controller (TRDC) in NXP's i.MX devices. It covers the TRDC's role in functional safety and security, its components (DAC, MBC, MRC), and how to configure it using registers, software, and tools.
Preview i.MX Linux Reference Manual - NXP Semiconductors
Comprehensive reference manual detailing the i.MX Linux Board Support Package (BSP) for NXP i.MX application processors. Covers system architecture, drivers, connectivity, graphics, audio, security, and more for embedded system development.