Return-Path: Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 01972E016E8 for ; Fri, 25 Oct 2013 09:44:07 -0700 (PDT) Received: from larry1 (ip68-108-244-202.sb.sd.cox.net [68.108.244.202]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0M932L-1VQ93W1Gf7-00Ch75; Fri, 25 Oct 2013 12:44:05 -0400 From: "Larry Weaver" To: "'Larry Weaver'" , "'Yocto discussion list'" References: <006e01ced103$09001330$1b003990$@LWConsulting.com> In-Reply-To: <006e01ced103$09001330$1b003990$@LWConsulting.com> Date: Fri, 25 Oct 2013 09:43:59 -0700 Message-ID: <00aa01ced1a1$6a9e6b70$3fdb4250$@LWConsulting.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 thread-index: AQIoEMbXoHGKQpN2/OrnFRoDOJOah5lSMn3g X-Provags-ID: V02:K0:2aJOglS8MoHEw7Wd4ZCMCiWSSLPvop1JGo+uKWCrEx8 PrL5/VOXUCGIOAwBiPaeJ3ceZVBxkxXthSOq0X1FtNtYN5rr2k nDN+GDLP32OBe0WqkOLMw2N9MXevzA5DmY6AWD120NApdRHq+f RvKXEr2FVrDUQXBKklQOlCFHWqoCLPFPaGTUzQPFW4g/jDYuZz ojdV6+WagsUn0ZJi29C0PkN2x4y6mmdgcDs6Q1StcsBqYroGVv OvL2MqILRBqlBZc3EWiX9ezedVDFIutJ9sxRA+b10aNXjiYOn/ mvL5WacE368EAONkb19GgzriwzSG3GOOuN7vsbq2kANX7vdGhP UOp7sBK/cyYE2C2TnO2ndz+W8b4loNF3BAaP3mzvk Subject: Re: problems with yocto eclipse ADT and beaglebone X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Oct 2013 16:44:08 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AB_01CED166.BE42A0B0" Content-Language: en-us ------=_NextPart_000_00AB_01CED166.BE42A0B0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I have managed to answer one of my questions. The tcf-agent from the = beagleboard build is apparently not complete. I set up a toolchain on = the beaglebone and compiled the tcf-agent from the git. The previous = tcf-agent didn=E2=80=99t have terminal or shell capability. The new one = does. . =20 So now if I can get the Build system derived toolchain directory figured = out I will have a full beaglebone development system. Any ideas? =20 Thanks, =20 Larry =20 =20 From: yocto-bounces@yoctoproject.org = [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Larry Weaver Sent: Thursday, October 24, 2013 2:50 PM To: 'Yocto discussion list' Subject: [yocto] problems with yocto eclipse ADT and beaglebone =20 I apologize in advance for my inexperience in this type of endeavor. = I've been a windows and microchip guy for some time, but the low cost = machines like the beaglebone have all my clients moving over to linux so = I need to become immersed in linux as well. =20 I've spent the last month studying and working with linux and have = reached something of an impasse (no forward progress for over 3 days = now). I'm not sure if this is the right platform to ask for eclipse ADT = help or if there is a better mailing list, but hopefully you will let me = know that. I also need to know if this is considered for text only or = can I include captured screen images (cut to only the info needed). =20 I have reinstalled a virtual Ubuntu machine, downloaded the yocto = angstrom scripts, compiled the kernel (and uboot) too many times to = count (and deployed to sd cards with success). While doing this I tried = various eclipse setups to do cross compiling and debugging with a lot of = success. A few days ago I saw that there was a new version of eclipse = (kepler) with new ADT tools that should make the cross compiling and = debugging much more elegant. I installed a new Ubuntu virtual machine, = got the angstrom scripts set up and the kernel compiled and then tried = to get the eclipse setup going. I've run into two problems that have me = completely stopped. =20 =20 The first is a configuration problem that I hope will be easy to get = past. When I try to set up the Build system derived toolchain debug = configuration (following the instructions in the Yocto Project = Development Manual) I have been completely stumped. I have run the = meta-ide-support with no problem, and the build directory and tmp = directory are there. No matter what directory off of setup-scripts I = use for a Toolchain Root Location it is rejected saying that the = toolchain directory does not contain a toolchain generated with "bitbake = meta-ide-support". I've rerun meta-ide-support many times, but no = subdirectory seems to contain the correct information when it is = finished. Where (and how) can I find the correct subdirectory that = contains the correct meta-ide-suport data? =20 Since that is a complete dead end for me at the moment, I bitbaked the = meta-toolchain and ran the resultant shell to extract the toolchain into = the /usr/local subdirectory. I then changed the debug configuration to = Standalone pre-built toolchain and selected the oecore-i686 directory = created off /usr/local as the toolchain root and it's subdirectory = sysroots as the sysroots directory. Eclipse is quite happy with this so = I thought I was finally to the next stage. I started a Yocto ADT C++ = project (again following the Yocto Project Development Manual), but ran = into some warnings when I compile the hello world project. These seem = to be warnings so I kind of ignored them (still currently doing that) = since I had other things I considered more important. T =20 Description Resource Path Location = Type Missing PROG dlltool HelloWorld -1 = Configure Problem Missing PROG arm-angstrom-linux-gnueabi-dlltool HelloWorld = -1 Configure Problem Missing PROG arm-angstrom-linux-gnueabi-mt HelloWorld = -1 Configure Problem =20 I then found that the new eclipse Yocto ADE setup requires the target to = be running a tcf-agent. According to the instructions I can add a = definition to my conf/local.conf file that will cause the tcf-agent to = be installed. I added this to the local.conf and recompiled. The = scripts sensed something had changed and gave me a new kernel image = file. Thinking I had success I put that on an sd card and booted, but = still no tcf-agent. I extracted the images and checked the differences = between them and it was very minimal. The image that was supposed to = have tcf-agent in it had some extra .sh files installed. While not an = expert on sh files these seem to have nothing to do with tcf-agent. = According to the Yocto Project Application Developers Guide the prebuilt = images of e-image-sato-sdk have the tcf-agent in them so I downloaded = the file for the beagleboard (if I compile using machine =3Dbeagleboard = instead of beaglebone it works fine on the beaglebone board) and = extracted the tcf-agent. I put it on the beaglebone and started it up. = Suddenly the eclipse Yocto plugin found the tcf daemon and I thought all = was good with the world. When I actually tried the debug it copied the = compiled program over to the beaglebone but then died with further = problems see tcf problems below). The program runs correctly on the = beaglebone if I execute it by hand. If I open up an eclipse remote = systems perspective over tcf, it sees the drive, process, etc. = I=E2=80=99m not sure how the tcf-agent needs to be started, so that may = be the problem. =20 =20 Any help on how to configure the Build System derived toolchain (what = directory is it looking for) or help on how to properly use tcf-agent so = that hostprocesses can start would be greatly appreciated. =20 =20 Thanks, =20 Larry =20 EXTRA_IMAGE_FEATURES =3D "tools-debug" =20 etc- | -run-postinsts =20 usr- | -share- | -run-postinsts =20 var- | -lib- | -opkg- | -info- | -run-postinsts.control -run-postinsts.list -run-postinsts.postinst -run-postinsts.postrm -run-postinsts.prerm =20 TCF problems =20 Error during file upload. Could not create the hostShellProcess. =20 Could not create the hostShellProcess. =20 An unexpected exception has occurred An unexpected exception has occurred An unexpected exception has occurred Could not create the hostShellProcess. =20 Could not create the hostShellProcess. =20 An unexpected exception has occurred An unexpected exception has occurred An unexpected exception has occurred Could not create the hostShellProcess. =20 Could not create the hostShellProcess. =20 Could not create the hostShellProcess. =20 An unexpected exception has occurred An unexpected exception has occurred An unexpected exception has occurred Could not create the hostShellProcess. =20 Could not create the hostShellProcess. =20 An unexpected exception has occurred An unexpected exception has occurred An unexpected exception has occurred =20 ------=_NextPart_000_00AB_01CED166.BE42A0B0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I have managed to answer = one of my questions.  The tcf-agent from the beagleboard build is = apparently not complete.  I set up a toolchain on the beaglebone = and compiled the tcf-agent from the git.  The previous tcf-agent = didn=E2=80=99t have terminal or shell capability.  The new one = does. .

 

So now if I can get the = Build system derived toolchain directory figured out I will have a full = beaglebone development system.  Any ideas?

 

Thanks,

 

Larry

 

 

From: = yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] = On Behalf Of Larry Weaver
Sent: Thursday, October 24, = 2013 2:50 PM
To: 'Yocto discussion list'
Subject: = [yocto] problems with yocto eclipse ADT and = beaglebone

 

