AM263P4-Q1: Unable to Establish Detection for 10BASE-T

Hi Mari,

Can you please share which PHY is the customer using with AM263Px?

Regards,
Shaunak

Hi Shaunak,

Here, you are asking for the PHY on the other end-point right? As in - the PHY that will connect to the PHY on the LaunchPad?

Best regards,

Mari

Hi Mari,

Would be good to have both the PHY details. (Other end as well as the AM26x connected PHY)

Regards,
Shaunak

Hi Shaunak, 

Thanks for the quick response.

I thought the PHY on the LP board was the DP83869? 

The schematics lists this as the PHY. Are you asking about some other PHY that they connect to the LP board?

Best regards,

Mari Tsunoda

1. Yes, AM263Px PHY is DP83869, Wanted to know what interface it is connected to on the other end

2. Also, I see some additional register settings are required (out-of-box PHY config might not be for 10Base-Te mode directly), Can you help confirm if these register settings are followed (if bootstrapping, then bootstrap registers, else the PHY register settings)?

This PHY datasheet contains the necessary information about register configuration for 10-Base Te mode, as well the strap information (incase the PHY is boot-strapped)

https://www.ti.com/lit/ds/symlink/dp83869hm.pdf

You can refer to the sections

(refer sections 7.5.1.2 and 7.4.8)

If the PHY Config and PHY registers are set correctly, then the PHY BMSR registers will show correct status and that will be probed in the Enet-LLD driver

If all the PHY config is also correct then, we should perform PHY loopback tests to see if PHY has no issues

If even that doesn't help, we can reach out to the PHY team for further help

Regards,
Shaunak

Hi Shaunak,

Thanks on the detailed information on the register settings.

They have asked us on how to configure auto-detection for 10BASE-T, 100BASE-TX, 1000BASE-T. Is this possible or will they have to change register configurations accordingly? My understanding is that the latter is correct.

Best regards,

Mari 

Hi Mari,

Shaunak Deshpande said:

Would be good to have both the PHY details. (Other end as well as the AM26x connected PHY)

Q1. Can you confirm the details for the Link partner which is connected to AM263Px? 

I had a discussion with our PHY team, please find their comments:

"For 10M, the link partner must only have 10M auto-negotiation advertisement enabled, If this is not the case, either PHY straps need to be modified, or driver needs to be adjusted"

"The SDK PHY drivers looks okay to support 10Base-Te mode. I believe the Link detection might indicate some issues with our configurations (both on the AM263Px as well as the Other side partner)."

Q2. Also, would it be possible to get a dump of the PHY-registers for us to review. In some cases, this also helps identify incorrect configs.

Regards,
Shaunak

Hi Shaunak,

Thanks for the reply and also for checking with the PHY team. 

Q1: The link partner is DP83869HMRGZR. Do you need additional details here?

Q2: I have asked the customer to provide the PHY register dump and will update once they send me the log.

Best regards,

Mari Tsunoda

Hi Mari,

Shaunak Deshpande said:

"For 10M, the link partner must only have 10M auto-negotiation advertisement enabled, If this is not the case, either PHY straps need to be modified, or driver needs to be adjusted"

Can we confirm if the link partner does the above mentioned config.

Mari Tsunoda said:

Q2: I have asked the customer to provide the PHY register dump and will update once they send me the log.

Sure, i'll review the register dump once available.

Regards,
Shaunak

Hi Shaunak,

They have checked the register contents.

7.6.1.1 BMCR Register (Offset = 0h)                        --> 1140h (Autonegotiation on,  Full Duplex mode)
7.6.1.2 BMSR Register (Offset = 1h)                      　--> 796Dh (PHY able 100Base-TX full/half, 10Base-Te full/half,  Auto Negotiation completed,  Link up)
7.6.1.5 ANAR Register (Offset = 4h)                        --> 01E1h (Advertise 100Base-TX Full/Half, 10Base-T Full/Half,  802.3)
7.6.1.6 ALNPAR Register (Offset = 5h)                    --> C461h (Link Partner advertises 10Base-T Full/Half)
7.6.1.7 ANER Register (Offset = 6h)                        --> 006Dh
7.6.1.8 ANNPTR Register (Offset = 7h)                    --> 2001h
7.6.1.9 ANLNPTR Register (Offset = 8h)                  --> 6801h
7.6.1.11 GEN_STATUS1 Register (Offset = Ah)        --> 0000h
7.6.1.10 GEN_CFG1 Register (Offset = 9h)               --> 0200h (Advertise 1000Base-T Full)
7.6.1.15 PHY_CONTROL Register (Offset = 10h)      --> 4000h
7.6.1.16 PHY_STATUS Register (Offset = 11h)         --> 2F02h
7.6.1.27 GEN_CTRL Register (Offset = 1Fh)             --> 0000h
7.6.1.122 OP_MODE_DECODE Register (Offset = 1DFh)  --> 0000h (RGMII to Copper)
7.6.1.125 FX_CTRL Register (Offset = C00h)           --> 1140h

Does this look OK? 

On the LP board, the Ethernet driver was connected to a PC set to 10BASE-T Full Duplex with a straight cable. 

Best regards,

Mari Tsunoda

Hi Mari,

Let me review this and get back on Monday

Regards,
Shaunak

Hi Mari,

This register dump shows expected PHY status for auto-negotiation resolution and link in 10M speed. I see link is up, with 10M speed negotiated in half-duplex.

As MDI-side connection is valid, the issue is more likely with MAC interface. Is RGMII or MII being used?

Thank you,
Evan

Hi Evan, Shaunak,

Sorry for the late reply. I just got a response from my customer.

They are using RGMII.

Best regards,

Mari Tsunoda

Hi Team, 

Any update on this?

Best regards,

Mari

Hi Mari,

I am investigating the issue. Allow me some time on this.

Regards,

Aswin

Hi Aswin,

Any update on this?

Best regards,

Mari 

Hi Mari,

I tried to establish a 10 Base T connection between an AM263P launchpad and my PC.

Can you check if customer is facing this issue in LP or in their custom board?

For a start, can we achieve this on customer's LauchPad.

Please follow the steps below,

1. Take the stock enet_layer2_cpsw example (enet_l2_cpsw_am263px-lp_r5fss0-0_freertos_ti-arm-clang) from SDK and build the debug version of the same.

2. Change the ethernet adapter configuration of the PC by disabling auto-negotiation and enabling 10Mbs Full Duplex.

3. The LP can be set in Auto negotiation.

4. Now run the example.

I was able to obtain the Port Link and was able to send packets from PC to the board. In the below screen snip we can see how 10Mbps Full Duplex connection has been obtained.

If the customer is using launchpad then by following the above steps, 10 Base T connection can be established

Regards,

Aswin