Bug 1964

Jack,

Can you be more precise, when saying you "accidentally built for beagleboard", what is your setings, e.g. when lauch Project->Change Yocto Project Settings, what do you have? (a scree shot will be great).  Then you're saying "I switched the build to qemu, then reconfigure the project"  what exactly are these steps, my understanding is you change the configuration in the Yocto Project Settings window?  Again, please attach a screen shot here.  By saying "reconfigure the project", are you referring to Project->Reconfigure Project?  Also, you mention the "external build script", is it the external qemu launch script, e.g. qemu_armv5te-poky-linux-gnueabi?  Also, have you checked Run->External Tools->External Tools Configurations... under program, do you see the expected qemy launch task?

Any detailed infomation will be great help for me to have a better understanding of your issue and further debug it.

Thanks,
Jessica

Created attachment 328 [details]
Screenshot1

Hi Jessica,

Sorry I wasn't more precise, looks like I didn't really have my brain in gear when I was writing it!

First I built a fresh core-image-minimal for beagleboard

I then set up an yocto eclipse project using the beagleboard rootfs and kernel, but to boot on qemu

It then wouldn't boot (obviously) so I went back and re-configured bitbake to build for qemuarm and build core-image-minimal using the same build directory as before

I then went back to my eclipse project, changed the kernel and rootfs to the new qemuarm rootfs and kernel and then did Project > Re-configure

What happened then was the external tools menu did not contain the ARMv5, but only the previous ARMv7 script.

That should be a lot clearer, sorry for my absent mindedness before!

Jack.

Created attachment 329 [details]
Screenshot2

Created attachment 330 [details]
Screenshot3

Please note that I changed the external build parameters MANUALLY, which is why is states ARMv5 in the External Tool Configuration screenshot - please don't let that confuse you, it was still ARMv7 before I changed it.

Jack,

One more thing to clear or help me verify.  Can you bring up your project's configuration window, make sure the toolchain location, sysroot location, qemu kernel file, and esp. Target Architecture are the right selections armv5.  Then reconfigure the project.  According to the code:

ILaunchConfigurationWorkingCopy w_copy = configType.newInstance(null, "qemu_"+elem.getStrTarget());

As long as your target selection is the right one, it should create the right qemu launcher for you.

Also, I've noticed that you're selecting the build tree toolchain, so I'm also assuming that when you switch to qemuarm, you also did run "bitbake meta-ide-support" to generate a new environment setup script for armv5, right?

BTW, I'll be attending ELC full week next week, please expect slow response.

thanks,
Jessia

Hi Jessica,

Unfortunatly I had a partition table meltdown late last week and cannot do any furter testing due to losing the build directory. However, I don't believe I did run bitbake meta-ide-support after I had changed from the beagleboard to qemuarm. I strongly believe that this would have fixed have the issue.

If I get chance I will test the theory again sometime, but until then I suggest the bug be closed!

Thanks for your help,
Jack.

updated per Jack's email info