Qt Creator Embedded Debugging Setup

Hi Ralf,

The DebugExample.pro can be downloaded.  In the same wiki article you reference there is a Required Software section. In that section - #4 is the Debug Example link.

For debugger setup,  the port number is setup in the section named "Connecting a Linux Device". It is done while you are setting up the SSH settings.  It is port 22.

Also make sure you are setting your configuration to debug.  If it is a release version, you can not debug it.

Also there is another training wiki with much more detailed step by step info, you can verify your settings with this link if it still doesn't work - look at Lab 2 for QT Creator setup: http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_Hands_on_with_QT

Yes, I have noticed this and downloaded the example. It did not change. My own previous test settings for debugging remained unchanged.

Later, I read that: "Note: DaVinci EZSDK can only build the project. In order to deploy the executable onto the device with Qt Creator the DropBear binaries must be added to the Linux filesystem first".

Is this also true for my system (E335x EVM)?

I installed Dropbear and now i see at every boot of Ubuntu 10.03 (within VirtualBox) shortly following error messages:

Mount: mounting none on /dev/pts failed: Device or resource busy

ipconfig: eth0: SIOCGIFINDEX: No such device

ipconfig: no devices to configure

/scripts/init-premount/dropbear: .: line 32: can't open /tmp/net-eth0.conf

[   12.417869] piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr

The error messages disappear quickly because the Linux desktop starts.

On one hand, "/dev/pts" is not displayed on the Unbuntu 10.04 Linux system:

root@SoftwUbuntu32BitVM:/dev# ls -a /dev/pts*
.  ..  0  1  ptmx
root@SoftwUbuntu32BitVM:/dev#

On the other hand /dev/pts does seem to be present, because mkdir /dev/pts fails with the message, that it is already present:

root@SoftwUbuntu32BitVM:/dev# mkdir /dev/pts
mkdir: kann Verzeichnis „/dev/pts“ nicht anlegen: Die Datei existiert bereits
root@SoftwUbuntu32BitVM:/dev#

Is this a kernel bug?

I repeated subsequently the configuration from http://processors.wiki.ti.com/index.php/Qt_Creator_Embedded_Debugging_Setup. Result: The Project can be translated as a release and debug version and starts automatically on the target, but the Debug button is gray.

After repeating all steps of a new behavior. Maybe the settings for the target system before is only for the release version and were not automatically transferred to the debug variant. Or in this case there are delays and I was too fast on click?

Debug button is now ready, but both debug and release version can not be started anymore. Although the file is automatically rebuilt on the target, if it has been deleted.

It appears when I trying to start an error message, that the program could not be started, possibly problem with path or rights. Both displaying paths:

root/Projekte/DebugExample-build-desktop-Qt_4_7_2__Sitara-335xEVM-linux-devkit__Debug/DebugExample

or

/root/Projekte/DebugExample-build-desktop-Qt_4_7_2__Sitara-335xEVM-linux-devkit__Release/DebugExample

Starting the newly created and to target: /home/root/ copied programs currently works only over the serial port of the target system.

Hi Ralf,

Dropbear is already installed in the AM335x-05.05.00.00 Linux release you mentioned.  For your Ubuntu host, running the setup.sh script should automatically download all the packages you need. That is referenced in step 4 here: http://processors.wiki.ti.com/index.php/Sitara_Linux_Software_Developer%E2%80%99s_Guide#Start_your_Linux_Development 

You may want do a clean install.

I've seen issues where you can not start when an old program is running on the target.  Sometimes, I've had to kill a previous QT application over on the target before being able to start a new one.

Other thoughts - 

Under Tools->options->Linux Devices->Device Configurations, you can run the "Test" again which tests the connection with the Target EVM. If that works you should be able to launch.  If that does not work, you may try just to ping the target.

Sorry for the delay, I have made ​​14 days holiday.

Running root@SoftwUbuntu32BitVM:/usr/local/ti-sdk-am335x-evm# ./setup.sh

does not install anything. Only the configuration is executed again as described.

root@SoftwUbuntu32BitVM:/usr/local/ti-sdk-am335x-evm# apt-get install xinetd tftpd nfs-kernel-server minicom build-essential libncurses5-dev uboot-mkimage autoconf automake

also says that everything is already the newest version.

Tools->options->Linux Devices->Device Configurations, "Test" gives the following (translated from the German):

------------------------

connect to Host...
Checking kernel version...
Linux 3.2.0 armv7l

Check availability of the specified ports...
All specified ports are available.

Check Qt-Libraries...
Error on check Qt-Libraries: sh: dpkg-query: not found

Error in test connectivity...

Failed to test the device.

------------------------

I suspect "QML debugging" is a new option in Qt Creator 2.4.1, which is not necessarily needed. Is that correct?

Ping the target is ok. The IP is correct:

------------------------

ping 192.168.1.4

PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.
64 bytes from 192.168.1.4: icmp_seq=1 ttl=64 time=0.849 ms
64 bytes from 192.168.1.4: icmp_seq=2 ttl=64 time=0.669 ms
64 bytes from 192.168.1.4: icmp_seq=3 ttl=64 time=0.530 ms

------------------------

If I manually delete the executable file "DebugExample" from the target and then start debugging, the file will be automatically recreated. However, in the QT Creator status window appear immediately after "debugging starts" ... "finished debugging" without any error message.

I can run the newly created program currently only manually on the target, the graphical interface of the program then appear on the screen of the target.

If I only try to run (not debug) the executable from QT Creator, the following error messages appear:

------------------------

Start /root/Projekte/DebugExample-build-desktop-Qt_4_7_2__Sitara-335xEVM-linux-devkit__Release/DebugExample...The program could not be started. It is possible that the path or the permissions are not sufficient?

/root/Projekte/DebugExample-build-desktop-Qt_4_7_2__Sitara-335xEVM-linux-devkit__Release/DebugExample completed, return value of -1

------------------------

Maybe the QT creator try to start the DebugExample executable on my local Ubuntu system and not on the target. If I click on the QT Creator to "Debug" -> "Debug external running Application", I see the process list of my local Ubuntu system, not the process list of the remote target. Is that correct or a mistake?

The QT Creator is started by me from a script StartQtCreator.sh as follows:

------------------------

. /usr/local/ti-sdk-am335x-evm/linux-devkit/environment-setup
/opt/QtSDK/QtCreator/bin/qtcreator

------------------------