All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gamble, Bradley <bradley.gamble@ncipher.com>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling Device Tree with Buildroot
Date: Tue, 8 Oct 2019 11:39:46 +0000	[thread overview]
Message-ID: <1570534786731.48992@ncipher.com> (raw)

Howdy,


I'm trying to get Buildroot to compile our custom Device Tree file as part of the build process.

I've previously been compiling it to a DTB file using "dtc" standalone and then embedding that as a node in a FIT image, however if possible I'd like to integrate this as a stage in Buildroot. I can use a post-build script to achieve this but if there is a "standard" method that would be preferred.


Alternatively I was trying to build the Device Tree as part of the kernel. My Device Tree is comprised of three files under "br2-external/company/board/device-tree":

- board.dts

- board-pre.dtsi

- board-post.dtsi

The file board.dts includes board-pre.dtsi and board-post.dtsi.

I've configured Buildroot to use an out-of-tree Device Tree however when it attempts to compile the board.dts file it is unable to find the pre and post files. Do I need to add a specific argument or flag so that the include directory is added?


Regards,

Bradley Gamble

________________________________

 [cid:imageac0699.PNG at 7f5cf8a1.48a90a4d] <http://www.ncipher.com>
Bradley Gamble
Software Engineer
Tel: +44 1293 580000


nCipher Security
Manor Royal
Crawley RH10 9HA
United Kingdom

www.ncipher.com<http://www.ncipher.com>

[cid:image17ce6e.JPG at aa840ebd.4ea6c329]<https://www.eventbrite.com/e/simon-singh-the-simpsons-and-their-mathematical-secrets-tickets-71658240727>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191008/9f096b74/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imageac0699.PNG
Type: image/png
Size: 3675 bytes
Desc: imageac0699.PNG
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191008/9f096b74/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image17ce6e.JPG
Type: image/jpeg
Size: 54303 bytes
Desc: image17ce6e.JPG
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191008/9f096b74/attachment.jpe>

             reply	other threads:[~2019-10-08 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 11:39 Gamble, Bradley [this message]
2019-10-10 21:01 ` [Buildroot] Compiling Device Tree with Buildroot Arnout Vandecappelle

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=1570534786731.48992@ncipher.com \
    --to=bradley.gamble@ncipher.com \
    --cc=buildroot@busybox.net \
    /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.