How to open UMD, KMD log and dump diagrams in CAMX architecture

1.UMD Log

stay UMD log In two parts , Namely camx This way log and chi This way log. Yes camx This is the core , So there are many corresponding modules , The module is distinguished .chi This is mainly OEM There is only one customization here prop Control

CAMX log：

camx Of grop:

File name involved ：camxypes.h( Back camx Split into three folders , Remember to look for them all )

 camx Designed to group There are these , Just put the corresponding position 1, You can print out the corresponding log.

Involved prop There are mainly these kinds , In fact, it's the corresponding log level：

File name involved ：camxsettings.xml（ Almost all prop It's all in it ）

persist.vendor.camera.logConfigMask
persist.vendor.camera.logEntryExitMask
persist.vendor.camera.logWarningMask
persist.vendor.camera.logInfoMask
persist.vendor.camera.logVerboseMask
persist.vendor.camera.logDRQEnable（ open DRQ log, I usually just put this prop Set as true）persist.vendor.camera.enableAsciiLogging（ qualcomm case You need to catch offline at ordinary times log, You need to turn on this switch , Set as true That's it ）

In fact, there are other configuration schemes , I feel that these are enough for normal use

note: offline log

I take offline log Yes, just a little bit , Last log Will appear on the mobile phone  /data/vendor/camera Under the path

Then export that folder , Use Qualcomm's tools to synthesize a log file

Tool path ：vendor/qcom/proprietary/chi-cdk/tools/binary_log/

command ：python merge_text_logs.py -d  xxx( Folder name )  -o xxx( Generated log file name )

CHI log：

Because there are not so many modules, there is only one prop control

vendor.camera.camera.overridLogLevels

There's a total of 8bit control , You can set the corresponding value as required  

open log The way ：

1. command ：adb shell setprop    xxxx( Corresponding prop)   0xxxx(16 Base number )

2. According to camxsettings.xml The corresponding variable name is written in camxoverridesettings.txt In file

then push To mobile /vendor/etc/camera In the path

All the above mobile phones need root jurisdiction , And it needs to be killed after the setting is completed camera The process will take effect

2.KMD Log

stay KMD It is also divided into many modules , We switch mainly by writing the value of the node log

The path of the corresponding node ：/sys/module/camera/parameters   ( The path in the phone )

  Our main operation nodes are the two in the red box

kernel Corresponding module ：

file name ：cam_debug_util.h   ( In the corresponding camera Just search under the driver directory )

  Usage method ：  echo  0xxxx(16 Decimal digit )   > debug_mdl

stay kernel There is a corresponding log level these

Usage method ：echo  xxx( Enumerated values )  > debug_type

It seems that there is also a kind of separate opening of a single module log Methods , I will update it later

3.Dump Images

dump Images can only be used for IFE Output and subsequent nodes dump, But some formats （TP10） We cannot parse locally , You can ask Qualcomm for help in parsing

File name involved ：camxsettings.xml

There are several corresponding ones here prop： But the control here is more delicate , Can be accurate to the corresponding node Example , And the corresponding node Of port

persist.vendor.camea.autoImageDump  This is a dump output The switch of
persist.vendor.camea.dumpInputatOutput  This is a dump imput The switch of , Premise is output Need to open , After opening, because dump More , So it will be very too laggy
persist.vendor.camea.autoInputImageDumpMask  This is a dump Which? node Of prop, Configure according to your own needs

persist.vendor.camea.autoImageDumpMask

persist.vendor.camea.autoImageDumpIFEoutputPortMask

 

persist.vendor.camea.autoImageDumpIFEInstanceMask

These two are corresponding port and node Of instance id You can confirm the flow of your own running and the corresponding pipelie To assign , Usually mainly in dump （IFE IPE） There are a series of corresponding node Can be done dump, Need to go camxsettings.xml Middle confirmation

In fact, there are many prop Can be used in combination , These are enough for me to use , You can continue to communicate later .