Serial logging for WiFi related issues

I am trying to isolate a problem with the WICED network stack - particularly how the device handles bad credentials for an available WAP - this is to determine whether the application is triggering an apparent hang.
Using OS 2.1.0 and SerialLogHandler logHandler(LOG_LEVEL_ALL); I am getting this level of output:

0000097955 [comm.protocol] TRACE: Reply recieved: type=2, code=0
0000097955 [comm.protocol] TRACE: message id 57325 complete with code 0.00
0000097956 [comm.protocol] TRACE: rcv'd message type=13
0000113149 [comm.protocol] TRACE: Reply recieved: type=2, code=0
0000113149 [comm.protocol] TRACE: message id 57326 complete with code 0.00
0000113149 [comm.protocol] TRACE: rcv'd message type=13
0000120755 [comm.protocol] TRACE: rcv'd message type=8

When the WAP is out of range

0000727090 [comm.protocol] ERROR: Event loop error 24
0000727091 [system] INFO: Cloud: disconnecting
0000727091 [system] INFO: Cloud: disconnected
0000727191 [system] INFO: Cloud: connecting
0000727202 [system] WARN: Cloud socket connection failed: -230
0000727202 [system] WARN: Internet test failed: DNS
0000727202 [system] WARN: Handling cloud error: 2

Is this the maximum output from logging for system/comms?

@armor, yes, due to space constraints in the flash logging on newer DeviceOS versions for the Gen2 WiFi has been severely restricted.

The only way to add more logs is to build for debug (DEBUG_BUILD=y) and with monolithic firmware.

2 Likes