Skip to content

请求O大适配下移动盒子sy910 #3462

@SilveryFantasia

Description

@SilveryFantasia

sy910配置:
rk3528
2g内存+8g eMMC
内置紫光展锐 UWE5621DS wifi蓝牙二合一网卡
2个usb2.0 一个usb3.0
1个hdmi
一个usb3.0千兆网卡

目前情况:

经过多轮镜像与DTB文件测试,目前仅h96-max-m2的Armbian镜像可成功开机,但USB接口完全无法使用;二是进系统后,四五分钟必定死机,无任何报错提示。

将该镜像内 armbianEnv.txt 文件中的DTB修改为rock 2a的DTB后,设备依旧能正常开机,且USB2.0、USB3.0、HDMI全部正常工作,但四五分钟死机的问题完全没有改善。后续更换多款不同DTB文件反复测试,均出现同样的死机现象。

本人无编程基础,完全看不懂代码,所以借助AI编程工具,从设备原厂安卓系统中提取DTS文件进行移植适配Armbian可用dtb,虽存在外设故障,但可成功开机,可依旧会在进入系统四五分钟后死机。

另外存在两个关键现象:

1. 首次进系统设置密码后死机,断电重启大概率出现设置未保存的情况,会重新跳转到首次密码设置界面,该问题为偶发性;

2. 刷入h96 max对应的飞牛系统,仅存在外设故障,完全不会出现死机情况,但飞牛系统内无法替换为rock 2a的DTB,替换后直接无法开机,原因不明。

目前使用rock 2a的DTB时,仅设备自带无线网卡无法使用、电源指示灯与WiFi指示灯不亮,其余功能均正常,是对SY910外设支持最完善的DTB。不过gpu vpu 无法使用

另外:尝试通过串口抓取死机原因,死机后串口直接输出乱码,无法获取有效故障信息。

安卓提取的dts:
sy910.dts.txt

以下是日志:

