We offer many ready-to-use apps, among them a serial-over-IP (SoI) app and Modbus Gateway app.
Tibbo > Linux Ecosystem > C++ API
Eclipse is a highly-customizable integrated development environment (IDE). It supports many different programming languages and environments through plugins.
It is recommended to install TCF-agent in your LTPS box for convenient debugging with Eclipse IDE. Please, read instructions for Installing Debugger on LTPS.
The most convenient and quick way to start developing with Eclipse is to get Eclipse with all required development plugins from Tibbo website.
Download Eclipse from LTPS SDK download area: http://tibbo.com/downloads/LTPS/SDK/ and unpack it to your home directory and run Eclipse IDE:
[dv@dvpc ~]$ wget http://tibbo.com/downloads/LTPS/SDK/EclipseOx-2.4.tar.gz
[dv@dvpc ~]$ tar -cxvf ./EclipseOx-2.4.tar.gz
[dv@dvpc ~]$ cd ~/EclipseOx-2.4/
[dv@dvpc EclipseOx-2.4]$ ./eclipse
Choose Workspace location and close the Welcome message.
Click Window (in the top menu) - Preferences.
Find Yocto Project SDK in the left menu.
Find Toolchain Root Location and click Browse. Set it to the folder of your SDK installation (/home/dv/klmsdk/ in my case).
Find Sysroot Location and click Browse. Set it to the subfolder sysroots/cortexa8hf-neon-tps-linux-gnueabi at your SDK installation root directory (/home/dv/klmsdk/sysroots/cortexa8hf-neon-tps-linux-gnueabi in my case).
Click Apply. Click Apply and Close.
Click File (in the top menu) - New - C/C++ Project.
In the popup dialog select All in the left menu and C Managed Build. Click Next.
Give the project a name ("myproject" in our case).
Expand Yocto Project SDK Autotools Project in the left menu tree ("Project Type" panel) and choose Hello World ANSI C Autotools Project.
GNU Autotools Toolchain will be activated in the menu at the Toolchains panel.
Click Next.
Review the project configuration and click Finish.
New project workspace will be activated.
Expand the project tree in the Project Explorer menu and right-click on the project name. Choose Reconfigure Project in the context menu.
Autotools "configure" program from the LTPS SDK will be executed. The results will be shown in the Console window.
Right-click on the project name and choose Build Project.
Autotools "make" program from the LTPS SDK will be executed. The results will be shown in Console window.
Now we have a program built for our target device.
Expand the project tree in the Project Explorer panel, find src subtree and expand it. Double-click on your C-file name ("myproject.c" in my case).
File source will be loaded into the editor. Scroll down to the "main()" function definition. Right-click on the line numbers area to the left of the
puts("Hello World"); /* prints Hello World */
line and choose Toggle Breakpoint in the pop-up menu.
In the top menu, choose Run - Debug As... - Remote Application.
Expand C/C++ Remote Application and choose myproject_gdb_arm-tps-linux-gnueabi to see the debugger settings.
Find the Conection field and click New and choose connection type SSH in the pop-up window. Click OK.
Name your connection ("LTPS .218" in our case).
Input the IP-address of your target LTPS device.
Username is root.
Password is your root user password ("123" in our case).
Click Finish.
Eclipse may ask if you want to store your password. Agree or disagree and close the password save dialog.
Go back to the "Debug Configurations" dialog. Click Apply.
Note a warning message at the top of the Window:
"Remote executable path is not specified."
Find Remote Absolute File P for C/C++ Application field, click Browse and choose the location for your application in the remote LTPS filesystem (we choose "/home/root/myproject" for our project).
Click Apply, click Debug.
The Debug Configurations dialog will be closed and you'll go back to the source editor.
The console reports: GDBServer on the remote LTPS device has been started.
Press F11 to debug (the shortcut for Run - Debug As... in the top menu).
Eclipse will show the "Confirm Perspective Switch" dialog.
Click Yes to switch to debug workspace.
The Debug workspace will be activated, the program will be stopped at the breakpoint, the call stack and other debugger panels will be shown.
Now you may step over the function calls and control the variables state.
Next time, when you deal with some other project the debugging and deploying will be easier:
You have already defined the toolchain location and configured your target device.