TipsAndTricks/RunningEclipseAgainstBuiltImage: Difference between revisions
(Created page with "= Cookbook guide to Making an Eclipse Debug Capable Image = Suppose you are building images and would like to be able to use Eclipse and the Yocto Eclipse plugin to develop/de...") |
No edit summary |
||
| Line 4: | Line 4: | ||
So that the commands are specific and can be cut and pasted to try, we will assume the following: | So that the commands are specific and can be cut and pasted to try, we will assume the following: | ||
* Target Image-> core-image-sato | * Target Image-> core-image-sato | ||
* Target Machine -> qemux86 | * Target Machine -> qemux86 | ||
<br> | <br> | ||
The Steps | The Steps | ||
| Line 13: | Line 13: | ||
*** <code>EXTRA_IMAGE_FEATURES += " ssh-server-openssh "</code> | *** <code>EXTRA_IMAGE_FEATURES += " ssh-server-openssh "</code> | ||
**** This defaults to the openssl ssh server rather than dropbear. You can use either so this line can be omitted since the sftp server works with either. | **** This defaults to the openssl ssh server rather than dropbear. You can use either so this line can be omitted since the sftp server works with either. | ||
** Execute: <code> $bitbake core-image-sato</code> | |||
*** This makes a rootfs in tmp/deploy/images/qemux86/core-image-sato-qemux86.tar.bz2 | |||
* We need to build the toolchain eclipse will use | |||
** Execute <code> $bitbake core-image-sato -c populate_sdk </code> | |||
*** This makes sdk stuff such as the toolchains eclipse will use to build, | |||
* We need to build a version of qemu that can run natively on our workstation as well as a userspace nfs daemon. | |||
To run Eclipse against the newly built image: | |||
=== Adding static tap devices === | |||
It is often easier to preconfigure several tap devices so that qemu can run and use them without needing to be root or use sudo. To do this, run <code> runqemu-gen-tapdevs `id -u <username>` `id -g <username>` 4 `find ./tmp/sysroots -iname tunctl`</code> as root. This will make the inet devices tap0,tap1,tap2,tap3. You can see them with <code> ifconfig -a | grep tap </code>. Typically, tap0 is 192.168.7.1 and so when the first qemu is run it's address will be 192.168.7.2 and 192.168.7.1 will be that qemu instance's gateway. The runqemu-gen-tapdevs is located in bitbake/scripts. | |||
scripts/runqemu-gen-tapdevs | |||
Revision as of 22:08, 15 August 2016
Cookbook guide to Making an Eclipse Debug Capable Image
Suppose you are building images and would like to be able to use Eclipse and the Yocto Eclipse plugin to develop/debug a C/C++ application on either a remote hardware target or on qemu. This cookbook will explain the small number of steps needed to accomplish this.
So that the commands are specific and can be cut and pasted to try, we will assume the following:
- Target Image-> core-image-sato
- Target Machine -> qemux86
The Steps
- We need to build a core-image-sato that has the pieces needed by Eclipse, so we add/change the following in our conf/local.conf:
- We add the following to EXTRA_IMAGE_FEATURES in conf/local.conf
EXTRA_IMAGE_FEATURES += " eclipse-debug "- This adds gdbserver,tcf-agent (for Target Communication Framework), and openssh-sftp-server)
EXTRA_IMAGE_FEATURES += " ssh-server-openssh "- This defaults to the openssl ssh server rather than dropbear. You can use either so this line can be omitted since the sftp server works with either.
- Execute:
$bitbake core-image-sato- This makes a rootfs in tmp/deploy/images/qemux86/core-image-sato-qemux86.tar.bz2
- We add the following to EXTRA_IMAGE_FEATURES in conf/local.conf
- We need to build the toolchain eclipse will use
- Execute
$bitbake core-image-sato -c populate_sdk- This makes sdk stuff such as the toolchains eclipse will use to build,
- Execute
- We need to build a version of qemu that can run natively on our workstation as well as a userspace nfs daemon.
To run Eclipse against the newly built image:
Adding static tap devices
It is often easier to preconfigure several tap devices so that qemu can run and use them without needing to be root or use sudo. To do this, run runqemu-gen-tapdevs `id -u <username>` `id -g <username>` 4 `find ./tmp/sysroots -iname tunctl` as root. This will make the inet devices tap0,tap1,tap2,tap3. You can see them with ifconfig -a | grep tap . Typically, tap0 is 192.168.7.1 and so when the first qemu is run it's address will be 192.168.7.2 and 192.168.7.1 will be that qemu instance's gateway. The runqemu-gen-tapdevs is located in bitbake/scripts.
scripts/runqemu-gen-tapdevs
