Osmocom tools for Qualcomm DIAG
Go to file
Harald Welte a32c769bb7 Generate GSMTAP messages from raw received DIAG frames
This forwards the raw DIAG messages via GSMTAP, so the receiver (e.g.
wireshark) will have to do a full DIAG protocol decode.  I currently
prefer this idea to that of converting only the protocol payload to
"native" GSMTAP messages like GSMTAP_UM.

One of the problems is that the LAPDm headers are alrady stripped, and
we would have to re-add fake LAPDm headers to generate GSMTAP_UM.  So
let's rather forward all information we have and let wireshark deal with
it.

I'm not entirely sure if this is  the best strategy, but we can always
implement both modes and switch between them at runtime.
2017-01-08 16:04:01 +01:00
doc Add some notes and examples on the protocol 2013-05-30 17:50:39 +02:00
src Generate GSMTAP messages from raw received DIAG frames 2017-01-08 16:04:01 +01:00
.gitignore add .gitignore 2013-12-24 00:48:51 +01:00
COPYING Add GPLv2-or-later license text + headers + rename to osmo-qcdiag-log 2016-12-24 10:31:07 +01:00
HISTORY Modernize README, move the old information to HISTORY 2016-12-26 16:04:02 +01:00
README Modernize README, move the old information to HISTORY 2016-12-26 16:04:02 +01:00
TODO Fix typos 2016-12-28 15:12:38 +01:00

README

Utility to configure Qualcomm DIAG, read, decode and display the
DIAG messages. It can enable logging and format/print the log
messages generated by the various subsystems of the baseband.

To build this software a copy of the Osmocom libosmocore
library is required. Your distribution might already contain
the necessary utility.

In general all Qualcomm devices that export DIAG should be
supported. We have tested it with the Quectel UC20, EC20 and
EC25 devices.