• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 1024 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.

Remote System Explorer dependency

Chris Roed
Intellectual 960 points

Hello,

I downloaded the EZSDK v 7.00 and have been using the precompiled image on a beaglebone black.  With this configuration, I've been able to connect to the device using the remote system explorer without any issues.

Since the precompiled image is huge, I built my own distribution using the Arago-project.  For some reason, the remote system explorer doesn't work anymore.

All of my tests have used MACHINE ?=beaglbone.

I've built  "arago-console-image", and "arago-core-tisdk-image".  In each of these builds, I've added ARAGO_EXTRA_IMAGE_INSTALL += "dropbear openssh openssl"

I can run an SSH terminal into the board just fine, it's the sftp that doesn't seem to be working.  Are there other software packages I need to install to use sftp?

Thanks!

  • 0
    TI__Guru**** 161600 points
    Hi Chirs,

    To my knowledge you don't need additional packages. However you may need to configure your openssh properly, before using the sftp command.
    Can you try the following guide: wiki.archlinux.org/.../SFTP ?

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Intellectual 960 points

    Hi Yordon,

    I followed the instructions from that webpage.   That line "Subsytem sftp ..." is in the config file.  In addition, I copied the sshd_config file from the working filesystem to the yocto (non working) filesystem, and it still didn't work.

    I did a PS while the system was idle, and I verified that I'm running /usr/sbin/sshd

    I did a PS while I was trying to connect the sftp, and got

    /usr/sbin/sshd

    sshd: [accepted]

    sshd: [net]

    but it never seems to start the sftp-server (which does get started in the working distribution).  On the code composer studio end, I get a message that the connection was recieved, I put in a password, it informs me that the RSA key is different and then just fails to connect.

    *** SOLVED***

    Added this line to /etc/ssh/sshd_config 

    ForceCommand internal-sftp

    serverfault.com/.../sftp-and-filezilla-connection-closed-by-server-with-exitcode-128

  • 0 in reply to Yordan Kovachev
    Intellectual 960 points
    Hi Yordan, It turns out that I haven't solved my problem.

    It turns out that adding

    ForceCommand internal-sftp

    makes the SFTP work, but now SSHD refuses regular SSH connections. If I remove that line from the conf file and restart the SSHD service, then I can SSH but can't sftp. I know that this should work, because I was doing it on the prebuilt EZSDK 7.00 images.

    I noticed that the EZSDK is running both dropbear and openssh (is that how you get both functionalities?), but for some reason, my system will not start both services. My system starts openssh, and then fails on dropbear. If I switch the startup order, it will start dropbear, but fail on the openssh.
  • 0 in reply to Chris Roed
    Guru 20755 points

    Hi Chris,

    I have the same issue.

    Did you resolve it ?

    Thanks

    Ran