From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Compiled in boot environment and dtbo files
Date: Mon, 21 Jun 2021 16:21:06 +0200 [thread overview]
Message-ID: <D71BFF12-5C4D-4C41-B15F-2D53376F5669@inside-m2m.de> (raw)
In-Reply-To: <20210621040155.GD9782@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2769 bytes --]
Dear community, dear Sascha,
an accident happened on my side. I totally overlooked that after my initial mail with the
initial quoted error message the message changed.
Probably either the change of compiling the dtb file (make dtbs DTC_FLAGS=-@) got
me a __symbols__ node or another thing was sorted out by me on accident meanwhile
since still I am trying to get used to device tree handling.
In detail, this messages are not valid any more:
>>>> Loading ARM Linux zImage '/boot/uImage'
>>>> Loading devicetree from '/boot/am335x-boneblack.dtb'
>>>> ERROR: of_resolver: __symbols__ missing from base devicetree
>>>> WARNING: Failed to fixup node in of_overlay_fixup+0x1/0x4: Invalid argument
>>>> ERROR: of_resolver: __symbols__ missing from base devicetree
>>>> WARNING: Failed to fixup node in of_overlay_fixup+0x1/0x4: Invalid argument
but I get a different set of errors. Probably since including Friday and I overlooked this.
How embarassing, sorry!
Now I get:
ERROR: of_resolver: cannot find node ocp in base devicetree
WARNING: Failed to fixup node in of_overlay_fixup+0x1/0x4: Invalid argument
ERROR: of_resolver: cannot find node ocp in base devicetree
WARNING: Failed to fixup node in of_overlay_fixup+0x1/0x4: Invalid argument
which is very reasonable:
> Have a look at the generated dtb file with 'dtc -I dtb -O dts <file>'.
> It should contain a __symbols__ node.
The decompiled result of “my” dtb has a __symbols__ note at the bottom of the file, yes!
I suppose each “fragment@n {target = XYZ …”) in a overlay has to have a matching
counterpart XYZ in the __symbols__ node in the base file, right? Because in my overlay
there is an "target = <&ocp>!" without a matching counterpart in the base dtb.
Two other entries (uart1, am33xx_pinmux) have a matching entry.
> BTW do you have a good reason to use overlays? Overlays only have a
No indeed I don’t necessarily - I realized meanwhile by myself.
Additionally I relaized the overlays I have here in question only do some GPIO
multiplexing I can do by hand/script in the /sys gpio section anyway. Only interesting
for serial line availability at boot. May be later it’s interesting for us for different
variante, I hope I am used to this stuff then.
> value when you have different hardware variants in which different
> overlays are loaded. If that's not the case I'd just go with a static
> devicetree and be done with it.
For now I agree and I try to understand how to enable the UART1 and UART4
in a static dtb way and I currently search the vanille device tree on how to do
this and how this currently this is done at least with the working UART0 :-)
Sadly not barebox related :-)
Kind Regards
Konsti
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4124 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-06-21 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 8:10 Konstantin Kletschke
2021-06-16 12:34 ` Sascha Hauer
2021-06-16 15:57 ` Konstantin Kletschke
2021-06-16 19:55 ` Trent Piepho
2021-06-18 12:43 ` Konstantin Kletschke
2021-06-17 6:41 ` Sascha Hauer
2021-06-18 13:15 ` Konstantin Kletschke
2021-06-21 4:01 ` Sascha Hauer
2021-06-21 14:21 ` Konstantin Kletschke [this message]
2021-06-22 10:40 ` Konstantin Kletschke
2021-06-18 6:48 ` Ahmad Fatoum
2021-06-18 13:16 ` Konstantin Kletschke
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=D71BFF12-5C4D-4C41-B15F-2D53376F5669@inside-m2m.de \
--to=konstantin.kletschke@inside-m2m.de \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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