• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 185 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.

LAUNCHXL-F28P65X: EtherCAT example with DP83826E PHY

Al M
Prodigy 50 points
Part Number: LAUNCHXL-F28P65X
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hi,

I am trying to narrow down an issue with our design, which is a copy of the LAUNCHXL-F28P65X design. We cannot get PORT 0 to be detected in TwinCAT using the TI example f28p65x_cpu1_pdi_hal_test_app.

We've tried everything we could on the hardware side, and now I want to make sure it's not related to the firmware.

When we started the project back in December 2023, the LAUNCHXL-F28P65X had the "wrong" PHY revision assembled. The EtherCAT examples were not working until we received instructions for a firnware workaround:
FAQ: How do I fix the EtherCAT issue where the LaunchPad cannot be scanned in TwinCAT.

Now I am confused about when to apply this firmware patch. We took the same launchpad, replaced the PHY with brand new ones from TI (826E TI 2A8 AH8X G4), but the example f28p65x_cpu1_pdi_hal_test_app still does not function straight from C2000Ware_5_03.

I also swapped the PHY with a batch from Digi-Key (826E TI 348 AHLD G4), and had the same issue.

When we apply the patch instructions, it works, but I don’t understand why. It is supposed to be a fresh PHY with an up-to-date revision, so there should be no need for the F28P65X_REVA_workaround.

Could you confirm whether, if I buy a LaunchPad from TI today (September 30th, 2024), and try to run the f28p65x_cpu1_pdi_hal_test_app from C2000Ware_5_03, it should work without needing the patch?

  • +1
    TI__Mastermind 43056 points

    Hi,

    Can you try the 'f28p65x_cpu1_echoback_solution' instead and see if you can scan with TwinCAT without the workaround? This should work. I haven't tried 'f28p65x_cpu1_pdi_hal_test_app' recently before programming the EEPROM, but it should work too.

    Al M said:
    When we apply the patch instructions, it works, but I don’t understand why. It is supposed to be a fresh PHY with an up-to-date revision, so there should be no need for the F28P65X_REVA_workaround.

    Are you programming the EEPROM first when you do the workaround?

    To confirm if the PHY DP83826 silicon is Rev0 or Rev1 the PHY registers can be read over the MI interface (MDIO / MDC).

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 50 points

    That's correct, f28p65x_cpu1_echoback_solution works with new PHYs