Tool/software:
Hello everyone,
We are currently working on SDK 10.0 for a custom board based on the J784S4 and need assistance with the configuration and proper usage of the MAIN_CPSW2g Ethernet (2G).
We have enabled all the relevant sections for the MAIN_CPSW2g Ethernet interface, and it is visible in Linux when using the ifconfig -a
command. When we enable the interface with ifconfig eth1 up
, the PHY link comes up as expected. However, after manually setting the IP address, netmask, and gateway, we are unable to ping a remote PC. Interestingly, following the same steps for the MCU_CPSW2g Ethernet allows us to ping the remote PC without issue.
To debug further, we attempted to configure the MAIN_CPSW2g Ethernet in U-Boot, following the steps outlined in a Texas Instruments post. By disabling the MCU_CPSW2g Ethernet in the DTS (likely due to U-Boot’s limitation of supporting a single interface), we were able to successfully ping the remote PC using the MAIN_CPSW2g Ethernet.
However, we encountered a separate issue when testing on the J784S4 EVM board with the default image. After flashing the EVM and attempting to use the MAIN_CPSW2g Ethernet, connecting the cable resulted in no activity; the link seemed completely inactive, leaving us in a worse state compared to our custom board.
This raises several questions:
- Is the MAIN_CPSW2g Ethernet expected to work in conjunction with the MCU_CPSW2g Ethernet in Linux? Our attempts to enable both interfaces simultaneously on the EVM were unsuccessful.
- Are there specific configurations or additional steps required in Linux to ensure the MAIN_CPSW2g Ethernet operates correctly?
- Could any hardware or DTS configuration issues be contributing to these inconsistencies, either on our custom board or the EVM?
We would greatly appreciate any guidance or recommendations to address this issue.
Thank you in advance for your support.
Best regards,
Dušan