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.

DRA821U: CPSW5G does not work when connected to Bottom-P0 port of DRA821U EVM

Part Number: DRA821U

Hi TI

There's request that Customer wants to resolve an issue regarding CPSW5G working.

Customer found an issue even though they followed the steps what was introduced from original thread.

  • set dorprocboot = 1
  • set do_main_cpsw0_qsgmii_phyinit = 1
  • save env
  • boot

The following symptoms are observed.

Symptom 1. Only Bottom – P0 does not operate after booting by connecting to Bottom – P0 or connecting to another port before connecting to Borrom - P0.

Symptom 2. If you connect the cable connected to the other port to Bottom – P0, the system becomes stuck or ping does not work.

Symptom 3. After connecting to Bottom – P0, system hang when ifconfig eth1 down or reboot -f.

4. According to log message, EnetPhy_bindDriver: PHY 16: OUI:3fffff Model:3f Ver:0f <-> 'generic': Okay, Their though is that the chip information can not be read.

6)	root@j7200-evm:~# cat /sys/kernel/debug/remoteproc/remoteproc*/trace0
7)	Starting Sciserver..... PASSED
8)	IPC_echo_test (core : mcu1_0) .....
9)	IPC Driver Revision: 01.00.00.01
10)	mcu1_0 <--> mcu2_1, Ping- 10000, pong - 10000 completed
11)	=======================================================
12)	            CPSW Ethernet Firmware
13)	=======================================================
14)	CPSW_5G Test on MAIN NAVSS
15)	EnetPhy_bindDriver: PHY 16: OUI:3fffff Model:3f Ver:0f <-> 'generic' : OK
16)	EnetPhy_bindDriver: PHY 17: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
17)	EnetPhy_bindDriver: PHY 18: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
18)	EnetPhy_bindDriver: PHY 19: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
19)	PHY 0 is alive
20)	PHY 3 is alive
21)	PHY 16 is alive
22)	PHY 17 is alive
23)	PHY 18 is alive
24)	PHY 19 is alive
25)	PHY 23 is alive
26)	
27)	ETHFW Version   : 0.01.01
28)	ETHFW Build Date: Jul 13, 2021
29)	ETHFW Build Time: 15:43:32
30)	ETHFW Commit SHA: 4cb38131
31)	
32)	Starting lwIP, local interface IP is dhcp-enabled
33)	Host MAC address: 70:ff:76:1d:92:c2
34)	[LWIPIF_LWIP] NETIF INIT SUCCESS
35)	Added interface 'ti1', IP is 0.0.0.0
36)	IPC_echo_test (core : mcu2_0) .....
37)	Remote demo device (core : mcu2_0) .....
38)	CpswMacPort_checkSgmiiStatus: MAC 2: SGMII link parter config port: link up: 1-Gbps Full-Duplex
39)	Cpsw_handleLinkUp: Port 2: Link up: 1-Gbps Full-Duplex
40)	Added interface 'ti1', IP is 192.168.0.4
41)	EthFw: TimeSync PTP enabled
42)	Rx Flow for Software Inter-VLAN Routing is up
43)	REMOTE_SERVICE: Init ... !!!
44)	REMOTE_SERVICE: Init ... Done !!!
45)	Function:CpswProxyServer_attachExtHandlerCb,HostId:0,CpswType:5
46)	Function:CpswProxyServer_registerMacHandlerCb,HostId:0,Handle:a287c00c,CoreKey:38acb7e6, MacAddress:70:ff:76:1d:92:c1, FlowIdx:84, FlowIdxOffset:0
47)	Cpsw_ioctlInternal: CPSW: Registered MAC address.ALE entry:10, Policer Entry:3IPC_echo_test (core : mcu2_1) .....
48)	IPC Driver Revision: 01.00.00.01
49)	mcu2_1 <--> mcu1_0, Ping- 10000, pong - 10000 completed
50)	root@j7200-evm:~# [   33.867405] vdd_mmc1: disabling

  1. root@j7200-evm:~# cat /sys/kernel/debug/remoteproc/remoteproc*/trace0
  2. Starting Sciserver..... PASSED
  3. IPC_echo_test (core : mcu1_0) .....
  4. IPC Driver Revision: 01.00.00.01
  5. mcu1_0 <--> mcu2_1, Ping- 10000, pong - 10000 completed
  6. =======================================================
  7.             CPSW Ethernet Firmware
  8. =======================================================
  9. CPSW_5G Test on MAIN NAVSS
  10. EnetPhy_bindDriver: PHY 16: OUI:3fffff Model:3f Ver:0f <-> 'generic' : OK
  11. EnetPhy_bindDriver: PHY 17: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
  12. EnetPhy_bindDriver: PHY 18: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
  13. EnetPhy_bindDriver: PHY 19: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
  14. PHY 0 is alive
  15. PHY 3 is alive
  16. PHY 16 is alive
  17. PHY 17 is alive
  18. PHY 18 is alive
  19. PHY 19 is alive
  20. PHY 23 is alive
  21.  
  22. ETHFW Version   : 0.01.01
  23. ETHFW Build Date: Jul 13, 2021
  24. ETHFW Build Time: 15:43:32
  25. ETHFW Commit SHA: 4cb38131
  26.  
  27. Starting lwIP, local interface IP is dhcp-enabled
  28. Host MAC address: 70:ff:76:1d:92:c2
  29. [LWIPIF_LWIP] NETIF INIT SUCCESS
  30. Added interface 'ti1', IP is 0.0.0.0
  31. IPC_echo_test (core : mcu2_0) .....
  32. Remote demo device (core : mcu2_0) .....
  33. CpswMacPort_checkSgmiiStatus: MAC 2: SGMII link parter config port: link up: 1-Gbps Full-Duplex
  34. Cpsw_handleLinkUp: Port 2: Link up: 1-Gbps Full-Duplex
  35. Added interface 'ti1', IP is 192.168.0.4
  36. EthFw: TimeSync PTP enabled
  37. Rx Flow for Software Inter-VLAN Routing is up
  38. REMOTE_SERVICE: Init ... !!!
  39. REMOTE_SERVICE: Init ... Done !!!
  40. Function:CpswProxyServer_attachExtHandlerCb,HostId:0,CpswType:5
  41. Function:CpswProxyServer_registerMacHandlerCb,HostId:0,Handle:a287c00c,CoreKey:38acb7e6, MacAddress:70:ff:76:1d:92:c1, FlowIdx:84, FlowIdxOffset:0
  42. Cpsw_ioctlInternal: CPSW: Registered MAC address.ALE entry:10, Policer Entry:3IPC_echo_test (core : mcu2_1) .....
  43. IPC Driver Revision: 01.00.00.01
  44. mcu2_1 <--> mcu1_0, Ping- 10000, pong - 10000 completed

root@j7200-evm:~# [   33.867405] vdd_mmc1: disabling

Symptom 5. Sometimes The size of rootfs becomes 0 when set dorprocboot = 1

 Kernel boot fails after set dorprocboot = 1 on uboot prompt, 

And the size of rootfs is identified as 0 when checking with 'ls mmc 0:2' command on uboot

Please check these issues regarding CPSW5G' Bottom-P0 Port.

Thanks.

Regards, 

Jack

  • Hi Jack,

    Apologies for the delay.

    I was unable to observe this issue on my setup. Could you go into the details of your setup and provide me with help to recreate the issue?

    If you are using EVM it is possible that the issue is due to some loose connection. I suggest you to disconnect the Quad-ethernet expansion card (the highlighted card in image) and reconnect it carefully.

    Regards,
    Tanmay

  • Hi Tanmay

    Customer moved to SDK8.x. The same issue was not asked recently.

    Let's close this thread. I will ask a new ticket if re-opended.

    thanks.

    Regards, 

    Jack