Sierra_Linux_QMI not working?



I’ve tired to collect MC8704 logs using the tool from Sierra_Linux_QMI_SDK_v1.09.04 tarball SLQS1.09.04.tar.gz. e.g.

./ -l -d /dev/ttyUSB0 -f SwiLogPlus_generic_filter_6.3.sqf -o test_20130614_3.raw

However, I think they are probably useless for trouble shooting problems: the tool didn’t log any information while calls were being made, only about 7k at the start.

Please can anyone help with the following:

  • is the tool working as expected? It writes some information at the start of the test but while the modem is making calls no more information is output to the log file. This isnt my idea of what a logging tool does i.e. log information in the course of testing for post test analysis.
  • If the tool is not working (I think this is the case) please can you provide guidance for getting it working?
  • Is there any configuration required on the modem to get it to emit more logging information? As the script is so straight forward and just logging what comes out of ttyUSB0 it suggest that the modem is not emitting it in the first place, and this might be a config problem, or a problem with the filter (which is written to ttyUSB0 first).


I don’t think the tool is working as the capture log sizes are 0bytes at a minimum or ~7K at a maximum. I would expect the logs to be much bigger and to be continually logging information while the modem is making calls. When the is started, it writes some information to the file and then no more during the test as calls are being made.

I tried the SwiLogPlus_generic_filter_6.3.sqf filter which I found in the SDK. I tested on 2 different modems with differing FW as noted below. Here are the details of some tests:


  • ran:
    ./ -l -d /dev/ttyUSB0 -f SwiLogPlus_generic_filter_6.3.sqf -o test_20130614_3.raw
  • test on modem 0 with T3_0_2_2 FW
  • made ~10 voice calls
  • file size 6674bytes


  • ran:
    ./ -l -d /dev/ttyUSB0 -f SwiLogPlus_generic_filter_6.3.sqf -o test_20130614_5.raw
  • test on modem 1 with T3_0_4_1 FW
  • made ~10 voice calls
  • file size 7016bytes

I took a look at the tool which is actually just cat-ing what comes out of /dev/ttyUSB0 into the output file. I did what the script does at the console and got the following:

stty -F /dev/ttyUSB0 raw -echo
cat SwiLogPlus_generic_filter_6.3.sqf > /dev/ttyUSB0
cat /dev/ttyUSB0

or for a different filter I got this:

cat /dev/ttyUSB0
~�y}^T3_0_4_1BT R605 CNSZXD00000155 2013/03/15 09:51:38T3_0_4_1AP R605
CNSZXD00000155 2013/03/15 09:51:3803~~TbT3_0_4_1AP R605 CNSZXD00000155
2013/03/15 09:51:38���������������������������������~

This is so uncomplicated that it makes me think that the modem is not emitting the required logging information. Hence I asked the question of whether there is something to configure on the modem e.g. the filters.

I thought about using the remote logging options, but it just relays what comes out of /dev/ttyUSB0. If the above doesnt work then remote logging wont work.

Any help would be appreciated.


This is probably because the DM port on MC8704 is /dev/ttyUSB1, not /dev/ttyUSB0 but waiting for confirmation.