19:27 <macromorgan> anybody have rk3588 working on mainline U-Boot? I can get it to start, but it takes a crap with "DRAM init failed: -19". Tested with different TPL stages and different A-TF binaries to no avail.

19:29 <Tenkawa> Let me check mine

19:30 <Tenkawa> I have a few but I think they are all vendor uboot

19:35 <Tenkawa> Yeah I just confirmed our images ( 3588 and 3588s ) are all vendor still

19:38 <macromorgan> damn

19:38 <macromorgan> okay, trying to do mainline and getting stuck there. Can't see an obvious error.

19:40 <macromorgan> I can confirm this is explicitly where it fails with the -19 error: https://source.denx.de/u-boot/u-boot/-/blob/master/arch/arm/mach-rockchip/sdram.c#L202

19:41 <Tenkawa> Yeah we are running into something similar with Radxa E25 based on the Rock CM3

19:42 <Tenkawa> debug trace seems to indicate it can't read the mmc

19:42 <Tenkawa> It tries to boot the kernel then the mmc can't be found.

19:43 <Tenkawa> We did discover today one more offset it might need in its dd write

19:43 <Tenkawa> its a gpt unlike most

19:45 <Tenkawa> RK3568 aren't difficult usually (I have an Odroid-M1) but this one is unique.. and two of us are trying to remotely debug it for a third person

20:08 <Kwiboo> macromorgan: my wip branch at https://github.com/Kwiboo/u-boot-rockchip/commits/rk35xx should have pretty decent rk35xx support now, my boards can boot from sd, emmc and/or spi

20:11 <Kwiboo> working on final touches on a rk3588 emmc series, will re-test the pushed branch on my rock 5b board

20:15 <Kwiboo> macromorgan: -19 is ENODEV, is your build missing ram driver, do you have SPL_RAM=y

20:16 <macromorgan> I do, I'm chasing down what I think the issue is now

20:16 <Kwiboo> if you are using u-boot master branch or v2023.04-rc4 it is missing important props in device tree

20:18 <Kwiboo> https://source.denx.de/u-boot/custodians/u-boot-rockchip/-/commits/u-boot-rockchip-20230319 include important fixes

20:19 <Kwiboo> this could be source of "missing device" issues: https://source.denx.de/u-boot/custodians/u-boot-rockchip/-/commit/8653e5d3b745925fced5fa6897c92f4a46ec2757

20:21 <Tenkawa> Kwiboo: whats your reference board you are using to run with?

20:23 <Tenkawa> I use a Rock5 here for the 3588 and Khadas Edge2 for the 3588s I will be eventually wanting to be moving to move to mainline once they can

20:25 <Kwiboo> I only have a rock-5b 8gb for rk3588 and for rk356x: rock-3a/3c, odroid-m1 and quartz64-a/b

20:31 <macromorgan> Kwiboo: I'm pretty sure that's exactly it... that's what I'm testing now

20:32 <Tenkawa> well... good news.. I have the 2 listed above. and a M1 and N2L

20:32 <Tenkawa> so I will definitely want to test that out when it is ready

20:35 <Tenkawa> I am working more and more nowadays on USB/NVMe and single file boot from eMMC/microsd to main media without full chainload

20:45 <Kwiboo> cool, my efforts with u-boot will probably stop soon, once main boot from sd/emmc/spi is working, network/usb/nvme from u-boot is not on my radar, I want to move on to linux kernel :-)

20:46 <Tenkawa> Kernel is my background..

20:47 <Tenkawa> I've been doing "something" in various forms on different sbcs after I was a build engineer since the late 90's

20:49 <Tenkawa> I'm currently spending a lot of time between RK35* builds/tuning and RISC-V

20:54 <Kwiboo> nice, my plan back in early january was to upstream my old libreelec hdmi and media linux patches, fell down in a u-boot rabbit hole instead

20:54 <Kwiboo> I have not event started linux on my rk3588 board, only u-boot proper :-)

20:54 <Tenkawa> I hear ya

20:55 <Tenkawa> I am part of a 2 person project for a custom sbc imager so we build a lot of new configs

21:04 <Kwiboo> I mostly play with sbcs and linux/u-boot development for fun on my off time

21:06 <Kwiboo> btw, with my u-boot wip branch I could boot rock 5b from sd, emmc and spi, will try to ready emmc patches for mail list now

21:17 <Tenkawa> Yeah this a hobby for me now (I'm out of the industry now as a job)