Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Compiling Device Tree with Buildroot
@ 2019-10-08 11:39 Gamble, Bradley
  2019-10-10 21:01 ` Arnout Vandecappelle
  0 siblings, 1 reply; 2+ messages in thread
From: Gamble, Bradley @ 2019-10-08 11:39 UTC (permalink / raw)
  To: buildroot

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>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Buildroot] Compiling Device Tree with Buildroot
  2019-10-08 11:39 [Buildroot] Compiling Device Tree with Buildroot Gamble, Bradley
@ 2019-10-10 21:01 ` Arnout Vandecappelle
  0 siblings, 0 replies; 2+ messages in thread
From: Arnout Vandecappelle @ 2019-10-10 21:01 UTC (permalink / raw)
  To: buildroot



On 08/10/2019 13:39, Gamble, Bradley wrote:
> 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":

 Indeed, Buildroot (currently) only supports compiling device trees as part of
the kernel build. In practice, you often need one or more of the in-kernel dtsis.

> 
> - 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?

 BR2_LINUX_KERNEL_CUSTOM_DTS_PATH takes a list of .dts and .dtsi files. Only the
.dts files in the list will be compiled in a .dtb, the rest is just copied into
the kernel tree so the includes still work.

 In other words, add the .dtsi files to BR2_LINUX_KERNEL_CUSTOM_DTS_PATH.

 Regards,
 Arnout


> 
> 
> 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>
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-10-10 21:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-10-08 11:39 [Buildroot] Compiling Device Tree with Buildroot Gamble, Bradley
2019-10-10 21:01 ` Arnout Vandecappelle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox