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: ssh cannot connect to TDA4

Part Number: TDA4VM

Dear Ti,

The init process uses port 22, but SSH cannot connect to TDA4.

How can I login with SSH?

  • Hi,

    Which SDK are you using?

    Are you using the native linux driver or ethfw as your controller?

    Are you able to ping the board.

    Regards,
    Tanmay

  • SDK:   ti-processor-sdk-linux-j7-evm-08_06_00_11-Linux-x86-Install.bin

    filesystem:  tisdk-default-image-j7-evm.tar.xz

    using native linux driver.

    I can ping the board.

    Port 23 can be accessed using telnet, but SSH on port 22 cannot.

    Regards,

    Ni Hua

  • Hi,

    Can you see if port 22 is visible in output of "netstat -tulpn".

    Regards,
    Tanmay

  • Hi,

    Can you provide me the output of "systemctl list-units --all > systemctl-unit-log.txt". I will compare this with my setup and see if any services are inactive.

    Please pipe the output to a txt file and share the txt file.

    Regards,
    Tanmay

  • Hi,

    I couldn't see any significant service differences between your setup and mine. I am attaching my log here for your reference: 

    systemctl-unit-log-evm.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    UNIT LOAD ACTIVE SUB DESCRIPTION
    dev-disk-by\x2did-mmc\x2dS0J56X_0x2f688aee.device loaded active plugged /dev/disk/by-id/mmc-S0J56X_0x2f688aee
    dev-disk-by\x2did-mmc\x2dS0J56X_0x2f688aee\x2dpart1.device loaded active plugged /dev/disk/by-id/mmc-S0J56X_0x2f688aee-part1
    dev-disk-by\x2did-mmc\x2dS0J56X_0x2f688aee\x2dpart2.device loaded active plugged /dev/disk/by-id/mmc-S0J56X_0x2f688aee-part2
    dev-disk-by\x2did-mmc\x2dSC16G_0x5cf2cea6.device loaded active plugged /dev/disk/by-id/mmc-SC16G_0x5cf2cea6
    dev-disk-by\x2did-mmc\x2dSC16G_0x5cf2cea6\x2dpart1.device loaded active plugged /dev/disk/by-id/mmc-SC16G_0x5cf2cea6-part1
    dev-disk-by\x2did-mmc\x2dSC16G_0x5cf2cea6\x2dpart2.device loaded active plugged /dev/disk/by-id/mmc-SC16G_0x5cf2cea6-part2
    dev-disk-by\x2dlabel-boot.device loaded active plugged /dev/disk/by-label/boot
    dev-disk-by\x2dlabel-root.device loaded active plugged /dev/disk/by-label/root
    dev-disk-by\x2dlabel-rootfs.device loaded active plugged /dev/disk/by-label/rootfs
    dev-disk-by\x2dpartuuid-0cf58fbb\x2d01.device loaded active plugged /dev/disk/by-partuuid/0cf58fbb-01
    dev-disk-by\x2dpartuuid-0cf58fbb\x2d02.device loaded active plugged /dev/disk/by-partuuid/0cf58fbb-02
    dev-disk-by\x2dpartuuid-f65a2e4c\x2d01.device loaded active plugged /dev/disk/by-partuuid/f65a2e4c-01
    dev-disk-by\x2dpartuuid-f65a2e4c\x2d02.device loaded active plugged /dev/disk/by-partuuid/f65a2e4c-02
    dev-disk-by\x2dpath-platform\x2d4f80000.mmc.device loaded active plugged /dev/disk/by-path/platform-4f80000.mmc
    dev-disk-by\x2dpath-platform\x2d4f80000.mmc\x2dboot0.device loaded active plugged /dev/disk/by-path/platform-4f80000.mmc-boot0
    dev-disk-by\x2dpath-platform\x2d4f80000.mmc\x2dboot1.device loaded active plugged /dev/disk/by-path/platform-4f80000.mmc-boot1
    dev-disk-by\x2dpath-platform\x2d4f80000.mmc\x2dpart1.device loaded active plugged /dev/disk/by-path/platform-4f80000.mmc-part1
    dev-disk-by\x2dpath-platform\x2d4f80000.mmc\x2dpart2.device loaded active plugged /dev/disk/by-path/platform-4f80000.mmc-part2
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Can you ssh to the loopbak interface (127.0.0.1)?

    Are you able to do iperf/netperf profiling? Do you see any issues with that. What I am going for here is if you are able to have other TCP/UDP traffic? If this is possible, then It might be problem with he ssh binary itself.

    Regards,
    Tanmay

  • I can SSH to the loopback interface (127.0.0.1).
    TCP/UDP works, and I can login with telnet because there is a telnetd process.
    Port 22 is occupied by the init process, and no sshd process here.

  • Hi,

    Not sure what the could be in this case.

    Maybe you can gain more insight in this issue if you reach out to linux community in this case. The TI owned components (Hardware and device drivers) are working as expected here. The issue is elsewhere.

    Regards,
    Tanmay