FRDM-MCXA577
Overview
FRDM-MCXA577 is a compact and scalable development board for rapid prototyping of MCX A577 MCUs. They offer industry standard headers for easy access to the MCUs input/output (I/O), integrated open-standard serial interfaces, external flash memory and an onboard MCU-Link debugger.
Hardware
MCX-A577 Arm Cortex-M33 microcontroller running at 12MHz
2048KB dual-bank on chip Flash
640 KB RAM
2x FlexCAN with FD, 1x RGB LED, 3x SW buttons
Ethernet: on-SoC 10BASE-T1S PHY, or 10/100 Mbit external PHY over MII
On-board MCU-Link debugger with CMSIS-DAP
Arduino Header, SmartDMA/Camera Header, mikroBUS
For more information about the MCX-A577 SoC and FRDM-MCXA577 board, see:
Supported Features
The frdm_mcxa577 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_mcxa577/mcxa577 target
On-target memory for this board target: 512 KiB of RAM, 2 MiB of Flash.
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M33F CPU1 |
|
ADC |
on-chip |
||
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)1 |
|
Counter |
on-chip |
||
on-chip |
NXP LPTMR1 |
||
on-chip |
NXP Wake Timer1 |
||
CRC |
on-chip |
NXP CRC device1 |
|
DAC |
on-chip |
||
DMA |
on-chip |
NXP SmartDMA controller1 |
|
on-chip |
|||
EDAC |
on-chip |
NXP Error Injection Module1 |
|
on-chip |
NXP Error Reporting Module1 |
||
ESPI |
on-chip |
NXP MCX A series eSPI target controller1 |
|
on-chip |
NXP MCX A series eSPI Target Attached Flash (TAF) controller1 |
||
Ethernet |
on-chip |
NXP ENET QOS Ethernet Controller1 |
|
on-chip |
Synopsys DesignWare MAC MDIO controller1 |
||
on-board |
Generic MII PHY1 |
||
on-chip |
Synopsys DesignWare MAC PTP (Precision Time Protocol) Clock1 |
||
on-chip |
NXP 10BASE-T1S PHY support1 |
||
Flash controller |
on-chip |
NXP MSF1 Flash Memory Module (FMU)1 |
|
GPIO & Headers |
on-chip |
Kinetis GPIO6 |
|
on-board |
GPIO pins exposed on NXP LCD 8080 interface (e.g., used on LCD-PAR-035 panel)1 |
||
on-board |
GPIO pins exposed on Arduino Uno (R3) headers1 |
||
Hardware information |
on-chip |
NXP LPC 128-bit Unique identifier1 |
|
I2C |
on-chip |
||
I3C |
on-chip |
||
Input |
on-chip |
NXP TSI V6 Touch Sensing Input Device1 |
|
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 |
|
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 |
NXP FlexSPI NOR1 |
|
on-board |
Flash node2 |
||
on-board |
Fixed partitions of a flash (or other non-volatile storage) memory1 |
||
MUX |
on-chip |
NXP INPUTMUX peripheral binding1 |
|
Pin control |
on-chip |
NXP PORT Pin Controller6 |
|
on-chip |
NXP PORT Pin Controller1 |
||
Power management |
on-chip |
NXP Smart Power Switch (VBAT)1 |
|
on-chip |
NXP Core Mode Controller (CMC)1 |
||
on-chip |
NXP System Power Control (SPC)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 Flexio PWM controller1 |
|
Regulator |
on-chip |
NXP SPC buffered bandgap output1 |
|
Reset controller |
on-chip |
NXP MRCC Peripheral reset controller1 |
|
RNG |
on-chip |
Kinetis TRNG (True Random Number Generator)1 |
|
RTC |
on-chip |
IRTC1 |
|
Sensors |
on-chip |
NXP LPADC_TEMP40 temperature sensor1 |
|
on-board |
NXP P3T1755 digital temperature sensor connected to I3C bus1 |
||
Serial controller |
on-chip |
||
SPI |
on-chip |
||
on-chip |
NXP FlexSPI controller1 |
||
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 EHCI USB device mode1 |
|
on-chip |
NXP EHCI USB host controller1 |
||
on-chip |
NXP USB High Speed PHY1 |
||
Watchdog |
on-chip |
||
on-chip |
NXP External Watchdog Monitor1 |
||
Wakeup Controller |
on-chip |
NXP Wakeup Unit (WUU) acting as a Wakeup Controller (WUC)1 |
frdm_mcxa577/mcxa577/mii target
On-target memory for this board target: 512 KiB of RAM, 2 MiB of Flash.
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M33F CPU1 |
|
ADC |
on-chip |
||
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)1 |
|
Counter |
on-chip |
||
on-chip |
NXP LPTMR1 |
||
on-chip |
NXP Wake Timer1 |
||
CRC |
on-chip |
NXP CRC device1 |
|
DAC |
on-chip |
NXP MCUX LPDAC2 |
|
DMA |
on-chip |
NXP SmartDMA controller1 |
|
on-chip |
|||
EDAC |
on-chip |
NXP Error Injection Module1 |
|
on-chip |
NXP Error Reporting Module1 |
||
ESPI |
on-chip |
NXP MCX A series eSPI target controller1 |
|
on-chip |
NXP MCX A series eSPI Target Attached Flash (TAF) controller1 |
||
Ethernet |
on-chip |
NXP ENET QOS Ethernet Controller1 |
|
on-chip |
Synopsys DesignWare MAC MDIO controller1 |
||
on-board |
Generic MII PHY1 |
||
on-chip |
Synopsys DesignWare MAC PTP (Precision Time Protocol) Clock1 |
||
on-chip |
NXP 10BASE-T1S PHY support1 |
||
Flash controller |
on-chip |
NXP MSF1 Flash Memory Module (FMU)1 |
|
GPIO & Headers |
on-chip |
Kinetis GPIO6 |
|
on-board |
GPIO pins exposed on NXP LCD 8080 interface (e.g., used on LCD-PAR-035 panel)1 |
||
on-board |
GPIO pins exposed on Arduino Uno (R3) headers1 |
||
Hardware information |
on-chip |
NXP LPC 128-bit Unique identifier1 |
|
I2C |
on-chip |
||
I3C |
on-chip |
||
Input |
on-chip |
NXP TSI V6 Touch Sensing Input Device1 |
|
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 |
|
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 |
NXP FlexSPI NOR1 |
|
on-board |
Flash node2 |
||
on-board |
Fixed partitions of a flash (or other non-volatile storage) memory1 |
||
MUX |
on-chip |
NXP INPUTMUX peripheral binding1 |
|
Pin control |
on-chip |
NXP PORT Pin Controller6 |
|
on-chip |
NXP PORT Pin Controller1 |
||
Power management |
on-chip |
NXP Smart Power Switch (VBAT)1 |
|
on-chip |
NXP Core Mode Controller (CMC)1 |
||
on-chip |
NXP System Power Control (SPC)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 Flexio PWM controller1 |
|
Regulator |
on-chip |
NXP SPC buffered bandgap output1 |
|
Reset controller |
on-chip |
NXP MRCC Peripheral reset controller1 |
|
RNG |
on-chip |
Kinetis TRNG (True Random Number Generator)1 |
|
RTC |
on-chip |
IRTC1 |
|
Sensors |
on-chip |
NXP LPADC_TEMP40 temperature sensor1 |
|
on-board |
NXP P3T1755 digital temperature sensor connected to I3C bus1 |
||
Serial controller |
on-chip |
||
SPI |
on-chip |
||
on-chip |
NXP FlexSPI controller1 |
||
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 EHCI USB device mode1 |
|
on-chip |
NXP EHCI USB host controller1 |
||
on-chip |
NXP USB High Speed PHY1 |
||
Watchdog |
on-chip |
||
on-chip |
NXP External Watchdog Monitor1 |
||
Wakeup Controller |
on-chip |
NXP Wakeup Unit (WUU) acting as a Wakeup Controller (WUC)1 |
frdm_mcxa577/mcxa577/ns target
On-target memory for this board target: 128 KiB of RAM, 2 MiB of Flash.
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M33F CPU1 |
|
ADC |
on-chip |
||
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)1 |
|
Counter |
on-chip |
||
on-chip |
NXP LPTMR1 |
||
on-chip |
NXP Wake Timer1 |
||
CRC |
on-chip |
NXP CRC device1 |
|
DAC |
on-chip |
NXP MCUX LPDAC2 |
|
DMA |
on-chip |
NXP SmartDMA controller1 |
|
on-chip |
|||
EDAC |
on-chip |
NXP Error Injection Module1 |
|
on-chip |
NXP Error Reporting Module1 |
||
ESPI |
on-chip |
NXP MCX A series eSPI target controller1 |
|
on-chip |
NXP MCX A series eSPI Target Attached Flash (TAF) controller1 |
||
Ethernet |
on-chip |
NXP ENET QOS Ethernet Controller1 |
|
on-chip |
Synopsys DesignWare MAC MDIO controller1 |
||
on-board |
Generic MII PHY1 |
||
on-chip |
Synopsys DesignWare MAC PTP (Precision Time Protocol) Clock1 |
||
on-chip |
NXP 10BASE-T1S PHY support1 |
||
Flash controller |
on-chip |
NXP MSF1 Flash Memory Module (FMU)1 |
|
GPIO & Headers |
on-chip |
Kinetis GPIO6 |
|
on-board |
GPIO pins exposed on NXP LCD 8080 interface (e.g., used on LCD-PAR-035 panel)1 |
||
on-board |
GPIO pins exposed on Arduino Uno (R3) headers1 |
||
Hardware information |
on-chip |
NXP LPC 128-bit Unique identifier1 |
|
I2C |
on-chip |
||
I3C |
on-chip |
||
Input |
on-chip |
NXP TSI V6 Touch Sensing Input Device1 |
|
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 |
|
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 |
NXP FlexSPI NOR1 |
|
on-board |
Flash node2 |
||
MUX |
on-chip |
NXP INPUTMUX peripheral binding1 |
|
Pin control |
on-chip |
NXP PORT Pin Controller6 |
|
on-chip |
NXP PORT Pin Controller1 |
||
Power management |
on-chip |
NXP Smart Power Switch (VBAT)1 |
|
on-chip |
NXP Core Mode Controller (CMC)1 |
||
on-chip |
NXP System Power Control (SPC)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 Flexio PWM controller1 |
|
Regulator |
on-chip |
NXP SPC buffered bandgap output1 |
|
Reset controller |
on-chip |
NXP MRCC Peripheral reset controller1 |
|
RNG |
on-chip |
Kinetis TRNG (True Random Number Generator)1 |
|
RTC |
on-chip |
IRTC1 |
|
Sensors |
on-chip |
NXP LPADC_TEMP40 temperature sensor1 |
|
on-board |
NXP P3T1755 digital temperature sensor connected to I3C bus1 |
||
Serial controller |
on-chip |
||
SPI |
on-chip |
||
on-chip |
NXP FlexSPI controller1 |
||
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 EHCI USB device mode1 |
|
on-chip |
NXP EHCI USB host controller1 |
||
on-chip |
NXP USB High Speed PHY1 |
||
Watchdog |
on-chip |
||
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.
Display Support
The frdm_mcxa577 board supports the following in-tree display module(s).
NXP LCD_PAR_S035
The NXP LCD_PAR_S035 TFT LCD Module connects to the board’s LCD socket, and is driven over the MIPI_DBI 8080 parallel interface using the FlexIO on-chip peripheral. The display sample can be built for this module like so:
west build -b frdm_mcxa577 --shield lcd_par_s035_8080 samples/drivers/display
Connections and IOs
The MCX-A577 SoC has 5 gpio controllers and has pinmux registers which can be used to configure the functionality of a pin.
Name |
Function |
Usage |
|---|---|---|
PIO1_8 |
UART |
UART RX |
PIO1_9 |
UART |
UART TX |
System Clock
The MCX-A577 SoC is configured to use FRO LF running at 12MHz as a source for the system clock.
Serial Port
The FRDM-MCXA577 SoC has 6 LPUART interfaces for serial communication. LPUART1 is configured as UART for the console.
Ethernet
Support for two Ethernet options: the on-SoC 10BASE-T1S PHY with its on-board PMD transceiver, and a 10/100 Mbit external PHY over MII.
10BASE-T1S (default)
The default target frdm_mcxa577/mcxa577 uses the on-SoC 10BASE-T1S PHY:
# From the root of the zephyr repository
west build -b frdm_mcxa577 samples/net/zperf
10BASE-T1S Board-to-Board Setup
Two boards can be connected directly with a twisted pair between their 10BASE-T1S connectors.
Exactly one node on the segment must be the PLCA coordinator (node ID 0), and the boards need
different MAC addresses. The board devicetree uses PLCA node ID 1 and a random MAC address,
which is identical on every board when CONFIG_TEST_RANDOM_GENERATOR is enabled, as in
zperf: Network Traffic Generator.
Build the first board with the default configuration (192.0.2.1). For the second board,
save the following overlay as samples/net/zperf/t1s_node0.overlay:
&enet {
/delete-property/ zephyr,random-mac-address;
local-mac-address = [00 04 9f 00 00 01];
};
&t1s {
plca-enable;
plca-node-id = <0>;
plca-node-count = <2>;
plca-burst-count = <0>;
plca-burst-timer = <0x80>;
plca-to-timer = <0x20>;
status = "okay";
};
and the following as samples/net/zperf/t1s_node0.conf to swap the IP addresses:
CONFIG_NET_CONFIG_MY_IPV6_ADDR="2001:db8::2"
CONFIG_NET_CONFIG_PEER_IPV6_ADDR="2001:db8::1"
CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.2"
CONFIG_NET_CONFIG_PEER_IPV4_ADDR="192.0.2.1"
Then build the second board with both files:
# From the root of the zephyr repository
west build -b frdm_mcxa577 samples/net/zperf -- -DEXTRA_DTC_OVERLAY_FILE=t1s_node0.overlay -DEXTRA_CONF_FILE=t1s_node0.conf
After flashing, net iface must show a different Link addr on each board, and
net ping 192.0.2.2 from the first board must succeed.
External PHY over MII
The frdm_mcxa577/mcxa577/mii variant uses the external 10/100 Mbit PHY:
# From the root of the zephyr repository
west build -b frdm_mcxa577/mcxa577/mii samples/net/zperf
MII needs P1_8/P1_9 for ENET0_TXD2/TXD3, which are also the LPUART1 MCU-Link VCOM pins. The variant therefore disables LPUART1 and moves the console/shell to LPUART2 (Arduino D0/D1 header, P2_11/P2_10); connect a USB-to-serial adapter there to get console output.
The MII signals reach the external PHY only after the following solder-jumper rework (this rework is not applicable to 10BASE-T1S mode):
Short 2-3 (and disconnect 1-2) of SJ13 (TXD2), SJ14 (TXD3), SJ16 (RXD2), SJ17 (RXD3), SJ18 (COL), SJ19 (CRS).
Disconnect 1-2 and 2-3 of SJ15 (RX_CLK) and SJ44 (RXER).
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 P3_17, routed to WUU external pin 26
with a falling-edge interrupt.
Deep Power Down can retain SRAM arrays A0 and A3 through the VBAT backup SRAM
regulator, not the board’s full RAM allocation. The
samples/boards/nxp/mcxn_a/s2ram/boards/frdm_mcxa577.overlay
limits zephyr,sram to A3, 16 KB at 0x20004000, so the entire retained
working set fits in a retainable array. Use this layout as a starting point
and check the application’s RAM usage before enabling suspend-to-RAM.
Programming and Debugging
The frdm_mcxa577 board supports the runners and associated west commands listed below.
| flash | debug | rtt | reset | attach | 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 ISP mode to program the firmware,
short jumper JP4.
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 ISP mode
by shortening the jumper JP4.
The second option is to attach a J-Link External Debug Probe to the
10-pin SWD connector (J11) of the board. Additionally, the jumper JP6 must
be shorted.
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_mcxa577 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_mcxa577/mcxa577
Debugging
Here is an example for the Hello World application.
# From the root of the zephyr repository
west build -b frdm_mcxa577/mcxa577 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_mcxa577/mcxa577
10BASE-T1S Throughput Tuning
10BASE-T1S is a shared bus arbitrated by PLCA, so the usable UDP throughput on
the default frdm_mcxa577/mcxa577 target is lower than the 10 Mbps line rate.
Near that limit the default network buffer sizing can be exhausted faster than
the driver drains it, and packets are dropped with -EBUSY.
Increasing the net_buf fragment size, the packet and buffer pools, and the network TX/RX thread stacks avoids the drops:
CONFIG_NET_BUF_DATA_SIZE=512
CONFIG_NET_PKT_RX_COUNT=48
CONFIG_NET_PKT_TX_COUNT=48
CONFIG_NET_BUF_RX_COUNT=96
CONFIG_NET_BUF_TX_COUNT=96
CONFIG_NET_TX_STACK_SIZE=2048
CONFIG_NET_RX_STACK_SIZE=2048
These raise RAM usage, so they are applied per application rather than enabled by default. For zperf: Network Traffic Generator they are set in samples/net/zperf/boards/frdm_mcxa577_mcxa577.conf.
If more headroom is needed, the ENET QoS driver’s descriptor rings and RX thread can be enlarged as well:
CONFIG_ETH_NXP_ENET_QOS_TX_BUFFER_DESCRIPTORS=32
CONFIG_ETH_NXP_ENET_QOS_RX_BUFFER_DESCRIPTORS=32
CONFIG_ETH_NXP_ENET_QOS_RX_THREAD_STACK_SIZE=2048
CONFIG_ETH_NXP_ENET_QOS_RX_THREAD_PRIORITY=2
Raising the priority of the application thread generating the traffic reduces inter-packet jitter. For zperf: Network Traffic Generator:
CONFIG_ZPERF_WORK_Q_THREAD_PRIORITY=7
CONFIG_ZPERF_WORK_Q_STACK_SIZE=4096
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.