LS2088A can't find device file using ls-main command

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

LS2088A can't find device file using ls-main command

1,442 Views
hengjianzhang
Contributor I

I want to add DAPP2 10GbE port in to system in order to run some sample that provide in LSDK19.06. But I found that using ls-main, ls-listni, ls-listmac are not working and all of them pop out a error message

root@localhost:~# ls-listmac
error: Did not find a device file
Restool wrapper scripts only support the latest major MC version
that currently is MC10.x. Use with caution.
error: Did not find a device file.

OS:using LSDK 19.06 default setting. command: flex-installer -i auto -m ls2088ardb -d /dev/sdb

I'm new boy in arm-based system, please help if OS is build in wrong way or other issue.

Labels (1)
0 Kudos
1 Reply

1,078 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please make sure MC, DPL and DPC firmware images are deployed at the following offset addresses on Flash. Please refer to the attached u-boot log, please make sure fsl-mc is set up successfully.
DPAA2 MC 0x00A00000
DPAA2 DPL 0x00D00000
DPAA2 DPC 0x00E00000
You could get these firmware images with the following method.
Please execute the following command and get MC firmware image in build/firmware/qoriq-mc-binary/ls2088a/mc_10.10.0_ls2088a_20180814.itb.
$ flex-builder -c qoriq-mc-binary -m ls2088ardb
You could execute the following command and get DPL and DPC firmware image in build/firmware/mc-utils/config/ls2088a/RDB/dpl-eth.0x2A_0x41.dtb(dpc.0x2A_0x41.dtb).
$ flex-builder -c mc-utils -m ls2088ardb

In addition, please run "fsl_mc lazyapply dpl 0x580d00000" to deploy DPL before booting up Linux Kernel, I assume that you have deployed dpl image at 0x580d00000.

root@TinyDistro:~# ls-addni dpmac.1
[   35.256512] iommu: Adding device dpbp.1 to group 1
[   35.372387] iommu: Adding device dpmcp.28 to group 1
[   35.491812] iommu: Adding device dpcon.1 to group 1
[   35.611740] iommu: Adding device dpcon.2 to group 1
[   35.733597] iommu: Adding device dpcon.3 to group 1
[   35.857659] iommu: Adding device dpcon.4 to group 1
[   35.984507] iommu: Adding device dpcon.5 to group 1
[   36.113581] iommu: Adding device dpcon.6 to group 1
[   36.243637] iommu: Adding device dpcon.7 to group 1
[   36.375477] iommu: Adding device dpcon.8 to group 1
[   36.529385] NOHZ: local_softirq_pending 80
[   36.533484] NOHZ: local_softirq_pending 80
[   36.537575] NOHZ: local_softirq_pending 282
[   36.541752] NOHZ: local_softirq_pending 282
[   36.545929] NOHZ: local_softirq_pending 282
[   36.550106] NOHZ: local_softirq_pending 282
[   36.564178] iommu: Adding device dpni.1 to group 1
[   36.617191] fsl_dpaa2_eth dpni.1: Key masks not supported. Steering is disabled
[   36.660687] fsl_dpaa2_eth dpni.1: Probed interface eth2
Created interface: eth2 (object:dpni.1, endpoint: dpmac.1)
root@TinyDistro:~# ifconfig eth2 100.10.1.159
[   62.653488] fsl_dpaa2_eth dpni.1 eth2: Link Event: state up
root@TinyDistro:~# ping 100.10.1.1
PING 100.10.1.1 (100.10.1.1): 56 data bytes
64 bytes from 100.10.1.1: seq=0 ttl=64 time=0.334 ms
64 bytes from 100.10.1.1: seq=1 ttl=64 time=0.150 ms
64 bytes from 100.10.1.1: seq=2 ttl=64 time=0.163 ms
64 bytes from 100.10.1.1: seq=3 ttl=64 time=0.137 ms
64 bytes from 100.10.1.1: seq=4 ttl=64 time=0.136 ms

0 Kudos