Call to mmwlan_scan_abort() works, but prints error on 2.7.2

Software
1

In 2.5.2, the call to mmwlan_scan_abort() did not cause an error.
in 2.7.2 we get:
E 11597 Command 44:120 failed with rc -114 (0xffffff8e)
E 11598 Failed to execute HW_SCAN command

Why do we call mmwlan_scan_abort() after the scan is complete?
If we don’t call it, all works well, but it takes a long time for us to bring the link up.
When we call mmwlan_scan_abort(), the link comes up much faster (20 or so seconds faster).
And as I said above, in 2.5.2 there was no error, now we get an error.
However, aside from the print out of the error, everything works fine.

So the question is: am I using mmwlan_scan_abort() correctly and I can ignore the error?
I assume so.

Thanks

=================
More detail:

  1. The scan completes
    * we know the SSID of the AP
    * and the scan_complete_callback() has been called.

  2. Then we call mmwlan_scan_abort()
    and on 2.7.2, we get the error:
    E 11597 Command 44:120 failed with rc -114 (0xffffff8e)
    E 11598 Failed to execute HW_SCAN command

2

Hi @Straff , we just released version 2.8.2 if you would like to try that instead

3 
/*   
 * We can no longer abort the scan
 *
 * In 2.7.2 
 *    we get errors if we call mmwlan_scan_abort();
 *    E 11597 Command 44:120 failed with rc -114 (0xffffff8e)
 *    E 11598 Failed to execute HW_SCAN command
 *
 * In 2.8.2
 *    If we call mmwlan_scan_abort();
 *    We no longer get any errors
 *    However, if we can this function
 *      Association fails
 *      power off of MorseMicro chip causes the system to reboot.
 */
// mmwlan_scan_abort();

Note: fi we don’t call the mmlan_scan_abort(), we can associate, send data, go into WNM sleep, and power off the MorseMicro chip.

4

Hi @Straff

We tried this with one of our example applications in 2.8.2 and did not see the association fail. We’ll continue trying to reproduce it, but if you have code you can share that would be helpful.

Regarding the reboot, that sounds like the system might be faulting? Is it hitting a fault handler?