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: Power off and restart the board, occasionally resulting in network connectivity

Part Number: TDA4VM

After the TDA4vm board is powered on and started, the network is disconnected, and there is a failure log in the dmesg. However, during the power-on running cycle where this issue does not occur, the dmesg also has this failure log:

[ 6.299183] j721e-cpsw-virt-mac main_r5fss_cpsw9g_virt_mac0: register_ipv4 rpmsg - fail -5
[ 6.318043] j721e-cpsw-virt-mac main_r5fss_cpsw9g_virt_mac0: virt_cpsw_nuss mac started

(Executing ifconfig eth0 down/up after powering on can result in a high probability of network connectivity issues, and it is unknown whether it is consistent with the current cause of the problem)

I am currently looking to see if the issue of this failure has any impact; May I ask colleagues from TI, what do you think may be causing this problem? Do you have any troubleshooting suggestions? thank you!

  • Hi,

    Can you please share the Ethernet Firmware Logs along with the Linux terminal.

    Also, can you share details about your test setup.

    Best Regards,
    Sudheer

  • Hi,

    Please refer to the attachment for Linux and vx logs;

    My operation process is as follows:

    After booting up, SSH login to the device is successful;

    Then execute: ifconfig eth0 down

    SSH links the device again (of course, it cannot be linked);

    Continue execution: ifconfig eth0 up

    SSH links the device again, but still cannot connect; The board ping computer is not working;

    Best Regards,

    weihaipeng

    linux and vx_app_linux_arm_remote log.txt

  • Hi,

    From log we see virtmac driver xmit API is invoking for the ping request.

    Can you please share the Ethernet Firmware Logs when ping fails, by following below sequence.
    1. Execute "# cat /sys/kernel/debug/remoteproc/remoteproc*/trace0" and collect Ethernet Firmware logs from MAIN UART2 debug termianl.
    2. Run Ping and execute command shared in step-1 and collect Ethernet Firmware Logs.
    3. Also, open Wireshark at PC side and check whether any ICMP packets been receiving or not.

    If MAIN UART2 is not available, Please use the attached patch (refer to readme.txt in zip file for usage) and follow above steps.
    8535.CPSW_Periodic_stat_dump.zip

    Best Regards,
    Sudheer