tmm1

Try adding `keep_bootcon` to the kernel command line to see more details

@Hefti Did you figure out how to restore your board? I just clobbered mine too (with `rkdeveloptool wl 0x40 idloader.bin` gone wrong). I think I will need to short the eMMC

I'm not so sure about this one. It says "- 12V DC Power supply" but all these android box have 5v supply. If you want the proper DTB, you can find it in the rockchip-linux/kernel tree. For example: https://github.com/rockchip-linux/kernel/blob/develop-5.10/arch/arm64/boot/dts/rockchip/rk3566-box-demo-v10.dts and this one is more similar to H96 MAX V56: https://github.com/rockchip-linux/kernel/blob/develop-5.10/arch/arm64/boot/dts/rockchip/rk3566-evb3-ddr3-v10.dts

eMMC boot partition is for u-boot. you don't need to touch that to change dtb, use /boot dir on rootfs partition. simply cd /boot and edit extlinux/extlinux.conf

Basically many things are broken. Serial console is not fully working, only with keep_bootcon hack. HDMI is not working. But there is enough to login and run commands over UART and see kernel debug messages. The main part to change in the DTS: chosen { - bootargs = "earlycon=uart8250,mmio32,0xfe660000 console=ttyFIQ0"; + bootargs = "earlycon=uart8250,mmio32,0xfe660000 keep_bootcon";

You can find it here https://www.t95plus.com/forums/index.php?threads/armbian-with-linux-5-18-19-kernel.8/#post-55 It should work on armbian standard too. But right now HDMI is not working so I think the DTB needs more modifications still

fiq-debugger requires rk_fiq_debugger from BSP kernel, so of-course it doesn't work on mainline 5.19 I was able to boot up 5.19.17-station-p2 fully by making this change to my DTS. Without console= override, it will use console=/dev/ttyS02,1500000 from the extlinux.conf @@ -2994,7 +2995,7 @@ serial@fe660000 dmas = <0x32 0x04 0x32 0x05>; pinctrl-names = "default"; pinctrl-0 = <0xcc>; - status = "disabled"; + status = "okay"; phandle = <0x17f>; }; @@ -4595,7 +4596,7 @@ }; chosen { - bootargs = "earlycon=uart8250,mmio32,0xfe660000 console=ttyFIQ0"; + bootargs = "earlycon=uart8250,mmio32,0xfe660000"; phandle = <0x19e>; }; @@ -4608,7 +4609,7 @@ fiq-debugger interrupts = <0x00 0xfc 0x08>; pinctrl-names = "default"; pinctrl-0 = <0xcc>; - status = "okay"; + status = "disabled"; }; debug@fd904000 {

Okay I see the DTS adds console=ttyFIQ0 So the problem is with fiq-debugger

I was able to fix some of these messages with these DTB changes.. --- t95plus.dts.orig 2022-12-02 15:49:12.000000000 -0800 +++ t95plus.dts 2022-12-02 17:21:10.000000000 -0800 @@ -929,8 +929,6 @@ rockchip,pmugrf = <0x30>; #clock-cells = <0x01>; #reset-cells = <0x01>; - assigned-clocks = <0x2e 0x32>; - assigned-clock-parents = <0x2e 0x05>; phandle = <0x2e>; }; @@ -938,6 +936,8 @@ compatible = "rockchip,rk3568-cru"; reg = <0x00 0xfdd20000 0x00 0x1000>; rockchip,grf = <0x2f>; + clocks = <0x125>; + clock-names = "xin24m"; #clock-cells = <0x01>; #reset-cells = <0x01>; assigned-clocks = <0x2e 0x05 0x1f 0x106 0x1f 0x10b 0x2e 0x01 0x2e 0x2b 0x1f 0x03 0x1f 0x19b 0x1f 0x09 0x1f 0x19c 0x1f 0x19d 0x1f 0x1a1 0x1f 0x19e 0x1f 0x19f 0x1f 0x1a0 0x1f 0x04 0x1f 0x10d 0x1f 0x10e 0x1f 0x173 0x1f 0x174 0x1f 0x175 0x1f 0x176 0x1f 0xc9 0x1f 0xca 0x1f 0x06 0x1f 0x7e 0x1f 0x7f 0x1f 0x3d 0x1f 0x41 0x1f 0x45 0x1f 0x49 0x1f 0x4d 0x1f 0x4d 0x1f 0x55 0x1f 0x51 0x1f 0x5d 0x1f 0xdd>; @@ -2980,6 +2980,7 @@ pinctrl-names = "default"; pinctrl-0 = <0xca 0xcb>; status = "okay"; + //uart-has-rtscts; phandle = <0x17e>; };

Okay I discovered how to get more output, by adding to extlinux/extlinux.conf APPEND line: keep_bootcon After that I see much more info, like [ 0.136698] Serial: AMBA PL011 UART driver ... [ 2.037974] Serial: 8250/16550 driver, 8 ports, IRQ sharing enabled [ 2.044881] fe650000.serial: ttyS1 at MMIO 0xfe650000 (irq = 29, base_baud = 1500000) is a 16550A [ 2.048292] Serial: AMBA driver So it seems maybe there are multiple serial drivers in upstream kernel which is causing console to go to the wrong place? I tried to change console=ttyS02,1500000 to ttyS1 but no luck.. With `keep_bootcon`, now the output stops here: [ 2.312994] psci_checker: PSCI checker started using 4 CPUs [ 2.313639] psci_checker: Starting hotplug tests [ 2.314097] psci_checker: Trying to turn off and on again all CPUs [ 2.315526] psci: CPU0 killed (polled 0 ms) [ 2.320474] psci: CPU1 killed (polled 0 ms) [ 2.324510] psci: CPU2 killed (polled 0 ms) [ 2.328780] Detected VIPT I-cache on CPU0 [ 2.328857] GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000 [ 2.328970] CPU0: Booted secondary processor 0x0000000000 [0x412fd050] [ 2.330794] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 2.333719] Detected VIPT I-cache on CPU1 [ 2.333783] GICv3: CPU1: found redistributor 100 region 0:0x00000000fd480000 [ 2.333879] CPU1: Booted secondary processor 0x0000000100 [0x412fd050] [ 2.337965] Detected VIPT I-cache on CPU2 [ 2.338009] GICv3: CPU2: found redistributor 200 region 0:0x00000000fd4a0000 [ 2.338079] CPU2: Booted secondary processor 0x0000000200 [0x412fd050] [ 2.341154] psci_checker: Trying to turn off and on again group 0 (CPUs 0-3) [ 2.343064] psci: CPU0 killed (polled 0 ms) [ 2.350089] psci: CPU1 killed (polled 0 ms) [ 2.353591] psci: CPU2 killed (polled 0 ms) [ 2.357124] Detected VIPT I-cache on CPU0 [ 2.357196] GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000 [ 2.357309] CPU0: Booted secondary processor 0x0000000000 [0x412fd050] [ 2.361968] Detected VIPT I-cache on CPU1 [ 2.362017] GICv3: CPU1: found redistributor 100 region 0:0x00000000fd480000 [ 2.362097] CPU1: Booted secondary processor 0x0000000100 [0x412fd050] [ 2.366512] Detected VIPT I-cache on CPU2 [ 2.366562] GICv3: CPU2: found redistributor 200 region 0:0x00000000fd4a0000 [ 2.366634] CPU2: Booted secondary processor 0x0000000200 [0x412fd050] [ 2.369954] psci_checker: Hotplug tests passed OK [ 2.370411] psci_checker: Starting suspend tests (10 cycles per state) [ 2.371559] psci_checker: CPU 3 entering suspend cycles, states 1 through 1 [ 2.371560] psci_checker: CPU 1 entering suspend cycles, states 1 through 1 [ 2.371559] psci_checker: CPU 2 entering suspend cycles, states 1 through 1 [ 2.371559] psci_checker: CPU 0 entering suspend cycles, states 1 through 1 [ 2.405703] ata1: SATA link down (SStatus 0 SControl 300) [ 2.413679] psci_checker: CPU 0 suspend test results: success 10, shallow states 0, errors 0 [ 2.414522] psci_checker: CPU 1 suspend test results: success 10, shallow states 0, errors 0 [ 2.415360] psci_checker: CPU 2 suspend test results: success 10, shallow states 0, errors 0 [ 2.416192] psci_checker: CPU 3 suspend test results: success 10, shallow states 0, errors 0 [ 2.417193] psci_checker: Suspend tests passed OK [ 2.417661] psci_checker: PSCI checker completed [ 2.418097] of_cfs_init [ 2.418726] of_cfs_init: OK

Maybe related to this commit in BSP https://github.com/rockchip-linux/kernel/commit/ec403a4036975584ff21a08282006b7ba9b32d72

I saw the same problem trying to boot 5.19 I think the problem is that the serial driver is not loading correctly, so when switching from bootconsole (earlycon=) to regular console the output stops. See https://github.com/sifive/freedom-u-sdk/issues/44#issuecomment-375174420 it says: I can't see the UART initialization in the console log. You should see something like this: >Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled >10000000.uart: ttyS0 at MMIO 0x10000000 (irq = 13, base_baud = 230400) is a 16550A I confirmed with 4.19 and 5.10 BSP kernel I see the "Serial: " output

Can you advise which pins to short for https://www.t95plus.com/forums/index.php?threads/maskrom-mode-for-unbricking.7/

Is wifi working for anyone?

You can use the same instructions as t95plus.com