Edison BSP SRCREV

Edison BSP SRCREV

[Chris Tapp]

I've been following the "BSP Development Example" section of the "Yocto Project Development Manual" for a new BSP called "mybsp". This results in the following in linux-yocto_3.0.bbappend:

COMPATIBLE_MACHINE_mybsp = "mybsp"
KMACHINE_mybsp  = "yocto/standard/common-pc/base"
KERNEL_FEATURES_append_mybsp += " cfg/smp.scc"

SRCREV_machine_pn-linux-yocto_mybsp ?= "f153b0eb8264dc1e69f59d4c9173619feb4d5bd9"
SRCREV_meta_pn-linux-yocto_mybsp ?= "a4ac64fe873f08ef718e2849b88914725dc99c1c"

as I'm trying to base the BSP on common-pc/base.

However, when I build I get an error telling me that the machine SRCREV is not valid:

Log data follows:
| ERROR f153b0eb8264dc1e69f59d4c9173619feb4d5bd9 is not a valid commit ID.
| The kernel source tree may be out of sync
| ERROR: Function 'do_validate_branches' failed (see ...

The value is the commit tag I get at http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/commit/?h=yocto/standard/common-pc/base

I'm guessing I've got the wrong commit ID here ;-) What should I be using? Do I need the commit ID for the 3.0.18 tagged commit at
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/tag/?h=yocto/standard/common-pc/base&id=v3.0.18 or something else ?

I'm using the tarball method described in the example, not local git.

Chris Tapp

opensource@keylevel.com
www.keylevel.com

Re: Edison BSP SRCREV

[Bruce Ashfield]

On 12-04-04 6:36 PM, Chris Tapp wrote:
> I've been following the "BSP Development Example" section of the "Yocto Project Development Manual" for a new BSP called "mybsp". This results in the following in linux-yocto_3.0.bbappend:
>
> COMPATIBLE_MACHINE_mybsp = "mybsp"
> KMACHINE_mybsp  = "yocto/standard/common-pc/base"
> KERNEL_FEATURES_append_mybsp += " cfg/smp.scc"
>
> SRCREV_machine_pn-linux-yocto_mybsp ?= "f153b0eb8264dc1e69f59d4c9173619feb4d5bd9"
> SRCREV_meta_pn-linux-yocto_mybsp ?= "a4ac64fe873f08ef718e2849b88914725dc99c1c"
>
> as I'm trying to base the BSP on common-pc/base.
>
> However, when I build I get an error telling me that the machine SRCREV is not valid:
>
> Log data follows:
> | ERROR f153b0eb8264dc1e69f59d4c9173619feb4d5bd9 is not a valid commit ID.
> | The kernel source tree may be out of sync
> | ERROR: Function 'do_validate_branches' failed (see ...
>
> The value is the commit tag I get at http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/commit/?h=yocto/standard/common-pc/base
>
> I'm guessing I've got the wrong commit ID here ;-) What should I be using? Do I need the commit ID for the 3.0.18 tagged commit at
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/tag/?h=yocto/standard/common-pc/base&id=v3.0.18 or something else ?
>
> I'm using the tarball method described in the example, not local git.

It's like that in edison we switched to a kernel repo that only takes
-stable updates (not unlike the upstream -stable).

So look for the commit IDs here:

git://git.yoctoproject.org/linux-yocto-3.0-1.1.x.git

Sounds like a doc might need a tweak.

Cheers,

Bruce

>
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: Edison BSP SRCREV

[Chris Tapp]

On 5 Apr 2012, at 03:49, Bruce Ashfield wrote:

> On 12-04-04 6:36 PM, Chris Tapp wrote:
>> I've been following the "BSP Development Example" section of the "Yocto Project Development Manual" for a new BSP called "mybsp". This results in the following in linux-yocto_3.0.bbappend:
>> 
>> COMPATIBLE_MACHINE_mybsp = "mybsp"
>> KMACHINE_mybsp  = "yocto/standard/common-pc/base"
>> KERNEL_FEATURES_append_mybsp += " cfg/smp.scc"
>> 
>> SRCREV_machine_pn-linux-yocto_mybsp ?= "f153b0eb8264dc1e69f59d4c9173619feb4d5bd9"
>> SRCREV_meta_pn-linux-yocto_mybsp ?= "a4ac64fe873f08ef718e2849b88914725dc99c1c"
>> 
>> as I'm trying to base the BSP on common-pc/base.
>> 
>> However, when I build I get an error telling me that the machine SRCREV is not valid:
>> 
>> Log data follows:
>> | ERROR f153b0eb8264dc1e69f59d4c9173619feb4d5bd9 is not a valid commit ID.
>> | The kernel source tree may be out of sync
>> | ERROR: Function 'do_validate_branches' failed (see ...
>> 
>> The value is the commit tag I get at http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/commit/?h=yocto/standard/common-pc/base
>> 
>> I'm guessing I've got the wrong commit ID here ;-) What should I be using? Do I need the commit ID for the 3.0.18 tagged commit at
>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/tag/?h=yocto/standard/common-pc/base&id=v3.0.18 or something else ?
>> 
>> I'm using the tarball method described in the example, not local git.
> 
> It's like that in edison we switched to a kernel repo that only takes
> -stable updates (not unlike the upstream -stable).
> 
> So look for the commit IDs here:
> 
> git://git.yoctoproject.org/linux-yocto-3.0-1.1.x.git
> 
> Sounds like a doc might need a tweak.

Thanks, that's got it sorted. And yes, it would be nice if the doc explained how to get the IDs for a base kernel :-)

Just need to go through the kernel configuration steps now...

Chris Tapp

opensource@keylevel.com
www.keylevel.com