Stefano,
Paulraj, Sandeep wrote:
Ben,
Hi,
When the board comes after I reflash with a new U-boot image, I no longer see the ethaddr being set. But when I do a tftp I can see the ethaddr being read. tftp complains and says no ethaddr set.
Not sure, but it seems that the mac address is read from the eeprom connected to the DM9000 and it is not used again. I see that the mac address is copied into the environment variable, but is is not copied to the dev structure.
Could you give the following simple patch a try ?
Regards, Stefano
Thanks for your patch. I tried an image with your patch The issues still persists.
I am wondering if any other board using this driver is facing this issue. To me it seems to be generic to the DM9000.
It does not exist on the EMAC driver for DM355.
I meant EMAC driver for DM365. Obviously Dm355 does not have both DM9000 and EMAC :-)
dhcp works just fine. I meant on the DM365. dhcp does not work on DM355. It just times out.
Thanks, Sandeep