Error in initializing network parameters

Deval Shah deval.maker at gmail.com
Mon Aug 8 18:13:31 UTC 2016


I ran both the dhcpcd examples. The boot logs are below. I am seeing the
same problem in these two examples too. Test program tries to get the
network interfaces but it is not found since the USB initialization is
still left.


*** LIBBSD DHCPCD 1 TEST ***

RTEMS Shell on /dev/console. Use 'help' to list commands.
[/] # nexus0: <RTEMS Nexus device>
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> on nexus0
bcm283x_dwcotg0: failed to set power state, err=-2
usbus0 on bcm283x_dwcotg0
usbus0: 480Mbps High Speed USB v2.0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
info: version 6.2.1 starting
err: no valid interfaces found
warning: no interfaces have a carrier
uhub0: 1 port with 1 removable, self powered
uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on
usbus0
uhub1: MTT enabled
uhub1: 5 ports with 4 removable, self powered
smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus0
smsc0: chip 0xec00, rev. 0002
miibus0: <MII bus> on smsc0
ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ue0: <USB Ethernet> on smsc0
ue0: Ethernet address: 5a:ee:60:74:67:92


*** LIBBSD DHCPCD 2 TEST ***

RTEMS Shell on /dev/console. Use 'help' to list commands.
[/] # nexus0: <RTEMS Nexus device>
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> on nexus0
bcm283x_dwcotg0: failed to set power state, err=-2
usbus0 on bcm283x_dwcotg0
usbus0: 480Mbps High Speed USB v2.0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
info: version 6.2.1 starting
err: no valid interfaces found
warning: no interfaces have a carrier
uhub0: 1 port with 1 removable, self powered
uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on
usbus0
uhub1: MTT enabled
uhub1: 5 ports with 4 removable, self powered
smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus0
smsc0: chip 0xec00, rev. 0002
miibus0: <MII bus> on smsc0
ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ue0: <USB Ethernet> on smsc0

Any other way to solve this problem ? Any example of mentioned routing
socket ?

ᐧ

On Tue, Aug 2, 2016 at 5:51 PM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> The USB enumeration runs after the BSD initialization in its own threads.
> Thus, you have to wait a bit before you attempt to use this interface. You
> could use a routing socket to do this event triggered, see dhcpcd for an
> example.
>
>
> On 02/08/16 14:17, Deval Shah wrote:
>
>> Hello all,
>>
>> With the USB and Ethernet working, I started running other tests like
>> ping01 on raspberry Pi.
>>
>> I am getting following error while running the PING test.
>>
>> ------------------------------------------------------------
>> --------------------------------------
>> *** LIBBSD PING 1 TEST ***
>> nexus0: <RTEMS Nexus device>
>> bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> on
>> nexus0
>> usbus0 on bcm283x_dwcotg0
>> usbus0: 480Mbps High Speed USB v2.0
>> uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
>> ifconfig: interface ue0 does not exist
>> assertion "exit_code == EX_OK" failed: file "/home/gadgetman/development/r
>> tems/rtems-libbsd/testsuite/include/rtems/bsd/test/default-network-init.h",
>> line 125, function: default_network_ifconfig_hwif0
>> ------------------------------------------------------------
>> --------------------------------------
>>
>> In general boot-log, like in init test, after detecting the "uhub0"
>> device it detects "uhub1" device, which is the usb_ethernet controller. And
>> after that the Ethernet interface "ue0" exists.
>>
>> ------------------------------------------------------------
>> --------------------------------------
>> *** LIBBSD INIT 1 TEST ***
>> nexus0: <RTEMS Nexus device>
>> bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> on
>> nexus0
>> usbus0 on bcm283x_dwcotg0
>> usbus0: 480Mbps High Speed USB v2.0
>> uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
>> Sleeping to see what happens
>> uhub0: 1 port with 1 removable, self powered
>> uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2>
>> on usbus0
>> uhub1: MTT enabled
>> uhub1: 5 ports with 4 removable, self powered
>> smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus0
>> smsc0: chip 0xec00, rev. 0002
>> miibus0: <MII bus> on smsc0
>> ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
>> ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>> ue0: <USB Ethernet> on smsc0
>> ue0: Ethernet address: 5a:ee:60:74:67:92
>> ------------------------------------------------------------
>> --------------------------------------
>>
>> I believe the default-network-init.h tries to access the ethernet
>> interface before it is created and the problem arises. I tried moving
>> bsp/nexus-devices.h before rtems/bsd/test/default-network-init.h, but
>> the problem remains the same. Any pointers ?
>>
>>
>> Regards,
>> Deval Shah
>>
>>>>
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>


-- 
Deval Shah
Graduate Student,
B.E. (Hons.) Electrical and Electronics Engineering
BITS Pilani Hyderabad Campus <http://www.bits-pilani.ac.in/hyderabad/>

Github Profile <https://github.com/deval-maker>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20160808/400376e7/attachment-0001.html>


More information about the devel mailing list