2024备忘知识点
1. adb shell dumpsys package f |grep fin
过滤查找指纹服务
１． adsp
write /sys/kernel/boot_adsp/boot 1
Please change replace dev_dbg into dev_err in kernel file adsp-loader.c.
Then check whether
"write /sys/kernel/boot_adsp/boot 1"
correponding function is invoked
adsp_boot_store()
2. 如何开启therla log 的配置log
enable dynamic debug log, get kernel log (beed debug version to get dynamic debug log)
echo 'file msm-tsens.c +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file battery_current_limit.c +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file msm_thermal.c +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file thermal_core.c +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file tsens2xxx.c +p' > /sys/kernel/debug/dynamic_debug/control
Use“adb shell thermal-engine -o” to output conf file
thermal-engine debug log
adb shell stop thermal-engine
adb shell thermal-engine --debug &
adb logcat -v time -s ThermalEngine > ThermalEngine.log
3. Audio problem
It looks like that FluenceNN is not running.
1.Please share the logcat showing which ACDB is using
2.Please share the ACDB
3.Please try to update the ACDB, adspso.bin(alorightm was in it) with adsp firmware.
timestamp:00:06:16.628==>timestamp:00:06:19.126 FP5_call_speaker_mode_issue_11-17.16-46-51-688.hdf.0x158A.pcm.0x100.VPTX_OUT.0x1.tx.8k.labels.txt
timestamp:00:06:19.161==>timestamp:00:06:29.761 FP5_call_speaker_mode_issue_11-17.16-46-51-688.hdf.0x158A.pcm.0x102.VPTX_OUT.0x1.tx.16k.labels.txt
timestamp:00:06:30.039==>timestamp:00:06:30.039 FP5_call_speaker_mode_issue_11-17.16-46-51-688.hdf.0x158A.pcm.0x100.VPTX_OUT.0x3.tx.16k.labels.txt
timestamp:00:06:19.173==>timestamp:00:06:29.753 FP5_call_speaker_mode_issue_11-17.16-46-51-688.hdf.0x158A.pcm.0x101.VPRX_OUT.0x3.rx.16k.labels.txt
timestamp:00:06:30.013==>timestamp:00:06:42.513 FP5_call_speaker_mode_issue_11-17.16-46-51-688.hdf.0x158A.pcm.0x100.VPRX_OUT.0x1.rx.48k.labels.txt
00:06:29.986250 [capi_v2_fluence_utils.cpp 2737] 305f:02: ADSP: FvX capi_v2 Fluence cmn set_param :: enable 1
00:06:29.986250 [capi_v2_fluence_kpps_delay.cp 305] 305f:02: ADSP: FVX Overall KPPS 16698 eai KPPS 0
00:06:29.986250 [capi_v2_fluence_kpps_delay.cp 305] 305f:02: ADSP: FVX Overall KPPS 16698 eai KPPS 0
00:06:29.986250 [capi_v2_fluence_kpps_delay.cp 305] 305f:02: ADSP: FVX Overall KPPS 16698 eai KPPS 0
00:06:29.986250 [capi_v2_fluence_kpps_delay.cp 305] 305f:02: ADSP: FVX Overall KPPS 16698 eai KPPS 0
00:06:30.001250 [capi_v2_fluence_utils.cpp 1153] 305f:02: ADSP: FvX capi_v2 Fluence cmn Data Init Done
00:06:30.001250 [capi_v2_fluence_utils.cpp 893] 305f:02: ADSP: FvX capi_v2 Fluence cmn Data Init Done
00:06:30.001250 [capi_v2_fluence_utils.cpp 2048] 305f:02: ADSP: FvX capi_v2 Fluence cmn RTM AEC size 532, state size 1844
00:06:30.001250 [capi_v2_fluence_kpps_delay.cp 305] 305f:02: ADSP: FVX Overall KPPS 231718 eai KPPS 0
00:06:30.038750 [capi_v2_fluence_utils.cpp 627] 305f:02: ADSP: FvX capi_v2 Fluence cmn process : opening communication with AVC/RVE Tx
00:06:30.038750 [capi_v2_fluence_utils.cpp 2207] 305f:02: ADSP: Buffer allocation failed by diag
00:06:30.038750 [capi_v2_fluence_utils.cpp 2315] 305f:02: ADSP: Buffer allocation failed by diag
00:06:30.040000 [sysmon_dcvs_adsppm.c 528] ADSP: SysMon DCVS bus clock request :: To: 200000 KHz, From: 0 KHz
00:06:30.040000 [ sysmon_prof.c 3418] ADSP: ICB Callback: Ab: 105175 KBps, Ib: 1484375 KBps, Extrapolated values: Bus clock: 200000 kHz, Bus voltage level: 5
4. How to enlarger the tz memory
as I mentioned, only TA memory size is meaningful to you and can change by you. the others can not. besides, there are not such way to check in running.
if you know that old way, it is similar in this platform. you can follow below steps to do,
+++
here, I assume you want to enlarge 10MB TA memory size upon the original TA memory size, you can refer to below changes,
1.
trustzone_images/ssg/securemsm/trustzone/qsee/mink/oem/config/kodiak/oem_config.xml
<props name="OEM_pil_secure_app_load_region_size" type=DALPROP_ATTR_TYPE_UINT32>
- 0x03900000
+ 0x04300000
</props>
<props name="OEM_pil_subsys_load_region_start" type=DALPROP_ATTR_TYPE_UINT32>
2，boot_images/boot/QcomPkg/SocPkg/Kodiak/Common/uefiplat.cfg
0x9FFFF000, 0x00001000, "Info Blk", AddMem, SYS_MEM, SYS_MEM_CAP, RtData, WRITE_BACK_XN
0xA0000000, 0x10000000, "Kernel", AddMem, SYS_MEM, SYS_MEM_CAP, Reserv, WRITE_BACK_XN
0xB0000000, 0x10000000, "HYP RESERVED", AddMem, SYS_MEM, SYS_MEM_CAP, Reserv, WRITE_BACK_XN
-0xC1800000, 0x03900000, "TZApps Reserved", HobOnlyNoCacheSetting, MEM_RES, UNCACHEABLE, Reserv, UNCACHED_UNBUFFERED_XN
+0xC1800000, 0x04300000, "TZApps Reserved", HobOnlyNoCacheSetting, MEM_RES, UNCACHEABLE, Reserv, UNCACHED_UNBUFFERED_XN
0xD0000000, 0x10000000, "Guest VM", AddMem, SYS_MEM, SYS_MEM_CAP, Reserv, WRITE_BACK_XN
0xE0000000, 0x00F00000, "DBI Dump", NoHob, MMAP_IO, INITIALIZED, Conv, UNCACHED_UNBUFFERED_XN
0xE1000000, 0x02400000, "Display Reserved", AddMem, MEM_RES, SYS_MEM_CAP, Reserv, WRITE_THROUGH_XN
3，yupik.dtsi:
removed_mem: removed_region@c0000000 {
no-map;
- reg = <0x0 0xc0000000 0x0 0x5100000>;
+ reg = <0x0 0xc0000000 0x0 0x5B00000>;
};
};
+++
, then recompile all the relevant components and flash your device to test.