for the records.! i missed yocto@yoctoproject.org as 'cc' in the previous reply. --------------------------------- Sudhangathan BS Ph:(+91) 9731-905-205 ---------------------------------
On Wed, Jul 24, 2013 at 8:36 AM, Amit Kumar <amit.ku...@lntinfotech.com>wrote: > Hi, > I have follow the steps you have suggested. > I have edit the local.conf file. > But for that mcsdk build i am not able to directly run the- bitbake > <keystone-II image> > It required the toolchan path and the proper Machine name. > ////////////////// > amit@amit-HP:~/OE/MCSDK/mcsdk/build$ bitbake -k core-image-minimal > ERROR: No valid toolchain in PATH > amit@amit-HP:~/OE/MCSDK/mcsdk/build$ TOOLCHAIN_BRAND=linaro bitbake -k > core-image-minimal > ERROR: OE-core's config sanity checker detected a potential > misconfiguration. > Either fix the cause of this error or at your own risk disable the > checker (see sanity.conf). > Following is the list of potential problems / advisories: > > Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH > (armv5).Toolchain tunings invalid: > Tuning 'cortexa8thf-neon' has no defined features, and cannot be used. > > ERROR: Execution of event handler 'check_sanity_eventhandler' failed > amit@amit-HP:~/OE/MCSDK/mcsdk/build$ vim conf/setenv > amit@amit-HP:~/OE/MCSDK/mcsdk/build$ MACHINE=keystone-evm > TOOLCHAIN_BRAND=linaro bitbake -k core-image-minimal > Parsing recipes: 100% > |######################################################################################################################| > Time: 00:02:45 > Parsing of 1523 .bb files complete (0 cached, 1523 parsed). 1887 targets, > 169 skipped, 7 masked, 0 errors. > > Build Configuration: > BB_VERSION = "1.17.0" > TARGET_ARCH = "arm" > TARGET_OS = "linux-gnueabi" > MACHINE = "keystone-evm" > the above line should be as MACHINE ="qemuarm" your change in the build/conf/local.conf has not taken effect, or did you change it at all...?? please do read previous messages(e-mails) carefully..! > DISTRO = "arago" > DISTRO_VERSION = "2013.04" > TUNE_FEATURES = "${TUNE_FEATURES_tune-cortexa8thf-neon}" > TARGET_FPU = "soft" > meta-arago-distro > meta-arago-extras = "(nobranch):bbd86e9ef42185f62b52a1932f6aba7ea44ca0a6" > toolchain-layer > meta-oe = "(nobranch):f00028caf257e386c0f3ae46bd4b3ba53dd0729d" > meta-ti = "(nobranch):e060e4729a9f3f433eac6af717ccc22b37686129" > meta-linaro = "(nobranch):d0558fa4304592622423582f8b464e1c22cfe6f1" > meta = "(nobranch):0785489d558c34cacf5cb349949a15e27084efbf" > > NOTE: Resolving any missing task queue dependencies > NOTE: Preparing runqueue > NOTE: Executing SetScene Tasks > NOTE: Executing RunQueue Tasks > NOTE: Tasks Summary: Attempted 1550 tasks of which 1546 didn't need to be > rerun and all succeeded. > amit@amit-HP:~/OE/MCSDK/mcsdk/build$ > ///////////////// > > > But result still the same i can't be execute that image in qemu. I don't > know what wrong i am doing.... > If you get any idea from the log or u need more detailed log plz let me > know > > Thanks > Amit K > > ________________________________________ > From: yocto-boun...@yoctoproject.org [yocto-boun...@yoctoproject.org] On > Behalf Of Sudhangathan B S [sudhangat...@gmail.com] > Sent: Monday, July 22, 2013 9:09 AM > To: amit kumar > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Arago project image fail to run in QEMU > > These simple steps should do.. > > change your local.conf file to appear like this: > > # > # Machine Selection > # > # You need to select a specific machine to target the build with. There > are a selection > # of emulated machines available which can boot and run in the QEMU > emulator: > # > MACHINE ?= "qemuarm" <---- note > this > #MACHINE ?= "qemumips" > #MACHINE ?= "qemuppc" > #MACHINE ?= "qemux86" > #MACHINE ?= "qemux86-64" > # > # There are also the following hardware board target machines included for > # demonstration purposes: > # > #MACHINE ?= "atom-pc" > #MACHINE ?= "beagleboard" > #MACHINE ?= "mpc8315e-rdb" > #MACHINE ?= "routerstationpro" > # > # This sets the default machine to be qemux86 if no other machine is > selected: > #MACHINE ??= "qemux86" > > now run (internet/downloading is necessary): > "bitbake <keystone-II image>" > you can find the built images in deploy/images folder, which you don't > need to > access, then to start the virtual machine, just type (from the same path > as bitbake): > "runqemu qemuarm" > Type *your user password when asked for. Done. > > Best, > --------------------------------- > Sudhangathan BS > Ph:(+91) 9731-905-205 > --------------------------------- > > > On Mon, Jul 22, 2013 at 8:02 AM, amit kumar <kumaramit...@gmail.com > <mailto:kumaramit...@gmail.com>> wrote: > 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 <sudhangat...@gmail.com > <mailto:sudhangat...@gmail.com>> 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 <kumaramit...@gmail.com<mailto:kumaramit...@gmail.com>> 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 > yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> > https://lists.yoctoproject.org/listinfo/yocto > > > > > > -- > Sent from Kaiten Mail. Please excuse my brevity. > > > > -- > Thanks & Regards > Amit Kumar > > > The contents of this e-mail and any attachment(s) may contain confidential > or privileged information for the intended recipient(s). Unintended > recipients are prohibited from taking action on the basis of information in > this e-mail and using or disseminating the information, and must notify > the sender and delete it from their system. L&T Infotech will not accept > responsibility or liability for the accuracy or completeness of, or the > presence of any virus or disabling code in this e-mail" >
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto