[Buildroot] Starting network...

[Buildroot] Starting network...

[Lee, Tommy]

Hi Buildroot mailing list,

My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have made the former meet the latter's requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. Last week I succeeded in the building of the zImage file of my Linux system which has a rootfilesystem integrated, and a armada-385-db-ap.dtb file, The DB-88F6820-GP on-board U-Boot-1.73 commands are able to the boot up the system. The U-Boot bootargs string is:

"setenv bootargs console=ttyS0,115200 root=/dev/ram0 rw rootdelay=2"
But, I discovered, this system cannot enable the eth0 device at the boot time. The "Starting network..." messages are:

Starting network...
[    1.618607] mvneta f1030000.ethernet eth0: could not find the PHY
[    1.624732] mvneta f1030000.ethernet eth0: cannot probe MDIO busip: SIOCSIFFLAGS: No such device

Before I boot the system, the board's eth0 interface connects to a DHCP server. The attached is my .config. I am resolving this eth0-enabling issue. Your experience sharing is definitely welcome.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150824/d31923de/attachment.html>

[Buildroot] Starting network...

[Thomas Petazzoni]

Tommy,

On Mon, 24 Aug 2015 16:36:22 -0700, Lee, Tommy wrote:
> Hi Buildroot mailing list,
> 
> My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have made the former meet the latter's requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. Last week I succeeded in the building of the zImage file of my Linux system which has a rootfilesystem integrated, and a armada-385-db-ap.dtb file, The DB-88F6820-GP on-board U-Boot-1.73 commands are able to the boot up the system. The U-Boot bootargs string is:
> 
> "setenv bootargs console=ttyS0,115200 root=/dev/ram0 rw rootdelay=2"
> But, I discovered, this system cannot enable the eth0 device at the boot time. The "Starting network..." messages are:
> 
> Starting network...
> [    1.618607] mvneta f1030000.ethernet eth0: could not find the PHY
> [    1.624732] mvneta f1030000.ethernet eth0: cannot probe MDIO busip: SIOCSIFFLAGS: No such device

This is a kernel/hardware issue, that has nothing to do with Buildroot.

However, beware that if you run the mainline (official) Linux kernel on
Armada 38x, the first network interface (from a HW point of view) is
seen as eth1 in Linux, and the second network interface (from a HW
point of view) is seen as eth0 in Linux. This is due to the ordering of
the nodes in the Device Tree, which are ordered by register address.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Starting network...

[Lee, Tommy]

Thomas,

My system's dhcpcd command only enables the unexpected eth2 for networking with no problems. What I am expecting is that Eth0 and eth1 are initially enabled by my system boot process - one for corporate networking; other for local segment engineering work.

Reading your "Device Tree for Dummies" PDF, I rebuilt my zImage and armada-385-db-ap.dtb with the .config DTS settings as:

BR2_LINUX_KERNEL_DTS_SUPPORT=y
# BR2_LINUX_KERNEL_USE_INTREE_DTS is not set
BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y
BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="./output/build/linux-4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts"

The make process ends up with an erratic message saying:

cp: './output/build/linux-4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts' and '/home/tclee/Downloads/aug10mon15/buildroot-2015.05/output/build/linux-4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts' are the same file
make: *** [/home/tclee/Downloads/aug10mon15/buildroot-2015.05/output/build/linux-4.0.4/.stamp_built] Error 1

I am resolving this error now. Your help is definitely welcome.

Tommy



-----Original Message-----
From: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com]
Sent: Tuesday, August 25, 2015 10:55 AM
To: Lee, Tommy
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Starting network...

Tommy,

On Mon, 24 Aug 2015 16:36:22 -0700, Lee, Tommy wrote:
> Hi Buildroot mailing list,
>
> My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have made the former meet the latter's requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. Last week I succeeded in the building of the zImage file of my Linux system which has a rootfilesystem integrated, and a armada-385-db-ap.dtb file, The DB-88F6820-GP on-board U-Boot-1.73 commands are able to the boot up the system. The U-Boot bootargs string is:
>
> "setenv bootargs console=ttyS0,115200 root=/dev/ram0 rw rootdelay=2"
> But, I discovered, this system cannot enable the eth0 device at the boot time. The "Starting network..." messages are:
>
> Starting network...
> [    1.618607] mvneta f1030000.ethernet eth0: could not find the PHY
> [    1.624732] mvneta f1030000.ethernet eth0: cannot probe MDIO busip: SIOCSIFFLAGS: No such device

