[OE-core] [oe-core] QEMU with ARM Cortex A9 with hard float configuration - Kernel panic

[Bruce Ashfield]

On Thu, Aug 29, 2013 at 2:53 PM,  <rewitt at declaratino.com> wrote:
>
>
>> -------- Original Message --------
>> Subject: Re: [OE-core] [oe-core] QEMU with ARM Cortex A9 with hard float
>> configuration - Kernel panic
>> From: Elvis Dowson <elvis.dowson at gmail.com>
>> Date: Thu, August 29, 2013 12:28 pm
>> To: Bruce Ashfield <bruce.ashfield at windriver.com>
>> Cc: OpenEmbedded Core Mailing List
>> <openembedded-core at lists.openembedded.org>
>>
>>
>> On Aug 29, 2013, at 8:23 PM, Bruce Ashfield <bruce.ashfield at windriver.com> wrote:
>>
>> > On 13-08-29 10:02 AM, Elvis Dowson wrote:
>> >> Hi Bruce,
>> >>
>> >> On Aug 29, 2013, at 4:35 PM, Bruce Ashfield <bruce.ashfield at windriver.com> wrote:
>> >>
>> >>> With that, it's always been a manual setup for me in the past. The typical
>> >>> workflow is to test them via the usermode NFS boot. Have you given
>> >>> that a go ?
>> >>
>> >> Does yocto have some wrapper script/command to setup nfs boot automatically
>> >> without too much manual configuration? The runqemu and runqemu-internal
>> >> scripts seems to indicate that, but haven't tried this before.
>> >>
>> >> Let me know if it exists! If not, if you could point me to a link that describes how
>> >> to set NFS boot, and use it to load a beagleboard image it would be great!
>> >
>> > This is supported right out of the box, and it should be documented in
>> > the project docs.
>> >
>> > Search for users-space NFS in http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html
>>
>> I saw this, its only for the rootfs. what I've read on the net alluded to the fact that you need to have
>> xload, uboot and the kernel image on a specific partition inside an sdcard image. Those were
>> the boot procedures used for the beagleboard using qemu.
>>
>> This is for -M beagle, with qemu-system-arm.
>>
>> Anyway, I just need a way to boot vexpress-a9 using QEMU. I'll send a private email, with the
>> patch to you, so that you can start off from where I left, in terms of modifications to poky-master
>> and be able to debug the issue directly at your end.
>
> I actually set up a build to get a vexpress-a15 booting in qemu with
> neon support. However, I didn't use the yocto kernel and just pointed at
> my own defconfig and kernel version 3.10.7. If it would be helpful for
> you, I could put my changes up on github.
>
> The weirdest thing was if I just used the defconfig that is in the
> kernel for vexpress it wouldn't boot, I had to tweak it a bit.

I have a vexpress A15 that works here as well, but I wouldn't mind comparing
configs. If you send it along, I'd have a look.

I'm not surprised it needed some changes .. when going to qemu mileage varies
with in tree defconfigs.

Bruce


>
>> Best regards,
>>
>> Elvis Dowson
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"