Other Parts Discussed in Thread: DP83867ERGZ-S-EVM, , DP83869, DP83869HM
Hi again,
(this is a followup of https://e2e.ti.com/support/interface/f/138/p/764147/2824692. Thanks for the first answer there & sorry for not responding.)
We habe a module with [Linux-SOM => Ethernet => DP83867IS => SGMII => connector] and a 3rd party host [connector => SGMII => unknown]. In production and development we want to be independant of the 3rd party host (There are several reasons for this). Our idea is to use a second DP83867 and create a bridge like this: [Linux-SOM => Ethernet => DP83867IS => SGMII => connector] [connector => SGMII => DP83867ERGZ-S-EVM => Ethernet => RJ45 => cable => Laptop/Switch/"house ethernet"].
Here are registers from our module (where Ethernet between SOM and DP83967 should be active, but apparently isn't)
Register 0000 is: 1140
Register 0001 is: 796D
Register 0002 is: 2000
Register 0003 is: A231
Register 0004 is: 01E1
Register 0005 is: C5E1
Register 0006 is: 006F
Register 0007 is: 2001
Register 0008 is: 6801
Register 0009 is: 0300
For comparison, the registers of the DP83867ERGZ-S-EVM, connected to a Ethernet-switch:
Register 0000 is: 1140
Register 0001 is: 796D
Register 0002 is: 2000
Register 0003 is: A231
Register 0004 is: 0181
Register 0005 is: 4DE1
Register 0006 is: 0067
Register 0007 is: 2001
Register 0008 is: 0000
Register 0009 is: 0300
Questions:
- The link status refers to the (Ethernet) PHY link, not the SGMII link, correct?
- Is the approach of connecting two DP83867 via SGMII the right approach anyway? Crossing So and SI pairs?
- Any hints of debugging what's wrong/different on the module's DP, compared to the EVM?