T1040RDB DPAA Fman issue

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

T1040RDB DPAA Fman issue

3,546 Views
weizhao
Contributor I

I have a T1040RDB, I  can run Linux 3.12 Kernel with Topaz Hypervisor with no issue.  However, when I try to run Linux 4.1 with same hardware device tree, Hypervisor device tree, and Topaz Hypervisor, I always got following error info:

      [ 2.485455] cpu1/1: ! MAJOR FM Error [CPU01, /localdisk/data/perforce/wezhao_t1040rdb/main/packages/linux- 

      git/drivers/net/ethernet/freescale/fman/Peripherals/FM/fm.c:514 FwNotResetErratumBugzilla6173WA]: Invalid State;
      [ 2.540851] cpu1/1: Invalid debug status register value is '0'[ 2.557489] cpu1/1:

      .

      .

      .

      [ 2.705342] fsl_mac ffe4e0000.ethernet: 2. of_find_device_by_node(/devices/fman0/port@88000) failed
      [ 2.732411] fsl_mac: probe of ffe4e0000.ethernet failed with error -22

      [ 2.892733] fsl_mac ffe4e2000.ethernet: 2. of_find_device_by_node(/devices/fman0/port@89000) failed
      [ 2.919797] fsl_mac: probe of ffe4e2000.ethernet failed with error -22

      [ 3.080125] fsl_mac ffe4e4000.ethernet: 2. of_find_device_by_node(/devices/fman0/port@8a000) failed
      [ 3.107188] fsl_mac: probe of ffe4e4000.ethernet failed with error -22     

      [ 3.267517] fsl_mac ffe4e6000.ethernet: 2. of_find_device_by_node(/devices/fman0/port@8b000) failed
      [ 3.294580] fsl_mac: probe of ffe4e6000.ethernet failed with error -22

      [ 3.454910] fsl_mac ffe4e8000.ethernet: 2. of_find_device_by_node(/devices/fman0/port@8c000) failed
      [ 3.481971] fsl_mac: probe of ffe4e8000.ethernet failed with error -22

The board still boot successfully, however, no Ethernet port (fm1-gb3, fm1-gb4) show up.  Any idea please ?

Thanks,

Wei

0 Kudos
Reply
6 Replies

2,935 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Wei,

Would you please try whether there is problem to boot up Linux Kernel in the normal environment without Hypervisor?

Would you please provide your hv.dts and the target dts file?

Thanks,

Yiping

0 Kudos
Reply

2,935 Views
weizhao
Contributor I

Forgot attachment

0 Kudos
Reply

2,935 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Wei,

I tried to compile your dts file in SDK 2.0 environment, however there was compilation problem. I suspect your dts file is not compatible with Linux Kernel 4.1.

Would you please try to use the dts file arch/powerpc/boot/dts/fsl/t1040d4rdb.dts(or t1040rdb.dts) provided in Linux Kernel source 4.1.

Thanks,

Yiping

0 Kudos
Reply

2,935 Views
weizhao
Contributor I

Hi Yiping,

My hardware device tree file sending to you is generated from arch/powerpc/boot/dts/fsl/t1040rdb.dts as I am using t1040rdb board (not the DDR4 memory one). The only thing I modified is adding “fsl,P5040RDB” to both model and compatible so that I can reuse some code we added for P5040, please see the following:

Thanks,

Wei

diff --git a/arch/powerpc/boot/dts/t1040rdb.dts b/arch/powerpc/boot/dts/t1040rdb.dts

index af1db40..8f89900 100644

--- a/arch/powerpc/boot/dts/t1040rdb.dts

+++ b/arch/powerpc/boot/dts/t1040rdb.dts

@@ -35,8 +35,12 @@

/include/ "fsl/t104xsi-pre.dtsi"

/ {

- model = "fsl,T1040RDB";

+/* model = "fsl,T1040RDB";

compatible = "fsl,T1040RDB";

+*/

+ model = "fsl,T1040RDB", "fsl,P5040RDB";

+ compatible = "fsl,T1040RDB", "fsl,P5040RDB";

+

#address-cells = <2>;
#size-cells = <2>;
interrupt-parent = <&mpic>;

0 Kudos
Reply

2,935 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Wei,

Please use T1040RDB dts file provided in Linux Kernel 4.1 in arch/powerpc/boot/dts/fsl/t1040rdb.dts.

I verified t1040rdb.dts provided in SDK 2.0 working with Linux Kernel 4.1.8 on a T1040RDB DDR3 board without any problem.

Please refer to the attached log.

Please try the attached dtb file on your target board.


Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply

2,934 Views
weizhao
Contributor I

Hi Yiping,

Sorry for replying later as I took few day off.

I still get same issue even without running Hypervisor. The hardware device tree and Hypervisor device tree files are attached. I used hardware device tree from Linux 4.1 (SDK 2.0) for t1040rdb boards. The hypervisor configuration tree from Hypervisor 1.3 for t10404rdb.

Thanks,

Wei

0 Kudos
Reply