Yocto Programming with Eclipse: Difference between revisions
(Created page with "<!-- Set release according to "release" parameter in URL and use MORTY_BETA_DART-6UL as default --> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!-- --> {{#lst:Yocto_Plat...") |
No edit summary |
||
(13 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
<!-- Set release according to "release" parameter in URL and use | <!-- Set release according to "release" parameter in URL and use MORTY_v1.0_DART-6UL as default | ||
--> {{# | --> {{INIT_RELEASE_PARAM|RELEASE_MORTY_V1.0_DART-6UL}} <!-- | ||
--> {{#lst: | --> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!-- | ||
--> {{#lst:B2QT_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!-- | |||
--> {{COMMON_YOCTO_VARS}} <!-- | |||
--> {{PageHeader|{{#var:HARDWARE_NAME}} - Yocto Programming with Eclipse}} {{DocImage|category1={{#var:HARDWARE_NAME}}|category2=Yocto}} | --> {{PageHeader|{{#var:HARDWARE_NAME}} - Yocto Programming with Eclipse}} {{DocImage|category1={{#var:HARDWARE_NAME}}|category2=Yocto}} | ||
This guide describes how to use Eclipse to develop and debug applications on the | This guide describes how to use Eclipse to develop and debug applications on the {{#var:HARDWARE_NAME}}. | ||
__toc__ | __toc__ | ||
= Create your rootfs with Eclipse debug support = | = Create your rootfs with Eclipse debug support = | ||
Append the following to the conf/local.conf file in your Yocto build directory: | Append the following to the conf/local.conf file in your Yocto build directory: | ||
... | |||
EXTRA_IMAGE_FEATURES = " \ | |||
debug-tweaks \ | |||
tools-debug \ | |||
eclipse-debug \ | |||
" | |||
IMAGE_INSTALL{{#var:YOCTO_OVERRIDE_PREFIX}}append = " \ | |||
tcf-agent \ | |||
openssh-sftp-server \ | |||
" | |||
<!-- Since Zeus and above, the dropbear recipe introduced a patch that limits some ciphers | |||
that are defined as weak. Eclipse still seems to use those ciphers, causing ssh compatible | |||
issues. Let's add here a note for the customers: --> | |||
For Yocto Zeus and above, using dropbear, one may need to append the following to the conf/local.conf file to avoid SSH compatible ciphers issues: | |||
= | PACKAGECONFIG{{#var:YOCTO_OVERRIDE_PREFIX}}remove{{#var:YOCTO_OVERRIDE_PREFIX}}pn-dropbear = " disable-weak-ciphers" | ||
Now bitbake your image. | |||
= Host tools = | |||
To install the toolchain follow {{Varlink2|Yocto Toolchain installation|{{#var:RELEASE_LINK}}}} guide. | |||
= Eclipse installation = | = Eclipse installation = | ||
Line 123: | Line 101: | ||
Select "Preferences" from the "Window" menu.<br> | Select "Preferences" from the "Window" menu.<br> | ||
* Click on "Yocto Project ADT" from the left options and then under "Cross Compiler Options:" select the "Standalone pre-built toolchain" radio button. | * Click on "Yocto Project ADT" from the left options and then under "Cross Compiler Options:" select the "Standalone pre-built toolchain" radio button. | ||
* Under "Toolchain Root Location:" enter " | * Under "Toolchain Root Location:" enter "{{#var:TOOLCHAIN_ROOT_LOCATION}}". | ||
* Under "Sysroot Location:" enter " | * Under "Sysroot Location:" enter "{{#var:TOOLCHAIN_TARGET_SYSROOT_LOCATION}}" | ||
* Under "Target Options:" make sure "External HW" is selected. | * Under "Target Options:" make sure "External HW" is selected. | ||
* Click OK. | * Click OK. | ||
Line 176: | Line 154: | ||
== Remote debug == | == Remote debug == | ||
Follow the below steps to remotely debug your application on the | Follow the below steps to remotely debug your application on the {{#var:HARDWARE_NAME}}. | ||
* Select "Debug Configurations..." from the "Run" menu. | * Select "Debug Configurations..." from the "Run" menu. | ||
Line 183: | Line 161: | ||
* Enter the absolute path which you want to deploy the application to. Use the "Remote Absolute File Path for C/C++Application:" field. For example, enter /home/root/hello | * Enter the absolute path which you want to deploy the application to. Use the "Remote Absolute File Path for C/C++Application:" field. For example, enter /home/root/hello | ||
* Click on the "Debugger" tab to see the cross-tool debugger you are using. | * Click on the "Debugger" tab to see the cross-tool debugger you are using. | ||
[[File:Eclipse_DebugConfiguration_Degugger.png]] | |||
* Check the lower red rectangle contents and be sure that the selected launcher is the "Automatic Remote Debugger Launcher" | |||
* If any other launcher is selected: | |||
** copy to clipboard the contents of upper red rectangle | |||
** select "Automatic Remote Debugging Launcher" in the lower red rectangle | |||
** paste from the clipboard to reset the contents of the upper red rectangle | |||
** remember that the debugger path is expected to be something like <sdk_path>/sysroots/x86_64-fslcsdk-linux/usr/bin/arm-fslc-linux-gnueabi/arm-fslc-linux-gnueabi-gdb | |||
* Click on the "Main" tab. | * Click on the "Main" tab. | ||
* Hit Debug | * Hit Debug |
Latest revision as of 21:14, 23 August 2024
This page is using the default release RELEASE_MORTY_V1.0_DART-6UL.
To view this page for a specific Variscite SoM and software release, please follow these steps:
- Visit variwiki.com
- Select your SoM
- Select the software release
This guide describes how to use Eclipse to develop and debug applications on the DART-6UL.
Create your rootfs with Eclipse debug support
Append the following to the conf/local.conf file in your Yocto build directory:
... EXTRA_IMAGE_FEATURES = " \ debug-tweaks \ tools-debug \ eclipse-debug \ " IMAGE_INSTALL_append = " \ tcf-agent \ openssh-sftp-server \ "
For Yocto Zeus and above, using dropbear, one may need to append the following to the conf/local.conf file to avoid SSH compatible ciphers issues:
PACKAGECONFIG_remove_pn-dropbear = " disable-weak-ciphers"
Now bitbake your image.
Host tools
To install the toolchain follow Yocto Toolchain installation guide.
Eclipse installation
Download Eclipse
Download Eclipse Luna from here: http://www.eclipse.org/downloads/packages/eclipse-ide-cc-developers/lunasr2
Run the following command to unpack and install the downloaded Eclipse IDE tarball into a clean directory using the default name eclipse:
$ cd ~ $ tar -xf ~/Downloads/eclipse-cpp-luna-SR2-linux-gtk-x86_64.tar.gz
Configuring the Eclipse IDE
Run the Eclipse IDE with the following command:
$ cd eclipse $ ./eclipse
Select a new workspace (you can just click OK).
Choose "Install New Software" from the "Help" pull-down menu.
- In the "Work with" area select "Luna - http://download.eclipse.org/releases/luna".
- Uncheck the "Hide items that are already installed" box.
- Expand the "Linux Tools" option and select:
Linux Tools LTTng Tracer Control Linux Tools LTTng Userspace Analysis LTTng Kernel Analysis
- Expand the "Mobile and Device Development" option and select:
C/C++ Remote Launch (Requires RSE Remote System Explorer) Remote System Explorer End-user Runtime Remote System Explorer User Actions Target Management Terminal (Core SDK) TCF Remote System Explorer add-in TCF Target Explorer
- Expand the "Programming Languages" option and select:
C/C++ Autotools Support C/C++ Development Tools
- Click Next twice, accept the necessary EULA and click Finish.
- If asked if you trust the Eclipse certificates, make sure you select the certificates and click OK.
- Click to restart Eclipse when asked to.
Adding the Yocto Plug-in to the Eclipse IDE
In Eclipse, select "Install new Software" from the "Help" menu.
- Click the "Add..." button to add a repository, enter the following and click OK.
Name: Yocto Jethro (you can actually use any name) Location: http://downloads.yoctoproject.org/releases/eclipse-plugin/2.0/luna/
- Make sure the repository above is selected on the "Work with" drop-down menu and select the following plug-ins from the list:
Yocto Project ADT Plug-in Yocto Project Bitbake Commander Plug-in Yocto Project Documentation plug-in
- Click Next twice, accept the necessary EULA and click Finish.
- Click to restart Eclipse when asked to.
Configuring the Eclipse Yocto Plug-in
In this section we will configure the Cross Compiler and the Target options. These will then be used as default for your projects from within your workspace.
Select "Preferences" from the "Window" menu.
- Click on "Yocto Project ADT" from the left options and then under "Cross Compiler Options:" select the "Standalone pre-built toolchain" radio button.
- Under "Toolchain Root Location:" enter "/opt/fslc-x11/2.2.1".
- Under "Sysroot Location:" enter "/opt/fslc-x11/2.2.1/sysroot/armv7at2hf-neon-fslc-linux-gnueabi"
- Under "Target Options:" make sure "External HW" is selected.
- Click OK.
Create and run a simple application
Create the Project
You can create two types of projects: Autotools-based, or Makefile-based. This section describes how to create Autotools-based projects from within the Eclipse IDE. To create a project based on a Yocto template and then display the source code, follow these steps:
- File->New->C Project
- Click "Yocto Project ADT Autotools Project".
- Select "Hello World ANSI C Autotools Project". This is an Autotools-based project based on a Yocto template.
- Enter a name for the project under the "Project name" field. Do not use hyphens as part of the name.
- Click "Next".
- Add information in the Author field and make sure the License field is correct.
- Click "Finish".
- Click on "Workbench".
- You should now be in the C/C++ perspective. The left-hand navigation pane shows your project. You can display your source by double clicking the project's source file.
- Hit Ctrl+B or click the hammer icon to build your project.
Create communication link
Using the console of your target set a password with "passwd" command. choose a simple one named "root".
The target should be connected to the network via Ethernet or WIFI.
Use the "ifconfig" command on the target to get its IP address.
From Eclipse:
- Window->Open Perspective->Other
- Double click on Remote System Explorer
- In the left bar right click and New->Connection
- Choose TCF and click Next
- Set the Host name to the target's IP address and click Finish
- On the left bar right click on the target IP and select connect
- Set "User ID:" to root, "Password:" to root and check the "Save password"
- Enter the root password again in the next poop up.
Once connected you can browse the target file system, browse target process and lunch a terminal to the target.
Remote debug
Follow the below steps to remotely debug your application on the DART-6UL.
- Select "Debug Configurations..." from the "Run" menu.
- In the left area, expand C/C++ Remote Application.
- Locate your project and select it to pop up a new tabbed view in the Debug Configurations Dialog.
- Enter the absolute path which you want to deploy the application to. Use the "Remote Absolute File Path for C/C++Application:" field. For example, enter /home/root/hello
- Click on the "Debugger" tab to see the cross-tool debugger you are using.
- Check the lower red rectangle contents and be sure that the selected launcher is the "Automatic Remote Debugger Launcher"
- If any other launcher is selected:
- copy to clipboard the contents of upper red rectangle
- select "Automatic Remote Debugging Launcher" in the lower red rectangle
- paste from the clipboard to reset the contents of the upper red rectangle
- remember that the debugger path is expected to be something like <sdk_path>/sysroots/x86_64-fslcsdk-linux/usr/bin/arm-fslc-linux-gnueabi/arm-fslc-linux-gnueabi-gdb
- Click on the "Main" tab.
- Hit Debug
- Accept the debug perspective.
You can now run and debug your program via eclipse. The actual program execution is done on the target, and the output is seen on the Remote Shell on Eclipse.