
Hello,
Manuel Sahm wrote:
In the U-Boot 1.3.3 there is already this patch included....
yes, of course this is already included. I meant you have to _reverse_ this patch (or in other words un-apply it, "patch -p1 -R"), as it was not included in U-Boot 1.3.0 and as you sad, with U-Boot 1.3.0 ethernet did work. Un-applying this patch and test without it could quickly show if MII mode configuration was your problem.
But I see another problem:
I uses the AT91SAM9260 microcontroller so I defined in the header:
#define CONFIG_AT91SAM9260 1
Instead of the Davicom Phy (RMII), which is used in the DevBoard AT91SAM9260EK I want to use the Teridian Phy(MII), so I write in the header:
#undef CONFIG_RMII
Now have a look at the patch:
+#if defined(CONFIG_AT91CAP9) || defined(CONFIG_AT91SAM9260) || \
- defined(CONFIG_AT91SAM9263)
- macb_writel(macb, USRIO, MACB_BIT(CLKEN));
#else macb_writel(macb, USRIO, MACB_BIT(MII)); #endif
I don“t go to the line : macb_writel(macb, USRIO, MACB_BIT(MII)); ,because of CONFIG_AT91SAM9260
BUT I have to go there or not ?
Probably. If you un-apply the patch, you end up in something like this:
#ifdef CONFIG_RMII macb_writel(macb, USRIO, 0); #else macb_writel(macb, USRIO, MACB_BIT(MII)); #endif
and this is the macb.c code in U-Boot-1.3.0 (drivers/macb.c:419).
Best regards, Anatolij