* Custom device tree overlay for BBB
@ 2023-12-21 11:34 Lukasz Przenioslo
2023-12-21 14:58 ` [meta-ti] " Jon Cormier
0 siblings, 1 reply; 9+ messages in thread
From: Lukasz Przenioslo @ 2023-12-21 11:34 UTC (permalink / raw)
To: meta-ti
Hello there,
I was able to compile the Poky image (Dunfell) with meta-ti included for the BBB. I am working on an open source project intended for home automation based on the BBB: https://github.com/Beaglenode/BeagleNodeHW
The next step I am trying to make is to prepare a proper device tree overlay that would align with the HW requirements of this project (or "cape"). I need to:
- Disable the HDMI pins,
- configure multiple pins as either PRU0 or PRU1 controlled.
For that I thought the best approach would be to prepare a DTO, instead of modifying the default one for BBB. I don't know how to prepare that DTO yet and I don't know how to include it in my build. I would like to ask for some help in this manner, especially the prior part (how to load the custom DTO). Right now I am still modifying everything in the local.conf, as I do not have the knowledge yet to build my own distro for this device (that's the end plan).
I would appreciate all help!
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-ti] Custom device tree overlay for BBB
2023-12-21 11:34 Custom device tree overlay for BBB Lukasz Przenioslo
@ 2023-12-21 14:58 ` Jon Cormier
2023-12-21 15:03 ` Bremenpl
0 siblings, 1 reply; 9+ messages in thread
From: Jon Cormier @ 2023-12-21 14:58 UTC (permalink / raw)
To: Lukasz Przenioslo; +Cc: meta-ti
[-- Attachment #1: Type: text/plain, Size: 2283 bytes --]
Here is a possible example overlay that configures pinmuxes with the
expectation that the pru's will use them. There is likely a similar
example in that long list of overlays that disables hdmi.
https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-RPROC-4-19-TI-PRUCAPE-00A0.dts
Note its entirely possible these examples won't build or apply correctly on
a different kernel version, but they should still be a decent starting
point.
On Thu, Dec 21, 2023 at 6:34 AM Lukasz Przenioslo <bremenpl@gmail.com>
wrote:
> Hello there,
>
> I was able to compile the Poky image (Dunfell) with meta-ti included for
> the BBB. I am working on an open source project intended for home
> automation based on the BBB: https://github.com/Beaglenode/BeagleNodeHW
>
> The next step I am trying to make is to prepare a proper device tree
> overlay that would align with the HW requirements of this project (or
> "cape"). I need to:
> - Disable the HDMI pins,
> - configure multiple pins as either PRU0 or PRU1 controlled.
>
> For that I thought the best approach would be to prepare a DTO, instead of
> modifying the default one for BBB. I don't know how to prepare that DTO yet
> and I don't know how to include it in my build. I would like to ask for
> some help in this manner, especially the prior part (how to load the custom
> DTO). Right now I am still modifying everything in the local.conf, as I do
> not have the knowledge yet to build my own distro for this device (that's
> the end plan).
>
> I would appreciate all help!
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#17360):
> https://lists.yoctoproject.org/g/meta-ti/message/17360
> Mute This Topic: https://lists.yoctoproject.org/mt/103298715/7902621
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
> jcormier@criticallink.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
--
Jonathan Cormier
Software Engineer
Voice: 315.425.4045 x222
http://www.CriticalLink.com <http://www.criticallink.com/>
6712 Brooklawn Parkway, Syracuse, NY 13211
<https://www.linkedin.com/company/critical-link-llc>
<https://twitter.com/Critical_Link>
[-- Attachment #2: Type: text/html, Size: 4509 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-ti] Custom device tree overlay for BBB
2023-12-21 14:58 ` [meta-ti] " Jon Cormier
@ 2023-12-21 15:03 ` Bremenpl
2023-12-21 15:17 ` Jon Cormier
0 siblings, 1 reply; 9+ messages in thread
From: Bremenpl @ 2023-12-21 15:03 UTC (permalink / raw)
To: Jon Cormier; +Cc: meta-ti
[-- Attachment #1: Type: text/plain, Size: 2390 bytes --]
Hi and thank you for the answer Jonathan!
Do you happen to also know a good reference on how to incorporate an
overlay into the yocto build?
On December 21, 2023 15:58:56 Jon Cormier <jcormier@criticallink.com> wrote:
> Here is a possible example overlay that configures pinmuxes with the
> expectation that the pru's will use them. There is likely a similar
> example in that long list of overlays that disables hdmi.
>
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-RPROC-4-19-TI-PRUCAPE-00A0.dts
>
> Note its entirely possible these examples won't build or apply correctly on
> a different kernel version, but they should still be a decent starting point.
>
>
>
> On Thu, Dec 21, 2023 at 6:34 AM Lukasz Przenioslo <bremenpl@gmail.com> wrote:
>
> Hello there,
>
> I was able to compile the Poky image (Dunfell) with meta-ti included for
> the BBB. I am working on an open source project intended for home
> automation based on the BBB: https://github.com/Beaglenode/BeagleNodeHW
>
> The next step I am trying to make is to prepare a proper device tree
> overlay that would align with the HW requirements of this project (or
> "cape"). I need to:
> - Disable the HDMI pins,
> - configure multiple pins as either PRU0 or PRU1 controlled.
>
> For that I thought the best approach would be to prepare a DTO, instead of
> modifying the default one for BBB. I don't know how to prepare that DTO yet
> and I don't know how to include it in my build. I would like to ask for
> some help in this manner, especially the prior part (how to load the custom
> DTO). Right now I am still modifying everything in the local.conf, as I do
> not have the knowledge yet to build my own distro for this device (that's
> the end plan).
>
> I would appreciate all help!
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#17360):
> https://lists.yoctoproject.org/g/meta-ti/message/17360
> Mute This Topic: https://lists.yoctoproject.org/mt/103298715/7902621
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
> [jcormier@criticallink.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
>
>
> --
>
> Jonathan Cormier
> Software Engineer
>
> Voice: 315.425.4045 x222
>
>
>
>
>
>
> http://www.CriticalLink.com
>
> 6712 Brooklawn Parkway, Syracuse, NY 13211
[-- Attachment #2: Type: text/html, Size: 5574 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-ti] Custom device tree overlay for BBB
2023-12-21 15:03 ` Bremenpl
@ 2023-12-21 15:17 ` Jon Cormier
2023-12-21 20:51 ` Re[2]: " Łukasz Przeniosło
0 siblings, 1 reply; 9+ messages in thread
From: Jon Cormier @ 2023-12-21 15:17 UTC (permalink / raw)
To: Bremenpl; +Cc: meta-ti
[-- Attachment #1: Type: text/plain, Size: 3322 bytes --]
This solution seems like a good place to start. I haven't tried it myself
but it looks clean and easy to implement.
https://stackoverflow.com/a/68650774
The alternative would be to bbappend the kernel and patch your overlay into
the correct folder.
https://stackoverflow.com/a/39343720
On Thu, Dec 21, 2023 at 10:03 AM Bremenpl <bremenpl@gmail.com> wrote:
> Hi and thank you for the answer Jonathan!
>
> Do you happen to also know a good reference on how to incorporate an
> overlay into the yocto build?
>
> On December 21, 2023 15:58:56 Jon Cormier <jcormier@criticallink.com>
> wrote:
>
>> Here is a possible example overlay that configures pinmuxes with the
>> expectation that the pru's will use them. There is likely a similar
>> example in that long list of overlays that disables hdmi.
>>
>>
>> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-RPROC-4-19-TI-PRUCAPE-00A0.dts
>>
>> Note its entirely possible these examples won't build or apply correctly
>> on a different kernel version, but they should still be a decent starting
>> point.
>>
>> On Thu, Dec 21, 2023 at 6:34 AM Lukasz Przenioslo <bremenpl@gmail.com>
>> wrote:
>>
>>> Hello there,
>>>
>>> I was able to compile the Poky image (Dunfell) with meta-ti included for
>>> the BBB. I am working on an open source project intended for home
>>> automation based on the BBB: https://github.com/Beaglenode/BeagleNodeHW
>>>
>>> The next step I am trying to make is to prepare a proper device tree
>>> overlay that would align with the HW requirements of this project (or
>>> "cape"). I need to:
>>> - Disable the HDMI pins,
>>> - configure multiple pins as either PRU0 or PRU1 controlled.
>>>
>>> For that I thought the best approach would be to prepare a DTO, instead
>>> of modifying the default one for BBB. I don't know how to prepare that DTO
>>> yet and I don't know how to include it in my build. I would like to ask for
>>> some help in this manner, especially the prior part (how to load the custom
>>> DTO). Right now I am still modifying everything in the local.conf, as I do
>>> not have the knowledge yet to build my own distro for this device (that's
>>> the end plan).
>>>
>>> I would appreciate all help!
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> View/Reply Online (#17360):
>>> https://lists.yoctoproject.org/g/meta-ti/message/17360
>>> Mute This Topic: https://lists.yoctoproject.org/mt/103298715/7902621
>>> Group Owner: meta-ti+owner@lists.yoctoproject.org
>>> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
>>> jcormier@criticallink.com]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>>>
>>
>> --
>> Jonathan Cormier
>> Software Engineer
>>
>> Voice: 315.425.4045 x222
>>
>>
>>
>> http://www.CriticalLink.com <http://www.criticallink.com/>
>> 6712 Brooklawn Parkway, Syracuse, NY 13211
>>
>> <https://www.linkedin.com/company/critical-link-llc>
>> <https://twitter.com/Critical_Link>
>>
>
>
--
Jonathan Cormier
Software Engineer
Voice: 315.425.4045 x222
http://www.CriticalLink.com <http://www.criticallink.com/>
6712 Brooklawn Parkway, Syracuse, NY 13211
<https://www.linkedin.com/company/critical-link-llc>
<https://twitter.com/Critical_Link>
[-- Attachment #2: Type: text/html, Size: 7831 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re[2]: [meta-ti] Custom device tree overlay for BBB
2023-12-21 15:17 ` Jon Cormier
@ 2023-12-21 20:51 ` Łukasz Przeniosło
2023-12-22 1:49 ` Denys Dmytriyenko
0 siblings, 1 reply; 9+ messages in thread
From: Łukasz Przeniosło @ 2023-12-21 20:51 UTC (permalink / raw)
To: Jon Cormier; +Cc: meta-ti
[-- Attachment #1: Type: text/plain, Size: 4022 bytes --]
Hi Jon,
I guess the first option is more feasible, as I would not like to modify
any files provided by the Poky repo, but rather create my own recipe
that would somehow cover the default settings during the build. There is
still a lot ahead for me to understand though...
Thank you for the useful links.
--
Łukasz Przeniosło
------ Original Message ------
From "Jon Cormier" <jcormier@criticallink.com>
To "Bremenpl" <bremenpl@gmail.com>
Cc meta-ti@lists.yoctoproject.org
Date 2023-12-21 16:17:38
Subject Re: [meta-ti] Custom device tree overlay for BBB
>This solution seems like a good place to start. I haven't tried it
>myself but it looks clean and easy to implement.
>https://stackoverflow.com/a/68650774
>
>The alternative would be to bbappend the kernel and patch your overlay
>into the correct folder.
>https://stackoverflow.com/a/39343720
>
>On Thu, Dec 21, 2023 at 10:03 AM Bremenpl <bremenpl@gmail.com> wrote:
>>Hi and thank you for the answer Jonathan!
>>
>>Do you happen to also know a good reference on how to incorporate an
>>overlay into the yocto build?
>>
>>On December 21, 2023 15:58:56 Jon Cormier <jcormier@criticallink.com>
>>wrote:
>>
>>>Here is a possible example overlay that configures pinmuxes with the
>>>expectation that the pru's will use them. There is likely a similar
>>>example in that long list of overlays that disables hdmi.
>>>
>>>https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-RPROC-4-19-TI-PRUCAPE-00A0.dts
>>>
>>>Note its entirely possible these examples won't build or apply
>>>correctly on a different kernel version, but they should still be a
>>>decent starting point.
>>>
>>>On Thu, Dec 21, 2023 at 6:34 AM Lukasz Przenioslo
>>><bremenpl@gmail.com> wrote:
>>>>Hello there,
>>>>
>>>>I was able to compile the Poky image (Dunfell) with meta-ti included
>>>>for the BBB. I am working on an open source project intended for
>>>>home automation based on the BBB:
>>>>https://github.com/Beaglenode/BeagleNodeHW
>>>>
>>>>The next step I am trying to make is to prepare a proper device tree
>>>>overlay that would align with the HW requirements of this project
>>>>(or "cape"). I need to:
>>>>- Disable the HDMI pins,
>>>>- configure multiple pins as either PRU0 or PRU1 controlled.
>>>>
>>>>For that I thought the best approach would be to prepare a DTO,
>>>>instead of modifying the default one for BBB. I don't know how to
>>>>prepare that DTO yet and I don't know how to include it in my build.
>>>>I would like to ask for some help in this manner, especially the
>>>>prior part (how to load the custom DTO). Right now I am still
>>>>modifying everything in the local.conf, as I do not have the
>>>>knowledge yet to build my own distro for this device (that's the end
>>>>plan).
>>>>
>>>>I would appreciate all help!
>>>>
>>>>-=-=-=-=-=-=-=-=-=-=-=-
>>>>Links: You receive all messages sent to this group.
>>>>View/Reply Online (#17360):
>>>>https://lists.yoctoproject.org/g/meta-ti/message/17360
>>>>Mute This Topic: https://lists.yoctoproject.org/mt/103298715/7902621
>>>>Group Owner: meta-ti+owner@lists.yoctoproject.org
>>>><mailto:meta-ti%2Bowner@lists.yoctoproject.org>
>>>>Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
>>>>[jcormier@criticallink.com]
>>>>-=-=-=-=-=-=-=-=-=-=-=-
>>>>
>>>
>>>
>>>--
>>>Jonathan Cormier
>>>Software Engineer
>>>
>>>Voice: 315.425.4045 x222
>>>
>>>
>>>
>>>http://www.CriticalLink.com <http://www.criticallink.com/>
>>>6712 Brooklawn Parkway, Syracuse, NY 13211
>>>
>>><https://www.linkedin.com/company/critical-link-llc>
>>><https://twitter.com/Critical_Link>
>>
>
>
>--
>Jonathan Cormier
>Software Engineer
>
>Voice: 315.425.4045 x222
>
>
>
>http://www.CriticalLink.com <http://www.criticallink.com/>
>6712 Brooklawn Parkway, Syracuse, NY 13211
>
><https://www.linkedin.com/company/critical-link-llc>
><https://twitter.com/Critical_Link>
[-- Attachment #2: Type: text/html, Size: 9679 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-ti] Custom device tree overlay for BBB
2023-12-21 20:51 ` Re[2]: " Łukasz Przeniosło
@ 2023-12-22 1:49 ` Denys Dmytriyenko
2023-12-22 5:14 ` Bremenpl
0 siblings, 1 reply; 9+ messages in thread
From: Denys Dmytriyenko @ 2023-12-22 1:49 UTC (permalink / raw)
To: Lukasz Przenioslo; +Cc: Jon Cormier, meta-ti
You could simply add your overlay in one of the conf files, such as
local.conf:
KERNEL_DEVICETREE += "your-overlay.dtbo"
Check the existing machine conf files for examples.
On Thu, Dec 21, 2023 at 08:51:49PM +0000, Lukasz Przenioslo wrote:
> Hi Jon,
> I guess the first option is more feasible, as I would not like to
> modify any files provided by the Poky repo, but rather create my own
> recipe that would somehow cover the default settings during the
> build. There is still a lot ahead for me to understand though...
>
> Thank you for the useful links.
>
> --
> Łukasz Przeniosło
>
>
> ------ Original Message ------
> From "Jon Cormier" <jcormier@criticallink.com>
> To "Bremenpl" <bremenpl@gmail.com>
> Cc meta-ti@lists.yoctoproject.org
> Date 2023-12-21 16:17:38
> Subject Re: [meta-ti] Custom device tree overlay for BBB
>
> >This solution seems like a good place to start. I haven't tried it
> >myself but it looks clean and easy to implement.
> >https://stackoverflow.com/a/68650774
> >
> >The alternative would be to bbappend the kernel and patch your
> >overlay into the correct folder.
> >https://stackoverflow.com/a/39343720
> >
> >On Thu, Dec 21, 2023 at 10:03 AM Bremenpl <bremenpl@gmail.com> wrote:
> >>Hi and thank you for the answer Jonathan!
> >>
> >>Do you happen to also know a good reference on how to
> >>incorporate an overlay into the yocto build?
> >>
> >>On December 21, 2023 15:58:56 Jon Cormier
> >><jcormier@criticallink.com> wrote:
> >>
> >>>Here is a possible example overlay that configures pinmuxes
> >>>with the expectation that the pru's will use them. There is
> >>>likely a similar example in that long list of overlays that
> >>>disables hdmi.
> >>>
> >>>https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-RPROC-4-19-TI-PRUCAPE-00A0.dts
> >>>
> >>>Note its entirely possible these examples won't build or apply
> >>>correctly on a different kernel version, but they should still
> >>>be a decent starting point.
> >>>
> >>>On Thu, Dec 21, 2023 at 6:34 AM Lukasz Przenioslo
> >>><bremenpl@gmail.com> wrote:
> >>>>Hello there,
> >>>>
> >>>>I was able to compile the Poky image (Dunfell) with meta-ti
> >>>>included for the BBB. I am working on an open source project
> >>>>intended for home automation based on the BBB:
> >>>>https://github.com/Beaglenode/BeagleNodeHW
> >>>>
> >>>>The next step I am trying to make is to prepare a proper
> >>>>device tree overlay that would align with the HW
> >>>>requirements of this project (or "cape"). I need to:
> >>>>- Disable the HDMI pins,
> >>>>- configure multiple pins as either PRU0 or PRU1 controlled.
> >>>>
> >>>>For that I thought the best approach would be to prepare a
> >>>>DTO, instead of modifying the default one for BBB. I don't
> >>>>know how to prepare that DTO yet and I don't know how to
> >>>>include it in my build. I would like to ask for some help in
> >>>>this manner, especially the prior part (how to load the
> >>>>custom DTO). Right now I am still modifying everything in
> >>>>the local.conf, as I do not have the knowledge yet to build
> >>>>my own distro for this device (that's the end plan).
> >>>>
> >>>>I would appreciate all help!
> >>>>
> >>>>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-ti] Custom device tree overlay for BBB
2023-12-22 1:49 ` Denys Dmytriyenko
@ 2023-12-22 5:14 ` Bremenpl
2023-12-22 7:03 ` Denys Dmytriyenko
0 siblings, 1 reply; 9+ messages in thread
From: Bremenpl @ 2023-12-22 5:14 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: Jon Cormier, meta-ti
[-- Attachment #1: Type: text/plain, Size: 3534 bytes --]
Hi Denys,
Should be easy enough to test it quickly as a proof of concept, thank you.
Will bitbake know to compile this overlay, tell the u-boot to load it and
so on?
On December 22, 2023 02:49:39 Denys Dmytriyenko <denis@denix.org> wrote:
> You could simply add your overlay in one of the conf files, such as
> local.conf:
>
> KERNEL_DEVICETREE += "your-overlay.dtbo"
>
> Check the existing machine conf files for examples.
>
>
> On Thu, Dec 21, 2023 at 08:51:49PM +0000, Lukasz Przenioslo wrote:
>> Hi Jon,
>> I guess the first option is more feasible, as I would not like to
>> modify any files provided by the Poky repo, but rather create my own
>> recipe that would somehow cover the default settings during the
>> build. There is still a lot ahead for me to understand though...
>>
>> Thank you for the useful links.
>>
>> --
>> Łukasz Przeniosło
>>
>>
>> ------ Original Message ------
>> From "Jon Cormier" <jcormier@criticallink.com>
>> To "Bremenpl" <bremenpl@gmail.com>
>> Cc meta-ti@lists.yoctoproject.org
>> Date 2023-12-21 16:17:38
>> Subject Re: [meta-ti] Custom device tree overlay for BBB
>>
>> >This solution seems like a good place to start. I haven't tried it
>> >myself but it looks clean and easy to implement.
>> >https://stackoverflow.com/a/68650774
>> >
>> >The alternative would be to bbappend the kernel and patch your
>> >overlay into the correct folder.
>> >https://stackoverflow.com/a/39343720
>> >
>> >On Thu, Dec 21, 2023 at 10:03 AM Bremenpl <bremenpl@gmail.com> wrote:
>> >>Hi and thank you for the answer Jonathan!
>> >>
>> >>Do you happen to also know a good reference on how to
>> >>incorporate an overlay into the yocto build?
>> >>
>> >>On December 21, 2023 15:58:56 Jon Cormier
>> >><jcormier@criticallink.com> wrote:
>> >>
>> >>>Here is a possible example overlay that configures pinmuxes
>> >>>with the expectation that the pru's will use them. There is
>> >>>likely a similar example in that long list of overlays that
>> >>>disables hdmi.
>> >>>
>> >>>https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-RPROC-4-19-TI-PRUCAPE-00A0.dts
>> >>>
>> >>>Note its entirely possible these examples won't build or apply
>> >>>correctly on a different kernel version, but they should still
>> >>>be a decent starting point.
>> >>>
>> >>>On Thu, Dec 21, 2023 at 6:34 AM Lukasz Przenioslo
>> >>><bremenpl@gmail.com> wrote:
>> >>>>Hello there,
>> >>>>
>> >>>>I was able to compile the Poky image (Dunfell) with meta-ti
>> >>>>included for the BBB. I am working on an open source project
>> >>>>intended for home automation based on the BBB:
>> >>>>https://github.com/Beaglenode/BeagleNodeHW
>> >>>>
>> >>>>The next step I am trying to make is to prepare a proper
>> >>>>device tree overlay that would align with the HW
>> >>>>requirements of this project (or "cape"). I need to:
>> >>>>- Disable the HDMI pins,
>> >>>>- configure multiple pins as either PRU0 or PRU1 controlled.
>> >>>>
>> >>>>For that I thought the best approach would be to prepare a
>> >>>>DTO, instead of modifying the default one for BBB. I don't
>> >>>>know how to prepare that DTO yet and I don't know how to
>> >>>>include it in my build. I would like to ask for some help in
>> >>>>this manner, especially the prior part (how to load the
>> >>>>custom DTO). Right now I am still modifying everything in
>> >>>>the local.conf, as I do not have the knowledge yet to build
>> >>>>my own distro for this device (that's the end plan).
>> >>>>
>> >>>>I would appreciate all help!
>> >>>>
>> >>>>
[-- Attachment #2: Type: text/html, Size: 6497 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-ti] Custom device tree overlay for BBB
2023-12-22 5:14 ` Bremenpl
@ 2023-12-22 7:03 ` Denys Dmytriyenko
2023-12-22 8:34 ` Re[2]: " Łukasz Przeniosło
0 siblings, 1 reply; 9+ messages in thread
From: Denys Dmytriyenko @ 2023-12-22 7:03 UTC (permalink / raw)
To: Lukasz Przenioslo; +Cc: Jon Cormier, meta-ti
Sorry, this got a bit out of context - one of the solutions from Jon was
talking about adding a bbappend to a kernel recipe, which would then
automatically handle KERNEL_DEVICETREE list via kernel-devicetree,bbclass
Alternatively, if you add a standalne recipe, all you need is to add your
overlay to SRC_URI and inherit devicetree.bbclass
On Fri, Dec 22, 2023 at 06:14:51AM +0100, Lukasz Przenioslo wrote:
> Hi Denys,
> Should be easy enough to test it quickly as a proof of concept,
> thank you. Will bitbake know to compile this overlay, tell the
> u-boot to load it and so on?
>
> On December 22, 2023 02:49:39 Denys Dmytriyenko <denis@denix.org> wrote:
>
> >You could simply add your overlay in one of the conf files, such as
> >local.conf:
> >
> >KERNEL_DEVICETREE += "your-overlay.dtbo"
> >
> >Check the existing machine conf files for examples.
> >
> >
> >On Thu, Dec 21, 2023 at 08:51:49PM +0000, Lukasz Przenioslo wrote:
> >>Hi Jon,
> >>I guess the first option is more feasible, as I would not like to
> >>modify any files provided by the Poky repo, but rather create my own
> >>recipe that would somehow cover the default settings during the
> >>build. There is still a lot ahead for me to understand though...
> >>
> >>Thank you for the useful links.
> >>
> >>--
> >>Łukasz Przeniosło
> >>
> >>
> >>------ Original Message ------
> >>From "Jon Cormier" <jcormier@criticallink.com>
> >>To "Bremenpl" <bremenpl@gmail.com>
> >>Cc meta-ti@lists.yoctoproject.org
> >>Date 2023-12-21 16:17:38
> >>Subject Re: [meta-ti] Custom device tree overlay for BBB
> >>
> >>>This solution seems like a good place to start. I haven't tried it
> >>>myself but it looks clean and easy to implement.
> >>>https://stackoverflow.com/a/68650774
> >>>
> >>>The alternative would be to bbappend the kernel and patch your
> >>>overlay into the correct folder.
> >>>https://stackoverflow.com/a/39343720
> >>>
> >>>On Thu, Dec 21, 2023 at 10:03 AM Bremenpl <bremenpl@gmail.com> wrote:
> >>>>Hi and thank you for the answer Jonathan!
> >>>>
> >>>>Do you happen to also know a good reference on how to
> >>>>incorporate an overlay into the yocto build?
> >>>>
> >>>>On December 21, 2023 15:58:56 Jon Cormier
> >>>><jcormier@criticallink.com> wrote:
> >>>>
> >>>>>Here is a possible example overlay that configures pinmuxes
> >>>>>with the expectation that the pru's will use them. There is
> >>>>>likely a similar example in that long list of overlays that
> >>>>>disables hdmi.
> >>>>>
> >>>>>https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-RPROC-4-19-TI-PRUCAPE-00A0.dts
> >>>>>
> >>>>>Note its entirely possible these examples won't build or apply
> >>>>>correctly on a different kernel version, but they should still
> >>>>>be a decent starting point.
> >>>>>
> >>>>>On Thu, Dec 21, 2023 at 6:34 AM Lukasz Przenioslo
> >>>>><bremenpl@gmail.com> wrote:
> >>>>>>Hello there,
> >>>>>>
> >>>>>>I was able to compile the Poky image (Dunfell) with meta-ti
> >>>>>>included for the BBB. I am working on an open source project
> >>>>>>intended for home automation based on the BBB:
> >>>>>>https://github.com/Beaglenode/BeagleNodeHW
> >>>>>>
> >>>>>>The next step I am trying to make is to prepare a proper
> >>>>>>device tree overlay that would align with the HW
> >>>>>>requirements of this project (or "cape"). I need to:
> >>>>>>- Disable the HDMI pins,
> >>>>>>- configure multiple pins as either PRU0 or PRU1 controlled.
> >>>>>>
> >>>>>>For that I thought the best approach would be to prepare a
> >>>>>>DTO, instead of modifying the default one for BBB. I don't
> >>>>>>know how to prepare that DTO yet and I don't know how to
> >>>>>>include it in my build. I would like to ask for some help in
> >>>>>>this manner, especially the prior part (how to load the
> >>>>>>custom DTO). Right now I am still modifying everything in
> >>>>>>the local.conf, as I do not have the knowledge yet to build
> >>>>>>my own distro for this device (that's the end plan).
> >>>>>>
> >>>>>>I would appreciate all help!
> >>>>>>
> >>>>>>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re[2]: [meta-ti] Custom device tree overlay for BBB
2023-12-22 7:03 ` Denys Dmytriyenko
@ 2023-12-22 8:34 ` Łukasz Przeniosło
0 siblings, 0 replies; 9+ messages in thread
From: Łukasz Przeniosło @ 2023-12-22 8:34 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: Jon Cormier, meta-ti
[-- Attachment #1: Type: text/plain, Size: 5231 bytes --]
Thanks for the follow up Denys,
It's difficult for me to derive optimal solutions here, as I am only
learning the Yocto environment. Eventually I would like to create a
"custom OS" that would just build all needed ecosystem for the end
device.
At this point I am trying to make a proof of concept approach in which I
(via device tree overlay) will be able to deinitialize the HDMI pins and
configure at least one pin as a PRU mapped (mode 5 or 6 if I recall
correctly).
I will try to make something out of your's and Jon's answers for that
end. Thank you again.
--
Łukasz Przeniosło
------ Original Message ------
From "Denys Dmytriyenko" <denis@denix.org>
To "Lukasz Przenioslo" <bremenpl@gmail.com>
Cc "Jon Cormier" <jcormier@criticallink.com>;
meta-ti@lists.yoctoproject.org
Date 2023-12-22 08:03:56
Subject Re: [meta-ti] Custom device tree overlay for BBB
>Sorry, this got a bit out of context - one of the solutions from Jon was
>talking about adding a bbappend to a kernel recipe, which would then
>automatically handle KERNEL_DEVICETREE list via kernel-devicetree,bbclass
>
>Alternatively, if you add a standalne recipe, all you need is to add your
>overlay to SRC_URI and inherit devicetree.bbclass
>
>
>On Fri, Dec 22, 2023 at 06:14:51AM +0100, Lukasz Przenioslo wrote:
>> Hi Denys,
>> Should be easy enough to test it quickly as a proof of concept,
>> thank you. Will bitbake know to compile this overlay, tell the
>> u-boot to load it and so on?
>>
>> On December 22, 2023 02:49:39 Denys Dmytriyenko <denis@denix.org> wrote:
>>
>> >You could simply add your overlay in one of the conf files, such as
>> >local.conf:
>> >
>> >KERNEL_DEVICETREE += "your-overlay.dtbo"
>> >
>> >Check the existing machine conf files for examples.
>> >
>> >
>> >On Thu, Dec 21, 2023 at 08:51:49PM +0000, Lukasz Przenioslo wrote:
>> >>Hi Jon,
>> >>I guess the first option is more feasible, as I would not like to
>> >>modify any files provided by the Poky repo, but rather create my own
>> >>recipe that would somehow cover the default settings during the
>> >>build. There is still a lot ahead for me to understand though...
>> >>
>> >>Thank you for the useful links.
>> >>
>> >>--
>> >>Łukasz Przeniosło
>> >>
>> >>
>> >>------ Original Message ------
>> >>From "Jon Cormier" <jcormier@criticallink.com>
>> >>To "Bremenpl" <bremenpl@gmail.com>
>> >>Cc meta-ti@lists.yoctoproject.org
>> >>Date 2023-12-21 16:17:38
>> >>Subject Re: [meta-ti] Custom device tree overlay for BBB
>> >>
>> >>>This solution seems like a good place to start. I haven't tried it
>> >>>myself but it looks clean and easy to implement.
>> >>>https://stackoverflow.com/a/68650774
>> >>>
>> >>>The alternative would be to bbappend the kernel and patch your
>> >>>overlay into the correct folder.
>> >>>https://stackoverflow.com/a/39343720
>> >>>
>> >>>On Thu, Dec 21, 2023 at 10:03 AM Bremenpl <bremenpl@gmail.com> wrote:
>> >>>>Hi and thank you for the answer Jonathan!
>> >>>>
>> >>>>Do you happen to also know a good reference on how to
>> >>>>incorporate an overlay into the yocto build?
>> >>>>
>> >>>>On December 21, 2023 15:58:56 Jon Cormier
>> >>>><jcormier@criticallink.com> wrote:
>> >>>>
>> >>>>>Here is a possible example overlay that configures pinmuxes
>> >>>>>with the expectation that the pru's will use them. There is
>> >>>>>likely a similar example in that long list of overlays that
>> >>>>>disables hdmi.
>> >>>>>
>> >>>>>https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-RPROC-4-19-TI-PRUCAPE-00A0.dts
>> >>>>>
>> >>>>>Note its entirely possible these examples won't build or apply
>> >>>>>correctly on a different kernel version, but they should still
>> >>>>>be a decent starting point.
>> >>>>>
>> >>>>>On Thu, Dec 21, 2023 at 6:34 AM Lukasz Przenioslo
>> >>>>><bremenpl@gmail.com> wrote:
>> >>>>>>Hello there,
>> >>>>>>
>> >>>>>>I was able to compile the Poky image (Dunfell) with meta-ti
>> >>>>>>included for the BBB. I am working on an open source project
>> >>>>>>intended for home automation based on the BBB:
>> >>>>>>https://github.com/Beaglenode/BeagleNodeHW
>> >>>>>>
>> >>>>>>The next step I am trying to make is to prepare a proper
>> >>>>>>device tree overlay that would align with the HW
>> >>>>>>requirements of this project (or "cape"). I need to:
>> >>>>>>- Disable the HDMI pins,
>> >>>>>>- configure multiple pins as either PRU0 or PRU1 controlled.
>> >>>>>>
>> >>>>>>For that I thought the best approach would be to prepare a
>> >>>>>>DTO, instead of modifying the default one for BBB. I don't
>> >>>>>>know how to prepare that DTO yet and I don't know how to
>> >>>>>>include it in my build. I would like to ask for some help in
>> >>>>>>this manner, especially the prior part (how to load the
>> >>>>>>custom DTO). Right now I am still modifying everything in
>> >>>>>>the local.conf, as I do not have the knowledge yet to build
>> >>>>>>my own distro for this device (that's the end plan).
>> >>>>>>
>> >>>>>>I would appreciate all help!
>> >>>>>>
>> >>>>>>
[-- Attachment #2: Type: text/html, Size: 10921 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2023-12-22 8:34 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-12-21 11:34 Custom device tree overlay for BBB Lukasz Przenioslo
2023-12-21 14:58 ` [meta-ti] " Jon Cormier
2023-12-21 15:03 ` Bremenpl
2023-12-21 15:17 ` Jon Cormier
2023-12-21 20:51 ` Re[2]: " Łukasz Przeniosło
2023-12-22 1:49 ` Denys Dmytriyenko
2023-12-22 5:14 ` Bremenpl
2023-12-22 7:03 ` Denys Dmytriyenko
2023-12-22 8:34 ` Re[2]: " Łukasz Przeniosło
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.