root@armbian:~# dmesg | grep -i "error|fail|thermal|cpu"
[ 1.072768] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 1.077403] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-logo@0': base 0x0000000000000000, size 0 MiB
[ 1.077421] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-cubic-lut@0': base 0x0000000000000000, size 0 MiB
[ 1.123614] percpu: Embedded 30 pages/cpu s82856 r8192 d31832 u122880
[ 1.123639] pcpu-alloc: s82856 r8192 d31832 u122880 alloc=30*4096
[ 1.123649] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 1.123717] Detected VIPT I-cache on CPU0
[ 1.123768] CPU features: detected: ARM erratum 845719
[ 1.123955] Kernel command line: root=UUID=3eda81a5-9f83-426f-bbf5-a8ebd2e6e980 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=c9ff1462-61e1-420f-91b3-de7981a013a1 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u rw rootwait cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory androidboot.fwver=ddr-v1.09-665f3e4817,bl31-v1.17,uboot-rmbian-07/08/2024
[ 1.157305] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 1.157604] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 1.157615] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 1.200540] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 1.203304] smp: Bringing up secondary CPUs ...
[ 1.203819] Detected VIPT I-cache on CPU1
[ 1.203903] cacheinfo: Unable to detect cache hierarchy for CPU 1
[ 1.203942] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 1.204552] Detected VIPT I-cache on CPU2
[ 1.204634] cacheinfo: Unable to detect cache hierarchy for CPU 2
[ 1.204670] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 1.205337] Detected VIPT I-cache on CPU3
[ 1.205427] cacheinfo: Unable to detect cache hierarchy for CPU 3
[ 1.205463] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 1.205563] smp: Brought up 1 node, 4 CPUs
[ 1.205583] CPU features: detected: 32-bit EL0 Support
[ 1.205586] CPU features: detected: 32-bit EL1 Support
[ 1.205591] CPU features: detected: CRC32 instructions
[ 1.205649] CPU: All CPU(s) started at EL2
[ 1.226991] thermal_sys: Registered thermal governor 'fair_share'
[ 1.226999] thermal_sys: Registered thermal governor 'step_wise'
[ 1.227003] thermal_sys: Registered thermal governor 'user_space'
[ 1.227006] thermal_sys: Registered thermal governor 'power_allocator'
[ 1.227090] cpuidle: using governor menu
[ 1.778680] fiq_debugger fiq_debugger.0: error -ENXIO: IRQ fiq not found
[ 1.778704] fiq_debugger fiq_debugger.0: error -ENXIO: IRQ wakeup not found
[ 1.813046] rockchip-thermal ffad0000.tsadc: tsadc is probed successfully!
[ 1.883172] phy phy-ffe00000.hdmiphy.0: Looking up phy-supply property in node /hdmiphy@ffe00000 failed
[ 1.884573] rockchip-usb2phy ffdf0000.usb2-phy: error -ENXIO: IRQ index 0 not found
[ 1.884779] phy phy-ffdf0000.usb2-phy.1: Looking up phy-supply property in node /usb2-phy@ffdf0000/otg-port failed
[ 1.887441] phy phy-ffdc0000.phy.3: Looking up phy-supply property in node /phy@ffdc0000 failed
[ 1.902289] pwm-regulator vdd-cpu: Looking up pwm-supply from device tree
[ 1.902308] vdd_cpu: supplied by vcc5v0_sys
[ 1.902382] vdd_cpu: 746 <--> 1201 mV at 950 mV, enabled
[ 1.902850] arm-scmi firmware:scmi: Failed. SCMI protocol 22 not active.
[ 1.916867] [drm] failed to init overlay plane Esmart1-win0
[ 1.916994] [drm] failed to init overlay plane Cluster0-win1
[ 1.917072] rockchip-vop2 ff840000.vop: failed to init opp info
[ 1.917211] dwhdmi-rockchip ff8d0000.hdmi: Looking up avdd-0v9-supply property in node /hdmi@ff8d0000 failed
[ 1.917252] dwhdmi-rockchip ff8d0000.hdmi: Looking up avdd-1v8-supply property in node /hdmi@ff8d0000 failed
[ 1.920360] rockchip-drm display-subsystem: failed to parse loader memory
[ 1.920728] rockchip-drm display-subsystem: [drm] run display error_event monitor
[ 1.929654] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 1.942114] rk_gmac-dwmac ffbe0000.ethernet: Looking up phy-supply property in node /ethernet@ffbe0000 failed
[ 2.105425] cpu cpu0: bin=0
[ 2.105551] cpu cpu0: leakage=21
[ 2.105585] cpu cpu0: Looking up cpu-supply from device tree
[ 2.107151] cpu cpu0: pvtm=1456
[ 2.107803] cpu cpu0: pvtm-volt-sel=5
[ 2.107876] cpu cpu0: Looking up cpu-supply from device tree
[ 2.109271] cpu cpu0: avs=0
[ 2.109416] cpu cpu0: l=10000 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0
[ 2.109797] cpu cpu0: EM: created perf domain
[ 2.114129] sdhci-dwcmshc ffbf0000.mmc: Looking up vmmc-supply property in node /mmc@ffbf0000 failed
[ 2.114170] sdhci-dwcmshc ffbf0000.mmc: Looking up vqmmc-supply property in node /mmc@ffbf0000 failed
[ 2.114318] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.114385] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.
[ 2.116645] rockchip,bus gpu-bus: Looking up pvtm-supply property in node /gpu-bus failed
[ 2.116677] rockchip,bus gpu-bus: error -ENODEV: _opp_set_regulators: no regulator (pvtm) found
[ 2.116718] rockchip,bus gpu-bus: failed to set opp config
[ 2.116724] rockchip,bus gpu-bus: failed to init opp info
[ 2.116730] rockchip,bus gpu-bus: failed to get OPP table
[ 2.116735] rockchip,bus gpu-bus: failed to init power control
[ 2.121534] optee: probe of firmware:optee failed with error -22
[ 2.301692] rkvdec2_init:1224: failed on clk_get clk_core
[ 2.301738] rkvdec2_init:1227: failed on clk_get clk_cabac
[ 2.305283] mpp_rkvenc2 ff780000.rkvenc: failed to init opp info
[ 2.305303] mpp_rkvenc2 ff780000.rkvenc: failed to init_opp_table
[ 2.305308] rkvenc_init:2394: failed to add venc devfreq
[ 2.306907] rockchip-dmc dmc: failed to get vop bandwidth to dmc rate
[ 2.306913] rockchip-dmc dmc: failed to get vop pn to msch rl
[ 5.334755] r8152 2-1:1.0: Direct firmware load for rtl_nic/rtl8153b-2.fw failed with error -2
[ 12.512014] rk_gmac-dwmac ffbe0000.ethernet end1: validation of with support 00000000,00000000,00006000 and advertisement 00000000,00000000,00000000 failed: -EINVAL
[ 12.512344] rk_gmac-dwmac ffbe0000.ethernet end1: __stmmac_open: Cannot attach to PHY (error: -22)
[ 12.629776] rk_gmac-dwmac ffbe0000.ethernet end1: validation of with support 00000000,00000000,00006000 and advertisement 00000000,00000000,00000000 failed: -EINVAL
[ 12.639432] rk_gmac-dwmac ffbe0000.ethernet end1: __stmmac_open: Cannot attach to PHY (error: -22)
[ 12.704712] rk_gmac-dwmac ffbe0000.ethernet end1: validation of with support 00000000,00000000,00006000 and advertisement 00000000,00000000,00000000 failed: -EINVAL
[ 12.709076] rk_gmac-dwmac ffbe0000.ethernet end1: __stmmac_open: Cannot attach to PHY (error: -22)
[ 12.811096] rk_gmac-dwmac ffbe0000.ethernet end1: validation of with support 00000000,00000000,00006000 and advertisement 00000000,00000000,00000000 failed: -EINVAL
[ 12.811365] rk_gmac-dwmac ffbe0000.ethernet end1: __stmmac_open: Cannot attach to PHY (error: -22)
[ 12.908506] rk_gmac-dwmac ffbe0000.ethernet end1: validation of with support 00000000,00000000,00006000 and advertisement 00000000,00000000,00000000 failed: -EINVAL
[ 12.909431] rk_gmac-dwmac ffbe0000.ethernet end1: __stmmac_open: Cannot attach to PHY (error: -22)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions