Activating network during start

Sascha Hauer s.hauer at
Thu Nov 20 23:11:16 PST 2014

Hi Holger,

On Thu, Nov 20, 2014 at 08:50:17PM +0000, Holger Freyther wrote:
> Good Evening,
> I wrote a small command to send a LLDP frame over the network. Then I
> tried to integrate this command into the start script but I noticed that
> while a message is printed on the console no actual packet is being
> sent on the wire.
> I am using a Phytec AM335X SoM and I am not on the latest version of
> barebox either so this might be something that is already fixed.
> My assumption is that when I use eth_get_current/eth_send the network
> is being activated. I had a quick look at the return code of eth_send
> to see if I could see that my packet has been dropped but in both
> success/failure the method returns 0. Is this to be expected? My
> interim solution is to add a sleep after the first command invocation
> and then do it again?

I don't understand what the exact problem is. So your command generally
works, only when it's called from the start script it doesn't work. Did
I get that correctly? Also a second invocation of the command then
works, right?
This sounds like the phy is not yet ready. I often get the impression
that the very first packet sent to the network is lost, even though the
phy registers tell us the phy is ready. I never found out what the
problem is here.


Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 |  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

More information about the barebox mailing list