I = apologize in advance for my inexperience in this type of endeavor.  = I've been a windows and microchip guy for some time, but the low cost = machines like the beaglebone have all my clients moving over to linux so = I need to become immersed in linux as well.

 

I've spent the last = month studying and working with linux and have reached something of an = impasse (no forward progress for over 3 days now).  I'm not sure if = this is the right platform to ask for eclipse ADT help or if there is a = better mailing list, but hopefully you will let me know that.  I = also need to know if this is considered for text only or can I include = captured screen images (cut to only the info = needed).

 

I have reinstalled a = virtual Ubuntu machine, downloaded the yocto angstrom scripts, compiled = the kernel  (and uboot) too many times to count (and deployed to sd = cards with success).  While doing this I tried various eclipse = setups to do cross compiling and debugging with a lot of success.  = A few days ago I saw that there was a new version of eclipse (kepler) = with new ADT tools that should make the cross compiling and debugging = much more elegant.  I installed a new Ubuntu virtual machine, got = the angstrom scripts set up and the kernel compiled and then tried to = get the eclipse setup going.  I've run into two problems that have = me completely stopped. 

 

The first is a = configuration problem that I hope will be easy to get past.  When I = try to set up the Build system derived toolchain debug configuration = (following the instructions in the Yocto Project Development Manual) I = have been completely stumped.  I have run the meta-ide-support with = no problem, and the build directory and tmp directory are there.  = No matter what directory off of setup-scripts I use for a Toolchain Root = Location it is rejected saying that the toolchain directory does not = contain a toolchain generated with "bitbake = meta-ide-support".  I've rerun meta-ide-support many times, = but no subdirectory seems to contain the correct information when it is = finished.  Where (and how) can I find the correct subdirectory that = contains the correct meta-ide-suport data?

 

