Yesterday, after sometime the ping application was no longer connecting to softAP.
In order to debug that I put both the board with ping application and I tried connecting to ASIARF gateway which we purchased. Only one of the board was connecting to ASIARF gateway.
Today morning both the boards are not connecting to ASIARF gateway.
How do i debug this? Is it possible to get some logs from Firmware. Is it possible to get the list of frequency it is scanning?
Can you please share API reference manual for 2.9.2 SDK
There is an API reference manual in PDF form available here: https://github.com/MorseMicro/mm-iot-sdk/releases/download/2.9.7/Morse_Micro_IoT_SDK_2.9.7_API_Reference_Manual.pdf
It is also available by simply opening documentation.html with your web browser inside the extracted mm-iot-sdk
I am finding that the ping application made from 2.9.7 is no longer connecting to Access point. The old ping application(made with older build) is working. How can i further understand why it is not working
Is there a way by which i can check at the FW level, which frequency it is trying to connect etc…
The frequency list it is scanning is dictated by the regdb component in the 2.9.7 SDK.
There aren’t any easily accessible logs out of firmware to show what is scanning, and unfortunately until libmorse is open source, in the interest of keeping code size down there are only error level logs compiled into libmorse.
Your best chance at debugging this is to use a third linux device and get a sniffer capture. https://www.morsemicro.com/resources/appnotes/MM_APPNOTE-36_How_to_do_a_Sniffer_Capture.pdf
Common problems for MM-IoT-SDK based projects not finding APs on a scan and not connecting usually boil down to incorrect region settings. For the embedded platform, the configured region must match the region configured on the AP, even if there is channel overlap. ie, an AU configured device will not see a US configured AP.