Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - BeagleBoard RevC4 and D-Link E100: (6 Items)
   
BeagleBoard RevC4 and D-Link E100  
I have received a Beagleboard RevC4 with a QNX image on it.

i have connected a USB-Ethernet D-Link E100 that is suported by my image but I do not succeed to get an IP adress for 
the board.

here are the commands I have run
  [code]io-pkt-v4 -d asix -p tcpip,verbose
  waitfor /dev/io-net/en0
  dhcp.client
  [/code]

Hereunder is the result of ifconfig command.
[code]
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet 127.0.0.1 netmask 0xff000000
en0: flags=80008a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST,SHIM> mtu 1500
        address: 00:80:c8:3b:0f:72
        media: Ethernet 10baseT
        status: active
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
  [/code]

as you can see the network seems to be established but I have no IP address;

here is the sloinfo report

[code]Jan 01 00:02:00    5    14     0 tcpip starting
Jan 01 00:02:00    3    14     0 Unable to attach to pci server: No such file or directory
Jan 01 00:02:00    3    14     0 Using pseudo random generator.  See "random" option[/code]


Any idea on what is going wrong? previously I had a RevB with an other QNX image and the setup was ok :-(
Re: BeagleBoard RevC4 and D-Link E100  
One thing that does tend to happen with USB on these eval boards is power-limiting.  You might want to try plugging into
 a powered hub and see if that makes any difference. Haven't seen it before with a wired dongle, but it's common with 
wireless dongles.   An output from nicinfo would be helpful to see if packets are flowing.

  Does the USB subsystem work with other devices?

     Robert.
Re: BeagleBoard RevC4 and D-Link E100  
Hi

I am currently using a power hub. the same setup was working correctly with my previous RevB board and an other QNX 
image loaded on it.

hereunder the nicinfo

# nicinfo 

en0: 
  ax Ethernet Controller

  Link is DOWN

  Physical Node ID ........................... 0080C8 3B0F72
  Current Physical Node ID ................... 0080C8 3B0F72
  Current Operation Rate ..................... Unknown
  Active Interface Type ...................... MII
    Active PHY address ....................... 3
  Maximum Transmittable data Unit ............ 1514
  Maximum Receivable data Unit ............... 1514
  Promiscuous Mode ........................... Off
  Multicast Support .......................... Enabled

  Packets Transmitted OK ..................... 11
  Bytes Transmitted OK ....................... 3762
  Broadcast Packets Transmitted OK ........... 11
  Multicast Packets Transmitted OK ........... 0

  Packets Received OK ........................ 0
  Bytes Received OK .......................... 0
  Broadcast Packets Received OK .............. 0
  Multicast Packets Received OK .............. 0
  Memory Allocation Failures on Receive ...... 0

  Single Collisions on Transmit .............. 0
  Multiple Collisions on Transmit ............ 0
  Deferred Transmits ......................... 0
  Late Collision on Transmit errors .......... 0
  Transmits aborted (excessive collisions) ... 0
  Transmit Underruns ......................... 0
  No Carrier on Transmit ..................... 0
  Receive Alignment errors ................... 0
  Received packets with CRC errors ........... 0
  Packets Dropped on receive ................. 0
  Short packets .............................. 0
  Total Frames experiencing Collison(s) ...... 0

#I also see some differences in the /proc/boot directory between my two devices.
I have the following on RevB board and not on RevC

devh-usb.so                           
devi-hid                              
devn-asix.so                          
devn-pegasus.so                       
devn-rtl8150.so                       
devnp-shim.so                         
devu-kbd                              
devu-mouse                            
devu-omap3530.so                      
df                                    
dhcp.client                           
du                                    
fs-cifs                               
fs-nfs2                               
hogs                                  
ifconfig                              
inetd                                 
io-display                            
io-hid                                
io-pkt-v4                             
io-pkt-v4-hc                          
io-pkt-v6-hc                          
 libhiddi.so         
 libhiddi.so.1       
 nicinfo             
 pdebug              
 ping                
 qconn               
 route               
 stty                
 telnetd             
 vsync               


should I try to copy them to my other board?
Re: BeagleBoard RevC4 and D-Link E100  
I have just tried the exact same image on a RevC3 board and then network is working fine.
but not on the RevC4

one difference between the two is the UBoot version that is used and also the following
RevC3
In:    serial usbtty 
Out:   serial usbtty 
Err:   serial usbtty 

RevC4
In:    serial
Out:   serial
Err:   serial

but I did not succeed to change it with the setenv command.
Attachment: Text revc3.env 4.12 KB
Re: BeagleBoard RevC4 and D-Link E100  
RevC4 uBoot environment.
Attachment: Text revc4.env 3.89 KB
Re: BeagleBoard RevC4 and D-Link E100  
I have found a solution. instead of running network.sh during boot time I do the following.

once th boot is finished and logged in as root
I unplug/plug my ethernet dongle and then run network.sh and then I have an IP@

here is my network.sh 

echo Waiting 5 seconds before starting network stack.
sleep 5
io-pkt-v4 -d asix -p tcpip
waitfor /dev/io-net/en0
dhcp.client


so my question now is why does it work once the boot is finished and not during boot.
do I need to wiat something due to OTG initialization or so?