DM355 ethernet issue

Gerald Jackson gerald.jackson at reaonixsecurity.com
Tue Sep 16 11:52:41 CDT 2008


Phil,

I am very interested to see what you did in the script, if possible can you send it to the list or me?

Thanks,
Gerald
________________________________
From: davinci-linux-open-source-bounces at linux.davincidsp.com [davinci-linux-open-source-bounces at linux.davincidsp.com] On Behalf Of Phil Quiney [PQuiney at trinityconvergence.com]
Sent: Tuesday, September 16, 2008 10:47 AM
To: Maupin, Chase; davinci-linux-open-source
Subject: RE: DM355 ethernet issue

Hi Chase,

I have resolved the problem ;-)

Basically switching to the busybox 'udhcpc'  allows the board to start with the cable removed.

It isn't a simple change to get it to work as the 'default' default.script udhcpc runs to handle interface 'events' that is in the root filesystem is no good (known working script substituted) and the -p option for PID cache does not work either (resulting in some grepping for process ID on network shutdown rather than using the PID in the file). Also the 'ifup' config file has no way to pass options to 'udhcpc' so I had to investigate a 'manual' definition that called udhcpc as an external 'method' with the required options.

So now if I boot with the cable not present I get (the output of which takes around 3 secs)....

Starting network interfaces: eth0: link down
udhcpc (v1.6.0) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
...& the board continues to start up as normal.

Upon plugging in the cable the kernel prints out a 'link up' message and becuase udhcpc is running in the background it eventually gets an IP address.

Now to prise a DM6446 out of a developer's hands to see if the same changes work there as well...

Regards

Phil Q

Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com<http://www.trinityconvergence.com/>


________________________________
From: Maupin, Chase [mailto:chase.maupin at ti.com]
Sent: 12 September 2008 15:59
To: Phil Quiney; davinci-linux-open-source
Subject: RE: DM355 ethernet issue

Phil,

If you do not need the ethernet then you can set ip=off on the bootargs.  If not then you can enable ethernet after boot I believe by doing “/etc/init.d/network restart”.  If you want to boot with ethernet enabled but no cable you can try removing the ethernet startup scripts to prevent trying to start the ethernet at boot.

Sincerely,
Chase Maupin
Software Applications
Catalog DSP Products
e-mail: chase.maupin at ti.com<mailto:chase.maupin at ti.com>
phone: (281) 274-3285
________________________________
From: davinci-linux-open-source-bounces+chase.maupin=ti.com at linux.davincidsp.com [mailto:davinci-linux-open-source-bounces+chase.maupin=ti.com at linux.davincidsp.com] On Behalf Of Phil Quiney
Sent: Friday, September 12, 2008 4:43 AM
To: davinci-linux-open-source
Subject: DM355 ethernet issue

Hi All,

We have noticed that if a DM355 is started with the ethernet cable unplugged, the boot hangs for a considerable time doing the 'ifup'.

The interface is configured with the following lines in /etc/network/interfaces...

auto eth0
iface eth0 inet dhcp
If the cable is plugged in after the board eventually starts, then nothing happens, you get no link light on the connector.

Does anybody know a way to fix this?

One of our customers reported this on a DM6446 so it looks like it is a common issue for both boards. I am going to try a DM6446 myself to confirm this.

Incidentally, I tried using netlink to see if the linkup/link down events are seen by the driver & passed to netlink. If you allow the DM355 to boot with the cable plugged in then start the netlink test program then the events are generated as the cable is unplugged and plugged in....

root@(none):~# ./netlink_test_dm355
Started watching:
eth0: link down
msg_handler: RTM_NEWLINK
netlink_link_state: Link Down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
msg_handler: RTM_NEWLINK
netlink_link_state: Link Up
This is a lot better than some boards we have tried ;-)

If you ping a host on the network & unplug the cable, then the transmission stops - we have seen all kinds of errors on the console on other boards when this is done. Plugging the cable back in restores operation as you would expect (but don't always get).

Regards

Phil Q

Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com<http://www.trinityconvergence.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20080916/199a57b9/attachment.htm


More information about the Davinci-linux-open-source mailing list