Opening a PPP connection with the u-blox SARA-R500S, using LTE Cat M1, hangs until it's timed out. I have noted two things:
APN logged as response on the AT+CGDCONT? command is iot.t-mobile.nl.mnc040.mcc901.gprs, while I've configured it as iot.t-mobile.nl.
I believe this is no issue and simply some operator identifier, but please correct me if I'm wrong. I think I've read this somewhere but can't remember and quickly find where.
Weird characters after CONNECT.
In the small log section below there are weird characters after the CONNECT<cr><ln> response to start PPP, which I don't see with the other modems we use (u-blox SARA-R410M and u-blox SARA-G350).
Please see the full log at the end, including the expected behaviour from the R410M log. We're using basically the same code with the u-blox SARA-R410M and are able to establish a PPP connection normally with the same SIM, provider and settings.
[INFO][CELL]: CellularContext PPP connect
[INFO][CELL]: AT TX ( 9): ATD*99***
[INFO][CELL]: AT TX ( 1): 1
[INFO][CELL]: AT TX ( 1): #
[INFO][CELL]: AT TX ( 1): <cr>
[INFO][CELL]: AT RX ( 7): <cr><ln>CONNE
[INFO][CELL]: AT RX (27): CT<cr><ln>~<FF>}#<C0>!}!} } }6}"}&} } }
[DBG ][CELL]: ppp_status_cb: event 0, ptr 3
[DBG ][CELL]: callback: 0, ptr: 3
[DBG ][CELL]: process_oob, filehandle is not usable, return...
Connection timed out (180000 ms)
Same log section but with the u-blox SARA-R410M
```
[INFO][CELL]: CellularContext PPP connect
[INFO][CELL]: AT TX ( 9): ATD*99***
[INFO][CELL]: AT TX ( 1): 1
[INFO][CELL]: AT TX ( 1): #
[INFO][CELL]: AT TX ( 1):
[INFO][CELL]: AT RX (10): CONNECT
[DBG ][CELL]: ppp_status_cb: event 0, ptr 3
[DBG ][CELL]: callback: 0, ptr: 3
[DBG ][CELL]: process_oob, filehandle is not usable, return...
[DBG ][CELL]: process_oob, filehandle is not usable, return...
[DBG ][CELL]: process_oob, filehandle is not usable, return...
[DBG ][CELL]: ppp_status_cb: event 0, ptr 1
[DBG ][CELL]: callback: 0, ptr: 1
Connection status: 3, cellular status: 24
Global IP received but waiting for local IP (48707 ms)
Connected as X.X.X.X in 48811 ms
```
Things I've already tried and additional observations.
PPP connect using CGDATA.
Using different MNO profiles (1, 90, 100).
Increasing stack sizes (PPP to 2048, TCPIP to 4096).
We're connected/attached to the cellular network.
Additional logging shows that nsapi_ppp_connect is returning with OK code.
We're getting process_oob, filehandle is not usable, return... only once vs three times with the R410M.
ppp_status_cb isn't called after process_oob, filehandle is not usable, return... log.
Target(s) affected by this defect ?
u-blox?
Toolchain(s) (name and version) displaying this defect ?
arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Arm Embedded Toolchain 9-2020-q2-update) 9.3.1 20200408 (release)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
What version of Mbed-os are you using (tag or sha) ?
6.4.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
$ mbed --version
1.10.5
How is this defect reproduced ?
Essentially try to establish a cellular connection with an u-blox SARA-R500S module in non-blocking mode.
Description of defect
Opening a PPP connection with the u-blox SARA-R500S, using LTE Cat M1, hangs until it's timed out. I have noted two things:
AT+CGDCONT?command isiot.t-mobile.nl.mnc040.mcc901.gprs, while I've configured it asiot.t-mobile.nl. I believe this is no issue and simply some operator identifier, but please correct me if I'm wrong. I think I've read this somewhere but can't remember and quickly find where.CONNECT. In the small log section below there are weird characters after theCONNECT<cr><ln>response to start PPP, which I don't see with the other modems we use (u-blox SARA-R410M and u-blox SARA-G350).Please see the full log at the end, including the expected behaviour from the R410M log. We're using basically the same code with the u-blox SARA-R410M and are able to establish a PPP connection normally with the same SIM, provider and settings.
Same log section but with the u-blox SARA-R410M
``` [INFO][CELL]: CellularContext PPP connect [INFO][CELL]: AT TX ( 9): ATD*99*** [INFO][CELL]: AT TX ( 1): 1 [INFO][CELL]: AT TX ( 1): # [INFO][CELL]: AT TX ( 1):Things I've already tried and additional observations.
CGDATA.2048, TCPIP to4096).nsapi_ppp_connectis returning with OK code.process_oob, filehandle is not usable, return...only once vs three times with the R410M.ppp_status_cbisn't called afterprocess_oob, filehandle is not usable, return...log.Target(s) affected by this defect ?
u-blox?
Toolchain(s) (name and version) displaying this defect ?
What version of Mbed-os are you using (tag or sha) ?
6.4.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
How is this defect reproduced ?
Essentially try to establish a cellular connection with an u-blox SARA-R500S module in non-blocking mode.
The full logs below show the AT commands and everything to reproduce this further. Also the expected behaviour is shown with the R410M logs.
cellular AT logs from u-blox SARA-R500S
``` [DBG ][TLSW]: mbedtls_ssl_conf_ca_chain() [INFO][CELL]: New CellularContext (0x2000cae0) [INFO][CELL]: CellularContext set blocking 0 Waiting for connect connected 0, conn status 1 [INFO][CELL]: CellularContext set blocking 0 [INFO][CELL]: CellularContext connect Connection status: 2, cellular status: 0 [DBG ][CELL]: callback: 4106, err: 0, data: 4096 Connection status: 2, cellular status: 0 [INFO][CELL]: Start connecting (timeout 1000 ms) [INFO][CELL]: AT TX ( 2): AT [INFO][CELL]: AT TX ( 1):