This is a kernel/hardware issue, that has nothing to do with Buildroot.

However, beware that if you run the mainline (official) Linux kernel on Armada 38x, the first network interface (from a HW point of view) is seen as eth1 in Linux, and the second network interface (from a HW point of view) is seen as eth0 in Linux. This is due to the ordering of the nodes in the Device Tree, which are ordered by register address.

Best regards,

Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering http://free-electrons.com

This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

[Buildroot] Starting network...

[Thomas Petazzoni]

Hello,

On Tue, 1 Sep 2015 11:33:41 -0700, Lee, Tommy wrote:

> My system's dhcpcd command only enables the unexpected eth2 for networking with no problems. What I am expecting is that Eth0 and eth1 are initially enabled by my system boot process - one for corporate networking; other for local segment engineering work.
> 
> Reading your "Device Tree for Dummies" PDF, I rebuilt my zImage and armada-385-db-ap.dtb with the .config DTS settings as:
> 
> BR2_LINUX_KERNEL_DTS_SUPPORT=y
> # BR2_LINUX_KERNEL_USE_INTREE_DTS is not set
> BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y
> BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="./output/build/linux-4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts"
> 
> The make process ends up with an erratic message saying:
> 
> cp: './output/build/linux-4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts' and '/home/tclee/Downloads/aug10mon15/buildroot-2015.05/output/build/linux-4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts' are the same file
> make: *** [/home/tclee/Downloads/aug10mon15/buildroot-2015.05/output/build/linux-4.0.4/.stamp_built] Error 1

Yes, it does not make sense to use BR2_LINUX_KERNEL_USE_CUSTOM_DTS for
a Device Tree file that is inside the tree. You should be using
BR2_LINUX_KERNEL_USE_INTREE_DTS instead.

Basically, Buildroot supports two cases:

 * The Device Tree for your platform is part of the Linux kernel
   sources, i.e it is in arch/arm/boot/dts/ in your kernel tree. In
   this case, you should use BR2_LINUX_KERNEL_USE_INTREE_DTS=y, and
   then give only the name of that Device Tree (armada-385-gp). This is
   what you should be using.

 * The Device Tree for your platform is *not* part of the Linux kernel
   sources. It is available separately. In this case, you should use
   BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y, and specify the full path to your
   Device Tree file.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Starting network...

[Lee, Tommy]

Thomas,



In the buildroot-2015.05 folder the armada-385-gp.dts file does not exist but the armada-385-db-ap.dts one.



Last week I built armada-385-db-ap.dtb using the following .config DTS and eth0 with no problems:



BR2_SYSTEM_DHCP="eth0"

BR2_LINUX_KERNEL_DTS_SUPPORT=y

BR2_LINUX_KERNEL_USE_INTREE_DTS=y

# BR2_LINUX_KERNEL_USE_CUSTOM_DTS is not set

BR2_LINUX_KERNEL_INTREE_DTS_NAME="armada-385-db-ap"



I just used the settings again and built zImage and armada-385-db-ap. This time the armada-385-db-ap.dtb has the same md5sum value as the one I built last week.



On the board, the boot process shows:



Starting network...

udhcpc (v1.23.2) started

Sending discover...

[    4.732186] mvneta f1070000.ethernet eth2: Link is Up - 100Mbps/Half - flow f

Sending discover...

Sending select for 10.28.1.47...

Lease of 10.28.1.47 obtained, lease time 1209600

deleting routers

adding dns 10.28.5.20

adding dns 10.4.5.7

ssh-keygen: generating new host keys: RSA1 RSA DSA ECDSA ED25519

Starting sshd: OK

Starting network management serv[   11.715258] NET: Registered protocol family 0

