07:13 <Danct12> v5 of the vop2 u-boot patches https://lore.kernel.org/u-boot/20250607-vop2-pt2-v5-0-1d52f7a2cf3c@riseup.net

08:35 <warpme> detlevc : with latest code from https://gitlab.collabora.com/detlev/linux/-/commits/add-vdpu381-and-383-to-rkvdec we are almost good on 3576. iommu errors gone. decoding plays but with some artefacts like this: http://minimyth2.mooo.com/rk3576-h264.mov I tested on mythtv and kodi, with egl-dmabuf and direct-to-plane. artefacts are the same in all cases. interesting that on one try i got perfect picture but it was only once. i tried 20 times or so

08:36 <warpme> but can't get it again

19:04 <catcream> hey, trying to compile u-boot for my radxa 4se (rk3399). I first compile atf with PLAT=rk3399 and then compile u-boot with BL31=$atf/build/fvp/release/bl31/bl31.elf. I flashed idbloader-spi.img to sector 64 and u-boot.itb to 0xe000. When booting it complains about fit:atf-3 being empty and it stops. I did check with mkimage -l on u-boot.itb and in fact it is empty. Any clue what to do?

19:05 <catcream> mkimage -l https://paste.gentoo.zip/6QYERIvB

19:06 <catcream> boot log: https://paste.gentoo.zip/zUfhso0Z

19:09 <CounterPillow> What's "fvp"? Usually I'd expect it to be in build/rk3399/release/bl31/bl31.elf

19:09 <CounterPillow> also, modern mainline versions of u-boot should give you a unified u-boot-rockchip.bin, no separate idbloader

19:10 <catcream> no clue actually, it just puts bl31 in fvp directory when doing make PLAT=rk3399 bl31

19:10 <catcream> oh okay

19:11 <CounterPillow> I assume you're using some vendor u-boot from 2017 or so instead?

19:11 <catcream> so I can flash u-boot-rockchip-spi.bin directly?

19:11 <CounterPillow> sure, if you're flashing onto an SPI chip

19:11 <catcream> I use upstream u-boot 2025.07-rc4 on radxa 4c+

19:11 <CounterPillow> goes at offset 0 in that case. If you're flashing eMMC/SD, you'll want u-boot-rockchip.bin at sector 64

19:11 <catcream> okay nice

19:11 <CounterPillow> You don't need to use the mkimage in rkbins at all

19:13 <catcream> alright thanks!

19:13 <catcream> flashing now

19:16 <catcream> CounterPillow: tried it now, same thing sadly :/

19:16 <catcream> seems like something's messed up with atf-3 fit volume

19:16 <CounterPillow> what does `file build/rk3328/release/bl31/bl31.elf` say

19:16 <CounterPillow> also can you show me your full u-boot build log?

19:16 <CounterPillow> err

19:16 <CounterPillow> sub rk3328 with fvp there

19:17 <catcream> bl31.elf: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, not stripped

19:17 <CounterPillow> okay, so at least it's built for the right architecture

19:18 <catcream> yup, ill recompile u-boot and send log

19:19 <catcream> https://paste.gentoo.zip/ofvcvKWi - u-boot build log with V=1

19:22 <CounterPillow> apparently it's picking tf-a from "/home/cat/proj/sbc/4se/src/bl31.elf", is this correct?

19:22 <catcream> yea I copied it there

19:23 <catcream> btw I'm compiling atf from https://github.com/ARM-software/arm-trusted-firmware/archive/refs/tags/v2.13.0.tar.gz. Is that correct?

19:23 <catcream> make PLAT=rk3399 bl31

19:24 <catcream> here's my "source" file that I put envvars in https://paste.gentoo.zip/qXSYTac9

19:26 <CounterPillow> should be fine, yeah, though my atf when I `make PLAT=rk3399 bl31` does put it in the rk3399 subdirectory.

19:27 <CounterPillow> also since you're a gentoo user: make sure you don't have some insane cflag overrides set that are interfering

19:28 <catcream> seems fine with "env"

19:28 <catcream> btw should I use arm-trusted-firmware or trustedfirmware-a?

19:30 <CounterPillow> they're both the same, ARM just keeps changing the name

19:31 <CounterPillow> they call it trusted-firmware-a these days I think

19:35 <catcream> hmm tried cloning trusted-firmware-a lts-2.12.3 tag and now I get bl31.elf in trusted-firmware-a/build/rk3399/release/bl31/bl31.elf

19:35 <catcream> ill try it

19:38 <catcream> nice atf-3 seems to be 4096 bytes now

19:39 <catcream> takes like 2 mins to flash though

19:47 <catcream> CounterPillow: yay it starts u-boot now

19:47 <catcream> thanks!

19:47 <CounterPillow> Nice

19:48 <catcream> btw it says

19:48 <catcream> load_simple_fit: Skip load 'atf-5': image size is 0!

19:48 <catcream> NOTICE: BL31: v2.12.3(release):lts-v2.12.3

19:48 <catcream> NOTICE: BL31: Built : 21:34:21, Jun 15 2025

19:48 <catcream> U-Boot 2025.07-rc4 (Jun 15 2025 - 21:37:18 +0200)

19:48 <catcream> then it starts u-boot as normal, I guess I don't need to worry about atf-5?

19:49 <CounterPillow> imma be real I have no idea

19:50 <catcream> okay lol

19:50 <catcream> seems to work fine so whaterver

19:50 <CounterPillow> might be where it stores the optional MCU code, but that's a wild guess

19:57 <catcream> CounterPillow: yes I read somewhere that for some platforms you could compile some atf thing for cortex-m0 mcu