• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 32 subscribers
  • Views 306 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Linux/DP83848T: About Design Check and ping failed issue

yimin bai34
Genius 4755 points
Part Number: DP83848T
Other Parts Discussed in Thread: AM3352

Tool/software: Linux

Hi Sir 

We used AM3352 with DP83848T for design. And we would like to use Ethernet port for ping IP.

DP83848T is set as RMII mode and the connection between CPU and DP83848T is correct.

When we execute ping command and it always failed. 

we have measured some signal and need your suggestion as below

      a. we measure PFBOUT/ RBIAS pin and the voltage is  1.76V

      b.RESET_N(Pin23) is 3.0V

      c. RX_DV/MII_MODE (pin 39) pulled up to 3.3v --> configured as RMII mode

      d. AVD33 (pin18), IOVDD33(pin1, 26) - 3.3v

      e. X1 (pin 28) - 50 Mhz from osc

      f. MDC (pin 25)  - 1.0Mhz~1.9Mhz -> please help confirm this vfrequency is ok or not.

      g. COL/PHYAD0(Pin35) -> we have pull up this pin to 3.3V using a 2.2K resistor .

           At bootup status, this pin bring up from 0V to 3.3V sometimes. After entering system, the level of COL/PHYAD0 keep low.

          please help to confirm the status is ok or not. 

Thanks for your suggestion

BR

Yimin 

 


 

  • 0
    Genius 4755 points
    Hi SIr

    the auto-negotiation is always failed and below is the register value.

    please advise

    => mii read 1 0x00
    3100
    => mii read 1 0x01
    7849
    => mii read 1 0x02
    2000
    => mii read 1 0x03
    5C90
    => mii read 1 0x04
    01E1
    => mii read 1 0x05
    0000
    => mii read 1 0x06
    0007
    => mii read 1 0x07
    2801
    => mii read 1 0x10
    4100
    => mii read 1 0x14
    0000
    => mii read 1 0x15
    0000
    => mii read 1 0x16
    0100
    => mii read 1 0x17
    0021
    => mii read 1 0x18
    0000
    => mii read 1 0x19
    8001
    => mii read 1 0x1a
    0904
    => mii read 1 0x1b
    0000
    => mii read 1 0x1d
    6011
  • 0 in reply to yimin bai34
    TI__Expert 5670 points
    Hi Yimin,

    It looks like the DP83848T does not have the link with the link partner. Which link partner do you connect DP83848T to?

    To check for the link status, read register 0x1, bit 2 or register 0x10, bit 0.

    Regards,

    Hung Nguyen
  • 0 in reply to Hung Nguyen92
    Genius 4755 points
    Hi SIr

    => mii dump 1 0x00
    0. (3100) -- PHY control register --
    (8000:0000) 0.15 = 0 reset
    (4000:0000) 0.14 = 0 loopback
    (2040:2000) 0. 6,13 = b01 speed selection = 100 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:0100) 0. 8 = 1 duplex = full
    (0080:0000) 0. 7 = 0 collision test enable
    (003f:0000) 0. 5- 0 = 0 (reserved)

    => mii dump 1 0x01
    1. (7849) -- PHY status register --
    (8000:0000) 1.15 = 0 100BASE-T4 able
    (4000:4000) 1.14 = 1 100BASE-X full duplex able
    (2000:2000) 1.13 = 1 100BASE-X half duplex able
    (1000:1000) 1.12 = 1 10 Mbps full duplex able
    (0800:0800) 1.11 = 1 10 Mbps half duplex able
    (0400:0000) 1.10 = 0 100BASE-T2 full duplex able
    (0200:0000) 1. 9 = 0 100BASE-T2 half duplex able
    (0100:0000) 1. 8 = 0 extended status
    (0080:0000) 1. 7 = 0 (reserved)
    (0040:0040) 1. 6 = 1 MF preamble suppression
    (0020:0000) 1. 5 = 0 A/N complete
    (0010:0000) 1. 4 = 0 remote fault
    (0008:0008) 1. 3 = 1 A/N able
    (0004:0000) 1. 2 = 0 link status
    (0002:0000) 1. 1 = 0 jabber detect
    (0001:0001) 1. 0 = 1 extended capabilities

    => mii dump 1 0x17
    1. (7849) -- PHY status register --
    (8000:0000) 1.15 = 0 100BASE-T4 able
    (4000:4000) 1.14 = 1 100BASE-X full duplex able
    (2000:2000) 1.13 = 1 100BASE-X half duplex able
    (1000:1000) 1.12 = 1 10 Mbps full duplex able
    (0800:0800) 1.11 = 1 10 Mbps half duplex able
    (0400:0000) 1.10 = 0 100BASE-T2 full duplex able
    (0200:0000) 1. 9 = 0 100BASE-T2 half duplex able
    (0100:0000) 1. 8 = 0 extended status
    (0080:0000) 1. 7 = 0 (reserved)
    (0040:0040) 1. 6 = 1 MF preamble suppression
    (0020:0000) 1. 5 = 0 A/N complete
    (0010:0000) 1. 4 = 0 remote fault
    (0008:0008) 1. 3 = 1 A/N able
    (0004:0000) 1. 2 = 0 link status
    (0002:0000) 1. 1 = 0 jabber detect
    (0001:0001) 1. 0 = 1 extended capabilities
  • 0 in reply to yimin bai34
    TI__Expert 5670 points
    Hi,

    Which link partner you use to connect to DP83848?

    Can you provide the schematic for DP83848 connectivity?

    Regards,

    Hung Nguyen
  • 0 in reply to Hung Nguyen92
    Genius 4755 points
    Hi Sir

    thanks for your great support.

    This issue is fixed due to HW issue

    BR
    Yimin
  • 0 in reply to Hung Nguyen92
    Genius 4755 points
    Issue is fixed due to HW issue