Part Number: DP83822I
Other Parts Discussed in Thread: AM2631, DP83869, SYSCONFIG
Hello expert,
I am currently using TwinCAT together with the TI AM2631 demo board to debug EtherCAT functionality, and the communication is already working correctly.
In the demo example provided by TI, the PHY device used is DP83869, while in our final product we plan to use DP83822 as the Ethernet PHY.
During this process, we encountered the following two questions and would like to ask for clarification:
Question 1: PHY support and driver integration for DP83822
In SysConfig, there is no available option related to DP83822. The SDK link that I use is below:
INDUSTRIAL-COMMUNICATIONS-SDK-AM263X Software development kit (SDK) | TI.com
The version is the newest.
The SysConfig version that I use is SysConfig 1.21.0
For using DP83822 in an AM2631 EtherCAT application:
Is there existing driver support for DP83822?
How should the PHY driver be integrated or enabled (for example, by adding a dedicated PHY driver or adapting an existing DP8382x driver)?
Question 2: Build error after changing PHY type and the generation mechanism of tiescsoc.c
When we temporarily changed the PHY type in SysConfig from DP83869 to DP83826 for validation purposes, the project failed to build
We would like to confirm:
• Is the code in tiescsoc.c automatically generated by SysConfig, or is it expected to be modified manually by the user? I’m sorry that I cannot upload the screenshot. Here is the file path where it is stored. I am using this example. C:\ti\ind_comms_sdk_am263x_10_00_00_12\examples\industrial_comms\ethercat_slave_beckhoff_ssc_demo
• When a build error occurs due to a PHY type mismatch, should the issue be resolved purely through SysConfig configuration, or are corresponding changes required in the low-level source code?
These two questions are mainly related to software adaptation when switching the Ethernet PHY (from DP83869 to DP83822).
Any guidance or recommended approach would be greatly appreciated.
Thank you for your support.
