• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 97 subscribers
  • Views 3085 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Unable to ping from target to host in u-boot

Lakshmi Shetty
Prodigy 205 points

Part Number: TDA4VM

Hello Team,

Linux SDK pacakge: ti-processor-sdk-linux-j7-evm-08_01_00_07-Linux-x86-Install.bin

I am trying to ping from target to host. But ping is failing with host not alive. 

Do I need to modify in default binaries.

Thanks and regards,

Lakshmi

  • 0
    TI__Guru**** 171240 points

    Hi Lakshmi,

    I hope host and target both are on the same network. You can connect the ethernet cable to the CPSW2G port.

    Try the commands below from U-Boot prompt:

    dhcp
    ping host_ip

    Logs from my setup:

    dhcp
    k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
    k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled
    am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: rflow_id_base: 2
    link up on port 1, speed 1000, full duplex
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 4
    DHCP client bound to address 192.168.100.45 (2475 ms)
    *** ERROR: `serverip' not set
    Cannot autoload with TFTPGET
    => <INTERRUPT>
    => <INTERRUPT>
    => ping 192.168.100.1
    am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: rflow_id_base: 2
    link up on port 1, speed 1000, full duplex
    Using ethernet@46000000 device
    host 192.168.100.1 is alive
    =>

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Prodigy 205 points

    Hi Keerthy,

    Thanks for the reply.

    I have connected ethernet cable between CPSW2G and host PC(Windows).

    Both the side using static IP.

    In host: 

    ip address: 192.168.1.10

    subnet mask: 255.255.255.0

    Default gateway: 192.168.1.1

    In target:

    U-Boot # setenv ethact cpsw
    U-Boot # setenv ipaddr 192.168.1.2
U-Boot # setenv serverip 192.168.1.1
U-Boot # setenv gatewayip 192.168.1.1
U-Boot # setenv netmask 255.255.255.0

     But while executing ping to 192.168.1.10 getting below prints.

    => ping 192.168.1.10
    am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: rflow_id_base: 2
    link up on port 1, speed 1000, full duplex
    Using ethernet@46000000 device
    ping failed; host 192.168.1.10 is not alive

    is there any wrong command I am using here?

    Thanks and Best Regards,

    Lakshmi shetty

  • 0 in reply to Keerthy J
    Prodigy 205 points

    Hi Keerthy,

    I got below information from other discussion in forum:

    1. In SDK 7.1 , enableStaticIp in ndk.cfg is set to 0. 

    So I also tried dhcp.

    2. In dhcp, able to get the Ip address and ping from target to host. But unable to ping from host to target.

    Do I need to set anything for this?

    Thanks in advance,

    Lakshmi Shetty

  • 0 in reply to Lakshmi Shetty
    TI__Guru**** 171240 points

    Hi Lakshmi,

    Can you try with the latest SDK U-Boot so that we both are on the same page & it is easy to confirm the observations?

    https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-J721E


    Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Prodigy 205 points

    Hi Keerthy,

    Even I am using latest SDK Uboot(8.1).  Able to ping from target to host and when tftp is running in uboot, able to ping from host to target.

    In windows host I am running TFTP server and trying to load the  images in uboot using

    tftp ${loadaddr}  filename

    But it is not successful, getting maximum retry count reached error.

    Can you please help me to fix this issue?

    Thanks and Regards,

    Lakshmi Shetty

  • 0 in reply to Lakshmi Shetty
    TI__Guru**** 171240 points

    Hi Lakshmi,

    Thanks for the details. I am now able to reproduce the issue.

    Target ping --> Host -  Works
    Host Ping --> Target - fails.

    I tried the same experiment in kernel it works both ways.

    U-Boot is single threaded and is not always listening for incoming traffic. Hence its an expected behavior.

    Linux kernel on the other hand works well. Hope this clarifies the behavior.

    Closing this thread.

    - Keerthy