Hi Sudhangathan
Thanks for replay.
So i have to build a separate image to run under the QEMU, for that do i
need to build it with my yocto project build environment with adding the
layers.
Or do i need to use the same build environment and just change the
local.conf file?
Keystone-II is a arm processor.
Thanks & Regards
Amit K
On Sat, Jul 20, 2013 at 8:41 AM, Sudhangathan BS <[email protected]>wrote:
> Hi Amit,
>
> You have to build separate images to be run on qemu.. You have to set it
> in your local.conf file.. i.e. u have to change your build-target..
>
> Images built to run on hardware cannot be run on qemu right now..
>
> Virtualization is only available upto processor level, and not the
> complete hardware...!
>
> Which processor is keystone-II using..?
>
> Best,
> Sudhangathan B S
>
>
> amit kumar <[email protected]> wrote:
>>
>>
>> Hi,
>>
>> I have built the Arago project for keystone-II successfully. The images
>> are available under the deploy/Images dir.
>>
>> I have already added my module into the kernel and recompiled the kernel
>> image.
>>
>>
>>
>> Now my doubt is before putting the image on actual hardware I want to run
>> it on QEMU. Is it possible to run the built images on QEMU?
>>
>> I tried to run using the following command but getting an error-
>>
>>
>> /**************************************************************/
>>
>> amit@amit-HP:~/OE/MCSDK/mcsdk/build$ runqemu
>> arago-tmp-external-linaro-toolchain/deploy/images/uImage-keystone-evm.bin
>> arago-tmp-external-linaro-toolchain/deploy/images/core-image-minimal-keystone-evm-20130718181345.rootfs.ubi
>> Error: unknown file arg
>> [arago-tmp-external-linaro-toolchain/deploy/images/core-image-minimal-keystone-evm-20130718181345.rootfs.ubi]
>>
>> Usage: you can run this script with any valid combination
>> of the following options (in any order):
>> QEMUARCH - the qemu machine architecture to use
>> KERNEL - the kernel image file to use
>> ROOTFS - the rootfs image file or nfsroot directory to use
>> MACHINE - the machine name (optional, autodetected from KERNEL filename
>> if unspecified)
>> RAMFS - boot a ramfs-based image
>> Simplified QEMU command-line options can be passed with:
>> nographic - disables video console
>> serial - enables a serial console on /dev/ttyS0
>> kvm - enables KVM when running qemux86/qemux86-64 (VT-capable CPU
>> required)
>> qemuparams="xyz" - specify custom parameters to QEMU
>> bootparams="xyz" - specify custom kernel parameters during boot
>>
>> Examples:
>> runqemu qemuarm
>> runqemu qemux86-64 core-image-sato ext3
>> runqemu path/to/bzImage-qemux86.bin path/to/nfsrootdir/ serial
>> runqemu qemux86 ramfs
>> runqemu qemux86 qemuparams="-m 256"
>> runqemu qemux86 bootparams="psplash=false"
>> amit@amit-HP:~/OE/MCSDK/mcsdk/build$
>>
>> /**********************************************************/
>>
>> The build step I followed from the arago project build link-
>>
>> "http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment";
>>
>>
>> Please let me know if I have to do something else to run the image under
>> QEMU.
>>
>> --
>> Thanks & Regards
>> Amit Kumar
>>
>> ------------------------------
>>
>> yocto mailing list
>> [email protected]
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
> --
> Sent from Kaiten Mail. Please excuse my brevity.
>
--
Thanks & Regards
Amit Kumar
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
