Hello!

I have a custom board with at91sam9x25 mc. I have a problem with receiving ethernet packets. From u boot i tried to ping another host , arp packets goes from atmel but when my host answer, atmel do not see it, and then retransmit the packet. the same situation with dhcp requests. with my oscilloscope I check all MII pins, everything looks fine, including receiving packets. I view some signal changing on RX pins of PHY ethernet. Then i launch linux kernel 2.6.39 , i have not rootfs yet, because of flash size restriction, but in kernel config i setup ip self-configuring option, that enables getting ip address through dhcp while loading and again the same situation sending but could not receive.
U boot , kernel I configured with at91sam9x5 configs. Could it be same differences between sam9x25 and sam9x5 that lead such problem? they all from one die family.

Thanks!

As no one here is familiar with your custom board, perhaps you should start by explaining how your board deviates from the AT91SAM9X25-EK reference design both in wiring, layout and components, and what software changes you have made to accommodate these differences, if any.

Have you replicated the offending behaviour on an AT91SAM9X25-EK board?

We are seeing the same issue you are with a 9G25 design using the MII interface for ethernet. Turns out there is an error in the "u-boot-5series_1.0.patch" file in the MII section of the at91sam9x5devices.c file. The MII only pins are being assigned to peripheral B, but are actually on peripheral A in the at91sam9x5 series, (or at least the 9G25 we use). Once we changes the calls to periph_a, our ethernet MII interface started working correctly. Since the EK boards don't have a MII option, I bet the patch code was never verified. I also suspect the same issue for the Linux patch code, but have not verified it yet.