This is the documentation for the latest (master) development branch of Zephyr. If you are looking for the documentation of previous releases, use the drop-down menu on the left and select the desired version.
CONFIG_ETH_MCUX

MCUX Ethernet driver

Type: bool

Help

Enable MCUX Ethernet driver. Note, this driver performs one shot PHY setup. There is no support for PHY disconnect, reconnect or configuration change.

Direct dependencies

(NETWORKING && BOARD_IP_K66F) || (NET_L2_ETHERNET && SOC_SERIES_IMX_RT) || (NET_L2_ETHERNET && SOC_MK64F12 && SOC_SERIES_KINETIS_K6X) || (HAS_MCUX_ENET && NET_L2_ETHERNET)

(Includes any dependencies from ifs and menus.)

Defaults

Kconfig definitions

At boards/arm/ip_k66f/Kconfig.defconfig:28

Included via Kconfig:8Kconfig.zephyr:24

Menu path: (Top)

config ETH_MCUX
    bool
    default y if NET_L2_ETHERNET
    depends on NETWORKING && BOARD_IP_K66F

At soc/arm/nxp_imx/rt/Kconfig.defconfig.series:42

Included via Kconfig:8Kconfig.zephyr:25doc/_build/Kconfig/Kconfig.soc.defconfig:1soc/arm/nxp_imx/Kconfig.defconfig:4

Menu path: (Top)

config ETH_MCUX
    bool
    default y if HAS_MCUX_ENET
    depends on NET_L2_ETHERNET && SOC_SERIES_IMX_RT

At soc/arm/nxp_kinetis/k6x/Kconfig.defconfig.mk64f12:59

Included via Kconfig:8Kconfig.zephyr:25doc/_build/Kconfig/Kconfig.soc.defconfig:1soc/arm/nxp_kinetis/Kconfig.defconfig:3soc/arm/nxp_kinetis/k6x/Kconfig.defconfig.series:22

Menu path: (Top)

config ETH_MCUX
    bool
    default y
    depends on NET_L2_ETHERNET && SOC_MK64F12 && SOC_SERIES_KINETIS_K6X

At drivers/ethernet/Kconfig.mcux:6

Included via Kconfig:8Kconfig.zephyr:32drivers/Kconfig:18drivers/ethernet/Kconfig:49

Menu path: (Top) → Device Drivers → Ethernet Drivers

menuconfig ETH_MCUX
    bool "MCUX Ethernet driver"
    select NOCACHE_MEMORY if HAS_MCUX_CACHE
    select ARM_MPU if CPU_CORTEX_M7
    select NET_POWER_MANAGEMENT if DEVICE_POWER_MANAGEMENT
    depends on HAS_MCUX_ENET && NET_L2_ETHERNET
    help
      Enable MCUX Ethernet driver.  Note, this driver performs one shot PHY
      setup.  There is no support for PHY disconnect, reconnect or
      configuration change.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)