Other Parts Discussed in Thread: SYSBIOS
Hi Expert,
Customer Hirain encounter an eth issue as below：
Currently our project is having issues using the Eth Virtual Mac.
We refer to the TI SDK version as 0804, and the document location is MCUSW: Eth Virtual Mac User Guide (ti.com)
According to the build and running methods provided in the document, we compiled the binary on MCU2_1 and verified it on CCS, but we did not see the log phenomenon as given in the document.
In the code path mcusw\mcal_drv\mcal\examples\Eth\eth_app\target\EthVirtmacApp.c,
1. SemaphoreP_pend is waiting to post a semaphore. We found that the post semaphore operation is in EthVirtmacApp_initMainFunctionPoll(), but it can be seen in the figure that the code here is blocked by TI
2. We manually open the shield here, and the code will run away at the position shown in the figure below
The operation process is as follows:
Compilation instruction: eth_virtmac_app
$ cd mcusw/build/
$ make eth_virtmac_app CORE:=mcu2_1 BOARD:=j721e_evm
Generated result:
mcusw/binary/eth_virtmac_app/bin/j721e_evm/eth_virtmac_app_mcu2_1_${build_profile}.xer5f
Host-side application compilation instructions:
$ cd mcal_drv/mcal/examples/Eth/eth_app/host/
$ make
Program loading steps:
1. Run the host-side application with root privileges and specify the interface name to use, for example:
2. $ cd
mcal_drv/mcal/examples/Eth/eth_app/host/
3. $ sudo ./EthHostApp -i eth2
4. At this point, the host-side application will wait for the DUT
5. Load the Ethernet firmware on MAIN_Cortex_R5_0_0 on the target.
o ${ETHFW}/out/${soc}/R5F/SYSBIOS/${build_profile}/app_remoteswitchcfg_server.xer5f
6. Run MAIN_Cortex_R5_0_0
7. Load the target application on MAIN_Cortex_R5_0_1
8. eth_virtmac_app_mcu5_0_${build_profile}.xer1f
9. Run MAIN_Cortex_R5_0_1
When debugging: enter EthVirtmacApp_init() from main, and get stuck in an infinite loop at SemaphoreP_pend
customer question as below:
1. Where is SemaphoreP posted for SemaphoreP_pend detection
2. Is there any error in our operation method?
3. I compared the code implementation of this part in SDK 0805 and 0806. Here is the same implementation. Whether TI has realized the complete function of this part
BR,
Biao
