09:24 <xypron> Tartarus: I sent you fixes for riscv32 and Xilinx with GCC-12. There is still an open problem with the sandbox (https://source.denx.de/u-boot/custodians/u-boot-efi/-/jobs/510393).

10:03 <hays> I am a relative n00b to u-boot. where can I begin to understand/decode what this means? https://h0c.us/v/T-y1

10:08 <hays> where are all the environment variables coming from?

10:14 <hays> I am trying to validate what is at the end of this page -- a page that so far has been riddled with small errors and patches ive had to make.. and i want to make sure i don't brick the device https://espressobin.net/espressobin-ultra-build-instruction/

10:16 <LeSpocky> hays: do you have access to serial console, then `help env`, `help setenv`, `help saveenv` etc. might give you a good first hint

10:17 <hays> LeSpocky: I do--I will look there

10:17 <LeSpocky> hays: otherwise documentation should give you an idea what the environment is in u-boot: https://u-boot.readthedocs.io/en/latest/usage/environment.html

10:18 <LeSpocky> after that you might split up the contents of the bootcmd environment variable by ';' and look at each command separately

10:19 <LeSpocky> those commands are executed by u-boot to boot the device if you don't interrupt and go to u-boot shell

10:19 <hays> how different is all of this going to be given im using u-boot 2018 (u-boot-2018.03-armada-18.12-gti)

10:31 <LeSpocky> hays: those basic concepts have not changed for several years, 2018 is recent enough the docs still apply

10:31 <hays> great

10:31 <LeSpocky> (and typing `help …` on the shell of course gives you matching help texts for the actually running version

10:31 <LeSpocky> )

10:33 <hays> thanks for the tips. off to read and experiment

13:15 <Tartarus> xypron: thanks

13:15 <Tartarus> sjg1: llvm-14 shows a problem on sandbox: https://source.denx.de/u-boot/u-boot/-/jobs/510282#L287

14:34 <sjg1> Tartarus: OK I will take a look. It is a pain to debug due to the compiler optimisation, but it is dying at #252 in lists.c at the device_bind_with_driver_data() call

19:25 <bryanb> y5tcakbw

22:12 <hays> why is ext4load being called 3 times here -- setenv bootcmd 'mmc dev 0; ext4load mmc 0:1 $kernel_addr_r $image_name;ext4load mmc 0:1 $fdt_addr_r $fdt_name;setenv bootargs $console root=PARTUUID=89708921-01 rw rootwait net.ifnames=0 biosdevname=0; booti $kernel_addr_r - $fdt_addr_r'

22:12 <hays> I'm sorry-- wrong one... bootcmd=mmc dev 0; ext4load mmc 0:1 $kernel_addr_r $image_name;ext4load mmc 0:1

22:26 <Forty-Bot> it's loading the kernel and fdt separately

22:27 <Forty-Bot> two files, two load commands

22:29 <hays> ext4load mmc 0:1 this one doesn't have any args

22:31 <urja> did you copy that off minicom or something? (it seems like a truncated line, and minicom by default truncates lines...)

22:31 <hays> hmm yes minicom

22:33 <urja> the option to wrap lines is -w

22:33 <urja> it also exists somewhere in the menus but i havent used it in such a long time that i dunno

22:33 <hays> what do you use

22:37 <Forty-Bot> I like picocom

22:37 <urja> I mean, these days i most likely use picocom (i dunno about Forty-Bot tho)

22:37 <Forty-Bot> lol

22:38 <urja> dang lol

22:38 <Forty-Bot> although most terminal emulators are saner than minicom

22:58 <hays> alright tomorrow i think im going to run these commands and hopefully not brick the device

22:59 <hays> I might skip updating the bootloader with the one I build since it seems to be the same version...

23:12 <marex> Forty-Bot: meta-W in minicom - toggle line wrap

23:23 <Forty-Bot> marex: my main issue is that minicom has bad defaults

23:24 <Forty-Bot> so I use something with better defaults which effectively doesn't need to be configured

23:30 <marex> I'm just glad I can configure the tools to fit my needs ...

23:36 <Forty-Bot> only worth it if the tool is reasonable :)