• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 102 subscribers
  • Views 264 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.

[FAQ] TDA4VM-Q1: MDIO change in SR2.0

Biao Li
Expert 4800 points
Part Number: TDA4VM-Q1
Other Parts Discussed in Thread: TDA4VM

Tool/software:

Hi Expert,

My customer Motovis report an issue about ethernet link down issue, customer have catch the MDIO using the Logic analysis, they find there is some difference between B version (SR1.1) and C version (SR2.0). customer are using the same SW, and they actually only send the clause 22 protocol, and they can see only clause 22 in SR1.1 device, but in SR2.0, there is a lot of clause 45 you can see below screen shot. this difference cause customer line down, all SR2.0 board will link down so that the ethernet will work abnormal. need you help for this issue urgently; do you know any SW change need to be apply for this MDIO in GP device? or any difference between this? customer confirm this issue is related silicon version.

SDK version: SDK 8.4, GP Device

SR1.1:

SR2.0

0003.decoder--Bversion SR1.1 mdio.xlsx0003.decoder--C version SR2.0 mdio.csv

BR,

Biao

  • 0
    TI__Mastermind 30450 points

    Hi Biao,

    Caluse 22 vs clause 45 is chosen in S/W.

    That being said, in the linux drivers, there are some checks which toggle the mode based on the SOC revision. But unless specified in device-tree explicitly, clause 45 isn't used.

    What is the Ethernet controller being used for the customer? What SDK are they on?

    Regards,
    Tanmay

  • 0 in reply to Tanmay Patil
    TI__Expert 4800 points

    Hi Tanmay,

    customer is using SDK8.4 SBL to boot Uboot, then boot the kernel. what is the mean for Eth controller? I think customer is using the switch inside TDA4VM, MCU_CPSW2G_RGMII.

    BR,

    Biao

  • 0 in reply to Biao Li
    TI__Expert 4800 points

    Hi Tanmay,

    do we have some patch to customer to fix this? let SR2.0 chose the Caluse 22 only?

    BR,

    Biao

  • 0 in reply to Biao Li
    TI__Mastermind 30450 points

    Hi Biao,

    Biao Li said:
    what is the mean for Eth controller?

    Meaning what is controlling the CPSW? Is it linux or RTOS or MCAL?

    Regards,
    Tanmay

  • 0 in reply to Tanmay Patil
    TI__Expert 4800 points

    Hi Tanmay,

    customer feedback they are using linux to control.

    BR,

    Biao

  • 0 in reply to Biao Li
    TI__Mastermind 42690 points

    Hi,

    From 8.4 SDK, Default J721E, SR2.0 enables in MDIO Manual Mode. In Manual Mode C45 is mot supported from TI SDK.
    Please refer to below, for more details. 


    Can you confirm above is same in customer case also.

    Best Regards,
    Sudheer

  • 0 in reply to Doredla Sudheer Kumar
    TI__Expert 4800 points

    Hi Sudheer,

    Tanmay have help fix this issue:

    diff --git a/drivers/net/ethernet/ti/davinci_mdio.c b/drivers/net/ethernet/ti/davinci_mdio.c

    index 946b9753c..d26d6f4da 100644

    --- a/drivers/net/ethernet/ti/davinci_mdio.c

    +++ b/drivers/net/ethernet/ti/davinci_mdio.c

    @@ -487,6 +487,7 @@ static const struct soc_device_attribute k3_mdio_socinfo[] = {

    { .family = "J7200", .revision = "SR2.0", .data = &am65_mdio_soc_data },

    { .family = "J721E", .revision = "SR1.0", .data = &am65_mdio_soc_data },

    { .family = "J721E", .revision = "SR2.0", .data = &am65_mdio_soc_data },

    + { .family = "J721E", .revision = "SR3.0", .data = &am65_mdio_soc_data },

    { .family = "J721S2", .revision = "SR1.0", .data = &am65_mdio_soc_data},

    { /* sentinel */ },

    };

    BR,

    Biao