LS1012ARDB ETH0 not showing up in Tiny Linux

[christophe_schm]

Hi,

Using latest LSDK 19.09 and also able to build  firmware_ls1012ardb_uboot_qspiboot.img  I can flash and use.

During build I did not brought any changes to code or used some special build options.

A performed a simple "flex-builder -m ls1012ardb -b qspi" and then flashed the resulting "image firmware_ls1012ardb_uboot_qspiboot.img" as described in "LS1012ARDBGSG Getting Started Guide Rev. 5, 09/2018", §14.4 Step 2: Flashing LSDK composite firmware image. All went well so far.

NOTE: I flash it on bank 2 and not bank 1 of embedded QSPI flash device - maybe this is my problem and I shall put it on bank 1?

I also set the variables in u-boot prompt exactly as described above, but this does not help in my case.

Problem I've is I simply don't see and cannot mount the eth0 device despite in u-boot phase it seems to be up and running already. So I can boot and log into tiny Linux as root and there, in order to flash boot partition and userland I need first to bring up eth0 by doing " ifconfig eth0 hw ether <MyMAC address>". Doing that simply tells me there is no such device, I only can see "lo" and "sit0@NONE" devices, ping localhost works making me believe stack is up and alive. Looking into /etc/network/interfaces indeed shows eth0 is absent - what went wrong?

Any idea? Thx Christophe

[christophe_schm]

Just want let you know for the moment I wrote boot partition and user land on a USB stick, works like a charm, cool!

However the NXP LSDK does not let me in with root/root login/pwd, what's the correct one?

And yes, if you can help me on eMMC usage instead of USB I'd be glad, I need USB for other purpose here.

Thx Christophe

[christophe_schm]

For completeness I just flashed NXP's official image provided here:

https://lsdk.github.io/agreement.html?version=1909&down_idx=8&title=firmware_ls1012ardb_uboot_qspibo...

Result is same: no ETH0 in sight. Any help welcome since I'd like to move forward.

I now also look into the U-boot scripts and .cfg files to understand what I am missing.

Last thing: I enabled eMMC on my board maybe that could cause trouble? I don't use external SDIO interface (where you can e.g. connect a Wi-Fi SDIO card).

Thx Christophe

[yipingwang · Accepted solution]

Hello Christophe SCHMID,

You need to insert pfe.ko manually.

Please refer to the following.

root@TinyLinux:~# find /lib/ -name pfe.ko
/lib/modules/4.19.68/kernel/drivers/staging/fsl_ppfe/pfe.ko
root@TinyLinux:~# insmod /lib/modules/4.19.68/kernel/drivers/staging/fsl_ppfe/pfe.ko
[ 44.026087] pe_load_ddr_section: load address(3fb0000) and elf file address(ffff00000d385000) rcvd
root@TinyLinux:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:15:17:8e:7c:ea
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:29 Memory:4040000000-4040020000

eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

sit0 Link encap:UNSPEC HWaddr 00-00-00-00-31-00-6C-6F-00-00-00-00-00-00-00-00
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Thanks,

Yiping

[christophe_schm]

Hello Yiping,

That worked, thanks!

Is this behavior normal and configured as such in LSDK1909 standard configuration? Differently said: if I want this to automate where do I've to touch configuration during build (or maybe in u-boot boot params directly)?

Another question: I try to use the embedded eMMC on my LS1012ARDB board to flash boot boot partition and user land on it instead of an external SD card or USB/SATA device. Do I need to change build configurations first? Will look at this but if you've the answer directly here will be faster, thanks!

Christophe