Linux/DP83867IS: DP83867IS strap register read issue

Thejas KU68

Part Number: DP83867IS

Tool/software: Linux

We have configured strap register to PHY addres 4. But when reading those strap configuration register from uboot we are getting 0x00.Also tried 'dhcp' command from uboot to get ipaddr and this is the output

=>dhcp                    
Trying FM1@DTSEC4
 memac_set_interface_mode, if_mode = 5006
 memac_set_interface_mode, if_status = b000
BOOTP broadcast 1
DHCPHandler: got packet: (src=68, dst=67, len=300) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=67, dst=68, len=300) state: 3
Filtering pkt = -6
DHCPHandler: got packet: (src=1534, dst=1534, len=8) state: 3
Filtering pkt = -1
BOOTP broadcast 2
DHCPHandler: got packet: (src=137, dst=137, len=50) state: 3
Filtering pkt = -1
BOOTP broadcast 3
DHCPHandler: got packet: (src=137, dst=137, len=50) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=138, dst=138, len=202) state: 3
Filtering pkt = -1
BOOTP broadcast 4
DHCPHandler: got packet: (src=137, dst=137, len=50) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=1534, dst=1534, len=8) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=68, dst=67, len=300) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=67, dst=68, len=300) state: 3
Filtering pkt = -6
BOOTP broadcast 5
FM1@DTSEC4: Tx error, txbd->status = 0x8800
DHCPHandler: got packet: (src=138, dst=138, len=202) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=49154, dst=1947, len=40) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=68, dst=67, len=300) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=67, dst=68, len=300) state: 3
Filtering pkt = -6
DHCPHandler: got packet: (src=138, dst=138, len=202) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=62205, dst=1947, len=40) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=62206, dst=1947, len=40) state: 3
Filtering pkt = -1
BOOTP broadcast 6
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
DHCPHandler: got packet: (src=68, dst=67, len=300) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=67, dst=68, len=300) state: 3
Filtering pkt = -6
DHCPHandler: got packet: (src=60220, dst=1947, len=40) state: 3
Filtering pkt = -1
BOOTP broadcast 7
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
DHCPHandler: got packet: (src=1534, dst=1534, len=8) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=137, dst=137, len=50) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=137, dst=137, len=50) state: 3
Filtering pkt = -1
BOOTP broadcast 8
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
DHCPHandler: got packet: (src=137, dst=137, len=50) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=1534, dst=1534, len=8) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=60220, dst=1947, len=40) state: 3
Filtering pkt = -1
BOOTP broadcast 9
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
DHCPHandler: got packet: (src=17500, dst=17500, len=133) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=1534, dst=1534, len=8) state: 3
Filtering pkt = -1
BOOTP broadcast 10
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
DHCPHandler: got packet: (src=62209, dst=1947, len=40) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=62210, dst=1947, len=40) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=68, dst=67, len=300) state: 3
Filtering pkt = -1
BOOTP broadcast 11
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
BOOTP broadcast 12
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
DHCPHandler: got packet: (src=55095, dst=4920, len=1) state: 3
Filtering pkt = -1
BOOTP broadcast 13
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
BOOTP broadcast 14
FM1@DTSEC4: Tx buffer not ready, txbd->status = 0x8800
DHCPHandler: got packet: (src=57576, dst=4920, len=1) state: 3
Filtering pkt = -1
DHCPHandler: got packet: (src=1534, dst=1534, len=8) state: 3
Filtering pkt = -1

Retry time exceeded; starting again
Command failed, result=1

And mdio list command responds

=> mdio list
FSL_MDIO0:
4 - TI DP83867 <--> FM1@DTSEC4
FM_TGEC_MDIO:
1 - Generic 10G PHY <--> FM1@TGEC1

any idea whats going wrong?

thanks in advance!

over 7 years ago

0 Rob Rodrigues over 7 years ago

TI__Mastermind 19780 points

Hi Thejas,

Can you provide a schematic capture of your PHY? I suspect an issue with your strapping. Either the address is incorrect, or the GPIO lines are strapped into an N/A mode causing the MDIO of the DP83867IS to not respond.

Best Regards,

0 Thejas KU68 over 7 years ago in reply to Rob Rodrigues

Prodigy 40 points

Hi ,thank you for the quick responds. Please find attachment for PHY schematicsthread schem.pdf

0 Thejas KU68 over 7 years ago in reply to Rob Rodrigues

Prodigy 40 points

5340.thread schem.pdfplease see the attachment

0 Rob Rodrigues over 7 years ago in reply to Thejas KU68

TI__Mastermind 19780 points

Hi Thejas,

Are you having problems reading all registers? Or are you only having problems reading register 0x6E?

From your schematic, the RXCTL strap, R192 & R193 must be changed to mode 3. If you do not do this, you may not have a stable link using the DP83867.

If you can access register 0x0, or 0x2, but not register 0x6e, then you should follow the extended register access method shown in the DP83867 datasheet.

If you cannot access ANY registers, probe the MDIO line and see if the PHY is holding the MDIO line at some intermediate voltage. if that is the case, then the GPIO_0 line is probably being held high during reset by the processor. If GPIO_0 is held high, mode 4, the PHY's MDIO will not be operational.

Best Regards,

Interface

Interface forum

Linux/DP83867IS: DP83867IS strap register read issue