All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Barker" <paul@betafive.co.uk>
To: "Sergio Torres Soldado" <torres.soldado@gmail.com>,
	"Dimitris Tassopoulos" <dimtass@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: customising a bsp
Date: Mon, 01 Apr 2019 10:45:07 -0400	[thread overview]
Message-ID: <60ccde48-f785-48fa-a110-393e97ce51ab@www.fastmail.com> (raw)
In-Reply-To: <CAFuHCCANbbWqhEcXmv7Z921wZ+_8BEkChv+d07dQinHhwy9gvg@mail.gmail.com>

On Mon, 1 Apr 2019, at 08:49, Sergio Torres Soldado wrote:
> Hi Dimitris,
> 
>  That is very versatile thanks. It is a way of solving the issue.
> 
>  Just as a side note this is what I did so far trying to separate the 
> changes to the machine:
> 
>  added the following to a layer I created:
> . 
> |-- conf 
> | `-- machine 
> | `-- raspberrypi3-custom.conf 
> 
> Initially raspberrypi3-custom.conf was just a copy of raspberrpi3.conf 
> in meta-raspberry but I get the following excerpt of an error:
> """
> ERROR: linux-raspberrypi-1_4.14.98+gitAUTOINC+5d63a4595d-r0 
> do_kernel_metadata: Could not locate BSP definition for 
> raspberrypi3-custom/standard and no defconfig was provided
> """
> 
> To remedy this I added the following line to raspberrypi3-custom.conf:
> """
> KBUILD_DEFCONFIG_raspberrypi3-custom ?= "bcm2709_defconfig
> """
> 
> But then I get the error:
> """
> ERROR: bcm2835-bootfiles-20190212-r3 do_populate_lic: QA Issue: 
> bcm2835-bootfiles: LIC_FILES_CHKSUM points to an invalid file: 
> /opt/yocto/workspace/build/tmp/work/raspberrypi3_custom-poky-linux-gnueabi/bcm2835-bootfiles/20190212-r3/firmware-83977fe3b6ef54c1d29c83b0a778d330f523441f/boot/LICENCE.broadcom [license-checksum]
> ERROR: bcm2835-bootfiles-20190212-r3 do_populate_lic: Fatal QA errors 
> found, failing task.
> ERROR: bcm2835-bootfiles-20190212-r3 do_populate_lic: Function failed: 
> populate_lic_qa_checksum
> ERROR: Logfile of failure stored in: 
> /opt/yocto/workspace/build/tmp/work/raspberrypi3_custom-poky-linux-gnueabi/bcm2835-bootfiles/20190212-r3/temp/log.do_populate_lic.30228
> """
> 
> I ended up editing raspberrypi3.conf directly basically branching 
> meta-raspberrypi.
> 

Hi Sergio,

You could look at how we handle things in the BSP for the Sancloud BeagleBone Enhanced (BBE). This board is based on the BeagleBone Black and so in Yocto Project any overrides, COMPATIBLE_HOST values, etc which apply for the beaglebone should also apply for the bbe. To do this we add "beaglebone" to the MACHINEOVERRIDES list along with the appropriate separator which is ":". See https://bitbucket.sancloud.co.uk/projects/YB/repos/meta-sancloud/browse/conf/machine/bbe.conf for details.

So you should be able to add a line like this to your raspberrypi3-custom.conf file:

    MACHINEOVERRIDES =. "raspberrypi3:"

Thanks,

-- 
Paul Barker
Managing Director & Principal Engineer
Beta Five Ltd


      reply	other threads:[~2019-04-01 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30 17:33 customising a bsp Sergio Torres Soldado
2019-04-01  7:27 ` Dimitris Tassopoulos
2019-04-01  7:48   ` Sergio Torres Soldado
2019-04-01 14:45     ` Paul Barker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60ccde48-f785-48fa-a110-393e97ce51ab@www.fastmail.com \
    --to=paul@betafive.co.uk \
    --cc=dimtass@gmail.com \
    --cc=torres.soldado@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.