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.
Tool/software:
As mention in (CS2357401: Support for Ethernet on RMII port)
we have to use two Ethernet port, one for as server and second one for client in RMII mode
but giving error while configure RMII mode
kindly let me know how to solve this problem
Hi Vikas,
1. The AM263x only has one instance of CPSW. This CPSW0 instance has 3 ports (1 host and 2 MAC ports). So we can only add CONFIG_ENET_CPSW0. The error is caused because we try to add a resource which is not available.
To configure 2 ports within CPSW0. Add CONFIG_ENET_CPSW0 (I see this is already added, you can remove the CONFIG1).
2. Then configure the PINMUX to use RMII
3. Configure the MAC port-1 and MAC port-2 as you need
4. Configure the host port as per your needs
You can learn more about CPSW from this MCU+ Academy chapter that we recently released: dev.ti.com/.../node
Regards,
Shaunak
thanks Shaunak for Academy link,
We are designing custom board with 2 phy(RMII) and i have to configure the pins which are connected to both the phy,
So kindly let me know how to configure pins for both the phy
in above attachment Only one RMII connection is configured and how to configure other one?
if RGMII configured instead of RMII its configure all the pins for both the phys
Hi Vikas,
Seems like a bug in syscfg for adding the second RMII settings.
Can you try the following change? I tried the same on my end and saw no syscfg related issues:
Do the below change in the file at: "source/networking/.meta/enet_cpsw/am263x/enet_cpsw_am263x_pinmux.syscfg.js"
After this try opening the syscfg of your application again and do the required changes. Please let me know if this fixes your issue.
Regards,
Shaunak
Hi Vikas,
Im not sure what is causing this error. Did you make any change over the Patch I shared yesterday? Asking since I am not able to replicate this error on my end. Did you try the patch yesterday and resolve the error but it is only visible again today?
Regards,
Shaunak