Warning about auto generated BSP description

Warning about auto generated BSP description

[Paul D. DeRocco]

I'm getting the following warning:

[kernel]: An auto generated BSP description was used, this normally
indicates a misconfiguration.
Check that your machine (chroma-bsp) has an associated kernel description.

Googling turns up the information that this is sometimes a spurious error
and nothing to worry about, because a full BSP description isn't strictly
required. However, as far as I can see I do indeed have a BSP description.
I built the BSP using the yocto-bsp tool. It created a
linux-yocto-rt_3.14.bbappend (since I'm using the RT kernel), and the
following files:

    chroma-bsp.cfg
    chroma-bsp.scc
    chroma-bsp-preempt-rt.scc
    chroma-bsp-standard.scc
    chroma-bsp-tiny.scc
    chroma-bsp-user-config.cfg
    chroma-bsp-user-features.scc
    chroma-bsp-user-patches.scc

The bbappend refers to chroma-bsp-preempt-rt.scc and the last three
(empty) files. chroma-bsp-preempt-rt.scc contains the requisite KMACHINE,
KTYPE and KARCH, and includes chroma-bsp.scc, which refers to
chroma-bsp.cfg. This seems to fit the definition of a "BSP description" in
3.4.5 of the Kernel Development Manual. The whole BSP tree is called
"meta-chroma-bsp" and that is indeed listed in my bblayers.conf. So why is
it complaining?

Also, I don't know that "Check that your machine has an associated kernel
description" means. The term "kernel description" doesn't appear anywhere
in the docs.

-- 

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com 

Re: Warning about auto generated BSP description

[Robert Calhoun]

Your kernel recipe needs to have an entry for the machine, e.g. a kernel recipe called linux-mainline.bb contains
COMPATIBLE_MACHINE_mymachine = "mymachine"

Also, your machine config file mymachine.conf needs to have a preferred kernel version, e.g:
PREFERRED_PROVIDER_virtual/kernel ?= "linux-mainline"
PREFERRED_VERSION_linux-yocto ?= "3.19%"
PREFERRED_VERSION_linux-mainline ?= "4.2%"


(I am not certain these will fix your error but you should have them defined.)
-Rob




On 9/13/15, 4:15 PM, "yocto-bounces@yoctoproject.org on behalf of Paul D. DeRocco" <yocto-bounces@yoctoproject.org on behalf of pderocco@ix.netcom.com> wrote:

>I'm getting the following warning:
>
>[kernel]: An auto generated BSP description was used, this normally
>indicates a misconfiguration.
>Check that your machine (chroma-bsp) has an associated kernel description.
>
>Googling turns up the information that this is sometimes a spurious error
>and nothing to worry about, because a full BSP description isn't strictly
>required. However, as far as I can see I do indeed have a BSP description.
>I built the BSP using the yocto-bsp tool. It created a
>linux-yocto-rt_3.14.bbappend (since I'm using the RT kernel), and the
>following files:
>
>    chroma-bsp.cfg
>    chroma-bsp.scc
>    chroma-bsp-preempt-rt.scc
>    chroma-bsp-standard.scc
>    chroma-bsp-tiny.scc
>    chroma-bsp-user-config.cfg
>    chroma-bsp-user-features.scc
>    chroma-bsp-user-patches.scc
>
>The bbappend refers to chroma-bsp-preempt-rt.scc and the last three
>(empty) files. chroma-bsp-preempt-rt.scc contains the requisite KMACHINE,
>KTYPE and KARCH, and includes chroma-bsp.scc, which refers to
>chroma-bsp.cfg. This seems to fit the definition of a "BSP description" in
>3.4.5 of the Kernel Development Manual. The whole BSP tree is called
>"meta-chroma-bsp" and that is indeed listed in my bblayers.conf. So why is
>it complaining?
>
>Also, I don't know that "Check that your machine has an associated kernel
>description" means. The term "kernel description" doesn't appear anywhere
>in the docs.
>
>-- 
>
>Ciao,               Paul D. DeRocco
>Paul                mailto:pderocco@ix.netcom.com 
>
>-- 

Re: Warning about auto generated BSP description

[Paul D. DeRocco]

> From: Robert Calhoun [mailto:rcalhoun@shotspotter.com] 
> 
> Your kernel recipe needs to have an entry for the machine, 
> e.g. a kernel recipe called linux-mainline.bb contains
> COMPATIBLE_MACHINE_mymachine = "mymachine"
> 
> Also, your machine config file mymachine.conf needs to have a 
> preferred kernel version, e.g:
> PREFERRED_PROVIDER_virtual/kernel ?= "linux-mainline"
> PREFERRED_VERSION_linux-yocto ?= "3.19%"
> PREFERRED_VERSION_linux-mainline ?= "4.2%"
> 
> 
> (I am not certain these will fix your error but you should 
> have them defined.)

The linux-yocto-rt_3.14.bbappend file created by the yocto-bsp script
includes:

    COMPATIBLE_MACHINE_chroma_bsp = "chroma_bsp"

My bblayers.conf file contains:

    PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"

The chroma-bsp.conf file created by the script (in
meta-chroma-bsp/conf/machine/) includes:

    PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-rt"
    PREFERRED_VERSION_linux-yocto-rt ?= "3.14%"

I'm not sure if or how the last file is getting read.

Since I'm definitely using the RT kernel, I would assume I'd only need
references to linux-yocto-rt. See anything wrong?

-- 

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com 

Re: Warning about auto generated BSP description

[Bruce Ashfield]

On 15-09-13 04:15 PM, Paul D. DeRocco wrote:
> I'm getting the following warning:
>
> [kernel]: An auto generated BSP description was used, this normally
> indicates a misconfiguration.
> Check that your machine (chroma-bsp) has an associated kernel description.
>
> Googling turns up the information that this is sometimes a spurious error
> and nothing to worry about, because a full BSP description isn't strictly
> required. However, as far as I can see I do indeed have a BSP description.
> I built the BSP using the yocto-bsp tool. It created a
> linux-yocto-rt_3.14.bbappend (since I'm using the RT kernel), and the
> following files:
>
>      chroma-bsp.cfg
>      chroma-bsp.scc
>      chroma-bsp-preempt-rt.scc
>      chroma-bsp-standard.scc
>      chroma-bsp-tiny.scc
>      chroma-bsp-user-config.cfg
>      chroma-bsp-user-features.scc
>      chroma-bsp-user-patches.scc

The tool may have created these files, but the question is .. were they
actually used.

That's what the check in question is trying to determine.

Rather than fail to build, the tools (kernel, not yocto-bsp) will
generate a skeleton BSP, and start the build. Chances are that
skeleton BSP isn't what you want .. and that's what the tools are
warning.

Clearly the message still needs more tweaking, as do the docs.

>
> The bbappend refers to chroma-bsp-preempt-rt.scc and the last three
> (empty) files. chroma-bsp-preempt-rt.scc contains the requisite KMACHINE,
> KTYPE and KARCH, and includes chroma-bsp.scc, which refers to
> chroma-bsp.cfg. This seems to fit the definition of a "BSP description" in
> 3.4.5 of the Kernel Development Manual. The whole BSP tree is called
> "meta-chroma-bsp" and that is indeed listed in my bblayers.conf. So why is
> it complaining?

What release are you using ? If you check something in the kernel meta
directory, I can tell you if the warning is wrong, or something is 
really being missed.

The reason I asked about the release, is that the location of the kernel
meta directory will be in a different place between the various
releases. But it is always in the kernel source directory, whether it is
in work-shared, or in work. So if you head to that directory and look
for either .meta or .kernel-meta, you should see a file "top_tgt" in that
directory.

Look at the contents of that file. It should point to those generated
files you referenced above. If it doesn't .. they weren't used, and we
need to figure out why.

Cheers,

Bruce

>
> Also, I don't know that "Check that your machine has an associated kernel
> description" means. The term "kernel description" doesn't appear anywhere
> in the docs.
>

Re: Warning about auto generated BSP description

[Paul D. DeRocco]

> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] 
> 
> The tool may have created these files, but the question is .. 
> What release are you using ? If you check something in the kernel meta
> directory, I can tell you if the warning is wrong, or something is 
> really being missed.

I'm using Fido.

> The reason I asked about the release, is that the location of 
> the kernel
> meta directory will be in a different place between the various
> releases. But it is always in the kernel source directory, 
> whether it is
> in work-shared, or in work. So if you head to that directory and look
> for either .meta or .kernel-meta, you should see a file 
> "top_tgt" in that
> directory.
> 
> Look at the contents of that file. It should point to those generated
> files you referenced above. If it doesn't .. they weren't used, and we
> need to figure out why.

The file
"/home/pauld/yocto-fido/build/tmp/work-shared/chroma-bsp/kernel-source/.me
ta/top_tgt" contains
"/home/pauld/yocto-fido/build/tmp/work-shared/chroma-bsp/kernel-source/.me
ta/cfg/scratch/obj/home/pauld/yocto-fido/meta-chroma-bsp/recipes-kernel/li
nux/files/chroma-bsp-preempt-rt.scc". That referenced folder includes a
copy of all the .scc and .cfg files I mentioned before. I guess that means
that they are in fact being used.

Does that mean that this warning message is spurious, and can be ignored?
My kernel is hanging during the boot at this point, but I suspect my real
problem is elsewhere.

Thanks so much for your time helping me to figure this out.

-- 

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com 

Re: Warning about auto generated BSP description

[Bruce Ashfield]

On 15-09-14 01:38 PM, Paul D. DeRocco wrote:
>> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
>>
>> The tool may have created these files, but the question is ..
>> What release are you using ? If you check something in the kernel meta
>> directory, I can tell you if the warning is wrong, or something is
>> really being missed.
>
> I'm using Fido.
>
>> The reason I asked about the release, is that the location of
>> the kernel
>> meta directory will be in a different place between the various
>> releases. But it is always in the kernel source directory,
>> whether it is
>> in work-shared, or in work. So if you head to that directory and look
>> for either .meta or .kernel-meta, you should see a file
>> "top_tgt" in that
>> directory.
>>
>> Look at the contents of that file. It should point to those generated
>> files you referenced above. If it doesn't .. they weren't used, and we
>> need to figure out why.
>
> The file
> "/home/pauld/yocto-fido/build/tmp/work-shared/chroma-bsp/kernel-source/.me
> ta/top_tgt" contains
> "/home/pauld/yocto-fido/build/tmp/work-shared/chroma-bsp/kernel-source/.me
> ta/cfg/scratch/obj/home/pauld/yocto-fido/meta-chroma-bsp/recipes-kernel/li
> nux/files/chroma-bsp-preempt-rt.scc". That referenced folder includes a
> copy of all the .scc and .cfg files I mentioned before. I guess that means
> that they are in fact being used.

Yep. If everything was copied, then you are good.

And now that you point that out, I recall a bug that when I created
that warning, that it was catching the yocto BSP generated files.
I swear I fixed it, but obviously not. I'll need to track down that
bugzilla entry.

Bruce

>
> Does that mean that this warning message is spurious, and can be ignored?
> My kernel is hanging during the boot at this point, but I suspect my real
> problem is elsewhere.
>
> Thanks so much for your time helping me to figure this out.
>