Since that is a = complete dead end for me at the moment, I bitbaked the meta-toolchain = and ran the resultant shell to extract the toolchain into the /usr/local = subdirectory.  I then changed the debug configuration to Standalone = pre-built toolchain and selected the oecore-i686 directory created off = /usr/local as the toolchain root and it's subdirectory sysroots as the = sysroots directory.  Eclipse is quite happy with this so I thought = I was finally to the next stage.  I started a Yocto ADT C++ project = (again following the Yocto Project Development Manual), but ran into = some warnings when I compile the hello world project.  These seem = to be warnings so I kind of ignored them (still currently doing that) = since I had other things I considered more important.  = T

 

Description      &nbs= p;  = Resource           = ;  Path       = Location           = ;    Type

Missing PROG = dlltool      = HelloWorld          &nb= sp;           &nbs= p;  = -1            = Configure Problem

Missing PROG = arm-angstrom-linux-gnueabi-dlltool      &nb= sp;   = HelloWorld          &nb= sp;           &nbs= p;  = -1            = Configure Problem

Missing PROG arm-angstrom-linux-gnueabi-mt = HelloWorld          &nb= sp;           &nbs= p;  = -1            = Configure Problem

 

I then found that the = new eclipse Yocto ADE setup requires the target to be running a = tcf-agent.  According to the instructions I can add a definition to = my conf/local.conf file that will cause the tcf-agent to be = installed.  I added this to the local.conf and recompiled.  = The scripts sensed something had changed and gave me a new kernel image = file.  Thinking I had success I put that on an sd card and booted, = but still no tcf-agent.  I extracted the images and checked the = differences between them and it was very minimal.  The image that = was supposed to have tcf-agent in it had some extra .sh files = installed.  While not an expert on sh files these seem to have = nothing to do with tcf-agent.  According to the Yocto Project = Application Developers Guide the prebuilt images of e-image-sato= -sdk have the tcf-agent in them so I downloaded the = file for the beagleboard (if I compile using machine =3Dbeagleboard = instead of beaglebone it works fine on the beaglebone board) and = extracted the tcf-agent.  I put it on the beaglebone and started it = up.  Suddenly the eclipse Yocto plugin found the tcf daemon and I = thought all was good with the world.  When I actually tried the = debug it copied the compiled program over to the beaglebone but then = died with further problems see tcf problems below).  The program = runs correctly on the beaglebone if I execute it by hand.  If I = open up an eclipse remote systems perspective over tcf, it sees the = drive, process, etc.  I=E2=80=99m not sure how the tcf-agent needs = to be started, so that may be the problem.  =

 

Any help on how to = configure the Build System derived toolchain (what directory is it = looking for) or help on how to properly use tcf-agent so that = hostprocesses can start would be greatly appreciated.  =

 

Thanks,

 

Larry

 

EXTRA_IMAGE_FEATURES = =3D "tools-de= bug"

 

etc-

       = |

       = -run-postinsts          = ; 

usr-

       = |

         = -share-

        &nb= sp;           &nbs= p;   |

           = ;         &nb= sp;  -run-postinsts       &n= bsp;

var-

       = |

        = -lib-

        &nb= sp;      |

        &nb= sp;      -opkg-

           = ;         &nb= sp;    |

           = ;         &nb= sp;     -info-

           = ;         &nb= sp;           &nbs= p;   |

           = ;         &nb= sp;           &nbs= p;    -run-postinsts.control

           = ;         &nb= sp;           &nbs= p;     -run-postinsts.list

=

           = ;         &nb= sp;           &nbs= p;     -run-postinsts.postinst=

           = ;         &nb= sp;           &nbs= p;      -run-postinsts.postrm

           = ;         &nb= sp;           &nbs= p;       -run-postinsts.prerm

 

TCF = problems

 

Error = during file upload.

Could not create the = hostShellProcess.

 

Could not create the = hostShellProcess.

 

An unexpected exception has = occurred

An unexpected exception has = occurred

An unexpected exception has = occurred

Could not create the = hostShellProcess.

 

Could not create the = hostShellProcess.

 

An unexpected exception has = occurred

An unexpected exception has = occurred

An unexpected exception has = occurred

Could not create the = hostShellProcess.

 

Could not create the = hostShellProcess.

 

Could not create the = hostShellProcess.

 

An unexpected exception has = occurred

An = unexpected exception has occurred

An unexpected exception has = occurred

Could = not create the hostShellProcess.

 

Could not create the = hostShellProcess.

 

An unexpected exception has = occurred

An = unexpected exception has occurred

An unexpected = exception has occurred

           = ;  

------=_NextPart_000_00AB_01CED166.BE42A0B0--