ls1046a two XFI (10 GbE) interfaces

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ls1046a two XFI (10 GbE) interfaces

2,159 Views
hongyuanz
Contributor IV

LS1046ARDB design possessing SFP cage connected to the XFI interface of the processor

I think , Both XFI9 and XFI10 are compatible with SFP CAGE. . ? what needs to be changed

uboot: fm1-mac9 print

   could not get PHY for mdio@fd000:ddr0

0 Kudos
9 Replies

1,982 Views
hongyuanz
Contributor IV
 
Tags (1)
0 Kudos

1,984 Views
hongyuanz
Contributor IV

 dts file has been added

0 Kudos

2,133 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please refer to LS1046ARDB, XFI9 connects to aqr106_phy, only XFI10 is compatible with SFP CAGE.


ethernet@f0000 { /* 10GEC1 */
phy-handle = <&aqr106_phy>;
phy-connection-type = "xgmii";
};

ethernet@f2000 { /* 10GEC2 */
fixed-link = <0 1 1000 0 0>;
phy-connection-type = "xgmii";
};

 

0 Kudos

2,117 Views
hongyuanz
Contributor IV

custom board will XFI9 connects to SFP CAGE, and XFI10 is compatible with SFP CAGE.

ethernet@f0000 { /* 10GEC1 */
fixed-link = <0 1 1000 0 0>;
phy-connection-type = "xgmii";
};

ethernet@f2000 { /* 10GEC2 */
fixed-link = <0 1 1000 0 0>;
phy-connection-type = "xgmii";
};

This 10GEC2 does not work , 10GEC1 not tested yet

0 Kudos

2,080 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please configure SRDS_PRTCL_S1RCW[128-143] as 1133 in RCW.

0 Kudos

2,005 Views
hongyuanz
Contributor IV

 

I have configured as SRDS_PRTCL_S1RCW[128-143] as 1133 in RCW
mac9 defines its own board without connecting the phy chip
 

mac9 use usdpaa sec module to run encryption case

mac10 uses 10G optical port to communicate

DTS config
fsl-ls1046a-pscb.dts:

ethernet@f2000 { /* 10GEC2 */
fixed-link = <0 1 10000 0 0>;
phy-connection-type = "xgmii";
};

ethernet@f0000 {
fixed-link = <1 1 10000 0 0>;
phy-connection-type = "xgmii";

};

fsl-ls1046a-pscb-usdpaa.dts:

fsl,dpaa {
compatible = "fsl,ls1046a", "fsl,dpaa", "simple-bus";
dma-coherent;

ethernet@8 {
compatible = "fsl,dpa-ethernet-init";
fsl,bman-buffer-pools = <&bp7 &bp8 &bp9>;
fsl,qman-frame-queues-rx = <0x5e 1 0x5f 1>;
fsl,qman-frame-queues-tx = <0x7e 1 0x7f 1>;
};

dpa-fman0-oh@2 {
compatible = "fsl,dpa-oh";
/* Define frame queues for the OH port*/
/* <OH Rx error, OH Rx default> */
fsl,qman-frame-queues-oh = <0x60 1 0x61 1>;
fsl,fman-oh-port = <&fman0_oh2>;
};
};

 
 

 

linux startup log

