LS1088ARDB and LS2088ARDB network interfaces not found

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

LS1088ARDB and LS2088ARDB network interfaces not found

1,445 Views
omerer
Contributor I

Hi,

We bought new layerscape devices, which they are LS1088ARDB and LS2088ARDB. When I tried to configure eth1 or any other interface other than eth0 I got a message like this:

eth1: error fetching interface information: Device not found.

There is no such device named eth1 or eth2 or eth3 in "ifconfig -a" list.

What can I do to solve this problem ?

Any help will be appreciate.

Thanks

0 Kudos
2 Replies

1,154 Views
ufedor
NXP Employee
NXP Employee

Please confirm:
1) the boards are factory new and were not re-programmed after purchasing

2) you have read corresponding Getting Started Guide documents and perform the board bring-up as described

3) you see U-Boot and Linux booting logs on a console after the board is switched on.

Please provide complete boot logs for both boards as text files for inspection.

Please consider that current LSDK is v18.12:

Layerscape SDK | NXP 

0 Kudos

1,154 Views
dlciii
Contributor I

I ran into this same issue. The Ethernet interfaces have been renamed ni0, ni1, etc.

Also eth0 = ni0 is MAC 5 (this is especially useful in u-boot).

This stuff is in the QorIQ_SDKv2.0-1703 documentation but here is a summary snippet:

Configure eth 0 (dev board has ip range of 10.0.1.171-177)

root@ls2088ardb:# ifconfig ni0 10.0.1.171 up

Create additional Network Interface on the LS2088ARDB (by default, the only one created is ni0=ETH0)

Create network interfaces

  1. Check the network interfaces that are currently available using Layerscape script ls-listni.

    For example:

    $ ls-listni

    dprc.1/dpni.0 (interface: eth1, end point: dpmac.5)

    The default interface DPNI.0 is configured with a minimal set of resources.

    For example, it can only receive traffic on GPP0 and its intended uses are network boot and low-bandwidth traffic.

    For fully-featured DPNI objects, dynamic configuration (explained in upcoming steps) is recommended.

  2. Optional - Unbind and destroy existing interface. 

    $ echo dpni.0 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind

    $ restool dpni destroy dpni.0

    dpni.0 is destroyed

    The restool utility is a Linux user space command that allows DPAA2 objects to be managed (created, destroyed, and queried for status).
  3. Add new network interfaces using Layerscape script ls-addni.

    For example:

    $ ls-addni dpmac.5

    Created interface: eth0 (object:dpni.0, endpoint: dpmac.3)

    $ ls-addni dpmac.6

    Created interface: eth1 (object:dpni.1, endpoint: dpmac.4)

     

    Check that new interfaces are created using the ifconfig -a or ip link command.

     

  4. Enable the newly created interfaces using the ifconfig command

    For example:

    ifconfig ni0 192.168.1.23 up (ETH0 listed on LS2088ARDB)

    ifconfig ni1 192.168.1.24 up (ETH1 listed on LS2088ARDB)

0 Kudos