[U-Boot] Link problem with eTSEC2 on P2020RDB

[Felix Radensky <felix@embedded-sol.com>]

  Hi Peter,

On 6/26/2010 4:19 PM, Peter Tyser wrote:
> Hi Felix,
>
> In any case, our testing and the Freescale FAE's input showed that
> in-band auto-negotiation on the SGMII interface didn't work, thus I
> submitted the change you referenced.  If my memory is correct,
> empirically it looked like the MPC8572 did support 1000 base-X
> auto-negotiation, but not SGMII auto-negotiation.  Can you validate
> you're using SGMII and not 1000 base-X to connect the P2020 to the
> VSC8211 PHY?  A simple way to test this should be to connect the VSC8211
> to a 100 mpbs switch - this should work fine via SGMII but not 1000
> base-X (assuming you're using a copper interface).

I'm definitely using SGMII with eTSEC2. This is documented in board user manual.
Also, eTSEC2 works when connected to 100 mbps switch.

>> I'm not familiar with how SGMII is configured on this controller, but
>> it appears that Peter's patch turned of Autonegotiation.  Why this
>> would make a PHY work and a switch not work is curious...  Maybe we
>> should have a CONFIG option for SGMII parameters.  Settings could
>> default to the ones Peter set (since he submitted it in November and
>> problems are surfacing now), but could be overriden.  Does that sound
>> reasonable?  Something like:
>>
>>
>> #ifndef CONFIG TSEC_TBICR_SETTINGS
>> #define TBICR_SETTINGS ( \
>>                  TBICR_PHY_RESET \
>>                  | TBICR_FULL_DUPLEX \
>>                  | TBICR_SPEED1_SET \
>>                  )
>> #else
>> #define TBICR_SETTINGS CONFIG_TSEC_TBICR_SETTINGS
>> #endif
>>          Thanks.
> This solution is fine by me.  I'd be curious if anyone at Freescale has
> a definitive answer about SGMII and auto-negotiation.  I'm happy to try
> any patch on Monday

I've posted a patch, see http://lists.denx.de/pipermail/u-boot/2010-June/073208.html

Can you please test it ?

Thanks.

Felix.