On 09/05/2015 09:12 PM, Rudolf J Streif wrote:
> Robert,
>
> What version of Poky/OpenEmbedded Core (meta) are you using?
I am on the fido branch commit b50596d8f6e858e2e733f2d9913a19c6f3cd5863
plus
my own meta layer (which pulls in a 4.1.2 kernel with my own config) and
I build a
Hi Robert,
>
> Which Yocto version do you use? I use 1.8
I am using 1.8, too. Just sent another e-mail about the TCF agent. However,
that's only in addition since TCF is not used for debugging with GDB. Eclipse
wraps around GDB which then communicates directly with the GDB server on the
>
> I think I made some progress - see attached image.
Good.
>
> As you can see I stepped into printf and friends.
>
> For this to work I needed a few more things:
>
> 1) directory needs the be the same on host and target
>
> the executable on the host:
>
>
Hi,
On 09/05/2015 07:17 PM, Rudolf J Streif wrote:>>
> I do not have to do that. As a matter of fact the executable on my
target is
> copied to /usr/bin from the Eclipse workspace. See "Remote Absolute
File Path"
> in the Debug Configuration.
You are right. I erased the other folder on my
Robert,
What version of Poky/OpenEmbedded Core (meta) are you using?
I found that including Fido (1.8) the tcf-agent built by meta was stuck at
version 0.4.0. That causes issues with running on the target and getting the
console output back to Eclipse. That's now updated to 1.3 in master for
Hi,
I managed to step form HelloWorld into the C library and friends with a
.gdbinit file like this:
# don't use default libs from x86/Ubuntu:
set sysroot /opt/adt-target-sysroot/beagle-bone-black-ml
set solib-absolute-prefix /opt/adt-target-sysroot/beagle-bone-black-ml
set solib-search-path
