In v1.13.3 BLE full_stack it looks like general scanning is locked-out forever after terminating a direct connection establishment procedure. Using the Nucleo dev boards as a master and a slave, start general scanning with aci_gap_start_general_discovery_proc(), return is SUCCESS. The target slave is found, scanning is stopped and connection with it is started by master with aci_gap_create_connection(), return is SUCCESS. Before this connection completes, the slave goes out of range or just stops advertising and goes to its deep sleep. But then connection establishment is hung forever on the master. So, master cancels this indefinitely "hung" procedure with aci_gap_terminate_gap_proc(GAP_DIRECT_CONNECTION_ESTABLISHMENT_PROC), return is SUCCESS and soon receive the ACI_GAP_PROC_COMPLETE_VSEVT_CODE with the status of SUCCESS and the procedure code of GAP_DIRECT_CONNECTION_ESTABLISHMENT_PROC, all as expected.
The problem now is master can no longer re-start scanning, call to aci_gap_start_general_discovery_proc() is now only returning 0x0C (of course only using the same parameters as above when return was SUCCESS).
So is there another clean-up step required after terminating the direct connection establishment in order to be able to scan again?
