EM20-RG500 quectel-CM auto bring up on openwrt QmiThreadSendQMITimeout

IoT Modules 5G Module
1

HI openwrt system automatically startup quectel-CM & will always be QmiThreadSendQMITimeout!, if manual start is normal… Is this the reason?

[07-03_06:54:58:260] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[07-03_06:54:59:260] 01 0b 00 00 00 00 00 02 27 00 00 00
[07-03_06:54:59:261] TransactionId: 02
QMICTLType: 0027 QMICTL_SYNC_REQ
Length: 0000

[07-03_06:55:00:261] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[07-03_06:55:01:261] 01 0b 00 00 00 00 00 03 27 00 00 00
[07-03_06:55:01:261] TransactionId: 03
QMICTLType: 0027 QMICTL_SYNC_REQ
Length: 0000

[07-03_06:55:02:262] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[07-03_06:55:03:262] 01 0b 00 00 00 00 00 04 27 00 00 00
[07-03_06:55:03:262] TransactionId: 04
QMICTLType: 0027 QMICTL_SYNC_REQ
Length: 0000

2

openwrt system automatically startup quectel-CM。
does the driver probe successful before the quectel-CM started？
It’s better to upload much more dmesg logs with timetamps.

3

This might be normal if the quectel-CM starts before the modem is finished booting up. Sending periodical QMICTL_SYNC_REQ until the modem responds is a reasonable way to detect when the modem is ready to receive commands.

Note that I have no experience with the quectel-CM, RG500 or EM20, so I am just guessing based on generic QMI knowledge here…

4

Dear Sirs,
please refer to the linked files,Quectel_LTE&5G_Linux_USB_Driver_User_Guide_V2.0.pdf (564.5 KB)

5

if still have problems, please tell us your company name, we will ask local FAE to help you.thanks!