LX2160 : LSdk 21.08 : MC 10.32 : Restool 2.4 : dpmac.4/dpmac.3 not detecting

[Chidananda22]

Model: NXP Layerscape LX2160ARDB Board
Board: LX2160ACE Rev2.0-RDB, Board version: C, boot from FlexSPI DEV#0

fsl-mc: Booting Management Complex ... SUCCESS
fsl-mc: Management Complex booted (version: 10.32.0, boot status: 0x1)

[ 4.432377] fsl_dpaa2_mac dpmac.4: Adding to iommu group 10
[ 4.444118] fsl_dpaa2_mac dpmac.4 (unnamed net_device) (uninitialized): phylink_fwnode_phy_connect() = -19
[ 4.453773] fsl_dpaa2_mac dpmac.4: Error connecting to the MAC endpoint
[ 4.460893] fsl_dpaa2_mac dpmac.4: fsl_mc_driver_probe failed: -19
[ 4.467197] fsl_dpaa2_mac dpmac.3: Adding to iommu group 10
[ 4.478894] fsl_dpaa2_mac dpmac.3 (unnamed net_device) (uninitialized): phylink_fwnode_phy_connect() = -19
[ 4.488560] fsl_dpaa2_mac dpmac.3: Error connecting to the MAC endpoint
[ 4.495692] fsl_dpaa2_mac dpmac.3: fsl_mc_driver_probe failed: -19

[vilas_shetty]

Hello,
We are facing a similar issue but we are able to detect dpmac3 and dpmac4 but when we try to test the link the link shows down. We are not able to bring 10G link up. 

[Chidananda22]

Thanks I will change and update.

[Chidananda22]

thanks for Quick Reply and help .

After installing the dtb file getting the same error, Attached boot logs.

As per LSDK guide I will use the below command and try to load dpl file.

dtc -I dts -O dtb dpl-eth.19.dts -o dpl-eth.19.dtb

followed the below steps .

https://community.nxp.com/t5/Layerscape-Knowledge-Base/LX2160ARDB-How-to-update-MC-firmware-DPC-and-...

[Chidananda22]

fsl-mc: Deploying data path layout ... WARNING: Firmware returned an error (GSR: 0x3f)

Can you please suggest how to solve.

[yipingwang · Accepted solution]

It seems that there is problem with your dpl file, please modify LSDK 21.08 original DPL file dpl-eth.19.dts as the following.

/* ------------ DPNIs --------------*/
obj_set@dpni {
type = "dpni";
ids = <0x0 0x1>;
};

Modify to:

obj_set@dpni {
type = "dpni";
ids = <0x0 0x1 0x2 0x3>;
};

Then adding the following section in  "Connections" section.

connection@3 {
endpoint1 = "dpni@2";
endpoint2 = "dpmac@3";
};

connection@4 {
endpoint1 = "dpni@3";
endpoint2 = "dpmac@4";
};