<tlwoerner>
on boards, such as some of the rockchip ones, that have both emmc and sdmmc, is it possible to change the probe order dynamically (i.e. without a patch)?
ikarso has quit [Quit: Connection closed for inactivity]
<apteryx>
hi! if I use both a uEnv.txt and a boot.scr, is the former going to be used too?
monstr has quit [Remote host closed the connection]
<marex>
tlwoerner: probe order ?
<marex>
tlwoerner: why would you care ?
<tlwoerner>
marex: to save the environment
<tlwoerner>
(but not the planet)
<tlwoerner>
on the rock-pi-4b it can boot from either the emmc or the sdcard. in my case i don't have emmc, so i boot from the sdcard
<tlwoerner>
but when i try to save the environment, it complains about the card not responding to voltage select (blah blah blah)
<tlwoerner>
but switching the aliases, in code, will make it work for me
<tlwoerner>
so i was wondering if there was a fancier way of doing it that didn't require a patch
<Forty-Bot>
tlwoerner: the env selection is baked into the code
<Forty-Bot>
typically it is static, but iirc you can also select it dynamically
<marex>
board/dhelectronics/dh_imx6/dh_imx6_spl.c ... this one ... board_mmc_get_env_dev()
<apteryx>
how can I configure u-boot to *not* load a device tree? It shoud be already loaded in memory by the raspberry pi firmware I'm working with
<Forty-Bot>
CONFIG_OF_BOARD
<marex>
iirc that's already done in some fdtdec_board_setup or so
<marex>
just inhibit that functionality
<marex>
but then, wont you lose the crud firmware patches in ?
<apteryx>
OK, that seems to be already on (OF_BOARD [=y])
<apteryx>
the error I got when trying to boot the compressed Image kernel was: ERROR: Did not find a cmdline Flattened Device Tree
<apteryx>
I'm trying to boot the stock kernel8.img 64 bit kernel provided by the raspberry pi official images
<sylensky[m]>
apteryx: do you provide the address where the fdt is loaded to?
<sylensky[m]>
apteryx: assuming you run the booti cmd
<apteryx>
the default should be fine (0x02600000); I use "booti ${kernel_addr_r} - ${fdt_addr_r}" to boot the loaded kernel
<sylensky[m]>
apteryx: rpi has some propriatary firmware which expects some files.. in your case you need the bcm2*.dtb in your boot partition which gets loaded from the videocore to 0x2eff... somewhere..
<sylensky[m]>
apteryx: then you should be fine using ${fdt_addr_r}
<apteryx>
just checked, fdt_addr_r is at 0x02600000 as expected
<sylensky[m]>
apteryx: and is the dtb loaded?
<apteryx>
the board is a rpi 4 B, so it should use the bcm2711-rpi-4-b.dtb which is there
<apteryx>
sylensky[m]: how can I check if it's really loaded?
<apteryx>
I guess I can load it manually and retry the booti
<sylensky[m]>
apteryx: in the config.txt that the rpi wants to read upon start write uart_2ndstage=1 and enable_uart=1 then you see these related logs
<apteryx>
ah, I guess it wasn't loaded, after loading it manually and retrying booti the kernel started (and crashed)
guillaume_g has quit [Quit: Konversation terminated!]
<apteryx>
OK! I'll add uart_2ndstage=1 which I didn't have, thanks!
<sylensky[m]>
does someone save the environment on a ext4 filesystem in a bare file and experience bad crc issues when trying to read the environment from the userspace?
<sylensky[m]>
but reading from u-boot console it works just fine
persmule has quit [Ping timeout: 255 seconds]
persmule has joined #u-boot
<apteryx>
sylensky[m]: interesting, I had to add 'device_tree_address=0x02600000' in config.txt
<apteryx>
although I thought that should have been the default
<sylensky[m]>
apteryx: wierd.. allthough iam booting with downstream dtb's mine gets loaded to 0x2eff2e00 as default. which works perfectly fine
mckoan is now known as mckoan|away
prabhakarlad has quit [Quit: Client closed]
<apteryx>
my u-boot was built using rpi_arm64_defconfig
vagrantc has joined #u-boot
<sylensky[m]>
apteryx: i used the same as a base but didnt change addresses related to dtb and kernel
<vagrantc>
heya guix
<apteryx>
vagrantc: wrong channel? :-) o/
<vagrantc>
hah
frieder has quit [Remote host closed the connection]
* vagrantc
is happy to see apteryx in #u-boot :)
prabhakarlad has joined #u-boot
<apteryx>
hehe!
<apteryx>
can a 64 bit u-boot boot a 32 bit zImage?