Hello NXP Team,
I use eval board ls1043 ardb CPU with LAN8814 chip.
Linux rbozic_03 6.6.36-rbozic-gd23d64eea511-dirty #1 SMP Fri Sep 27 13:02:05 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux
0000:00:00.0 PCI bridge: Freescale Semiconductor Inc Device 8080 (rev 11)
PHY is -> Microsemi GE VSC8514 SyncE
Driver in kernel is disabled:
root@eval6:~# zcat /proc/config.gz | grep MICROSE
# CONFIG_NET_VENDOR_MICROSEMI is not set
# CONFIG_MICROSEMI_PHY is not set
Add sdk_dpaa:
root@eval6:~# zcat /proc/config.gz | grep SDK
CONFIG_FSL_SDK_FMAN=y
# CONFIG_FSL_SDK_FMAN_TEST is not set
CONFIG_FSL_SDK_FMAN_RTC_API=y
CONFIG_FSL_SDK_DPAA_ETH=y
CONFIG_FSL_SDK_DPA=y
CONFIG_FSL_SDK_BMAN=y
CONFIG_FSL_SDK_QMAN=y
root@eval6:~# zcat /proc/config.gz | grep DPAA
CONFIG_FSL_SDK_DPAA_ETH=y
# CONFIG_FSL_DPAA_HOOKS is not set
# CONFIG_FSL_DPAA_CEETM is not set
CONFIG_FSL_DPAA_OFFLINE_PORTS=y
CONFIG_FSL_DPAA_ADVANCED_DRIVERS=y
# CONFIG_FSL_DPAA_ETH_JUMBO_FRAME is not set
# CONFIG_FSL_DPAA_TS is not set
# CONFIG_FSL_DPAA_1588 is not set
CONFIG_FSL_DPAA_ETH_MAX_BUF_COUNT=128
CONFIG_FSL_DPAA_ETH_REFILL_THRESHOLD=80
CONFIG_FSL_DPAA_CS_THRESHOLD_1G=0x06000000
CONFIG_FSL_DPAA_CS_THRESHOLD_10G=0x10000000
CONFIG_FSL_DPAA_INGRESS_CS_THRESHOLD=0x10000000
CONFIG_FSL_DPAA_ETH_DEBUGFS=y
# CONFIG_FSL_DPAA_ETH_DEBUG is not set
# CONFIG_FSL_DPAA_DBG_LOOP is not set
# CONFIG_FSL_DPAA2_MAC is not set
# CONFIG_FSL_DPAA2_SWITCH is not set
CONFIG_FSL_USDPAA=y
# CONFIG_FSL_DPAA2 is not set
# CONFIG_FSL_DPAA is not set
CONFIG_DPAA2_CONSOLE=y
Driver in kernel is disabled:
root@eval6:~# zcat /proc/config.gz | grep MICROSE
# CONFIG_NET_VENDOR_MICROSEMI is not set
# CONFIG_MICROSEMI_PHY is not set
but qsgmii netwok Interfaces still working.
I use also other board with ls1043 CPU but with LAN8814 Chip.
Its possible also to use LAN8814 inside SDK_DPAA?
For debugging you can use CodeWarrior, on the other hand if you want to check the sent/received frames you can use the WireShark app.
the first thing is to have the driver added as a module in the Kernel, then you need to select it by make menuconfig
FYI, the LS1043ARDB use the F104S8A PHY for the QSGMII.
ls1043ardb board use VSC8514 QPHY with DPAA Ethernet:
Using SERDES1 Protocol: 5205 (0x1455)
My board use LAN8814 QPHY:
Using SERDES1 Protocol: 13397 (0x3455)
linux driver micrel.c -Phy Address 4 - 7 is added in device tree
I use this Linux https://github.com/nxp-qoriq/linux.git with branch lf-6.6.y and commit id is
d23d64eea5111e1607efcce1d601834fceec92cb.
I think this is the newest NXP Linux kernel and the micrel.c driver is also new.
Why you think is not possible to use ls1043 with LAN8814 QPHY?
You mean hardware combination ls1043 and LAN8814?
or
You mean software also u-boot, rcw, linux etc.?
or
you team don't have time to check this?
BR
Rade
Many thanks Luis Fernando and I understood your description. Of course I have to adapt the linux (device tree and the driver) to my hardware design and hardware settings.
Nevertheless, I would like to know how do I have to adapt/config the latest kernel (https://github.com/nxp-qoriq) to use the hardware LAN8814. We have 2 dpaa drivers, one with Bman and Fman (sdk_dpaa) in staging (drivers/staging) mode and other one fman driver in driver/net/ethernet/freescale without staging.
Maybe you can give me i hint how i can check and debug the dpaa?
Or, what exactly do I have to pay attention to when sending and receiving via DPAA?
FYI: I really expected it to work with the latest Linux kernel without staging driver.
BR
Rade Bozic