[ 2.518598] fsl_mac: fsl_mac: FSL FMan MAC API based driver
[ 2.524477] fsl_mac 1ae8000.ethernet: FMan MEMAC
[ 2.529125] fsl_mac 1ae8000.ethernet: FMan MAC address: 00:e0:0c:00:33:31
[ 2.536250] fsl_mac 1af0000.ethernet: FMan MEMAC
[ 2.540885] fsl_mac 1af0000.ethernet: FMan MAC address: 00:e0:0c:00:33:32
[ 2.547948] fsl_mac 1af2000.ethernet: FMan MEMAC
[ 2.552595] fsl_mac 1af2000.ethernet: FMan MAC address: 00:e0:0c:00:33:33
[ 2.559429] fsl_dpa: FSL DPAA Ethernet driver
[ 2.565522] fsl_dpa: fsl_dpa: Probed interface eth0
[ 2.572145] fsl_dpa: fsl_dpa: Probed interface eth1
[ 2.577089] fsl_advanced: FSL DPAA Advanced drivers:
[ 2.582061] fsl_proxy: FSL DPAA Proxy initialization driver
[ 2.587780] fsl_oh: FSL FMan Offline Parsing port driver
[ 2.593204] fsl_oh soc:fsl,dpaa:dpa-fman0-oh@2: Found OH node handle compatible with fsl,dpa-oh
[ 2.601924] fsl_oh soc:fsl,dpaa:dpa-fman0-oh@2: Allocating 0 ingress frame queues duples
[ 2.610078] fsl_oh soc:fsl,dpaa:dpa-fman0-oh@2: OH port port@83000 has no buffer pool. Fragmentation will not be enabled
[ 2.621055] fsl_oh soc:fsl,dpaa:dpa-fman0-oh@2: OH port port@83000 enabled.
[ 2.628021] fsl_oh soc:fsl,dpaa:dpa-fman0-oh@2: Default egress frame queue: 97
[ 2.635246] fsl_oh soc:fsl,dpaa:dpa-fman0-oh@2: Default error frame queue: 96
[ 2.642382] fsl_oh soc:fsl,dpaa:dpa-fman0-oh@2: Initialized queues:
[ 2.649292] hclge is initializing
[ 2.650668] ata1: SATA link down (SStatus 0 SControl 300)
 
 
 
First mac10 can ping the server, start mac9 /usr/local/dpdk/crypto_perf_test.sh dpaa_sec case, after a period of time, the mac10 network card will not work
 
dmesg View log
[ 258.640043] Qman ErrInt: Invalid Enqueue State
[ 258.640055] Qman ErrInt: DCP id 0
[ 258.640061] Qman ErrInt: ecir.fqid 0xe00
[ 573.424509] Qman ErrInt: Invalid Enqueue State
[ 573.424514] Qman ErrInt: DCP id 0
[ 573.424517] Qman ErrInt: ecir.fqid 0xe00
[ 574.448827] Qman ErrInt: Invalid Enqueue State
[ 574.448833] Qman ErrInt: DCP id 0
[ 574.448835] Qman ErrInt: ecir.fqid 0xe00
[ 575.472184] Qman ErrInt: Invalid Enqueue State
[ 575.472190] Qman ErrInt: DCP id 0
[ 575.472193] Qman ErrInt: ecir.fqid 0xe00
[ 576.495915] Qman ErrInt: Invalid Enqueue State
[ 576.495921] Qman ErrInt: DCP id 0
[ 576.495923] Qman ErrInt: ecir.fqid 0xe00
[ 576.616132] USDPAA release: 16396 FQIDs
 
0 Kudos

1,997 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please create your dts file based on fsl-ls1046a-rdb-sdk.dts.

Please define your dts file including the following section.

#include "fsl-ls1046a-rdb.dts"
#include "qoriq-qman-portals-sdk.dtsi"
#include "qoriq-bman-portals-sdk.dtsi"

&bman_fbpr {
compatible = "fsl,bman-fbpr";
alloc-ranges = <0 0 0x10000 0>;
};
&qman_fqd {
compatible = "fsl,qman-fqd";
alloc-ranges = <0 0 0x10000 0>;
};
&qman_pfdr {
compatible = "fsl,qman-pfdr";
alloc-ranges = <0 0 0x10000 0>;
};

&soc {
/delete-property/ dma-coherent;

#include "qoriq-dpaa-eth.dtsi"
#include "qoriq-fman3-0-6oh.dtsi"

 

0 Kudos

1,919 Views
hongyuanz
Contributor IV

 dts file has been added  still abnormal

0 Kudos

1,902 Views
yipingwang
NXP TechSupport
NXP TechSupport

It seems that there is no problem in the dts file.

Do you use LSDK 21.08?

Do you use Linux Kernel image built with the default Kernel configuration provided in LSDK?

Would you please provide your Linux Kernel configuration file?

0 Kudos