NB-IoT Module Series
BC660K-GL Log Capture Guide
BC660K-GL_Log_Capture_Guide 22 / 24
5 FAQs
5.1. How to solve the problem of DB file mismatch?
The DB file is used to decode the log messages. If it does not match with the target firmware, it will cause
decoding errors or exceptions, which are hard to detect, thus bringing difficulties to problem analyses.
Therefore, it is important to ensure that the DB file matches with the target firmware. If it does not match,
please update the DB file referring to Chapter 4.4.
5.2. How to get the DB file?
Generally, the DB file is included in the firmware package and in the file name "comdb.txt". If you don’t
have the firmware package, or cannot find the DB file therein, or you get a mismatched DB file, please
contact Quectel Technical Support.
5.3. Can the baud rate of the logging port be modified?
Yes, you can modify it referring to Chapter 4.3. The default baud rate for log capture is 6 M. Note that the
baud rate of the logging port should be modified both on EPAT and using AT+QCFG="logbaudrate". For
details on this command, see document [3].
5.4. What to do when the module cannot connect to PC?
When the module connects to a PC, Windows system will search for and install a USB-UART driver for
the connection. If the PC is not connected to the network, the driver cannot be downloaded. In this case,
you need to download the driver on another PC and install it on the PC to be used for the log capture. If
the PC fails to find any appropriate driver, please download a diver detection tool, such as Driver
Magician, DriverMax, etc., to search for the driver automatically, or contact Quectel Technical Support for
support.
To Next Page
Loading...
