Messages in this thread | | | Date | Thu, 13 Apr 2023 23:31:36 +0100 | Subject | Re: [PATCH v2 3/6] docs: qcom: Add qualcomm minidump guide | From | Srinivas Kandagatla <> |
| |
On 22/03/2023 13:30, Mukesh Ojha wrote: > +Dump collection > +--------------- > + > +The solution supports extracting the minidump produced either over USB or > +stored to an attached storage device. > + > +By default, dumps are downloaded via USB to the attached x86_64 machine > +running PCAT (Qualcomm tool) software. Upon download, we will see
Are these both PCAT and dexter tools public?
--srini > +a set of binary blobs starts with name md_* in PCAT configured directory > +in x86_64 machine, so for above example from the client it will be > +md_REGION_A.BIN. This binary blob depends on region content to determine > +whether it needs external parser support to get the content of the region, > +so for simple plain ASCII text we don't need any parsing and the content > +can be seen just opening the binary file. > + > +To collect the dump to attached storage type, one need to write appropriate > +value to IMEM register, in that case dumps are collected in rawdump > +partition on the target device itself. > + > +One need to read the entire rawdump partition and pull out content to > +save it onto the attached x86_64 machine over USB. Later, this rawdump > +can be pass it to another tool dexter.exe(Qualcomm tool) which converts > +this into the similar binary blobs which we have got it when download type > +was set to USB i.e a set of registered region as blobs and their name > +starts with md_*. > -- 2.7.4
| |