[yocto] How to change machine name in yocto

Hans Beckérus hans.beckerus at gmail.com
Thu Sep 12 02:32:14 PDT 2013 

On Thu, Sep 12, 2013 at 11:08 AM, amit tomer <amittomer25 at gmail.com> wrote:
> Hans, there are couple issue I have seen after I changed machine name to k2.
> First issue was->
>
> NOTE: make -j 16 CROSS_COMPILE=arm-poky-linux-gnueabi-
> CC=arm-poky-linux-gnueabi-gcc  --sysroot=/build/tmp/sysroots/k2
> argon_k2_config
> | make: *** No rule to make target `argon_k2_config'.  Stop.
> | make: *** [argon_k2_config] Error 1
> | ERROR: oe_runmake failed
> | ERROR: Function failed: do_compile (see
> /build/tmp/work/k2-poky-linux-gnueabi/u-boot/2013.01-r3+gitrAUTOINC+64c3aae8986eb05aa9b7c326a9432810839120b1/temp/log.do_compile.19901
> for further information)
> ERROR: Task 74 (/meta-ti/recipes-bsp/u-boot/u-boot_2013.01.bb, do_compile)
> failed with exit code '1'
>
>
> Now what I did was i replace pyp-ii to k2 at various places in
> :meta-xyz/recipes-bsp/u-boot/uboot.bbappend
>
> like below
>
> SRCREV_pyp-ii = "0ecb4d63c273abc395d11906ebf59d80263394e3" to SRCREV_k2 =
> "0ecb4d63c273abc395d11906ebf59d80263394e3"
>
> And this issue was resolved.
>
> Second issue I faced was->
>
> ERROR: Task 324 (/meta-xyz/recipes-kernel/linux/linux-pyp-ii.bb, do_compile)
> failed with exit code '1'
>
> Now to resolve it I renamed /meta-xyz/recipes-kernel/linux/linux-pyp-ii.bb
> to /meta-xyz/recipes-kernel/linux/linux-k2.bb
>
> and its fixed now
>
> But now I run into another problem after doing bitbake
>
>
> Build Configuration:
> BB_VERSION        = "1.18.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "RedHatEnterpriseServer-5.6"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "zzz_ii"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.4.1"
> TUNE_FEATURES     = "armv7a vfp neon callconvention-hard cortexa15"
> TARGET_FPU        = "vfp-neon"
> meta
> meta-yocto
> meta-yocto-bsp    = "(nobranch):beda5013e46da16a3d76f095869a5a5c5b1bc08a"
> meta-linaro-toolchain =
> "(nobranch):0f679485b945c1b929a44d1865eb517a096ac4ef"
> meta-ti           = "(nobranch):3eb71003af3ebb025285493721332111ac581a42"
> meta-nsn          = "master:d2f9cf6bc90df95d53db0973e07a52394191faf5"
>
> NOTE: Resolving any missing task queue dependencies
> NOTE: multiple providers are available for runtime kernel-image
> (linux-keystone, linux-k2)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match kernel-image
> NOTE: multiple providers are available for runtime kernel-devicetree
> (linux-keystone, linux-k2)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match
> kernel-devicetree
>
Now you suddenly changed to zzz_ii, or what?
Honestly, I am bit confused about the whole thing and what you are
trying to accomplish here really :(
You should also make sure to use PREFERRED_PROVIDER to point out what
version of the kernel you wish to build in your machine .conf. And,
are you not setting UBOOT_MACHINE = "<your uboot target>"?
Also, I set KERNEL_DEVICETREE in my kernel recipe to point out which
.dts file to build. Maybe I am doing it wrong but that has worked fine
for me so far. Maybe someone else that understands your use case
better can tune in and assist?

>
> NOTE: Preparing runqueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> Currently 1 running tasks (3160 of 3233):
> 0: linux-keystone-3.6.6-r0 do_fetch (pid 27433)
>
> and this job is hagging here for last 20 mins
>
> Could you tell me is it expected or what??
>
Probably not, but fetching the kernel source tree might take a *very* long time.
Also the server may experience problems. Try cloning the kernel source
manually using the URL from you recipe to check if things are
progressing normally.

>
>
>
>
>
> On Thu, Sep 12, 2013 at 1:25 PM, Hans Beckérus <hans.beckerus at gmail.com>
> wrote:
>>
>> On Thu, Sep 12, 2013 at 9:11 AM, amit tomer <amittomer25 at gmail.com> wrote:
>> > Thanks Hans for kind reply
>> >
>> > I somehow manage to change the machine name in build confriguation
>> >
>> > Build Configuration:
>> > BB_VERSION        = "1.18.0"
>> > BUILD_SYS         = "x86_64-linux"
>> > NATIVELSBSTRING   = "RedHatEnterpriseServer-5.6"
>> > TARGET_SYS        = "arm-poky-linux-gnueabi"
>> > MACHINE           = "k2"
>> > DISTRO            = "poky"
>> > DISTRO_VERSION    = "1.4.1"
>> > TUNE_FEATURES     = "armv7a vfp neon callconvention-hard cortexa15"
>> > TARGET_FPU        = "vfp-neon"
>> > meta
>> > meta-yocto
>> >
>> >
>> > Now machine name is K2 for me,what I did is rename the
>> > "/meta-xyz/conf/machine/pyp-ii.conf  to k2.conf and set  MACHINE=k2 in
>> > build/conf/local.conf .
>> >
>> >
>> > But my bitbake is still failing with different error this time.
>> >
>> > Could you please let me know whats needs to be changed in
>> > "build/conf/bblayers.conf file"  in order to change machine name. below
>> > is
>> > my "build/conf/bblayers.conf" file
>> >
>> Since your MACHINE is presented as "k2", the .conf file has been
>> picked up correctly. So far so good.
>> You should not need to add anything else in your bblayers.conf.
>> The new errors you are referring to might have nothing to do with your
>> current MACHINE setting.
>> You need to show the actual error you get. Not much we can do to help
>> otherwise.
>>
>> Thanks.
>> Hans
>>
>> >
>> > # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
>> > # changes incompatibly
>> > LCONF_VERSION = "6"
>> >
>> > BBPATH = "${TOPDIR}"
>> > BBFILES ?= ""
>> >
>> > BBLAYERS ?= " \
>> >   ${TOPDIR}/../poky/meta \
>> >   ${TOPDIR}/../poky/meta-yocto \
>> >   ${TOPDIR}/../poky/meta-yocto-bsp \
>> >   ${TOPDIR}/../linaro/meta-linaro-toolchain \
>> >   ${TOPDIR}/../meta-ti \
>> >   ${TOPDIR}/../meta-nsn \
>> >   "
>> > BBLAYERS_NON_REMOVABLE ?= " \
>> >   ${TOPDIR}/../poky/meta \
>> >   ${TOPDIR}/../poky/meta-yocto \
>> >   "
>> >
>> > BBMASK = "meta-ti/recipes-misc"
>> > BBMASK .= "|meta-ti/recipes-graphics"
>> >
>> > # meta-linaro is only able to supply linaro-4.7 without
>> > # toolchain-layer, therefore mask out linaro-4.6.  Note
>> > # that an associated change in local.conf to remove
>> > # toolchain-layer from LAYERDEPENDS_linaro is required.
>> > BBMASK .= "|gcc.*_linaro-4\.[^7]"
>> >
>> > # mask out lrc specific layer(s)
>> > BBMASK .= "|meta-nsn/recipes-connectivity-lrc"
>> >
>> >
>> >
>> >
>> > On Wed, Sep 11, 2013 at 8:26 PM, Hans Beckérus <hans.beckerus at gmail.com>
>> > wrote:
>> >>
>> >> The MACHINE is simply a pointer to a machine specific configuration
>> >> file. So if you set your MACHINE=foo, then somewhere in your bblayer
>> >> path(s) you need to make sure that a conf/machine/foo.conf is
>> >> available. Then it will use that.
>> >> Typically, I think you should do this in your own bsp meta, eg.
>> >> meta-foo/conf/machine/foo.conf and then add meta-foo to your
>> >> build/conf/bblayers.conf file.
>> >>
>> >> Thanks,
>> >> Hans
>> >>
>> >>
>> >>
>> >> On Wed, Sep 11, 2013 at 4:30 PM, amit tomer <amittomer25 at gmail.com>
>> >> wrote:
>> >> >  I am new to opensource build framework Yocto and have a requirement
>> >> > wherein
>> >> > wanted to change the machine name ,when I do BITBAKE image-name
>> >> >
>> >> > Build Configuration:
>> >> >
>> >> > BB_VERSION        = "1.18.0"
>> >> > BUILD_SYS         = "x86_64-linux"
>> >> > NATIVELSBSTRING   = "RedHatEnterpriseServer-5.6"
>> >> > TARGET_SYS        = "arm-poky-linux-gnueabi"
>> >> > MACHINE           = "pyp-ii"
>> >> > DISTRO            = "poky"
>> >> > DISTRO_VERSION    = "1.4.1"
>> >> > TUNE_FEATURES     = "armv7a vfp neon callconvention-hard cortexa15"
>> >> > TARGET_FPU        = "vfp-neon"
>> >> > meta
>> >> > meta-yocto
>> >> > meta-yocto-bsp    =
>> >> > "(nobranch):beda5013e46da16a3d76f095869a5a5c5b1bc08a"
>> >> > meta-linaro-toolchain =
>> >> > "(nobranch):0f679485b945c1b929a44d1865eb517a096ac4ef"
>> >> > meta-ti           =
>> >> > "(nobranch):3eb71003af3ebb025285493721332111ac581a42
>> >> >
>> >> > Now MACHIEN name I wanted to change something like k2 from pyp-ii ,I
>> >> > tried
>> >> > changing it in local.conf file but I am getting error like
>> >> >
>> >> > 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:
>> >> >
>> >> > Please set a valid MACHINE in your local.conf or environment
>> >> >
>> >> > ERROR: Execution of event handler 'check_sanity_eventhandler' failed
>> >> >
>> >> > I also tried setting up export MACHINE="k2" but I am getting the same
>> >> > error
>> >> > message
>> >> >
>> >> > In my /var/fpwork/tomar_yocto1/snz-yocto/meta-xyz/conf/machine there
>> >> > exist a
>> >> > pyp-ii.conf file.
>> >> >
>> >> > I tried renaming it to k2.conf but it also didn't work out.
>> >> >
>> >> >
>> >> > Can anybody let me know what needs to be done in order to change
>> >> > MACHINE
>> >> > name here.
>> >> >
>> >> >
>> >> > Thanks
>> >> >
>> >> > Amit Singh Tomar
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > yocto mailing list
>> >> > yocto at yoctoproject.org
>> >> > https://lists.yoctoproject.org/listinfo/yocto
>> >> >
>> >
>> >
>
>

More information about the yocto mailing list