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.

TDA4VM: EthFw Server and Remote Client can not ping each other

Part Number: TDA4VM

Hi expert,

As the Ethfw User guide said, i can place remote client to MCU2_1 and enable A72 Core's virtual eth dirver.

I found that i can't ping Remote Client(MCU2_1) in A72 Core. But when i try to ping A72 Core and MCU2_1 through MAC Port 3, i can access both of them.

Could you help me to explain the situation? How to solve it ?

Thanks,

Hutian

  • Hi,

    I found that i can't ping Remote Client(MCU2_1) in A72 Core

    Because that would mean that you are trying to ping internally through the SoC, it's not supported right now. It would require A72, R5F to act as independent MAC entities.

    But when i try to ping A72 Core and MCU2_1 through MAC Port 3, i can access both of them

    Yes, as explained above, an external entity would be able to reach these MAC addresses.

    Regards

    Vineet

  • Hi Vineet,

    it's not supported right now. It would require A72, R5F to act as independent MAC entities.

    When would it be supported?  i want to use socket to achieve the communication between  R5F cores and  A72. Is it possible to put Remote Client to MCU3_0 and MCU3_1? Currently i only place the Remote Client to MCU2_1.

    Thanks,

    hutian

  • Hi,

    When would it be supported?

    I will check and get back to you.

    Is it possible to put Remote Client to MCU3_0 and MCU3_1? Currently i only place the Remote Client to MCU2_1.

    Yes, it's possible but the application would require changes. Here is a list of steps 

    1. EthFw – update autosarEthDriverRemoteCoreId in EthFw_initRemoteConfig()

    2. Update own proc ID

    3. Edit MPU configuration to add mcu3_0 IPC region

    Regards

    Vineet

  • Can you use MCUSW virtual client application ? The steps for migration are more detailed there

    Regards

    Vineet

  • Thanks for your suggestion, i will check the MCUSW virtual client.

    B&R

    hutian

  • Hi Vineet,

    Yes, it's possible but the application would require changes. Here is a list of steps 

    I want to double check that can i put the Remote Client to the cores at the same time ( MCU2_1 & MCU3_0 & MCU3_1)?

    When i try to add to both MCU2_1 and MCU3_0 and i got the following error log:

    [MCU2_0] 4.138668 s: Function:CpswProxyServer_attachExtHandlerCb,HostId:4,CpswType:6
    [MCU2_0] 4.139169 s: Function:CpswProxyServer_ioctlHandlerCb,HostId:4,Handle:a21de9fc,CoreKey:38acb976, Cmd:1010401,InArgsLen:0, OutArgsLen:4
    [MCU2_0] 4.139458 s: Function:CpswProxyServer_attachExtHandlerCb,HostId:5,CpswType:6
    [MCU2_0] 4.139687 s: EnetMod_ioctl: cpsw9g.rm: Failed to do IOCTL cmd 0x01000a02: -8
    [MCU2_0] 4.139739 s: EnetPer_ioctl: cpsw9g: Failed to do IOCTL cmd 0x01000a02: -8
    [MCU2_0] 4.139778 s: Enet_ioctl: cpsw9g: IOCTL 0x01000a02 failed: -8

    Could you help me?

    Thanks,

    hutian

  • Hi,

    When would it be supported?

    Support for inter-core communication will be enabled in SDK 8.1 (end of 2021)

    For porting MCUSW app to another core, can you check this thread ?

    Regards

    Vineet

  • Hi Vineet,

    The Max CPSW9G's DMA TX count is 8 and the code is shown below:

    ./pdk_jacinto_07_01_05_14/packages/ti/drv/enet/soc/j7x/j721e/enet_soc.c line: 507

    .txChCount = CSL_PSILCFG_NAVSS_MAIN_CPSW9_PSILD_THREAD_CNT,

    But the MCU2_0's core has consumed 4 TX channel and the code is shown below:

    [1] =
    {
    .coreId = IPC_MCU2_0,
    .numTxCh = 4U,
    .numRxFlows = 4U,
    .numMacAddress = 1U,
    },
    Do you know how to calculate this UDMA resources for each core?

    Thanks,

    hutian