Toybrick

标题: rk3588板子更新安卓固件后,无法启动。请问应该如何解决? [打印本页]

作者: knights    时间: 2024-6-11 11:37
标题: rk3588板子更新安卓固件后,无法启动。请问应该如何解决?
本帖最后由 knights 于 2024-6-11 15:02 编辑

安卓通过编译源码得到镜像文件并进行烧录,系统启动现状是:在运行上电后的初次运行,运行到一半会显示无法停止刺激CPU之后就崩了,开始运行第二遍,第二遍最后会一直循环运行以下文字。请问各位大佬应该如何解决?第一遍运行结果:
[   23.939880][  T264] X4: 0xffffff8106ac6020:
[   23.946222][  T264] 5e20  00000100 00000000 00000001 00000000 00000000 00000000 00000000 00000000
[   23.955081][  T264] 5e40  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   23.957118][    T1] SMP: failed to stop secondary CPUs 0,5

第二遍运行结果:
[   25.503164][    T1] init: Control message: Could not find 'aidl/package_native' for ctl.interface_start from pid: 328 (/system/bin/servicemanager)
[   25.694483][    T1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 328 (/system/bin/servicemanager)
[   26.503670][    T1] init: Control message: Could not find 'aidl/package_native' for ctl.interface_start from pid: 328 (/system/bin/servicemanager)
[   26.694867][    T1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 328 (/system/bin/servicemanager)
[   27.000545][    T1] init: starting service 'vendor.audio-hal'...
[   27.006034][  T833] libprocessgroup: Failed to open /dev/stune/foreground/tasks: No such file or directory
[   27.006047][  T833] libprocessgroup: Failed to apply HighPerformance task profile: No such file or directory
[   27.052007][    T1] init: starting service 'audioserver'...
[   27.053840][    T1] init: processing action (init.svc.audioserver=running) from (/system/etc/init/audioserver.rc:38)
[   27.053953][    T1] init: Command 'start vendor.audio-hal-4-0-msd' action=init.svc.audioserver=running (/system/etc/init/audioserver.rc:40) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[   27.163009][  T351] type=1400 audit(21.450:73): avc: denied { read } for comm="surfaceflinger" name="arm.graphics-V3-ndk_platform.so" dev="dm-2" ino=1540 scontext=u:r:surfaceflinger:s0 tcontext=ubject_r:vendor_file:s0 tclass=file permissive=0
[   27.205822][  T351] type=1400 audit(21.493:74): avc: denied { read } for comm="android.hardwar" name="ubject_r:boot_status_prop:s0" dev="tmpfs" ino=71 scontext=u:r:hal_audiocontrol_default:s0 tcontext=ubject_r:boot_status_prop:s0 tclass=file permissive=0
[   27.258674][  T195] binder: release 839:839 transaction 3322 in, still active
[   27.258707][  T195] binder: release 839:839 transaction 3319 out, still active
[   27.258716][  T195] binder: send failed reply for transaction 3322 to 405:405
[   27.258895][  T405] binder: 405:405 transaction failed 29189/0, size 4-0 line 2668
[   27.258906][  T405] binder: send failed reply for transaction 3319, target dead
[   27.457169][  T351] type=1400 audit(21.743:75): avc: denied { search } for comm="move_widevine_d" name="mediadrm" dev="dm-30" ino=320 scontext=u:r:move-widevine-data-sh:s0 tcontext=ubject_r:mediadrm_vendor_data_file:s0 tclass=dir permissive=0
[   27.457285][  T351] type=1400 audit(21.743:76): avc: denied { read } for comm="move_widevine_d" name="mediadrm" dev="dm-30" ino=119 scontext=u:r:move-widevine-data-sh:s0 tcontext=ubject_r:media_data_file:s0 tclass=dir permissive=0
[   27.457351][  T351] type=1400 audit(21.743:77): avc: denied { search } for comm="move_widevine_d" name="mediadrm" dev="dm-30" ino=119 scontext=u:r:move-widevine-data-sh:s0 tcontext=ubject_r:media_data_file:s0 tclass=dir permissive=0
[   27.468439][  T351] type=1400 audit(21.756:78): avc: denied { getattr } for comm="restorecon" path="/data/vendor/mediadrm" dev="dm-30" ino=320 scontext=u:r:move-widevine-data-sh:s0 tcontext=ubject_r:mediadrm_vendor_data_file:s0 tclass=dir permissive=0
[   27.468717][  T351] type=1400 audit(21.756:79): avc: denied { search } for comm="move_widevine_d" name="mediadrm" dev="dm-30" ino=320 scontext=u:r:move-widevine-data-sh:s0 tcontext=ubject_r:mediadrm_vendor_data_file:s0 tclass=dir permissive=0
[   27.474853][  T351] type=1400 audit(21.756:80): avc: denied { read } for comm="rild" name="ql-ril.conf" dev="dm-0" ino=905 scontext=u:r:rild:s0 tcontext=ubject_r:system_file:s0 tclass=file permissive=0



作者: jefferyzhang    时间: 2024-6-11 15:15
谁出的固件找谁调试
作者: knights    时间: 2024-6-11 15:35
jefferyzhang 发表于 2024-6-11 15:15
谁出的固件找谁调试

这个固件是我根据你们给的源码编译的,用的版本是andriod12

作者: jefferyzhang    时间: 2024-6-11 16:27
knights 发表于 2024-6-11 15:35
这个固件是我根据你们给的源码编译的,用的版本是andriod12

只要全套用我们的固件,编译后是一定能起来的,目前没有听说有客户起不来。
这种情况还是请自行排查下哪些步骤跟我们wiki编译不一致或者固件烧错漏烧
作者: knights    时间: 2024-6-11 16:37
jefferyzhang 发表于 2024-6-11 16:27
只要全套用我们的固件,编译后是一定能起来的,目前没有听说有客户起不来。
这种情况还是请自行排查下哪 ...

你好,请问RK3588的dts板级支持包的应该选择那一个进行编译?以下是相关结果
./kernel-5.10/arch/arm64/boot/dts/rockchip/rk3588-toybrick-x0.dtsi
./kernel-5.10/arch/arm64/boot/dts/rockchip/rk3588-toybrick-edp-x0.dtsi
./kernel-5.10/arch/arm64/boot/dts/rockchip/rk3588-toybrick-x0-android.dts
./kernel-5.10/arch/arm64/boot/dts/rockchip/rk3588-toybrick.dtsi
./kernel-5.10/arch/arm64/boot/dts/rockchip/rk3588-toybrick-imx258.dtsi
./kernel-5.10/arch/arm64/boot/dts/rockchip/rk3588-toybrick-x0-android.dtb
./kernel-5.10/arch/arm64/boot/dts/rockchip/rk3588-toybrick-x0-linux.dts
作者: jefferyzhang    时间: 2024-6-11 17:04
knights 发表于 2024-6-11 16:37
你好,请问RK3588的dts板级支持包的应该选择那一个进行编译?以下是相关结果
./kernel-5.10/arch/arm64/b ...

这些在android的device中都已经写好了,无需指定,非要指定的话就是x0-android那个
作者: knights    时间: 2024-6-12 09:16
jefferyzhang 发表于 2024-6-11 17:04
这些在android的device中都已经写好了,无需指定,非要指定的话就是x0-android那个 ...

你好请问编译步骤就是
source build/envsetup.sh
lunch rk3588m-car_userdebug
./build.sh -AUCKu
运行以上步骤就行了?
作者: jefferyzhang    时间: 2024-6-12 09:17
knights 发表于 2024-6-12 09:16
你好请问编译步骤就是
source build/envsetup.sh
lunch rk3588m-car_userdebug

lunch的东西不对吧,为什么编译car的
作者: knights    时间: 2024-6-12 14:59
jefferyzhang 发表于 2024-6-12 09:17
lunch的东西不对吧,为什么编译car的

请问lunch后面是加这个吗?lunch rk3588m_s-user   。如果不是 的话请问选择什么,和3588没相关的只有这些了。rk3588m_car-user
rk3588m_car-userdebug
rk3588m_s-user
rk3588m_s-userdebug
作者: jefferyzhang    时间: 2024-6-12 15:33
你确定用的是我们代码吗,我们代码android12是lunch rk3588_s-userdebug
作者: knights    时间: 2024-6-13 09:18
jefferyzhang 发表于 2024-6-12 15:33
你确定用的是我们代码吗,我们代码android12是lunch rk3588_s-userdebug

你好,我有rk3588_s-userdebug这个提示,我想请教的是我用的芯片是rk3588m,我lunch选择的时候也用您说的这个?
作者: jefferyzhang    时间: 2024-6-13 10:09
knights 发表于 2024-6-13 09:18
你好,我有rk3588_s-userdebug这个提示,我想请教的是我用的芯片是rk3588m,我lunch选择的时候也用您说的 ...

pin2pin的,你有3588m为什么会用toybrick代码?板子都不一样吧,怎么能通用
作者: knights    时间: 2024-6-13 11:25
那我可以修改源码进行适配吗?
作者: knights    时间: 2024-6-13 11:27
jefferyzhang 发表于 2024-6-13 10:09
pin2pin的,你有3588m为什么会用toybrick代码?板子都不一样吧,怎么能通用

请问那我可以通过修改源码的方式进行适配吗?

作者: jefferyzhang    时间: 2024-6-13 11:36
knights 发表于 2024-6-13 11:27
请问那我可以通过修改源码的方式进行适配吗?

kernel不一样,没有办法,请联系板商或者代理商获取源码




欢迎光临 Toybrick (https://t.rock-chips.com/) Powered by Discuz! X3.3