UBLOX_EVK_ODIN_W2 wifi connection breaks after a few minutes

[tommikas]

Description

I modified mbed-cloud-client-example (2.1.0) to send notifications every second and then built the application for UBLOX_EVK_ODIN_W2. I used the onboard wifi to connect to a hotspot right next to the device. Client connects fine and keeps sending notifications for some minutes, but typically before 10 minutes client loses connection and thereafter DNS resolution consistently fails. After resetting the device the same repeats.

Target: UBLOX_EVK_ODIN_W2
Toolchain: GCC_ARM 6.3.1
Tools: mbed-cli 1.8.3
Mbed OS: bf6f2c3

Steps to reproduce:

1. Apply the modifications included below to the PDMC example application.
2. Configure wifi ssid and password.
3. Run the application.

Example application modifications:

diff --git i/configs/wifi_odin_v4.json w/configs/wifi_odin_v4.json
index 5ae9859..ad8a6a8 100644
--- i/configs/wifi_odin_v4.json
+++ w/configs/wifi_odin_v4.json
@@ -15,7 +15,7 @@
 "update-client.storage-address" : "(1024*1024*64)",
 "update-client.storage-size" : "(1024*1024*2)",
 "update-client.storage-locations" : 1,
- "mbed-trace.enable": null,
+ "mbed-trace.enable": 1,
 "nsapi.default-wifi-security" : "WPA_WPA2",
 "nsapi.default-wifi-ssid" : "\"SSID\"",
 "nsapi.default-wifi-password" : "\"Password\""
diff --git i/main.cpp w/main.cpp
index 204280e..b948989 100644
--- i/main.cpp
+++ w/main.cpp
@@ -132,7 +132,7 @@ void main_application(void)
 // make sure the line buffering is on as non-trace builds do
 // not produce enough output to fill the buffer
 setlinebuf(stdout);
-#endif 
+#endif
 
 // Initialize trace-library first
 if (application_init_mbed_trace() != 0) {
@@ -220,10 +220,8 @@ void main_application(void)
 
 while (mbedClient.is_register_called()) {
 static int button_count = 0;
- mcc_platform_do_wait(100);
- if (mcc_platform_button_clicked()) {
- button_res->set_value(++button_count);
- }
+ mcc_platform_do_wait(1000);
+ button_res->set_value(++button_count);
 }
 
 // Client unregistered, exit program.

example log: 2018-11-28_101125_ttyACM0.log

Issue request type

[ ] Question
[ ] Enhancement
[x] Bug

[0xc0170]

cc @ARMmbed/team-ublox

[ciarmcom]

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-306

[AmmadRehmatCUS]

Does this scenario appears when the mbed traces are disabled?

[cmonr]

@tommikas ^^^

[screamerbg]

Bump @tommikas

[AmmadRehmatCUS]

@screamerbg @0xc0170 please close this if its not relevant anymore

[0xc0170]

cc @SeppoTakalo @tommikas

[SeppoTakalo]

Not relevant to us.
From the given log file, I can only see Client errors, and I know that it does not handle network state events, also the socket error is not shown, therefore impossible to tell if the device was working correctly or not.

[tommikas]

I carved out some time to quickly test this.

What seems to happen is that the device loses connection to the AP and isn't able to reconnect until it is reset. Tracing doesn't seem to affect it.

impossible to tell if the device was working correctly or not

It loses network connection and isn't able to reconnect until the device is reset. So ... no, it's not working correctly.

[aqib-ublox]

@todor603 your description matches with #9621 and it being resolved in #10454

please see discussion at #9621

[aqib-ublox]

Summary of issue handled under #9621

Client lost connection with AP and immediately try re-connecting that cause assertion and avoid re-connection so need to reset device

WIFI status was not handled in firmware that added and solve problem

[tommikas]

That particular problem caused an assert though. This didn't.

Edit: but, I can see how fixing that might resolve this too...