11:47 <pmolloy> 👋 I trying to get the SPL to initialize a GPIO expander and enable a GPIO (already defined as a hog in the dt) which enables the main UART. I'm not sure that the devicetree is even being parsed. I have CONFIG_OF_EMBED, but does that embed in U-Boot proper and the SPL? I assume not? If I'm loading SPL over JTAG do I also need to load the dtb into

11:47 <pmolloy> memory to a address configured at build time in the SPL?

12:06 <pmolloy> https://elixir.bootlin.com/u-boot/v2025.04/source/README#L1427-L1429 should probably get updated with the SPL-XPL renaming

12:13 <pmolloy> Also if there is anyone here at denx or around Munich, you may be interested in https://www.munich-embedded.com

12:39 <mkorpershoek> pmolloy: do you use the bootph properties in your DT to make sure it's part of SPL ? https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/bootph.yaml

12:40 <mkorpershoek> also see: https://docs.u-boot.org/en/latest/develop/driver-model/design.html#pre-relocation-support

12:40 <mkorpershoek> > To reduce the size of SPL and TPL, only the nodes with pre-relocation properties (‘bootph-all’, ‘bootph-pre-ram’ or ‘bootph-pre-sram’) are kept in their device trees

12:43 <pmolloy> Hey mkorpershoek, yah, bootph-pre-ram on the expander node and each GPIO node

12:44 <pmolloy> It is a bit hard to parse through what will be done automatically and what needs to be in board_init. I know the driver for the expander isn't getting called based on a breakpoint. But I'm not sure what other functions I can break on to help debug it

12:44 <pmolloy> Something like spl_*_of_*()

15:03 <Tartarus> Sigh

15:03 <Tartarus> A number of things about "allyesconfig" seem to rely on the "default to 0 if not specified" behavior in current kbuild

15:03 <Tartarus> Which I *really* dislike for papering over bugs in the not-COMPILE_TEST use case

15:19 <Tartarus> And, oh, yeah, 'allyesconfig' is gonna be different for U-Boot, hah

15:20 <Tartarus> Since I didn't realize it throws away an existing config, really, oops. So we can't do an ARM-allyesconfig because architecture is a choice

15:20 <Tartarus> So sandbox only it is

18:48 <rty> hi. is there some way in u-boot to load and inspect the compiled device tree for u-boot itself at runtime, like of_fixup in barebox? for debugging purposes

18:50 <rty> when I tried to use fdt command according to the example in the docs, I got some error about bad magic. the documentation is not particularly helpful...

18:54 <Forty-Bot> fdt addr $fdtcontroladdr

18:54 <Forty-Bot> I think

18:58 <rty> also, I need an advice on how to debug the splash screen in u-boot. I managed to make it work more or less, but it seems like my display just "fades out" when the kernel boot is about to start and I'd like to know why, and what I can do about that. can I send a link to a video?

21:28 <Guest82> include/config.h:3:10: fatal error: configs/.h: No such file or directory 3 | #include <configs/.h>|          ^~~~~~~~~~~~ compilation terminated.. Can anyone tell me whjat does this error mean? I have already included my header file under include/configs