Simon-renegade Posted March 16, 2022 Posted March 16, 2022 Has anyone tried the latest version Jammy with legacy 4.19 kernel and edge with 5.16 kernel? I've tried the firmware on my 3566 BOX with dtb replaced with the dtb from the box. It is strange that the 5.16 kernel can't boot but the legacy kernel works very well. Here is the log of the boot. It blocks after "Failed to get pclk for 'rk_timer'" Is the same issue occurs on Station M2? Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050] [ 0.000000] Linux version 5.16.11-media (root@1e9690486ec5) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #22.02.1 SMP PREEMPT Sun Feb 27 09:04:03 UTC 2022 [ 0.000000] Machine model: Rockchip RK3566 EVB3 DDR3 V10 Board [ 0.000000] earlycon: uart8250 at MMIO32 0x00000000fe660000 (options '') [ 0.000000] printk: bootconsole [uart8250] enabled [ 0.000000] efi: UEFI not found. [ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-logo@00000000': base 0x0000000000000000, size 0 MiB [ 0.000000] Reserved memory: created CMA memory pool at 0x00000001f8000000, size 128 MiB [ 0.000000] OF: reserved mem: initialized node rknpu, compatible id shared-dma-pool [ 0.000000] Reserved memory: created CMA memory pool at 0x0000000008000000, size 8 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000001ffffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x1f6fe9a40-0x1f6febfff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000200000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal [mem 0x0000000100000000-0x00000001ffffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000200000-0x00000000083fffff] [ 0.000000] node 0: [mem 0x0000000009400000-0x00000000efffffff] [ 0.000000] node 0: [mem 0x0000000100000000-0x00000001ffffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x00000001ffffffff] [ 0.000000] On node 0, zone DMA: 512 pages in unavailable ranges [ 0.000000] On node 0, zone DMA: 4096 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 30 pages/cpu s82200 r8192 d32488 u122880 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: Virtualization Host Extensions [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] alternatives: patching kernel code [ 0.000000] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1995336 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: root=UUID=2f79ba47-2200-477e-bf95-e6aaa8a500bc console=ttyFIQ0 console=tty0 rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian earlycon=uart8250,mmio32,0xfe660000 [ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] software IO TLB: mapped [mem 0x00000000ec000000-0x00000000f0000000] (64MB) [ 0.000000] Memory: 7697224K/8108032K available (17984K kernel code, 3310K rwdata, 7844K rodata, 4864K init, 771K bss, 271544K reserved, 139264K cma-reserved) [ 0.000000] random: get_random_u64 called from cache_random_seq_create+0x84/0x180 with crng_init=0 [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Rude variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 320 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000 [ 0.000000] ITS [mem 0xfd440000-0xfd45ffff] [ 0.000000] ITS@0x00000000fd440000: Devices doesn't stick: f9070001000d0600 f9070000000d0600 [ 0.000000] ITS@0x00000000fd440000: failed probing (-6) [ 0.000000] ITS: No ITS available, not enabling LPIs [ 0.000000] clk: couldn't get assigned clock 0 for /clock-controller@fdd00000 [ 0.000000] rockchip_clk_of_add_provider: could not register clk provider [ 0.000000] rockchip_clk_of_add_provider: could not register clk provider [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000001] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001744] Failed to get pclk for 'rk_timer' [ 0.003301] Console: colour dummy device 80x25 [ 0.003755] printk: console [tty0] enabled [ 0.004173] printk: bootconsole [uart8250] disabled
Werner Posted March 16, 2022 Posted March 16, 2022 Moved to P2P help. Edge kernel generally unsupported Userspace unsupported.
balbes150 Posted March 16, 2022 Posted March 16, 2022 1 час назад, Werner сказал: Moved to P2P help Pls change the name of the theme, it has nothing to do with Station M2, the user does not have a supported TV box.
Hqnicolas Posted October 27, 2022 Posted October 27, 2022 (edited) hello, same problem here, TTL RK3566 DUMP Quote Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050] [ 0.000000] Linux version 5.19.17-station-p2 (root@ubuntu2) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #trunk SMP PREEMPT Wed Oct 26 23:54:00 -03 2022 [ 0.000000] Machine model: Rockchip RK3566 EVB3 DDR3 V10 Board [ 0.000000] earlycon: uart8250 at MMIO32 0x00000000fe660000 (options '') [ 0.000000] printk: bootconsole [uart8250] enabled [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x0000000010000000, size 8 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000001ffffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x1ff767a40-0x1ff769fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000200000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal [mem 0x0000000100000000-0x00000001ffffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000200000-0x00000000083fffff] [ 0.000000] node 0: [mem 0x0000000009400000-0x00000000efffffff] [ 0.000000] node 0: [mem 0x00000001f0000000-0x00000001ffffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x00000001ffffffff] [ 0.000000] On node 0, zone DMA: 512 pages in unavailable ranges [ 0.000000] On node 0, zone DMA: 4096 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 30 pages/cpu s83048 r8192 d31640 u122880 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: Virtualization Host Extensions [ 0.000000] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009 [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] alternatives: patching kernel code [ 0.000000] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1027656 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: root=UUID=9ce56e40-5c5c-41cf-a520-9def17300c99 console=ttyFIQ0 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian earlycon=uart8250,mmio32,0xfe660000 [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] software IO TLB: mapped [mem 0x00000000e9f00000-0x00000000edf00000] (64MB) [ 0.000000] Memory: 3953788K/4175872K available (17024K kernel code, 2870K rwdata, 7028K rodata, 4288K init, 721K bss, 213892K reserved, 8192K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 320 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: GICv3 features: 16 PPIs [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000 [ 0.000000] ITS [mem 0xfd440000-0xfd45ffff] [ 0.000000] GIC: enabling workaround for ITS: Rockchip RK3568 force no_local_cache [ 0.000000] ITS@0x00000000fd440000: allocated 8192 Devices @2410000 (indirect, esz 8, psz 64K, shr 0) [ 0.000000] ITS@0x00000000fd440000: allocated 32768 Interrupt Collections @2420000 (flat, esz 2, psz 64K, shr 0) [ 0.000000] ITS: using cache flushing for cmd queue [ 0.000000] ITS ALLOCATE PROP WORKAROUND [ 0.000000] GICv3: using LPI property table @0x0000000002430000 [ 0.000000] GIC: using cache flushing for LPI property table [ 0.000000] GICv3: CPU0: using allocated LPI pending table @0x0000000002440000 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] clk: couldn't get assigned clock 0 for /clock-controller@fdd00000 [ 0.000000] rockchip_clk_of_add_provider: could not register clk provider [ 0.000000] rockchip_clk_of_add_provider: could not register clk provider [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000001] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001187] Failed to get pclk for 'rk_timer' [ 0.002230] Console: colour dummy device 80x25 [ 0.002659] printk: console [tty0] enabled [ 0.003051] printk: bootconsole [uart8250] disabled My DTS File have a Kernel 4.19 conf Quote clock-controller@fdd00000 { compatible = "rockchip,rk3568-pmucru"; reg = <0x00000000 0xfdd00000 0x00000000 0x00001000>; rockchip,grf = <0x00000032>; rockchip,pmugrf = <0x00000033>; #clock-cells = <0x00000001>; #reset-cells = <0x00000001>; assigned-clocks = <0x00000031 0x00000032>; assigned-clock-parents = <0x00000031 0x00000005>; phandle = <0x00000031>; }; clock-controller@fdd20000 { compatible = "rockchip,rk3568-cru"; reg = <0x00000000 0xfdd20000 0x00000000 0x00001000>; rockchip,grf = <0x00000032>; #clock-cells = <0x00000001>; #reset-cells = <0x00000001>; assigned-clocks = <0x00000031 0x00000005 0x0000001f 0x00000106 0x0000001f 0x0000010b 0x00000031 0x00000001 0x00000031 0x0000002b 0x0000001f 0x00000003 0x0000001f 0x0000019b 0x0000001f 0x00000009 0x0000001f 0x0000019c 0x0000001f 0x0000019d 0x0000001f 0x000001a1 0x0000001f 0x0000019e 0x0000001f 0x0000019f 0x0000001f 0x000001a0 0x0000001f 0x00000004 0x0000001f 0x0000010d 0x0000001f 0x0000010e 0x0000001f 0x00000173 0x0000001f 0x00000174 0x0000001f 0x00000175 0x0000001f 0x00000176 0x0000001f 0x000000c9 0x0000001f 0x000000ca 0x0000001f 0x00000006 0x0000001f 0x0000007e 0x0000001f 0x0000007f 0x0000001f 0x0000003d 0x0000001f 0x00000041 0x0000001f 0x00000045 0x0000001f 0x00000049 0x0000001f 0x0000004d 0x0000001f 0x0000004d 0x0000001f 0x00000055 0x0000001f 0x00000051 0x0000001f 0x0000005d 0x0000001f 0x000000dd>; assigned-clock-rates = <0x00008000 0x11e1a300 0x11e1a300 0x0bebc200 0x05f5e100 0x3b9aca00 0x1dcd6500 0x13d92d40 0x0ee6b280 0x07735940 0x05f5e100 0x03b9aca0 0x02faf080 0x017d7840 0x46cf7100 0x08f0d180 0x05f5e100 0x1dcd6500 0x17d78400 0x08f0d180 0x05f5e100 0x11e1a300 0x08f0d180 0x47868c00 0x17d78400 0x05f5e100 0x46cf7100 0x46cf7100 0x46cf7100 0x46cf7100 0x46cf7100 0x46cf7100 0x46cf7100 0x46cf7100 0x46cf7100 0x1dcd6500>; assigned-clock-parents = <0x00000031 0x00000008 0x0000001f 0x00000004 0x0000001f 0x00000004>; phandle = <0x0000001f>; }; pmucru = "/clock-controller@fdd00000"; cru = "/clock-controller@fdd20000"; Edited October 27, 2022 by hotnikq
tmm1 Posted December 3, 2022 Posted December 3, 2022 (edited) 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 Edited December 3, 2022 by tmm1
tmm1 Posted December 3, 2022 Posted December 3, 2022 33 minutes ago, tmm1 said: I confirmed with 4.19 and 5.10 BSP kernel I see the "Serial: " output Maybe related to this commit in BSP https://github.com/rockchip-linux/kernel/commit/ec403a4036975584ff21a08282006b7ba9b32d72
tmm1 Posted December 3, 2022 Posted December 3, 2022 On 10/27/2022 at 10:04 AM, hotnikq said: [ 0.003051] printk: bootconsole [uart8250] disabled 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
tmm1 Posted December 3, 2022 Posted December 3, 2022 On 10/27/2022 at 10:04 AM, hotnikq said: [ 0.000000] clk: couldn't get assigned clock 0 for /clock-controller@fdd00000 [ 0.000000] rockchip_clk_of_add_provider: could not register clk provider [ 0.000000] rockchip_clk_of_add_provider: could not register clk provider 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>; };
tmm1 Posted December 3, 2022 Posted December 3, 2022 Okay I see the DTS adds console=ttyFIQ0 So the problem is with fiq-debugger
tmm1 Posted December 3, 2022 Posted December 3, 2022 (edited) 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 { Edited December 3, 2022 by tmm1
Hqnicolas Posted December 3, 2022 Posted December 3, 2022 @tmm1 Please Share the "T95 PLUS DTSI" File i think that you can make it work on Armbian standart.
tmm1 Posted December 3, 2022 Posted December 3, 2022 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
tmm1 Posted December 3, 2022 Posted December 3, 2022 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";
thc013 Posted January 8, 2023 Posted January 8, 2023 lol that is all not gonna work same as with that h96 v56 a decompiled dtb is not a dts for use in kernel and it is sure not gonna work with a 4.19 on a 5.10 kernel just check if your board has a pmic and if it is a rk817 or rk809 otherwise things get very hot for 4.19 below 219 there are some name changes in the dts to work on +219 version and for 5.10 you have to adjust some settings in storage devices
maka Posted January 8, 2023 Posted January 8, 2023 (edited) Has anyone checked minimyth2 x96_x6 dtb? This is a fully working dtb for edge mainline kernel. I think is a rebuild of an SBC dtb where you need a lot of deprecated nodes deletions and the addition of a Phantom pmic20 node. Works well but its not a compiled one but a "Frankenstein" and runs cool. Maybe dangerous for some bosses! Edited January 8, 2023 by maka
thc013 Posted January 8, 2023 Posted January 8, 2023 more nonsens maka ? it is a dts for a x96_x6 wich dont have a pmic because it is a cheaptv box and indeed too dangereous for you !
maka Posted January 8, 2023 Posted January 8, 2023 Can you explain me the other non senses? There is no real pmic in the tvbox. I have to explain you the meaning of Phantom?
thc013 Posted January 8, 2023 Posted January 8, 2023 h96 v56 has a rk809 the h96 v58 (rk3588) has a pmic x88 has no pmic from other boards i cannot see it so quick quartz64-a has rk817 firefly has rk809 etc etc at least warpme did a proper dtb downstream > bad decompiled dts > dts proper downstream ( adapt one from device tree folder or make dts wich at the end match compiled with original dtb ) conversion and then changed it for mainline in other words he did ALL the steps then just 1 not working hdmi is just 1 name change in a dts from below 4.19.206 would you also like a explanation about ? "a decompiled dtb is not a dts for use in kernel and it is sure not gonna work with a 4.19 on a 5.10 kernel" or your gonna call the Ghostbusters Hotnikq is not gonna find it in my outdated guide to build from bsp that is a guide of building from bsp and has nothing to do with reverse engineer a dtb . Tmm1 is not gonna make it either as long he thinks that some editing in a decompiled dts is gonna make it work . and posting about a end result is not gonna help either as long you did not all the steps from the dtb of your board . And why "devs" have no interest is they dont have that board for testing and helping remotly is just not gonna work , just buy a sbc from one of the vendors like pine64 raxda firefly etc they just as cheap as a tvbox and 100% more support
maka Posted January 8, 2023 Posted January 8, 2023 Thanks for explaining your thoughts and let forget about nonsenses. I think someone can reverse his dtb making a comparison with the X96 X6 one. Current dtb is more simple but this work is always difficult and not for everyone. The problem is that nowadays there is little sharing about findings.
thc013 Posted January 8, 2023 Posted January 8, 2023 your confusing dtb and dts and you realy have no clue when you say compare a 4.19 dtb with a mainline dtb your still wanna go from step 1 to end result wich is not gonna work the problem is that people dont read and are lazy !
Recommended Posts