ices:.



Welcome to Buildroot

buildroot login:



After login, the ifconfig result is:



# ifconfig

eth2      Link encap:Ethernet  HWaddr 00:50:43:EC:16:4D

          inet addr:10.28.1.47  Bcast:10.28.1.255  Mask:255.255.255.0

          inet6 addr: fe80::250:43ff:feec:164d/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1877 errors:0 dropped:0 overruns:0 frame:0

          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:532

          RX bytes:213843 (208.8 KiB)  TX bytes:1332 (1.3 KiB)

          Interrupt:38



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:0

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)



The interesting point is that eth2 is still picked up by the system for the dhcpcd process, not eth0 which is set in the .config file. Probably you know the reason for this unexpected result.



I am resolving the eth0 issue now. Your help will be definitely appreciated.



Tommy







-----Original Message-----
From: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com]
Sent: Tuesday, September 01, 2015 12:14 PM
To: Lee, Tommy
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Starting network...



Hello,



On Tue, 1 Sep 2015 11:33:41 -0700, Lee, Tommy wrote:



> My system's dhcpcd command only enables the unexpected eth2 for networking with no problems. What I am expecting is that Eth0 and eth1 are initially enabled by my system boot process - one for corporate networking; other for local segment engineering work.

>

> Reading your "Device Tree for Dummies" PDF, I rebuilt my zImage and armada-385-db-ap.dtb with the .config DTS settings as:

>

> BR2_LINUX_KERNEL_DTS_SUPPORT=y

> # BR2_LINUX_KERNEL_USE_INTREE_DTS is not set

> BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y

> BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="./output/build/linux-4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts"

>

> The make process ends up with an erratic message saying:

>

> cp:

> './output/build/linux-4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts'

> and

> '/home/tclee/Downloads/aug10mon15/buildroot-2015.05/output/build/linux

> -4.0.4/arch/arm/boot/dts/armada-385-db-ap.dts' are the same file

> make: ***

> [/home/tclee/Downloads/aug10mon15/buildroot-2015.05/output/build/linux

> -4.0.4/.stamp_built] Error 1



Yes, it does not make sense to use BR2_LINUX_KERNEL_USE_CUSTOM_DTS for a Device Tree file that is inside the tree. You should be using BR2_LINUX_KERNEL_USE_INTREE_DTS instead.



Basically, Buildroot supports two cases:



* The Device Tree for your platform is part of the Linux kernel

   sources, i.e it is in arch/arm/boot/dts/ in your kernel tree. In

   this case, you should use BR2_LINUX_KERNEL_USE_INTREE_DTS=y, and

   then give only the name of that Device Tree (armada-385-gp). This is

   what you should be using.



* The Device Tree for your platform is *not* part of the Linux kernel

   sources. It is available separately. In this case, you should use

   BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y, and specify the full path to your

   Device Tree file.



Best regards,



Thomas

--

Thomas Petazzoni, CTO, Free Electrons

Embedded Linux, Kernel and Android engineering http://free-electrons.com

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150901/282071e5/attachment.html>

[Buildroot] Starting network...

[Thomas Petazzoni]

Hello,

On Tue, 1 Sep 2015 15:03:58 -0700, Lee, Tommy wrote:

> In the buildroot-2015.05 folder the armada-385-gp.dts file does not exist but the armada-385-db-ap.dts one.

Buildroot does *not* contain any armada-*.dts file. Those files come
with the kernel sources. You are confusing things, it seems.

There is indeed no armada-385-gp.dts file in the kernel, as it's called
armada-388-gp.dts.

> Last week I built armada-385-db-ap.dtb using the following .config DTS and eth0 with no problems:
> 
> 
> 
> BR2_SYSTEM_DHCP="eth0"
> 
> BR2_LINUX_KERNEL_DTS_SUPPORT=y
> 
> BR2_LINUX_KERNEL_USE_INTREE_DTS=y
> 
> # BR2_LINUX_KERNEL_USE_CUSTOM_DTS is not set
> 
> BR2_LINUX_KERNEL_INTREE_DTS_NAME="armada-385-db-ap"
> 
> 
> 
> I just used the settings again and built zImage and armada-385-db-ap. This time the armada-385-db-ap.dtb has the same md5sum value as the one I built last week.

