2008/10/29 Jerry Van Baren <[EMAIL PROTECTED]>:
> Simon Boman wrote:
>>
>> I added this code to the uec.c file:
>> int i;
>> for(i=0;i<20;i++)
>> printf("PHY value %d is %x\n", i, phy_read(uec->mii_info, i));
>>
>> and got this to the prompt..
>>
>> PHY value 0 is 0
>> PHY value 1 is 0
>> PHY value 2 is 0
>> PHY value 3 is 0
>> PHY value 4 is 0
>> PHY value 5 is 0
>> PHY value 6 is 0
>> PHY value 7 is 0
>> PHY value 8 is 0
>> PHY value 9 is 0
>> PHY value 10 is 0
>> PHY value 11 is 0
>> PHY value 12 is 0
>> PHY value 13 is 0
>> PHY value 14 is 0
>> PHY value 15 is 0
>> PHY value 16 is 0
>> PHY value 17 is 0
>> PHY value 18 is 0
>> PHY value 19 is 0
>
> Please don't top post.
>
> I think you first need to *find* your phy. This is likely a
> hardware/software issue: I/O lines, I/O configuration, PHY address
> strapping.
>
> I wasn't advocating adding code to print PHY registers, I was advocating
> using the "mii" command: "help mii". If it isn't in your build, add it.
> Then do "mii device", IIRC, it will scan the MII bus to see who is out
> there. That will identify mis-strapped (or misunderstood strapping) PHY
> address strapping. If nobody answers the call, you likely have a I/O pin
> misconfiguration or a more serious hardware problem.
>
> gvb
I'm sorry, and thank you for your quick reply!
I have now figured out that MDIO uses the SPI2-bus and what I can see
U-boot does'nt support that. If it is, I will really appreciate if you
tell me how to use it.
/Simon
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
