Compatibility of Simple CMUX Client Library with CAVLI C16QS Modem (IDFGH-12078) #507
Comments
github-actions
bot
changed the title
|
HI, |
|
Hi @Noushadalik Have you tried this library with your modem? If you experience a specific problem, please report it here, with verbose logging enabled. (we were able to fix many issues in the past just by analyzing generic issue reports) |
|
HELLO @david-cermak I changed the AT command to enable CMUX (from AT+CMUX=0 to AT+CMUX=1) as per the But I can't enter CMUX mode. Detailed verbose logs are attached below `I (1680) cmux_example: GSM POWER Off !! D (7200) command_lib: Response: ^boot.rom'v V (7300) CMUX Received: 0x3ffbf90c f9 03 73 01 d7 f9 |..s...| |
|
Hi @david-cermak |
|
hello @david-cermak |
|
Thanks for testing this and sorry for the delay. From the log, I can see that the device successfully switched to CMUX protocol, but failed later, probably trying to get one channel into data mode. This could be also related to the fact, that you've set the CMUX mode directly after powering the device up. Could you please try to run the console example (with the modified command library) and try to run these commands? Especially The expected behavior would be
|
|
hi @david-cermak
|
|
hi @david-cermak |
|
Hi @Noushadalik What I meant was using the console application to interact with the device (not updating the app to send these commands):
The interaction should look something like:
PS: Not sure if the VS code console allows you to type in commands, but you can use any other Windows terminal... PPS: I've already ordered an evaluation board with this modem, so I'll take a look into it |
|
Hi, As per your instructions, we tested the Modem console on Putty and waited for the device to boot up. The detailed logs are attached below. Steps to reproduce:
|
|
Thanks for testing this, could you please try to
|
|
|
Hi @Noushadalik Thanks for testing this! Could you please remove (or comment out) these few lines? esp-protocols/components/esp_modem/src/esp_modem_cmux.cpp Lines 241 to 245 in cffe268 and test again (with |
|
Hi @david-cermak
|
|
Nice, we're one step closer. diff --git a/components/esp_modem/src/esp_modem_cmux.cpp b/components/esp_modem/src/esp_modem_cmux.cpp
index b1bfc78..34a87c5 100644
--- a/components/esp_modem/src/esp_modem_cmux.cpp
+++ b/components/esp_modem/src/esp_modem_cmux.cpp
@@ -137,7 +137,7 @@ bool CMux::data_available(uint8_t *data, size_t len)
} else {
return false;
}
- } else if (data == nullptr && type == (FT_UA | PF) && len == 0) { // notify the initial SABM command
+ } else if (data == nullptr && (type == (FT_UA | PF) || type == 0x3f) && len == 0) { // notify the initial SABM command
Scoped<Lock> l(lock);
sabm_ack = dlci;
} else if (data == nullptr && dlci > 0) {(and could you please share your results as text only? it's easier for me to go through, copy-paste and is just smaller) |
|
Hi@david-cermak Here is the test outcome |
|
Oh, very nice, looks like success already (with a few warnings which i'll fix real quick) |
|
Thank you for the update! |
|
Hi @Noushadalik Sorry it takes so long, but it seems like the changes we added to make it working on the CAVLI device are not compliant with cmux/gsm0710 standard. (so it's not only an issue of your device or a wrong firmware). I'm not sure what we should do in this case. I'll add this info to the list of "known issues" for a start, it already mentions some limitations, deviations and patches. esp-protocols/docs/esp_modem/en/README.rst Lines 212 to 236 in 1476388 |
|
Hi @david-cermak |
|
Hi @david-cermak |
|
I'm not very familiar with PlatformIO, but it should be possible based on their docs: https://docs.platformio.org/en/latest/frameworks/espidf.html#esp-idf-components |
Answers checklist.
General issue report
Hi,
The purpose of this issue is to assess the compatibility of the Simple CMUX Client Library with the CAVLI C16QS Modem. Additionally, an application note for CMUX integration on the CAVLI C16QS Modem (based on 3GPP 27.010) has been provided for reference
@david-cermak
C16QS CMUX Application Note1.0.pdf
The text was updated successfully, but these errors were encountered: