"No such file or Directory found error in deploying to a TI Sitara AM355x EVM Kit"
-
Hello,
I am having a problem deploying to a Sitara AM355x EVM Kit after compilation, it keeps giving me the "No such file or Directory found error". However after I did the "New Generic Linux Device Configuration Setup" and did the Device test, it says that the "Device Test Finished Successfully". When I press the green arrow button there is a message saying Deploying finished 3 of 4 and it will just sit there like it got stuck or something.
But the funny thing is I am able to copy the executable using the command scp helloworld root@192.168.0.100:/home/root from the Linux shell from the host laptop to the remote Linux device. Here is the project file.
QT += core gui webkit
greaterThan (QT_MAJOR_VERSION, 4): QT += widgets
TARGET = terminal
TEMPLATE = appSOURCES += main.cpp
terminal.cppHEADERS += terminal.h
FORMS += terminal.ui
keyboard/keyboard.uitarget.path += /home/root
INSTALLS += target -
Hello,
I am having a problem deploying to a Sitara AM355x EVM Kit after compilation, it keeps giving me the "No such file or Directory found error". However after I did the "New Generic Linux Device Configuration Setup" and did the Device test, it says that the "Device Test Finished Successfully". When I press the green arrow button there is a message saying Deploying finished 3 of 4 and it will just sit there like it got stuck or something.
But the funny thing is I am able to copy the executable using the command scp helloworld root@192.168.0.100:/home/root from the Linux shell from the host laptop to the remote Linux device. Here is the project file.
QT += core gui webkit
greaterThan (QT_MAJOR_VERSION, 4): QT += widgets
TARGET = terminal
TEMPLATE = appSOURCES += main.cpp
terminal.cppHEADERS += terminal.h
FORMS += terminal.ui
keyboard/keyboard.uitarget.path += /home/root
INSTALLS += targetWe have seen the same problem and are in the process to investigate this issue. We should get back to you when we find the root cause. In the mean time, if you do not get any response here, try to post the issue to QT Bug report and you may get some quick response.