<derRichard>
Tartarus: test/py/tests/test_ut.py is more of a mess than i have expected. in the good case, setup_bootflow_image() silently fails. mount_image() fails, and it falls back to copy_prepared_image()
<derRichard>
*after* my changes, mount_image() no longer fails because it does not need sudo nor root permissions and image creation files because the path to[D[D mkimage is wrong
enok has joined #u-boot
enok has quit [Ping timeout: 252 seconds]
Clamor has quit [Read error: Connection reset by peer]
Clamor has joined #u-boot
Clamor has quit [Ping timeout: 244 seconds]
Clamor has joined #u-boot
Clamor has quit [Ping timeout: 255 seconds]
Clamor has joined #u-boot
slobodan has joined #u-boot
slobodan has quit [Read error: Connection reset by peer]
dsimic has quit [Ping timeout: 252 seconds]
slobodan has joined #u-boot
dsimic has joined #u-boot
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #u-boot
rockosov has quit [Ping timeout: 244 seconds]
rockosov has joined #u-boot
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #u-boot
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #u-boot
jdiez has joined #u-boot
<jdiez>
hi. is it possible to boot a FIT image with a kernel and ramdisk, but no fdt image? I'm trying to boot a yocto build with meta-updater, and the FIT image this builds contains a FDT that is not exactly what I want and I'd like to use the FDT passed to u-boot by the raspberry pi bootloader
<jdiez>
I can boot the FIT image like this, without the ramdisk: `bootm $loadaddr - $fdt_addr` (fdt_addr is the fdt provided by the rpi bootloader)
<jdiez>
and I'm not sure I can know the address of the ramdisk ahead of time, to put it in the second argument instead of '-'
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #u-boot
<marex>
jdiez: see help bootm , look for : and #
<marex>
jdiez: there is a section which lets you pick an image for each of the three parameters using : , so ... bootm $loadaddr:kernel-1 $loadaddr:ramdisk-1 $someotheraddr
<marex>
that should work
<jdiez>
marex: brilliant, thank you!
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #u-boot
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #u-boot
<jdiez>
I'm also getting a "data abort exception" when trying to start the kernel. the PC is very close to the entry point of the kernel (0x00008000 -> 0x00080024), but I'm fairly certain this kernel is compiled correctly for this machine: https://paste.sr.ht/~jdiez/fd6d0e9b563b36fc5c554d77c7e0708c44b837a6
<jdiez>
could it be because the ramdisk load address is undefined, and the kernel tries to access it early on?
<marex>
the fitImage load code checks for overlaps, so unlikely
<marex>
if this is arm64, then the entrypoint shouldn't be at 4-byte aligned offset
<marex>
it has to be at 2 MiB aligned offset
<jdiez>
this is 32 bit arm
<marex>
do you have fdt_high set ?
<jdiez>
yeah, it is 0xffffffff
<marex>
which soc / system / ... is this ? U-Boot version ?
<jdiez>
rpi zero w, u-boot 2024.01
<marex>
right, so fdt_high=0xffffffff you shouldn't use in most cases
<marex>
that means use fdt in place , and that may not work well
<marex>
try and unset it
<jdiez>
same result
<jdiez>
not sure what is meant by "fdt in place", but my understanding is that the 2nd stage RPi bootloader creates a FDT according to /boot/config.txt, which is passed to u-boot at $fdt_addr
<marex>
that's possible, yes, rpi does something about passing DT around
<jdiez>
and my intention is to pass that to the kernel as-is without using the FDT in my FIT image
<jdiez>
which i think is now happening with the image selections in the `bootm` command, but the ramdisk may still not be passed properly