FRDM-MCXE247
Overview
FRDM-MCXE247 is compact and scalable development board for rapid prototyping of MCX E245/246/247 MCUs. It offers industry standard headers for easy access to the MCU’s I/Os, integrated open-standard serial interfaces, external flash memory and an on-board MCU-Link debugger.
Hardware
MCXE247VLQ Arm Cortex-M4F 32-bit CPU
Supports up to 112 MHz frequency (HSRUN mode)
LQFP144 package
2 MB on chip flash memory
64 kB FlexNVM for data flash memory and EEPROM emulation
256 kB SRAM
4 kB of FlexRAM for use as SRAM or EEPROM emulation
2x ADC, 1x CMP, TRGMUX
2x LPI2C, 3xLPSPI, 1x FlexIO, 3x LPUART, 2x SAI, QSPI, 3xFlexCAN, IEEE1588 100 Mbps ETH MAC
8x FlexTimer, Internal and external WDOG, 1x LPIT, 1x LPTMR, 2x PDB, RTC
NMH1000 magnetic switch
FXLS8974CF accelerometer
RGB user LED
On-board MCU-Link debugger with CMSIS-DAP
Arduino Header, mikroBUS, Pmod
For more information about the MCXE247 SoC and FRDM-MCXE247 board, see these references:
Supported Features
The frdm_mcxe247 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_mcxe247/mcxe247 target
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M4F CPU1 |
|
ADC |
on-chip |
NXP ADC122 |
|
CAN |
on-chip |
NXP FlexCAN CANFD controller3 |
|
Clock control |
on-chip |
NXP Kinetis SCG (System Clock Generator) IP node1 |
|
on-chip |
Generic fixed-rate clock provider4 |
||
on-chip |
Generic fixed factor clock provider13 |
||
on-chip |
NXP Kinetis PCC (Peripheral Clock Controller) IP node1 |
||
Comparator |
on-chip |
NXP Kinetis ACMP (Analog CoMParator)1 |
|
Counter |
on-chip |
NXP LPTMR1 |
|
DMA |
on-chip |
NXP MCUX EDMA controller1 |
|
Ethernet |
on-chip |
NXP ENET IP Module1 |
|
on-chip |
NXP ENET MAC/L2 Device1 |
||
on-chip |
NXP ENET PTP (Precision Time Protocol) Clock1 |
||
Flash controller |
on-chip |
NXP Kinetis Flash Memory Module C (FTFC)1 |
|
GPIO & Headers |
on-chip |
Kinetis GPIO5 |
|
on-board |
GPIO pins exposed on Arduino Uno (R3) headers1 |
||
I2C |
on-chip |
NXP LPI2C controller2 |
|
I2S |
on-chip |
NXP mcux SAI-I2S controller2 |
|
Input |
on-board |
Group of GPIO-bound input keys1 |
|
Interrupt controller |
on-chip |
ARMv7-M NVIC (Nested Vectored Interrupt Controller)1 |
|
LED |
on-board |
Group of GPIO-controlled LEDs1 |
|
MDIO |
on-chip |
NXP ENET MDIO Features1 |
|
Miscellaneous |
on-chip |
NXP FlexIO controller1 |
|
MMU / MPU |
on-chip |
NXP System Memory Protection Unit (SYSMPU)1 |
|
MTD |
on-chip |
Flash node1 |
|
Pin control |
on-chip |
NXP PORT Pin Controller5 |
|
on-chip |
NXP PORT Pin Controller1 |
||
RTC |
on-chip |
NXP Real Time Clock (RTC)1 |
|
Serial controller |
on-chip |
||
SPI |
on-chip |
NXP LPSPI controller3 |
|
SRAM |
on-chip |
Generic on-chip SRAM1 |
|
Timer |
on-chip |
ARMv7-M System Tick1 |
|
on-chip |
NXP FlexTimer Module (FTM)8 |
||
Watchdog |
on-chip |
NXP External Watchdog Monitor1 |
|
on-chip |
NXP watchdog (WDOG32)1 |
Connections and IOs
The MCX E247 SoC has five pairs of pinmux/gpio controllers (PORTA/GPIOA, PORTB/GPIOB, PORTC/GPIOC, PORTD/GPIOD, and PORTE/GPIOE).
Name |
Function |
Usage |
|---|---|---|
PTC13 |
GPIO |
Red LED |
PTB11 |
GPIO |
Green LED |
PTC12 |
GPIO |
Blue LED |
PTD17 |
LPUART2_RX |
UART Console |
PTE12 |
LPUART2_TX |
UART Console |
PTA5 |
RESET |
RESET Button SW1 |
PTA9 |
GPIO |
User button SW2 |
PTC10 |
GPIO |
User button SW3 |
PTA2 |
I2C0_SDA |
I2C sensor |
PTA3 |
I2C0_SCL |
I2C sensor |
System Clock
The MCXE247 SoC is configured to use SPLL running at 80 MHz (RUN mode) as a system clock source.
Serial Port
The MCX E247 LPUART2 is used for the console.
Programming and Debugging
The frdm_mcxe247 board supports the runners and associated west commands listed below.
| flash | debug | attach | debugserver | rtt | |
|---|---|---|---|---|---|
| jlink | ✅ | ✅ | ✅ | ✅ | ✅ |
| linkserver | ✅ (default) | ✅ (default) | ✅ | ✅ |
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 JP2.
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 JP2.
The second option is to attach a J-Link External Debug Probe to the
10-pin SWD connector (J10) of the board.
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 J13, 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_mcxe247 samples/hello_world
west flash
Open a serial terminal, reset the board (press the SW1 button), and you should see the following message in the terminal:
*** Booting Zephyr OS build v4.1.0-5194-ge7d44ce91cb3 ***
Hello World! frdm_mcxe247/mcxe247
Debugging
Here is an example for the Hello World application.
# From the root of the zephyr repository
west build -b frdm_mcxe247 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 v4.1.0-5194-ge7d44ce91cb3 ***
Hello World! frdm_mcxe247/mcxe247
Support Resources for Zephyr
MCUXpresso for VS Code, wiki documentation and Zephyr lab guides
NXP’s Zephyr landing page (including training resources)