Description
Description
- Type: Bug
- Related issue: Status callbacks #6032
- Priority: Minor
Bug
Target
UBLOX_C027/UBLOX_C030_U201/any cellular
Toolchain:
GCC_ARM
mbed-cli version:
1.2.0
mbed-os sha:
636ced8
Expected behavior
The tests in mbed-os-features-netsocket-cellular-generic_modem_driver-tests-unit_tests-default should pass on a cellular platform, specifically UBLOX_C027 and UBLOX_C030_U201.
Actual behavior
The first test passes but all subsequent tests fail. The connection actually succeeds ('cos I can see the IP address and DNS information being printed out) but the connect() call does not return at that point, instead it times out with error -3004 NSAPI_ERROR_NO_CONNECTION. To be completely sure, I then modifed the tests so that the second test is the first test run once more. A log of the failure behaviour is attached in
generic_modem_driver_test.txt (note that I'm bouncing off my own echo server in that test run so that I can see the echo requests arriving (or not)).
If I switch to the commit before #6032 was merged (5a74826) then the tests pass, so I suspect that's caused the problem.
NOTE: this implies that the process of an application calling connect(), disconnect() and then connect() again would probably also not work.
Steps to reproduce
Get a cellular platform, e.g. UBLOX_C027 or UBLOX_C030_U201 with a valid SIM, set the right APN in mbed_app.json (if required) and run the following:
mbed test -v -n mbed-os-features-netsocket-cellular-generic_modem_driver-tests-unit_tests-default
@hasnainvirk, @kjbracey-arm FYI.