Tool/software:
I'm finding STRAP7 pulled to 1 is setting phy address 0, to 1, not 0.
Additionally, the PHY_ID is returning 0x2000a110, not 0x2000a136.
Why does the datasheet appear to be incorrect? Could someone please verify?
Thanks
Tool/software:
I'm finding STRAP7 pulled to 1 is setting phy address 0, to 1, not 0.
Additionally, the PHY_ID is returning 0x2000a110, not 0x2000a136.
Why does the datasheet appear to be incorrect? Could someone please verify?
Thanks
Hi,
I'm finding STRAP7 pulled to 1 is setting phy address 0, to 1, not 0. -> This is a typo on our part, I am working on update the 826A datasheet to correct this mistake.
Additionally, the PHY_ID is returning 0x2000a110, not 0x2000a136. -> Can you please share the top marking of the part? I want to make sure we do have the latest 826A silicon.
Thanks
David
Hi,
Thanks for the info. I requested some 826AE parts and let me test them on my board.
Thanks
David
Hi,
I checked and the correct PHY_ID for 826A is 0x2000A134. Are you reading 0x2000a110 from multiple units?
Thanks
David
Hi David, yes, each of the boards reports that number.
I noticed the PHY_ID table has a mask with each number, 0xfffffff0, so I suppose it's ignoring the bottom 4 bits, but then I'd still expect 0x2000A130, not 0x2000a110.
Hi David,
Could I just ship you one of the chips?
As a sanity check, I ran mdio tools to dump the info, it's 0x2000a114 on our boards.
mdio 8000f00.mdio phy 0
BMCR(0x00): 0x3000
flags: -reset -loopback +aneg-enable -power-down -isolate -aneg-restart
-collision-test
speed: 100-half
BMSR(0x01): 0x7849
capabilities: -100-t4 +100-tx-f +100-tx-h +10-t-f +10-t-h -100-t2-f -100-t2-h
flags: -ext-status -aneg-complete -remote-fault +aneg-capable -link
-jabber +ext-register
ID(0x02/0x03): 0x2000a114
Hi,
I read the PHY ID again on the DP83826A EVM, and below are the return values.
Can you please accept my friendship request so I can send you my mailing address?
Thanks
David