Hi All.
I had downloaded the linux demo, provide by Atmel(9260_linux_demo), to my own 9260 board.The linux start successfully, however, when input ifconfig -a in the shell, it shows only one loopback device there, that is to say, the DM9161 is unrecognized in Linux, right?
In u-boot, after set the env values: ipaddr, serveraddr, netmask, ethaddr, the PING command under u-boot can reach the other PC on the net(... is alive), but after starting the Linux, there is no eth0 found.
Does anybody who know something about this?
Thanks!

I remember that in the ".bin" demo the ethernet driver is not compiled. So eth0 doesn't work. If you want use this interface you must make your own image.

Sorry Im totally new to all this.

How do you create an image?...And of what?

Hi there

The 2.6.19 kernel from TimeSys for the at91sam9260 does have Ethernet configured, but networking may not be enabled on boot.

With U-Boot 1.1.5_atmel_1.2 the number 1 rule to remember is to make the Ethernet connection _before_ the board is booted. U-Boot only performs a full initialization of the Ethernet device when it finds a good Ethernet connection; a connection to a switch is sufficient, but not a hub by itself.

IIRC the MAC address would only be setup in the PHY on a boot, so after you type 'setenv ethaddr xxxxxx', you need to save this using the saveenv command in U-Boot. Then reboot. If you start Linux w/o this step, the MAC address (ethaddr) seems to be defined in U-Boot, but this info does not get passed on to the kernel.

Once the kernel starts, you have to use the shell command 'ifconfig eth0 xxx.xxx.xxx.xxx' to set the IP address and activate the port. This info can also be passed by U-Boot to the kernel in the startup command line.

Regards

Cheers blue_z,

But Im still getting the following error:

# ifconfig eth0 192.168.1.37
Out: serial
SIOCSIFADDR: No such device
DM9161A PHY Detect
# ifconfig eth0 192.168.1.36k
MAC: error during R
SIOCSIFADDR: No such device

Any ideas?

Hi there

Is Ethernet working in U-Boot?
The 9260 port of Linux is dependant on U-Boot for a bunch of hardware initialization. So if critical HW functions are not setup properly by U-Boot, there's no chance you're going to get it working in the kernel.

Which kernel version are you using?

Regards

i have the same problem ..but i found the following error when booting the kernel ..

Davicom DM9161A: Registered new driver
PPP generic driver version 2.4.2
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (3a:1f:34:08:54:54)
eth0: attached PHY driver [Davicom DM9161A] (mii_bus:phy_addr=ffffffff:00, irq=-1)

is there an problem with the linux driver ? ..any himts or tips ??

Linux version 2.6.22.1 (root@vienna.rdcs.at) (gcc version 4.2.1) #3 Wed Jan 23 17:09:28 CET 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Atmel AT91SAM9260-EK


my linux version ..with buildroot ..


thanks
Wolfgang

My EK board came from the factory set up for RMII, not MII. Maybe the driver does not support the MII interface??