[U-Boot-Users] Teridian Phy Support tr78q21x3

Manuel Sahm Manuel.Sahm at feig.de
Wed Jun 18 09:39:05 CEST 2008


Hello,

I found out, why the Generic MACB MII driver for the AT91SAM9260 doesn´t 
work.

The problem is inside the file

/board/atmel/at91sam9260ek/at91sam9260ek.c


at91_set_B_periph(AT91_PIN_PA23, 0);   //ETX2
at91_set_B_periph(AT91_PIN_PA24, 0);   //ETX3

These lines are multiplexed with the TWI Interface of the AT91SAM9260 
and on the development board (AT91SAM9260EK) there is an EEPROM connected.
Instead of lines PA23 and PA24 you have to use

at91_set_B_periph(AT91_PIN_PA10, 0);   //ETX2
at91_set_B_periph(AT91_PIN_PA11, 0);   //ETX3

which have the same abilites.

Then it works perfect !!!!!


Is it possible to change this in the official U-Boot tree ?

Hopefully someone from denx.de could do that and I hope for a positive 
reply - Thank you


Anatolij Gustschin schrieb:
> 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
>
>   




More information about the U-Boot mailing list