From: "Łukasz Przeniosło" <bremenpl@gmail.com>
To: "Denys Dmytriyenko" <denis@denix.org>
Cc: "Jon Cormier" <jcormier@criticallink.com>,
meta-ti@lists.yoctoproject.org
Subject: Re[2]: [meta-ti] Custom device tree overlay for BBB
Date: Fri, 22 Dec 2023 08:34:16 +0000 [thread overview]
Message-ID: <em1018559f-c228-4883-b996-9c80784a44ce@ffb2c130.com> (raw)
In-Reply-To: <20231222070356.GN11745@denix.org>
[-- 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 --]
prev parent reply other threads:[~2023-12-22 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Łukasz Przeniosło [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=em1018559f-c228-4883-b996-9c80784a44ce@ffb2c130.com \
--to=bremenpl@gmail.com \
--cc=denis@denix.org \
--cc=jcormier@criticallink.com \
--cc=meta-ti@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).