08:27 <Kwiboo> naoki: I recently sent out an initial device tree for zero-3w/3e at https://lore.kernel.org/all/20240415150349.2207075-1-jonas@kwiboo.se/ and was planning on including them as different targets in mainline U-Boot

08:29 <Kwiboo> the different wifi cards used could probably be handled using overlays or similar, I could not find any mainline driver for aic8800 so I skipped everything regarding wifi/bt in the initial patch

08:33 <Kwiboo> also have an initial device tree for rock-3c inbound, that one also only include emmc, sdmmc, spi flash, gmac, hdmi, pcie, pmic and usb

08:35 <Kwiboo> naoki: btw, is the downstream limiting to 1080p on hdmi due to bad gpu performance at higher resolution or something else?, console framebuffer works great on my 1440p monitor, will verify 4k resolutions later

08:38 <naoki> I think I saw 1080p limit patch somewhere in our kernel tree, but I don't know why it's required. I'll ask it later. for mainline, there is no reason to limit it if it works on your side :)

13:28 <kilobyte_ch> I'm trying to use rkdeveloptool to flash a PX30 Board. Somehow the tool most of the time hangs. On `rkdeveloptool db loader.bin` it hangs forever in `Downloading bootloader...`. I maybe have a 1/100 chance to get past it. Any idea what this could be?

13:30 <qschulz> kilobyte_ch: it would probably help to have the console of the device when this happens. The loader usually prints stuff (1500000 bauds by default IIRC)

13:31 <kilobyte_ch> qschulz: it prints this, looks like loading the loader works. https://paste.debian.net/1314264/

13:33 <kilobyte_ch> Sometimes I get past loading the loader and can execute `sudo rkdeveloptool gpt parameter`. But then it hangs with `Writing gpt...`.

13:35 <kilobyte_ch> hmm, changed usb port and it worked immediately. Maybe thats already the solution.

13:38 <qschulz> kilobyte_ch: can you check what it prints when you get paste the db step?

13:42 <kilobyte_ch> qschulz: sure, with the other usb port it also worked directly now on the second db operation: https://paste.debian.net/1314266/

13:44 <kilobyte_ch> Another question, somehow I don't see anything about U-Boot via UART2. Any idea why this might be? With the Rockchip PX30 Mini EVB I see stuff about U-Boot with the same Image. https://paste.debian.net/1314267/

14:18 <robmur01> heh, reminds me of forgetting to switch on the main power with my RK3288 box - it managed to back-power itself from the OTG port enough to boot to maskrom mode, but then eMMC activity tended to draw too much and brown out :)

14:49 <qschulz> kilobyte_ch: which board with which version of U-Boot

15:00 <kilobyte_ch> qschulz: I'm running yocto with meta-rockchip. So this one https://github.com/JeffyCN/meta-rockchip/blob/master/recipes-bsp/u-boot/u-boot-rockchip.bb

15:00 <kilobyte_ch> It is built for px30 evb board. When running it on the evb, I get u-boot output. But on the custom board I've got not. I'm connected to UART2 of the PX30.

15:00 <kilobyte_ch> Linux console works fine though.

15:01 <kilobyte_ch> Not sure if there is some sort of OTP settings in the SoC or a Crystal which could be missing or something like that which could cause such a difference.

15:02 <qschulz> kilobyte_ch: PX30 is well supported upstream, I would recommend using upstream U-Boot and kernel for that?

15:02 <qschulz> kilobyte_ch: is it the same mux for UART2 controller on your custom board than the evb?

15:03 <kilobyte_ch> qschulz: What do you mean in terms of mux? It is connected to the same Pins of the SoC.

15:04 <qschulz> kilobyte_ch: uart2_m0/uart2_m1 that kind of things

15:04 <qschulz> but if they are the same pins on the SoC then it isn't this

15:05 <kilobyte_ch> Both connect to AA17 and AA18

15:07 <qschulz> Do you see absolutely nothing on the console after the TPL or still a few thing (e.g. SPL)? Rockchip's U-Boot does some very weird stuff around DTB in U-Boot

15:07 <qschulz> it loads some image from some specific partition and then use the DTB from a kernel image there instead of the one in U-Boot binary

15:08 <qschulz> There's support for the EVB in U-Boot upstream, would recommend to go with that instead

15:09 <qschulz> https://git.yoctoproject.org/meta-rockchip/ is community maintained, though there aren't any machine conf file for the OX30 mini evb yet but that can be arranged ;)

15:09 <kilobyte_ch> This is what I get over serial: https://paste.debian.net/1314267/

15:09 <qschulz> FWIW, we use the kirkstone branch for a PX30 product of ours, so it works on some level (though with a custom upstream-ish U-Boot)

15:10 <kilobyte_ch> I will try the commuinity maintained versions later, first I need to get the Hardware kind of working on that hardware.

15:10 <qschulz> kilobyte_ch: did you try other baudrates as well? e.g. 115200 ?

15:11 <qschulz> kilobyte_ch: having had to bring up two RK3588 devices on Rockchip's U-Boot, I would NEVER try to do a bring up on this anymoire if I had a choice with an upstream board

15:11 <kilobyte_ch> qschulz: just tried with 9600 and 115200, don't see more with it

15:11 <qschulz> I did the bring up of our module directly on upstream (2022.10)

15:11 <qschulz> (our PX30 module)

15:11 <kilobyte_ch> It is very weird that this works on the PX30 Mini EVB. I'm using the same devicetree/image.

15:12 <kilobyte_ch> Need to check the schematic again if something obvious is different.

15:12 <qschulz> yeah that kinda seems odd