Tool/software:
Hello TI Team,
I am trying to bringup Ethernet (Ethfw) with 9.2 SDK when i am debugging via UART i can see that it stuck below function, at what condition semaphore will be available ? another behaviour if i comment this function call complete core is not working so is this expected ?
application built for app_remoteconfig_server from ethfw.
Thanks and Regards,
Satya.
Added to my previous comment, i don't see any further log for MAIN2_0 core after this what could be the issue ?
We have some existing project with some basic drivers like UART, IPC and etc, there in the main function i just called
app_remoteSwitchcfg_server of MCU2_0 main function by renaming like below and all other required dependency libraries mapped to the build. 
and below MACROS enabled for build.
#define BUILD_CPU_MCU2_0
#define BUILD_SOC_LIST J721E
#define BUILD_APP_FREERTOS
//#define ETHAPP_ENABLE_INTERCORE_ETH
#define ETHFW_MONITOR_SUPPORT
#define ETHFW_IPERF_SERVER_SUPPORT
#define ETHFW_RAND_MACADDR_GEN
is it required to enable ETHAPP_ENABLE_INTERCORE_ETH also ? my aim is previously 7.3 SDK is working fine (with some changes in Ethfw and enet modules for VLAN) like Linux also able to create virtual Ethernet interface (Eth1 via j721e-cpsw-virt-mac), so now we are migrating to 9.2 SDK and should run everything like old.
Thanks and Regards,
Satya.
Hi Sudheer,
I have added below ports since we have phy's (DP83867) connected to PORT 5 and 6 with RGMII mode, still i am seeing error like not able to read phy registers, what could be the issue? phy addresses are 1 and 2 as mentioned in screenshot.
Hi Sudheer,
In our custom board we have total 4 ports are there 5 and 6 are RGMII and 7 and 8 are SGMII, 7 is connected to External switch again and 8 is connected to RTL9010 phy, at present i am going to do just bringup for 5 and 6 ports so from application i just enabled those as i mentioned in above screenshots. some how enet board type is detected as GESI board.
in some power cycles i can also different error like below also 
"is ENABLE_QSGMII_PORTS enabled or not? " : for now not enabled
"Also, from Port configuration I could see same PHY mode (dp83867) is connected to all Ports." : yes we have two phy's (dp83867) for two ports are connected to 5 and 6 with phy addr 1 and 2 respectively
Can you please check is PHY Is powered and out of reset? GPIOs used to bring PHY out of reset are configured properly or not? : i will check GPIO's
Thanks and Regards,
Satya.
Hi,
Can you please check is PHY Is powered and out of reset? GPIOs used to bring PHY out of reset are configured properly or not? : i will check GPIO's
Sure.
Also, can you please check once by disabling MDIO Manual Mode from enet_component.mk file.
After disabling, clean build ETHFW and check once.
Best Regards,
Sudheer
Hi Sudheer,
We have total 3 (DP83867) phy's and one is connected to cpsw2g switch and mapped to linux core other two are connected port 5 and 6 are connected to cpsw9g switch, and RESET Logic pins are same for all 3 phy's, but i can do ssh to linux means may be other two also may not have any issue with Reset logic right ? is there any other pins we need to take care?
i have disabled MDIO Manual mode i am seeing issue like below.
and i am seeing these below PHY numbers are random at every power cycle.
If possible could you please arrange one short call for debug today i will show you the schematic diagram then we may find some solution?
Thanks and Regards,
Satya.
Hi Sudheer,
I did clean build with disable MDIO Manual mode as you mentioned now i am not seeing any issues with phy is this confirms that PHY's are working fine ?
what will happen manual mode enable and disable could you please share any document if available?
As i mentioned previously IPCRX task, IPC TX, UART, these drivers are we are maintaining in separate repo created by our project team, i just created new task and calling all the functions as it is like from app_remoteconfig_server.c file into our repo build along with adding all the libraries from Ethfw and enet.
I can also simply flash binary but i am not able to see any UART logs.
0001: [0] <2024-11-06> 0x4100020x8100040x40030050x44015110x41000B0x810004 0002: [0] <2024-11-06> MCU2_0[INFO] - MCU started 0003: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW appMain task init 0004: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW Started 0005: [0] <2024-11-06> MCU2_0[DEBUG] - IpcRx task init 0006: [0] <2024-11-06> MCU2_0[DEBUG] - IpcTx task init 0007: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: EthFwBoard_init: test gesi initialize board: 1 0007: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: EthFwBoard_init: test gesi initialize board: 1 0008: [0] <2024-11-06> MCU2_0[DEBUG] - ======================================================= 0009: [0] <2024-11-06> MCU2_0[DEBUG] - CPSW Ethernet Firmware 0010: [0] <2024-11-06> MCU2_0[DEBUG] - ======================================================= 0011: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: Warning: Using 6 random MAC address(es) 0012: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: Shared multicasts: 0013: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: Reserved multicasts: 0014: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: 01:80:c2:00:00:0e 0015: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: 01:1b:19:00:00:00 0016: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: EthFw_initMcm: test enter to EnetMcm_acquireHandleInfo: 1 0016: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: EthFw_initMcm: test enter to EnetMcm_acquireHandleInfo: 1 0017: [0] <2024-11-06> MCU2_0[DEBUG] - EnetMcm: CPSW_9G on MAIN NAVSS 0018: [0] <2024-11-06> MCU2_0[DEBUG] - PHY 0 is alive 0019: [0] <2024-11-06> MCU2_0[DEBUG] - PHY 1 is alive 0020: [0] <2024-11-06> MCU2_0[DEBUG] - PHY 2 is alive 0021: [0] <2024-11-06> MCU2_0[DEBUG] - PHY 3 is alive 0022: [0] <2024-11-06> MCU2_0[DEBUG] - PHY 4 is alive 0023: [0] <2024-11-06> MCU2_0[DEBUG] - EnetPhy_bindDriver: PHY 1: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK 0023: [0] <2024-11-06> MCU2_0[DEBUG] - EnetPhy_bindDriver: PHY 1: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK 0024: [0] <2024-11-06> MCU2_0[DEBUG] - 0025: [0] <2024-11-06> MCU2_0[DEBUG] - EnetPhy_bindDriver: PHY 2: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK 0025: [0] <2024-11-06> MCU2_0[DEBUG] - EnetPhy_bindDriver: PHY 2: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK 0026: [0] <2024-11-06> MCU2_0[DEBUG] - 0027: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: EthFw_initMcm: test exit to EnetMcm_acquireHandleInfo: 1 0027: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: EthFw_initMcm: test exit to EnetMcm_acquireHandleInfo: 1 0028: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: VLAN 1024 member=0x1ed virtMember=0x7 regMcastFlood=0x1ed unregMcastFlood=0x1ed untag=0x0 0029: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW: 1 VLAN entries added in ALE table 0030: [0] <2024-11-06> MCU2_0[DEBUG] - unibase-1.1.5-jacinto 0031: [0] <2024-11-06> MCU2_0[DEBUG] - 0032: [0] <2024-11-06> ETHFW Version : 0.04.00 0033: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW Build Date: Nov 6, 2024 0034: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW Build Time: 13:43:23 0035: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW Commit SHA: 0036: [0] <2024-11-06> MCU2_0[DEBUG] - Running IpcRx_Main 0037: [0] <2024-11-06> MCU2_0[INFO] - MCU is alive 0038: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW appMain task RUN 0039: [0] <2024-11-06> MCU2_0[DEBUG] - Running IpcRx_Main 0040: [0] <2024-11-06> MCU2_0[INFO] - MCU is alive 0041: [0] <2024-11-06> MCU2_0[DEBUG] - Cpsw_handleLinkUp: Port 6: Link up: 1-Gbps Full-Duplex 0042: [0] <2024-11-06> MCU2_0[DEBUG] - 0043: [0] <2024-11-06> MCU2_0[DEBUG] - Running IpcRx_Main 0044: [0] <2024-11-06> MCU2_0[INFO] - MCU is alive 0045: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW appMain task RUN 0046: [0] <2024-11-06> MCU2_0[DEBUG] - Running IpcRx_Main 0047: [0] <2024-11-06> MCU2_0[DEBUG] - Running IpcRx_Main 0048: [0] <2024-11-06> MCU2_0[INFO] - MCU is alive 0049: [0] <2024-11-06> MCU2_0[DEBUG] - ETHFW appMain task RUN 0050: [0] <2024-11-06> MCU2_0[DEBUG] - Running IpcRx_Main 0051: [0] <2024-11-06> MCU2_0[INFO] - MCU is alive 0052: [0] <2024-11-06> MCU2_0[DEBUG] - Running IpcRx_Main 0053: [0] <2024-11-06> MCU2_0[INFO] - MCU is alive
Thanks and Regards,
Satya.
Hi Sudheer,
i have disabled those IPC TX and RX tasks from applications now only enabled two tasks one is to handle UART and one is for ethremote config server application app.
Now my aim is to create virtual Ethernet port (MAC only) on linux side (uses j721e-cpsw-virt-mac driver ) so i tried enable ETHAPP_ENABLE_INTERCORE_ETH macro is this enough?
When i enabled ETHAPP_ENABLE_INTERCORE_ETH macro, control stuck at below function in screen shot. could you please verify my changes attached here and help to get out of this issue?
app_remoteswitchcfg_server_main() this function i am calling under task function and will be called in once after power on is it required to call periodically ?
app_ethRemoteConfigServerMain.capp_ethRemoteConfigServerMain.h
Hi Sudheer,
yes i gave task priority 2, still issue is same but i don't understand why it is waiting at that semaphore pending, could you please let me know which module should respond to this ? as per below screenshot EnetMcm_init creating MCM server Task and after return OK is control is going to acquire handle function, so i thought creation of MCM server Task may not be an issue. do i need to call any other functions from the application code what i shared ?
Thanks,
Satya.
Hi Sudheer,
from Server side i am sending the commands multiple times then only client may be able to receive, what could be the reason client not receiving consistently but what ever client sends server able to receive.
Thanks regards,
Satya.
Hi Sudheer,
Can we make mailbox receive ISR based instead polling ? as per the the below code snippet if yes how to make changes?
Thanks,
Satya.
