FRDM-MCXN236
Overview
FRDM-MCXN236 are compact and scalable development boards for rapid prototyping of MCX N23X MCUs. They offer industry standard headers for easy access to the MCUs I/Os, integrated open-standard serial interfaces, external flash memory and an on-board MCU-Link debugger. MCX N Series are high-performance, low-power microcontrollers with intelligent peripherals and accelerators providing multi-tasking capabilities and performance efficiency.
Hardware
MCX-N236 Arm Cortex-M33 microcontroller running at 150 MHz
1MB dual-bank on chip Flash
352 KB RAM
USB high-speed (Host/Device) with on-chip HS PHY. HS USB Type-C connectors
8x LP Flexcomms each supporting SPI, I2C, UART
8 MB external QSPI flash (Winbond W25Q64JVSSIQ) on LP Flexcomm 6
2x FlexCAN with FD, 2x I3Cs, 2x SAI
On-board MCU-Link debugger with CMSIS-DAP
Arduino Header, FlexIO/LCD Header, SmartDMA/Camera Header, mikroBUS
For more information about the MCX-N236 SoC and FRDM-MCXN236 board, see:
Supported Features
The frdm_mcxn236 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_mcxn236/mcxn236 target
On-target memory for this board target: 192 KiB of RAM, 1 MiB of Flash.
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M33F CPU1 |
|
ADC |
on-chip |
||
Audio |
on-board |
Dialog DA7212 audio codec1 |
|
on-chip |
NXP PDM Microphone Interface (MICFIL)1 |
||
CAN |
on-chip |
||
Clock control |
on-chip |
LPC SYSCON & CLKCTL IP node1 |
|
Clock monitor |
on-chip |
NXP Frequency Measurement (FREQME) module1 |
|
Comparator |
on-chip |
NXP Low Power Comparator (LPCMP)2 |
|
Counter |
on-chip |
||
on-chip |
NXP Multirate Timer1 |
||
on-chip |
|||
on-chip |
NXP LPTMR2 |
||
CRC |
on-chip |
NXP CRC device1 |
|
Cryptographic accelerator |
on-chip |
NXP EdgeLock Secure Subsystem1 |
|
DMA |
on-chip |
NXP SmartDMA controller1 |
|
on-chip |
|||
EDAC |
on-chip |
NXP Error Injection Module1 |
|
on-chip |
NXP Error Reporting Module1 |
||
Flash controller |
on-chip |
NXP MSF1 Flash Memory Module (FMU)1 |
|
GPIO & Headers |
on-chip |
||
on-board |
GPIO pins exposed on Arduino Uno (R3) headers1 |
||
on-board |
GPIO pins exposed on NXP LCD 8080 interface (e.g., used on LCD-PAR-035 panel)1 |
||
on-board |
ArduCam 20-pin header camera connector.1 |
||
Hardware information |
on-chip |
NXP LPC 128-bit Unique identifier1 |
|
I2C |
on-chip |
||
I2S |
on-chip |
NXP mcux SAI-I2S controller2 |
|
I3C |
on-chip |
||
Input |
on-board |
Group of GPIO-bound input keys1 |
|
Interrupt controller |
on-chip |
ARMv8-M NVIC (Nested Vectored Interrupt Controller)1 |
|
LED |
on-board |
Group of GPIO-controlled LEDs1 |
|
Multi-Function Device |
on-chip |
||
MIPI-DBI |
on-chip |
NXP FlexIO LCD controller1 |
|
Miscellaneous |
on-chip |
NXP FlexIO controller1 |
|
MMU / MPU |
on-chip |
ARMv8-M MPU (Memory Protection Unit)1 |
|
MTD |
on-board |
Properties supporting Zephyr spi-nor flash driver (over the Zephyr SPI API) control of serial flash memories using the standard M25P80-based command set1 |
|
on-chip |
Flash node1 |
||
MUX |
on-chip |
NXP INPUTMUX peripheral binding1 |
|
OTP memory |
on-chip |
NXP OTPC eFuse controller1 |
|
Performance state |
on-chip |
NXP MCXN series implementation of custom properties for performance state (pstate)3 |
|
Pin control |
on-chip |
NXP PORT Pin Controller6 |
|
on-chip |
NXP PORT Pin Controller1 |
||
Power management |
on-chip |
NXP System Power Control (SPC)1 |
|
on-chip |
NXP Core Mode Controller (CMC)1 |
||
on-chip |
NXP Smart Power Switch (VBAT)1 |
||
Power domain |
on-chip |
This power domain will Turn On and Off devices when transitioning in and out a specified Power State1 |
|
PWM |
on-chip |
NXP eFLEX PWM module with mcux-pwm submodules2 |
|
on-chip |
|||
Regulator |
on-chip |
NXP VREF SOC peripheral1 |
|
Reset controller |
on-chip |
LPC SYSCON Peripheral reset controller1 |
|
RNG |
on-chip |
NXP EdgeLock Secure Subsystem TRNG1 |
|
RTC |
on-chip |
IRTC1 |
|
Sensors |
on-chip |
NXP LPADC_TEMP40 temperature sensor1 |
|
on-board |
FXLS8974 3-axis accelerometer sensor1 |
||
on-chip |
NXP MCUX QDC2 |
||
Serial controller |
on-chip |
||
SPI |
on-chip |
||
SRAM |
on-chip |
Generic on-chip SRAM1 |
|
Timer |
on-chip |
ARMv8-M System Tick1 |
|
on-chip |
NXP OS Timer on i.MX-RT5xx/6xx1 |
||
USB |
on-chip |
NXP USB High Speed PHY1 |
|
on-chip |
NXP EHCI USB device mode1 |
||
on-chip |
NXP EHCI USB host controller1 |
||
Video |
on-board |
NXP SmartDMA Video Driver1 |
|
Watchdog |
on-chip |
LPC Windowed Watchdog Timer1 |
|
on-chip |
NXP External Watchdog Monitor1 |
||
Wakeup Controller |
on-chip |
NXP Wakeup Unit (WUU) acting as a Wakeup Controller (WUC)1 |
frdm_mcxn236/mcxn236/ns target
On-target memory for this board target: 160 KiB of RAM, 1 MiB of Flash.
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M33F CPU1 |
|
ADC |
on-chip |
||
Audio |
on-board |
Dialog DA7212 audio codec1 |
|
on-chip |
NXP PDM Microphone Interface (MICFIL)1 |
||
CAN |
on-chip |
||
Clock control |
on-chip |
LPC SYSCON & CLKCTL IP node1 |
|
Clock monitor |
on-chip |
NXP Frequency Measurement (FREQME) module1 |
|
Comparator |
on-chip |
NXP Low Power Comparator (LPCMP)2 |
|
Counter |
on-chip |
||
on-chip |
NXP Multirate Timer1 |
||
on-chip |
|||
on-chip |
NXP LPTMR2 |
||
CRC |
on-chip |
NXP CRC device1 |
|
Cryptographic accelerator |
on-chip |
NXP EdgeLock Secure Subsystem1 |
|
DMA |
on-chip |
NXP SmartDMA controller1 |
|
on-chip |
|||
EDAC |
on-chip |
NXP Error Injection Module1 |
|
on-chip |
NXP Error Reporting Module1 |
||
Flash controller |
on-chip |
NXP MSF1 Flash Memory Module (FMU)1 |
|
GPIO & Headers |
on-chip |
||
on-board |
GPIO pins exposed on Arduino Uno (R3) headers1 |
||
on-board |
GPIO pins exposed on NXP LCD 8080 interface (e.g., used on LCD-PAR-035 panel)1 |
||
on-board |
ArduCam 20-pin header camera connector.1 |
||
Hardware information |
on-chip |
NXP LPC 128-bit Unique identifier1 |
|
I2C |
on-chip |
||
I2S |
on-chip |
NXP mcux SAI-I2S controller2 |
|
I3C |
on-chip |
||
Input |
on-board |
Group of GPIO-bound input keys1 |
|
Interrupt controller |
on-chip |
ARMv8-M NVIC (Nested Vectored Interrupt Controller)1 |
|
LED |
on-board |
Group of GPIO-controlled LEDs1 |
|
Multi-Function Device |
on-chip |
||
MIPI-DBI |
on-chip |
NXP FlexIO LCD controller1 |
|
Miscellaneous |
on-chip |
NXP FlexIO controller1 |
|
MMU / MPU |
on-chip |
ARMv8-M MPU (Memory Protection Unit)1 |
|
MTD |
on-board |
Properties supporting Zephyr spi-nor flash driver (over the Zephyr SPI API) control of serial flash memories using the standard M25P80-based command set1 |
|
on-chip |
Flash node1 |
||
MUX |
on-chip |
NXP INPUTMUX peripheral binding1 |
|
OTP memory |
on-chip |
NXP OTPC eFuse controller1 |
|
Performance state |
on-chip |
NXP MCXN series implementation of custom properties for performance state (pstate)3 |
|
Pin control |
on-chip |
NXP PORT Pin Controller6 |
|
on-chip |
NXP PORT Pin Controller1 |
||
Power management |
on-chip |
NXP System Power Control (SPC)1 |
|
on-chip |
NXP Core Mode Controller (CMC)1 |
||
on-chip |
NXP Smart Power Switch (VBAT)1 |
||
Power domain |
on-chip |
This power domain will Turn On and Off devices when transitioning in and out a specified Power State1 |
|
PWM |
on-chip |
NXP eFLEX PWM module with mcux-pwm submodules2 |
|
on-chip |
|||
Regulator |
on-chip |
NXP VREF SOC peripheral1 |
|
Reset controller |
on-chip |
LPC SYSCON Peripheral reset controller1 |
|
RNG |
on-chip |
NXP EdgeLock Secure Subsystem TRNG1 |
|
RTC |
on-chip |
IRTC1 |
|
Sensors |
on-chip |
NXP LPADC_TEMP40 temperature sensor1 |
|
on-board |
FXLS8974 3-axis accelerometer sensor1 |
||
on-chip |
NXP MCUX QDC2 |
||
Serial controller |
on-chip |
||
SPI |
on-chip |
||
SRAM |
on-chip |
Generic on-chip SRAM1 |
|
Timer |
on-chip |
NXP OS Timer on i.MX-RT5xx/6xx1 |
|
on-chip |
ARMv8-M System Tick1 |
||
USB |
on-chip |
NXP USB High Speed PHY1 |
|
on-chip |
NXP EHCI USB device mode1 |
||
on-chip |
NXP EHCI USB host controller1 |
||
Video |
on-board |
NXP SmartDMA Video Driver1 |
|
Watchdog |
on-chip |
LPC Windowed Watchdog Timer1 |
|
on-chip |
NXP External Watchdog Monitor1 |
||
Wakeup Controller |
on-chip |
NXP Wakeup Unit (WUU) acting as a Wakeup Controller (WUC)1 |
Shields for Supported Features
Some features in the table above are tested with Zephyr shields. These shields are tested on this board:
NXP LCD_PAR_S035 TFT LCD Module - supports the Display interface. This board uses the MIPI_DBI interface of the shield, connected to the FlexIO on-chip peripheral.
DVP 20-pin OV7670 Camera Module - supports the SmartDMA video interface.
Connections and IOs
The MCX-N236 SoC has 6 gpio controllers and has pinmux registers which can be used to configure the functionality of a pin.
Name |
Function |
Usage |
|---|---|---|
P0_PIO1_8 |
UART |
UART RX |
P1_PIO1_9 |
UART |
UART TX |
P0_PIO3_20 |
SPI |
QSPI flash SDO (IO0) |
P1_PIO3_21 |
SPI |
QSPI flash SCK |
P2_PIO3_22 |
SPI |
QSPI flash SDI (IO1) |
P3_PIO3_23 |
SPI |
QSPI flash CS |
External Flash
The on-board Winbond W25Q64JVSSIQ (64 Mbit) QSPI flash is connected to LP
Flexcomm 6 and is exposed as a jedec,spi-nor device (node label
w25q64jvssiq) driven by the generic SPI NOR driver in single-bit SPI mode.
The spi_flash sample exercises it:
# From the root of the zephyr repository
west build -b frdm_mcxn236 samples/drivers/spi_flash
west flash
System Clock
The MCX-N236 SoC is configured to use PLL0 running at 150MHz as a source for the system clock.
Serial Port
The FRDM-MCXN236 SoC has 8 FLEXCOMM interfaces for serial communication. Flexcomm 4 is configured as UART for the console.
Power Management
Enable CONFIG_PM to use System Power Management. The SoC PM hooks
implement the following state mapping:
Zephyr state |
NXP power mode |
Availability |
|---|---|---|
|
Sleep |
Available with |
|
Deep Sleep |
Available with |
|
Power Down |
Available with |
|
Deep Power Down |
Disabled by default in the SoC devicetree |
The PM policy chooses among enabled states according to the expected idle duration, latency constraints, and power-state locks. The devicetree residency and exit-latency values are configuration defaults, not measured guarantees for every application.
Wakeup and Timekeeping
When SysTick is the kernel timer, it stops while the core clock is gated.
The board selects LPTMR0 through zephyr,system-timer-companion to keep time
and provide timed wakeups. Keep the companion timer enabled and use a clock
source that operates in the intended power mode. Other kernel timer
configurations must also provide timekeeping and wakeups across that mode.
The wakeup-button alias describes a button’s wakeup-ctrls connection to
the WUU. The alias alone does not arm a wakeup: enable the source through the
WUC API before entering low power. The button and WUU pin are
listed below.
Deep Power Down
Suspend-to-RAM is opt-in. Before enabling the deeppowerdown devicetree node
in an application overlay, place the entire retained working set, including
stacks, kernel objects, and saved CPU context, in RAM that survives this mode
and arm a wakeup source. Enabling the node with CONFIG_PM also enables
CONFIG_PM_S2RAM when supported by the architecture.
The NXP MCX suspend-to-RAM sample provides timer and button wakeup
configurations and board-specific memory layouts.
Deep Power Down resets the CORE domain and its peripheral register blocks.
Applications relying on peripheral recovery must enable
CONFIG_PM_DEVICE and the required power-domain support, and use drivers that restore their hardware after power
loss. System-managed device PM and
runtime device PM are separate mechanisms;
CONFIG_PM alone does not ensure peripheral recovery.
With CONFIG_POWEROFF, system off also enters Deep Power Down,
but wakeup starts through the reset path rather than resuming the suspended
application. See NXP MCX system off.
Debugging and Validation
Use CONFIG_SOC_FAMILY_MCXA_DEBUG_IN_LOW_POWER or
CONFIG_SOC_FAMILY_MCXN_DEBUG_IN_LOW_POWER, as appropriate, to
keep debug logic enabled in modes that retain the CORE domain, at the cost of
higher low-power current. Deep Power Down loses the debug connection regardless
of this option.
The tests/subsys/pm/power_mgmt_soc test covers the targets in its platform allow list. Its default configuration does not enable Deep Power Down. Validate the optional state with the S2RAM sample, then verify wakeup and peripheral operation with the application’s own configuration. A sample or test target listing is not evidence of measured power consumption.
Board-specific Requirements
The wakeup-button alias selects SW2 on P0_20, routed to WUU external pin 4
with a falling-edge interrupt.
Only SRAMA, the first 32 KB at 0x20000000, survives Deep Power Down through
the VBAT RAM LDO. The samples/boards/nxp/mcxn_a/s2ram/mcxn.overlay
limits zephyr,sram to the 24 KB at 0x20002000 to avoid the boot ROM’s
scratch area. The default board RAM allocation is not a suspend-to-RAM layout;
check that the entire retained working set fits before enabling this state.
Programming and Debugging
The frdm_mcxn236 board supports the runners and associated west commands listed below.
| flash | debug | reset | attach | rtt | debugserver | |
|---|---|---|---|---|---|---|
| jlink | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| linkserver | ✅ (default) | ✅ (default) | ✅ | ✅ | ||
| pyocd | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Build and flash applications as usual (see Building an Application and Run an Application for more details).
Configuring a Debug Probe
A debug probe is used for both flashing and debugging the board. This board is configured by default to use the MCU-Link CMSIS-DAP Onboard Debug Probe.
Using LinkServer
Linkserver is the default runner for this board, and supports the factory
default MCU-Link firmware. Follow the instructions in
MCU-Link CMSIS-DAP Onboard Debug Probe to reprogram the default MCU-Link
firmware. This only needs to be done if the default onboard debug circuit
firmware was changed. To put the board in DFU mode to program the firmware,
short jumper JP5.
Using J-Link
There are two options. The onboard debug circuit can be updated with Segger
J-Link firmware by following the instructions in
MCU-Link JLink Onboard Debug Probe.
To be able to program the firmware, you need to put the board in DFU mode
by shortening the jumper JP5.
The second option is to attach a J-Link External Debug Probe to the
10-pin SWD connector (J12) of the board. Additionally, the jumper JP7 must
be shortened.
For both options use the -r jlink option with west to use the jlink runner.
west flash -r jlink
Configuring a Console
Connect a USB cable from your PC to J10, and use the serial terminal of your choice (minicom, putty, etc.) with the following settings:
Speed: 115200
Data: 8 bits
Parity: None
Stop bits: 1
Flashing
Here is an example for the Hello World application.
# From the root of the zephyr repository
west build -b frdm_mcxn236 samples/hello_world
west flash
Open a serial terminal, reset the board (press the RESET button), and you should see the following message in the terminal:
*** Booting Zephyr OS build v3.6.0-4478-ge6c3a42f5f52 ***
Hello World! frdm_mcxn236/mcxn236
Debugging
Here is an example for the Hello World application.
# From the root of the zephyr repository
west build -b frdm_mcxn236/mcxn236 samples/hello_world
west debug
Open a serial terminal, step through the application in your debugger, and you should see the following message in the terminal:
*** Booting Zephyr OS build v3.6.0-4478-ge6c3a42f5f52 ***
Hello World! frdm_mcxn236/mcxn236
Troubleshooting
Using Segger SystemView and RTT
Note that when using SEGGER SystemView or RTT with this SOC, the RTT control
block address must be set manually within SystemView or the RTT Viewer. The
address provided to the tool should be the location of the _SEGGER_RTT
symbol, which can be found using a debugger or by examining the zephyr.map
file output by the linker.
The RTT control block address must be provided manually because this SOC supports ECC RAM. If the SEGGER tooling searches the ECC RAM space for the control block a fault will occur, provided that ECC is enabled and the RAM segment being searched has not been initialized to a known value.