09:17 <Kwiboo> naoki: please see https://github.com/Kwiboo/u-boot-rockchip/commits/rk3xxx-2025.01-ramboot/ for an alternative ramboot that only depends on maskrom usb, was hoping to send it as an RFC in near future ;-)

09:19 <Kwiboo> also needed to add no-write-symbols props to fix an binman issue, may be the same you face, see https://github.com/Kwiboo/u-boot-rockchip/commit/20e53552062a75b7d681c7b9a5fdf15560a44c34

09:26 <Kwiboo> one possible issue with appending the U-Boot FIT to the usb472 image is that the rk atags TPL write to RAM at ~2MiB is overwritten, could be an issue for >16GiB rk3588 devices

10:14 <naoki> Kwiboo: The code looks very good. How does SPL know the u-boot.itb address?

10:16 <naoki> I couldn't solve it with booting from RAM

10:18 <naoki> Btw boot_merger is a closed program for x86-64 only. The best solution is for rockusb to support "rockusb tpl spl(+u-boot)"

10:20 <naoki> ah CONFIG_SPL_LOAD_FIT_ADDRESS

10:27 <naoki> Kwiboo: SPL placed at CFG_SYS_SDRAM_BASE, and u-boot.itb in u-boot-rockchip-usb472.bin is placed at CONFIG_SPL_LOAD_FIT_ADDRESS, right?

10:31 <naoki> is 2MB too much? or SPL uses SDRAM_BASE+2MB space?

10:32 <naoki> ah, RK atags

10:32 <naoki> hmm

10:35 <naoki> no-write-symbols; is only for CONFIG_ROCKCHIP_SPI_IMAGE?

10:38 <naoki> Is it not compatible with RK3328?

10:53 <Kwiboo> naoki: correct, SPL is loaded to CFG_SYS_SDRAM_BASE, and FIT/u-boot.idb is placed at 2 MiB, mainly because 256KiB-2MiB may be used/reserved for TF-A, puting it at 1 MiB also works, but qschulz suggested to instead use the 2 MiB offset a few weeks back

10:55 <Kwiboo> regarding no-write-symbols, it seem it was only needed in the spi image, but only after a new binman image was added, feels like it should have already complained, not sure what is going on

11:12 <Kwiboo> the idea was to combine SPL + FIT/u-boot.itb as close as possible so that both payload could be sent using the 472 usb command, sending 2-3 MiB using the windows rkdevtool was very slow, using linux rkdeveloptool db or rockusb command was very fast, at least on the rk356x/rk3588 board I tested

11:12 <Kwiboo> tricky part is getting load addresses correct, so payload do not overlap where SPL want to load the images from FIT

11:16 <Kwiboo> and use of boot_merger is strictly not necessary, only for rkdeveloptool/rkdevtool/rockusb tools, beause they expect the input in that format, and if needed we could add simple support for that image format to the u-boot mkimage tool

11:18 <Kwiboo> however best would be to extend the tools to support separate 471 and 472 input files and do any special handling based on the usb product id or similar on the fly

11:20 <Kwiboo> should make u-boot development/CI for rockchip little bit easier, no need for e.g. sd-mux or similar

11:21 <Kwiboo> naoki: for reset to download mode at hang(), see https://patchwork.ozlabs.org/project/uboot/patch/20240202001221.531207-1-jonas@kwiboo.se/ :-)

11:51 <naoki> hmm

11:57 <naoki> Btw, there is "upgrade_tool" which is provided as binary only for Linux ;)

11:57 <naoki> rkdeveloptool is relatively new thing :)

12:01 <naoki> rkflashtool was born before everything was open, and it's dirty because its predecessor, `rkflash`, was very dirty. XD

12:10 <naoki> ah, sorry, your change supports rk3328 too

13:27 <naoki> Oh I noticed RK3528 is not supported yet in U-Boot ;)