And? I don't see where your question is here. Also, I don't understand
why you're sometimes referring to the Armada 388 GP and sometimes to
the Armada 385 DB AP. Those are completely different boards, so you
cannot use the Device Tree for one platform on the other platform.

> On the board, the boot process shows:
> 
> 
> 
> Starting network...
> 
> udhcpc (v1.23.2) started
> 
> Sending discover...
> 
> [    4.732186] mvneta f1070000.ethernet eth2: Link is Up - 100Mbps/Half - flow f
> 
> Sending discover...
> 
> Sending select for 10.28.1.47...
> 
> Lease of 10.28.1.47 obtained, lease time 1209600
> 
> deleting routers
> 
> adding dns 10.28.5.20
> 
> adding dns 10.4.5.7
> 
> ssh-keygen: generating new host keys: RSA1 RSA DSA ECDSA ED25519
> 
> Starting sshd: OK
> 
> Starting network management serv[   11.715258] NET: Registered protocol family 0
> 
> ices:.
> 
> 
> 
> Welcome to Buildroot
> 
> buildroot login:
> 
> 
> 
> After login, the ifconfig result is:
> 
> 
> 
> # ifconfig

Use ifconfig -a to see all interfaces.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Starting network...

[Lee, Tommy]

Thomas,

I should have noticed that the .dts files come along with the kernel source downloading.

I just discovered the output/build/linux-headers-4.0.4/arch/arm/boot/dts/armada-388-gp.dts. I will not use it since, as you mentioned, the 388 board differs from the 385 one I am using.

After I added following lines into the /etc/network/interfaces file and did the "ifdown eth0" and "ifup eth0" commands, my "ifconfig -a" command shows following result. Now my system has two network interfaces enabled.

Thanks for your help!

Tommy

# vi /etc/network/interfaces
.....
iface eth0 inet static
address 192.168.1.5
gateway 192.168.1.254
netmask 255.255.255.0

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:43:48:16:4D
          inet addr:192.168.1.5  Bcast:0.0.0.0  Mask:255.255.255.0
          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:532
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:36

eth1      Link encap:Ethernet  HWaddr 00:50:43:48:EC:4D
          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:532
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:37

eth2      Link encap:Ethernet  HWaddr 00:50:43:EC:16:4D
          inet addr:10.28.1.47  Bcast:10.28.1.255  Mask:255.255.255.0
          inet6 addr: fe80::250:43ff:feec:164d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4031 errors:0 dropped:3 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:461861 (451.0 KiB)  TX bytes:1332 (1.3 KiB)
          Interrupt:38

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:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

[Buildroot] Starting network...

[Lee, Tommy]

Here is my .config.

From: Lee, Tommy
Sent: Monday, August 24, 2015 4:36 PM
To: 'buildroot at busybox.net'
Subject: Starting network...

Hi Buildroot mailing list,

My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have made the former meet the latter's requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. Last week I succeeded in the building of the zImage file of my Linux system which has a rootfilesystem integrated, and a armada-385-db-ap.dtb file, The DB-88F6820-GP on-board U-Boot-1.73 commands are able to the boot up the system. The U-Boot bootargs string is:

"setenv bootargs console=ttyS0,115200 root=/dev/ram0 rw rootdelay=2"

But, I discovered, this system cannot enable the eth0 device at the boot time. The "Starting network..." messages are:

Starting network...
[    1.618607] mvneta f1030000.ethernet eth0: could not find the PHY
[    1.624732] mvneta f1030000.ethernet eth0: cannot probe MDIO busip: SIOCSIFFLAGS: No such device

Before I boot the system, the board's eth0 interface connects to a DHCP server. The attached is my .config. I am resolving this eth0-enabling issue. Your experience sharing is definitely welcome.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150824/6db120be/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.aug21fri15
Type: application/octet-stream
Size: 54042 bytes
Desc: config.aug21fri15
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150824/6db120be/attachment.obj>