This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DP83848Q-Q1: ARP Retry count exceeded; starting again

Part Number: DP83848Q-Q1

Hi,

I am getting the below Error,

"ARP Retry count exceeded; starting again" in Uboot

I had configured the PHY control register 00H as 0x1000 (Only Auto-Negotiation Enabled) under this condition  ping is not working in uboot. and I had also configured PHY control register 00H as 0x5000(loopback and Auto-Negotiation Enabled) Under hardware loop back also i am getting the same error.

Please find the log below and do advice how to resolve
-------------------------------------------------------------------------------------
u-boot=> mii dump                                                              
0.     (ffff)                 -- PHY control register --                        
  (8000:8000) 0.15    =     1    reset                                          
  (4000:4000) 0.14    =     1    loopback                                      
  (2040:2040) 0. 6,13 =   b11    speed selection = 10 Mbps                      
  (1000:1000) 0.12    =     1    A/N enable                                    
  (0800:0800) 0.11    =     1    power-down                                    
  (0400:0400) 0.10    =     1    isolate                                        
  (0200:0200) 0. 9    =     1    restart A/N                                    
  (0100:0100) 0. 8    =     1    duplex = full                                  
  (0080:0080) 0. 7    =     1    collision test enable                          
  (003f:003f) 0. 5- 0 =    63    (reserved)                                    
                                                                               
                                                                               
u-boot=> mii write 3 0 0x5000                                                  
u-boot=> mii dump                                                              
0.     (5000)                 -- PHY control register --                        
  (8000:0000) 0.15    =     0    reset                                          
  (4000:4000) 0.14    =     1    loopback                                      
  (2040:0000) 0. 6,13 =   b00    speed selection = 10 Mbps                      
  (1000:1000) 0.12    =     1    A/N enable                                    
  (0800:0000) 0.11    =     0    power-down                                    
  (0400:0000) 0.10    =     0    isolate                                        
  (0200:0000) 0. 9    =     0    restart A/N                                    
  (0100:0000) 0. 8    =     0    duplex = half                                  
  (0080:0000) 0. 7    =     0    collision test enable                          
  (003f:0000) 0. 5- 0 =     0    (reserved)                                    

u-boot=> mdio list

FEC0:

3 - NatSemi DP83848 <--> ethernet@30be0000

 

u-boot=> mii read 0x3 0-6            

addr=03 reg=00 data=1000

addr=03 reg=01 data=786D

addr=03 reg=02 data=2000

addr=03 reg=03 data=5C90

addr=03 reg=04 data=01E1

addr=03 reg=05 data=CDE1

addr=03 reg=06 data=000F                                                                             
                                                                               
u-boot=> printenv ipaddr                                                        
ipaddr=192.168.36.126                                                          
u-boot=> ping 192.168.36.126                                                    
LVDS: phy_startup                                                              
LVDS: genphy_update_link                                                        
Using ethernet@30be0000 device                                                  
                                                                               
ARP Retry count exceeded; starting again                                        
ping failed; host 192.168.36.126 is not alive                                  

-------------------------------------------------------------------------

Regards

Santhosh

  • Hi Santhosh,

    Have you confirmed your layout of your design and components fit our guidelines outlined in our app note? 

    http://www.ti.com/lit/an/snla079d/snla079d.pdf

    Thanks,

    Cecilia

  • Cecilia,

    Yes its been verified and all the guidelines are taken care and the same is verified by TI team

    Right now we checked with the scope on the processor TX/RX line and we are not seeing any data on the line. Any thing we can test


    Regards

    Santhosh

  • Hi Santhosh,

    I am unfamiliar with using uBoot for configurations however have you confirmed that both processor and PHY are set to the same interface?

    Are you able to see the clock line or any other data lines?

    Thanks,

    Cecilia

  • Hi Cecilia,

    Yes i have checked theTXD/RXD line and i dont see any data  on the scope

    In RMII Mode the TXC and RXC (clock lines ) are NC as per your TI document attached.

    We did an experiment We connected the board to network switch and checked the RX received data on the Ethernet cable and TI PHY  IC input (The waveform is available at Ethernet connector and TI PHY IC RX input ) and when we check on the Out put RX pin of TI Phy we did not see the waveform (We removed connection between TI PHY IC RXD pin and Processor MAC RXD pin for this test)

    On X1 and MDC line we are able to see 50MHZ clock and on MDIO line also we are able to see the data in the scope also auto negotiation is also happening when Ethernet cable is connected. 

    For your quick check, I have read all the register of TI Phy IC using mii read command, Please find below

    u-boot=> mii read 0 0-1d
    addr=00 reg=00 data=3100
    addr=00 reg=01 data=786D
    addr=00 reg=02 data=2000
    addr=00 reg=03 data=5C90
    addr=00 reg=04 data=01E1
    addr=00 reg=05 data=CDE1
    addr=00 reg=06 data=000D
    addr=00 reg=07 data=2801
    addr=00 reg=08 data=0000
    addr=00 reg=09 data=0000
    addr=00 reg=0a data=0000
    addr=00 reg=0b data=0000
    addr=00 reg=0c data=0000
    addr=00 reg=0d data=0000
    addr=00 reg=0e data=0000
    addr=00 reg=0f data=0000
    addr=00 reg=10 data=0615
    addr=00 reg=11 data=0000
    addr=00 reg=12 data=0000
    addr=00 reg=13 data=0000
    addr=00 reg=14 data=0000
    addr=00 reg=15 data=0000
    addr=00 reg=16 data=0100
    addr=00 reg=17 data=0021
    addr=00 reg=18 data=0000
    addr=00 reg=19 data=8020
    addr=00 reg=1a data=0904
    addr=00 reg=1b data=0000
    addr=00 reg=1c data=0000
    addr=00 reg=1d data=6011

      Do advice any further test or experiment you want us to do

    Regards

    Santhosh

    snla076a.pdf

  • Hi Santhosh,

    Are you testing your device in 100M or 10M speed? What are differences between the uboot dumps you sent in your initial question?

    I will have to reach out to our FW team to see if they have recommendations for you.

    Thanks,

    Cecilia