05:28 <mrkiko> marex: thanks! Uh, missed it.

08:58 <Guest22> Can anyone tell me how can I bring uboot to print debug messages from a file let's say fec_mxc.c? I have tried by adding 1) #debug 2)#define LOG_DEBUG in the file and kconfig to be CONFIG_LOG_MAX_LEVEL=9. However I am getting debug messages printed out. I have tried with other files as well e.g. with bootp.c. It never prints me anything on console.

08:58 <Guest22> Can anyone please help me with this regards

09:13 <LeSpocky> guest22: add '#define DEBUG' on top of the file and then adapt console log levels

11:05 <sjg1> mrkiko: marex: It should not 'fail to request the gpio if mtk pinctrl is not inited at dm_probe() time'. Why does it fail? Can that be fixed?

11:07 <Guest22> LeSpocky it doesn't help me. I have //#undef DEBUG

11:07 <Guest22> #define DEBUG in fec_mex.c

11:07 <Guest22> and CONFIG_LOG_MAX_LEVEL=7 in kconfig

11:18 <LeSpocky> guest22: there's a difference between CONFIG_LOGLEVEL and CONFIG_LOG_MAX_LEVEL and CONFIG_LOG_DEFAULT_LEVEL, you should also consider CONFIG_LOG and CONFIG_LOG_CONSOLE and maybe you should read https://docs.u-boot.org/en/latest/develop/logging.html again

11:36 <Guest22> LeSpocky thank you very much

12:27 <marex> Tartarus: hey so why are we not generating checksum into fitImage config node with mkimage -f auto ?

12:28 <marex> we only generate checksum for images, but not for the config node

12:31 <LeSpocky> marex: maybe try `mkimage -f auto-conf` instead?

12:33 <marex> LeSpocky: see tools/fit_image.c fit_add_hash_or_sign()

12:33 <marex> LeSpocky: AF_HASHED_IMG applies to images only, AF_SIGNED_CONF needs key material

12:34 <marex> what I wonder is, do we want a new option -f auto-hash or just make -f auto also add hash to conf by default

14:11 <Tartarus> marex: Ask sjg1 he's the FIT expert

17:35 <Tartarus> qschulz: Were you expecting more feedback on https://patchwork.ozlabs.org/project/uboot/patch/20241015-dm-debug-less-verbose-v1-1-366e8f00b556@cherry.de/ ?

18:11 <dormito> Is there a way to inspect u-boots control device tree at run time?

18:16 <dormito> mmm. I think : "fdt addr ${fdtcontroladdr}; fdt print" does what I want... at least on this board

18:18 <apalos> it does

18:26 <dormito> for a FIT image, is there anything other than the compatible that would cause bootm to report "Wrom Image Type for bootm" ?

18:54 <Tartarus> I guess the silly question would be did you manually checksum and compare with the file?

18:54 <Tartarus> like crc32 $addr $filesize vs rhash -C /local/file

18:59 <Sout_> which version of crc32 :P (fun with crypto and math)

19:10 <dormito> it seems the issue was sillier. previous version (&| builds) of u-boot "bootm", when given no args, would use the correct argument to find the image (I THINK it was loadaddr), but this build seems to have been looking elsehwere.