• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Subscribers 33 subscribers
  • Views 1802 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DP83822IF: Optical communication through SFP module

SANDEEP S
Prodigy 225 points
Part Number: DP83822IF
Other Parts Discussed in Thread: AM5728

Hi,

We are using DP83822IFRHBR for fiber optic communication. Which SFP modules are to be used with DP83822 ?

We tried with 100 base FX SFP on both ends. ie Processor side and Ethernet switch (GE reason S20).

But the communication is not success. Also tried with 1G multimode SFP, then also we cant communicate.

The fiber optic communication is successfull only when we tried with MOXA PT7710 switch, which has AFBR optical interface.

Can you suggest any  SFP modules compatible with DP83822IFRHBR.

Thanks and regards

Sandeep S

  • 0
    TI__Mastermind 24988 points

    Hi Sandeep,

    When you are connecting to the MOXA PT7710, which SFP module are you using on the PHY-side? Do you have the exact model of the SFP module on the switch-side?

    Also, please see this FAQ for fiber link status adjustment. I expect all 100Base-FX standard SFP modules to work for this, given both end-points are using identical models.

    Thank you,

    Evan

  • 0 in reply to Evan Mayhew
    Prodigy 225 points

    Hi Evan,

    I tried with SFPs Part No. is listed below. Photos also attaching here.

    1. AXCEN - AXFD-1314-0W23 : SFP-100FX-DD-IT-CL

    2. IHT - SF13G40 - 1.25G SFP 1310NM Dual Fiber 40 KM DDM - Single mode SFP

    3. Juniper Networks - Finisar FTLF8519P3BNL-J1 - 1G multi mode SFP

    Test Conditions are listed below.

    Test 1. PC     --to-     Reason S20 switch with AXCEN - AXFD-1314-0W23   --to--      MMF  --to--  MOXA PT7710  --to--   IHT - SF13G40 connected with our DP83822IF board.

    In this test condition we are able to communicate with PC. We are able to ping on both sides

    Test 2. PC --to-- Reason S20 switch with AXCEN - AXFD-1314-0W23   --to-- MMF --to--    AXCEN - AXFD-1314-0W23 connected with our DP83822IF board.

    In this test,  we are unable to ping with S20 switch or PC on both sides.

    3. PC --to-- Reason S20 switch with Finisar FTLF8519P3BNL-J1 --to-- MMF --to-- Finisar FTLF8519P3BNL-J1 connected with our DP83822IF board.

    In this test,  we are unable to ping with S20 switch or PC on both sides.

    Thanks and regards
    Sandeep S

  • 0 in reply to SANDEEP S
    TI__Mastermind 24988 points

    Hi Sandeep,

    Please share the schematic so I may review the connections (email to e-mayhew@ti.com for private share).

    Thank you,

    Evan

  • 0 in reply to Evan Mayhew
    Prodigy 225 points

    Hi Evan,

    I am attaching the schematic diagram here. We are using MitySOM AM5728 SOM

    https://www.criticallink.com/product/mitysom-am57f/ . We are using both RJ45 and SFP with DP83822IF, now RJ45 is isolated from the circuit.

    R101,R105,R254,R258 is not populated.

    PLED_LINK_S_E, PLED_ACT_S_E connected with RJ45 LED signal

     

    Thanks and regards

    Sandeep S

  • 0 in reply to SANDEEP S
    TI__Mastermind 24988 points

    Hi Sandeep,

    Thanks for sharing the schematic - I see no issues in the pinout that would cause the problem you are seeing.

    Please share a register dump in the failing ping case from addresses 0x0 to 0x1F so I may confirm the device configuration and LP advertisements.

    There are a couple tests I would like to check with you:

    1) For failing case with both DP83822 and AM5728, disable auto-negotiation and force 100Mbps on both end-points.

    2) For same failing case, write 0x1F = 0x4000 to soft reset the PHY.

    Do you see any difference in ping for these tests?

    Thank you,

    Evan

  • 0 in reply to Evan Mayhew
    Prodigy 225 points

    Hi Evan,

    register dump in the failing ping case is

    root@mitysom-am57x:~# phytool read eth0/0/0
    0x2100
    root@mitysom-am57x:~# phytool read eth0/0/1
    0x784d
    root@mitysom-am57x:~# phytool read eth0/0/2
    0x2000
    root@mitysom-am57x:~# phytool read eth0/0/3
    0xa240
    root@mitysom-am57x:~# phytool read eth0/0/4
    0x0101
    root@mitysom-am57x:~# phytool read eth0/0/5
    0000
    root@mitysom-am57x:~# phytool read eth0/0/6
    0x0004
    root@mitysom-am57x:~# phytool read eth0/0/7
    0x2001
    root@mitysom-am57x:~# phytool read eth0/0/8
    0000
    root@mitysom-am57x:~# phytool read eth0/0/9
    0000
    root@mitysom-am57x:~# phytool read eth0/0/10
    0x4100
    root@mitysom-am57x:~# phytool read eth0/0/11
    0x1000
    root@mitysom-am57x:~# phytool read eth0/0/12
    0000
    root@mitysom-am57x:~# phytool read eth0/0/13
    0000
    root@mitysom-am57x:~# phytool read eth0/0/14
    0000
    root@mitysom-am57x:~# phytool read eth0/0/15
    0000
    root@mitysom-am57x:~# phytool read eth0/0/16
    0x2805
    root@mitysom-am57x:~# phytool read eth0/0/17
    0x0108
    root@mitysom-am57x:~# phytool read eth0/0/18
    0xa300
    root@mitysom-am57x:~# phytool read eth0/0/19
    0000
    root@mitysom-am57x:~# phytool read eth0/0/20
    0x00ff
    root@mitysom-am57x:~# phytool read eth0/0/21
    0xffff
    root@mitysom-am57x:~# phytool read eth0/0/22
    0x0100
    root@mitysom-am57x:~# phytool read eth0/0/23
    0x0049
    root@mitysom-am57x:~# phytool read eth0/0/24
    0x0400
    root@mitysom-am57x:~# phytool read eth0/0/25
    0x8020
    root@mitysom-am57x:~# phytool read eth0/0/26
    0000
    root@mitysom-am57x:~# phytool read eth0/0/27
    0x007d
    root@mitysom-am57x:~# phytool read eth0/0/28
    0x05ee
    root@mitysom-am57x:~# phytool read eth0/0/29
    0000
    root@mitysom-am57x:~# phytool read eth0/0/30
    0x0002
    root@mitysom-am57x:~# phytool read eth0/0/31
    0000

    There are a couple tests I would like to check with you:

    1) For failing case with both DP83822 and AM5728, disable auto-negotiation and force 100Mbps on both end-points.

    2) For same failing case, write 0x1F = 0x4000 to soft reset the PHY.

    1). Here both end-points means AM5728 board and ethernet switch na..?

    2.) tried writing 0x1F = 0x4000 . but no change .

    Thanks and regards

    Sandeep S

  • 0 in reply to SANDEEP S
    TI__Mastermind 24988 points

    Hi Sandeep,

    This register log looks good to me, link is up and the speed is set correctly with fiber enabled. 

    Please confirm, is this the failing setup for ping:

    (AM5728 <-> DP83822) - Fiber - (DP83822 <-> AM5728)

    If so, please confirm that both DP83822 have auto-negotiation disabled and 100M speed forced.

    Can you also share the register log in the working case while connected to PT7710 switch?

    Thank you,

    Evan

  • 0 in reply to Evan Mayhew
    Prodigy 225 points

    Hi Evan,

    Does DP83822IF support both multimode and single mode SFP module?

    Please confirm, is this the failing setup for ping:

    (AM5728 <-> DP83822) - Fiber - (DP83822 <-> AM5728)

    No..

    failing setup for ping is AM5728 <-> DP83822IF <-> Fiber <-> GE reason S20 switch <-> RJ45 cable <-> PC

    In the DP83822 have auto-negotiation disabled and 100M speed

    Can you also share the register log in the working case while connected to PT7710 switch?

    root@mitysom-am57x:~# phytool read eth0/0/0
    0x2100
    root@mitysom-am57x:~# phytool read eth0/0/1
    0x784d
    root@mitysom-am57x:~# phytool read eth0/0/2
    0x2000
    root@mitysom-am57x:~# phytool read eth0/0/3
    0xa240
    root@mitysom-am57x:~# phytool read eth0/0/4
    0x0101
    root@mitysom-am57x:~# phytool read eth0/0/5
    0000
    root@mitysom-am57x:~# phytool read eth0/0/6
    0x0004
    root@mitysom-am57x:~# phytool read eth0/0/7
    0x2001
    root@mitysom-am57x:~# phytool read eth0/0/8
    0000
    root@mitysom-am57x:~# phytool read eth0/0/9
    0000
    root@mitysom-am57x:~# phytool read eth0/0/10
    0x4100
    root@mitysom-am57x:~# phytool read eth0/0/11
    0x1000
    root@mitysom-am57x:~# phytool read eth0/0/12
    0000
    root@mitysom-am57x:~# phytool read eth0/0/13
    0000
    root@mitysom-am57x:~# phytool read eth0/0/14
    0000
    root@mitysom-am57x:~# phytool read eth0/0/15
    0000
    root@mitysom-am57x:~# phytool read eth0/0/16
    0x2805
    root@mitysom-am57x:~# phytool read eth0/0/17
    0x0108
    root@mitysom-am57x:~# phytool read eth0/0/18
    0xa300
    root@mitysom-am57x:~# phytool read eth0/0/19
    0000
    root@mitysom-am57x:~# phytool read eth0/0/20
    0000
    root@mitysom-am57x:~# phytool read eth0/0/21
    0xffff
    root@mitysom-am57x:~# phytool read eth0/0/22
    0x0100
    root@mitysom-am57x:~# phytool read eth0/0/23
    0x0049
    root@mitysom-am57x:~# phytool read eth0/0/24
    0x0400
    root@mitysom-am57x:~# phytool read eth0/0/25
    0x8020
    root@mitysom-am57x:~# phytool read eth0/0/26
    0000
    root@mitysom-am57x:~# phytool read eth0/0/27
    0x007d
    root@mitysom-am57x:~# phytool read eth0/0/28
    0x05ee
    root@mitysom-am57x:~# phytool read eth0/0/29
    0000
    root@mitysom-am57x:~# phytool read eth0/0/30
    0x0002
    root@mitysom-am57x:~# phytool read eth0/0/31
    0000

    For the below case we used SFP module AXCEN - AXFD-1314-0W23 - 100Fx 1310nm. Here also ping is not successfull

    AM5728 <-> DP83822IF <-> Fiber <-> GE reason S20 switch <-> RJ45 cable <-> PC

    root@mitysom-am57x:~# phytool read eth0/0/0
    0x2100
    root@mitysom-am57x:~# phytool read eth0/0/1
    0x784d
    root@mitysom-am57x:~# phytool read eth0/0/2
    0x2000
    root@mitysom-am57x:~# phytool read eth0/0/3
    0xa240
    root@mitysom-am57x:~# phytool read eth0/0/4
    0x0101
    root@mitysom-am57x:~# phytool read eth0/0/5
    0000
    root@mitysom-am57x:~# phytool read eth0/0/6
    0x0004
    root@mitysom-am57x:~# phytool read eth0/0/7
    0x2001
    root@mitysom-am57x:~# phytool read eth0/0/8
    0000
    root@mitysom-am57x:~# phytool read eth0/0/9
    0000
    root@mitysom-am57x:~# phytool read eth0/0/10
    0x4100
    root@mitysom-am57x:~# phytool read eth0/0/11
    0x1000
    root@mitysom-am57x:~# phytool read eth0/0/12
    0000
    root@mitysom-am57x:~# phytool read eth0/0/13
    0000
    root@mitysom-am57x:~# phytool read eth0/0/14
    0000
    root@mitysom-am57x:~# phytool read eth0/0/15
    0000
    root@mitysom-am57x:~# phytool read eth0/0/16
    0x0005
    root@mitysom-am57x:~# phytool read eth0/0/17
    0x0108
    root@mitysom-am57x:~# phytool read eth0/0/18
    0xa000
    root@mitysom-am57x:~# phytool read eth0/0/19
    0000
    root@mitysom-am57x:~# phytool read eth0/0/20
    0000
    root@mitysom-am57x:~# phytool read eth0/0/21
    0000
    root@mitysom-am57x:~# phytool read eth0/0/22
    0x0100
    root@mitysom-am57x:~# phytool read eth0/0/23
    0x0049
    root@mitysom-am57x:~# phytool read eth0/0/24
    0x0400
    root@mitysom-am57x:~# phytool read eth0/0/25
    0x8020
    root@mitysom-am57x:~# phytool read eth0/0/26
    0000
    root@mitysom-am57x:~# phytool read eth0/0/27
    0x007d
    root@mitysom-am57x:~# phytool read eth0/0/28
    0x05ee
    root@mitysom-am57x:~# phytool read eth0/0/29
    0000
    root@mitysom-am57x:~# phytool read eth0/0/30

    With reagrds

    Sandeep S

  • 0 in reply to SANDEEP S
    TI__Mastermind 24988 points

    Hi Sandeep,

    Thank you for sharing the register logs. I don't see any configuration difference that would be the cause of the communication issue, so this does seem to be a compatibility issue with SFP.

    Regarding SFP compatibility and single/multi-mode support, please allow me until the end of the week to test with the SFP modules we have in lab.

    I will share results for expected compatible SFP modules then.

    Thank you,

    Evan

  • 0 in reply to Evan Mayhew
    TI__Mastermind 24988 points

    Hi Sandeep,

    These two SFP module pairs worked in lab for link and communication:

    [1] Avago AFBR-5712PZ (850nm Class 1)

    [2] Axcen AXFE-1314-0M04 (1310nm Class 1, 100-FX)

    There are a couple things I'd like to check with your setup:

    SANDEEP S said:
    failing setup for ping is AM5728 <-> DP83822IF <-> Fiber <-> GE reason S20 switch <-> RJ45 cable <-> PC

    For this setup, can you confirm that both GE reason S20 switch and DP83822 have auto-negotiation disabled with 100M forced? Both require this configuration, or the link up process will likely fail.

    Also, please try testing after writing address 0x40[13] = '1'.

    Thank you,

    Evan

  • 0 in reply to Evan Mayhew
    Prodigy 225 points

    Hi Evan,

    I tried with IHT - SF13G40 - 1.25G SFP (1310NM Dual Fiber 40 KM DDM - Single mode SFP) on DP83822IF side and Reason S20 switch side. Then link is up on both sides while forcing 100Mbps and disabling Auto-negotiation. But we can't ping the PC connected to the Switch as well as switch.

    But when using AXCEN - AXFD-1314-0W23 : SFP-100FX-DD-IT-CL , then link up is not showing in Reason S20 switch.

    The screenshots of setting of Reason S20 switch is attached here.

    Evan Mayhew said:
    For this setup, can you confirm that both GE reason S20 switch and DP83822 have auto-negotiation disabled with 100M forced? Both require this configuration, or the link up process will likely fail.

    Both GE reason S20 and DP83822 have auto-negotiation disabled with 100M forced.

    For DP83822 we disabled auto-negotiation with 100M forced by using the commands below

    $ ethtool -s eth0 autoneg off

    $ phytool write eth0/0/0 0x2100

    Evan Mayhew said:
    Also, please try testing after writing address 0x40[13] = '1'.

    When read 0x40, it shows 0xFFEA. Still we forced 100Mbps by setting the 13th Bit '1'. But no progress in the communication

    Thanks and regards

    Sandeep S

  • 0 in reply to SANDEEP S
    TI__Mastermind 24988 points

    Hi Sandeep,

    Thanks for sharing these details. As there are no apparent issues with the PHY-level schematic and register configuration, I'd like to isolate the issue to the PHY board or switch side.

    GE reason S20 switch <-> RJ45 cable <-> PC

    For this setup, does ping work directly from PC to switch?

    [ AM5728 <-> DP83822IF <-> Fiber ] <-> GE reason S20 switch <-> RJ45 cable <-> PC

    Do you have another fiber end-point to replace the AM5728 + DP83822? As you have seen a passing result with another switch, please help confirm if this issue is specific to the GE switch. Can GE reason S20 switch be daisy chained with PT7710 for ping?

    Thank you

    Evan

  • 0 in reply to Evan Mayhew
    Prodigy 225 points

    Hi Evan,

    Evan Mayhew said:

    GE reason S20 switch <-> RJ45 cable <-> PC

    For this setup, does ping work directly from PC to switch?

    Yes, from PC to switch ping works

    Evan Mayhew said:
    Do you have another fiber end-point to replace the AM5728 + DP83822?

    Yes. We have D link DES-1210-28 switch. We connected GE switch with D-Link switch and optical communication works fine for all SFPs we have.

    Evan Mayhew said:
    As you have seen a passing result with another switch, please help confirm if this issue is specific to the GE switch.

    We have tried to communicate DP83822IF with D-Link Switch. Then ping works with IHT - SF13G40 - 1.25G SFP 1310NM Dual Fiber 40 KM DDM - Single mode SFP.

    with other SFPs the communication is not successful.

    Evan Mayhew said:
    Can GE reason S20 switch be daisy chained with PT7710 for ping?

    Yes. We connected GE switch with both Moxa and D-Link switch. Then ping is working fine.

    In our schematic design, LED_1 left floating. Is it required or not?

    Thanks and regards

    Sandeep S

  • +1 in reply to SANDEEP S
    TI__Mastermind 24988 points

    Hi Sandeep,

    Thanks for clarifying these points, the issue appears isolated to the DP83822 board in this case.

    SANDEEP S said:
    In our schematic design, LED_1 left floating. Is it required or not?

    LED_1 can be left floating.

    Can you help me understand the termination scheme being used on the MDI side?

    We typically see 50ohm PU resistors on the MDI pins from the PHY-side before the cap coupling, is this application using LVPECL or another interface?

    Thank you,

    Evan

  • 0 in reply to Evan Mayhew
    Prodigy 225 points

    Hi Evan,

    Thank you for pointing out the PU resistor on the MDI. We put that PU resistor for RJ45 connection, and the same got isolated from the circuit when we are using SFP connection. Now we PU MDI pins and now everything works fine.

    Schematic for RJ45 side is

    Now we can communicate the PC through GE switch with 100Mbps forced and auto-negotiation off.

    Thank you for your quick and efficient support.

    With regards

    Sandeep S