"fsl_mc lazyapply dpl 0x80d00000" cause Kernel panic

[muaxi8]

=> pri bootcmd
bootcmd=sf probe 0:0; sf read 0x806c0000 0x6c0000 0x40000; env exists mcinitcmd && env exists secureboot && esbc_validate 0x806c0000; sf read 0x80d00000 0xd00000 0x100000; env exists mcinitcmd && fsl_mc lazyapply dpl 0x80d00000; run xspi_bootcmd; env exists secureboot && esbc_halt;

when i perform "run bootcmd", The system will Kernel panic。

When I remove the "fsl_mc lazyapply DPL 0x80d00000" command, the system can be up. but There are some  errors message output though: "FSL-MC: DPL not Deployed, DPAA2 Ethernet not work", "Failed to init entropy source HWRNG". How can I troubleshoot this problem。

The attachment is the kernel panic log file。

[yipingwang]

Did you create the DPL file by yourself? 

Would you please provide your DPL file?

[muaxi8]

I didn't create my own DPL file.In the beginning, I downloaded the composite firmware, which should include DPL, DPC, DDR and other firmware contents. Later, I updated my RCW, Uboot and kernel, these are the things I need to debug.

I think the problem is not the firmware, but the kernel, because I downloaded the ITB file you gave me before, but I did not report this error, and I downloaded the ITB compiled by myself with Flex-Builder, but I did not change the kernel configuration, it is too strange

[muaxi8]

Here's the thing: I have bought your developer board, AND I'm testing my ITB on lX2160ARDB, "FSL-MC: Deploying Data Path Layout...When I test my ITB on my custom board, if I run "run bootcmd", it will cause "Kernel panic". If I do not perform "run xspi_bootcmd",it can start the Kernel successfully, butThere will be a "FSL-MC: DPL not Deployed, DPAA2 Ethernet Not work" issue 。

=> pri bootcmd
bootcmd=sf probe 0:0; sf read 0x806c0000 0x6c0000 0x40000; env exists mcinitcmd && env exists secureboot && esbc_validate 0x806c0000; sf read 0x80d00000 0xd00000 0x100000; env exists mcinitcmd && fsl_mc lazyapply dpl 0x80d00000;run xspi_bootcmd; env exists secureboot && esbc_halt;

=> pri xspi_bootcmd
xspi_bootcmd=echo Trying load from flexspi..;sf probe 0:0 && sf read $load_addr $kernel_start $kernel_size ; env exists secureboot &&sf read $kernelheader_addr_r $kernelheader_start $kernelheader_size && esbc_validate ${kernelheader_addr_r}; bootm $load_addr

[yipingwang]

Can you start Kernel successfully when testing your ITB image on lX2160ARDB?

[yipingwang]

Would you please send your ITB image to me? I will verify it on my lx2160ardb demo board.

You could remove Linux Kernel build directory build/linux/linux/arm64/LS/ to rebuild Linux Kernel from the scratch, if it's necessary.

[muaxi8]

itb file is upload to iBaidu Netdisk:

链接：https://pan.baidu.com/s/1UGAQC402PHHcp5dnMwdn5w
提取码：2345

I follow the following instructions:

=> tftp a0000000 0734_linux.itb

=> pri bootcmd
bootcmd=sf probe 0:0; sf read 0x806c0000 0x6c0000 0x40000; env exists mcinitcmd && env exists secureboot && esbc_validate 0x806c0000; sf read 0x80d00000 0xd00000 0x100000; env exists mcinitcmd && fsl_mc lazyapply dpl 0x80d00000;run xspi_bootcmd; env exists secureboot && esbc_halt;
=> sf probe 0:0; sf read 0x806c0000 0x6c0000 0x40000; env exists mcinitcmd && env exists secureboot && esbc_validate 0x806c0000; sf read 0x80d00000 0xd00000 0x100000; env exists mcinitcmd && fsl_mc lazyapply dpl 0x80d00000
SF: Detected mt35xu512aba with page size 256 Bytes, erase size 128 KiB, total 64 MiB
device 0 offset 0x6c0000, size 0x40000
SF: 262144 bytes @ 0x6c0000 Read: OK
device 0 offset 0xd00000, size 0x100000
SF: 1048576 bytes @ 0xd00000 Read: OK
=>bootm 0xa0000000

[yipingwang]

I can boot your image 0734_linux.itb on my Lx2160ARDB demo board successfully with DPL file dpl-eth.19.dtb applied.

Please refer to the attached log.

[muaxi8]

 my custom board is different from your demo board. Do I need to modify DPL or DPC according to the specific design ？

after modified ,how to build my dpl/dpc file?

[yipingwang]

Please refer to the following procedure.

1. $ flex-builder -c mc_utils -m lx2160ardb

2.Please backup and modify  dpc-usxgmii.dts and dpl-eth.19.dts in folder flexbuild_lsdk2012/packages/firmware/mc_utils/config/lx2160a/RDB.

In dpc-usxgmii.dts, please modify the following section.

board_info {
ports {
mac@3 {
link_type = "MAC_LINK_TYPE_PHY";
enet_if = "USXGMII";
};

mac@4 {
link_type = "MAC_LINK_TYPE_PHY";
enet_if = "USXGMII";
};

mac@17 {
link_type = "MAC_LINK_TYPE_PHY";
};
mac@18 {
link_type = "MAC_LINK_TYPE_PHY";
};
};

In dpl-eth.19.dts, please modify the following section.

connections {
connection@1 {
endpoint1 = "dpni@0";
endpoint2 = "dpmac@17";
};

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

};

3. $ flex-builder -c mc_utils -m lx2160ardb

4. You will get new dpc-usxgmii.dtb and dpl-eth.19.dtb in folder flexbuild_lsdk2012/packages/firmware/mc_utils/config/lx2160a/RDB.