Two triggers to end the operation are set up by pParams->endTrigger/pParams->endTime and pParams->timeoutTrigger/pParams->timeoutTime, respectively. The triggers have the following behavior:

• If the timeout trigger occurs while waiting for sync on an advertiser packet, the operation shall end immediately
• If the timeout trigger occurs at another time while operating on a primary channel, the operation shall continue until the scan would otherwise be resumed on the primary channel, and then end.
• If an Aux pointer is followed, any timeout trigger (past or future) is ignored.
• If the end trigger occurs while waiting for sync on an advertiser packet, the operation shall end immediately.
• If the end trigger occurs at another time, the operation shall continue until an Aux pointer would be followed or the scan would otherwise be resumed on the primary channel, and then end.

If the immediate command CMD_STOP is received by the radio CPU, it shall have the same meaning as the end trigger occurring, except that the status code after ending shall be CMD_DONE_STOPPED. Typically, timeoutTrigger can be used at the end of a scan window, while endTrigger can be used when scanning is to end entirely.

The output structure pOutput contains fields which give information on the command being run. The radio CPU shall not initialize the fields, so this must be done by the system CPU when a reset of the counters is desired. The fields shall be updated by the radio CPU as described below. The list also indicates when interrupts shall be raised in the system CPU.

• If a SCAN_REQ or AUX_SCAN_REQ packet is transmitted, nTxScanReq (CMD_BLE_SCANNER) or nTxReq (CMD_BLE5_SCANNER) is incremented and a Tx_Done interrupt is raised.
• If a SCAN_REQ or AUX_SCAN_REQ is not transmitted due to the backoff procedure, nBackedOffScanReq (CMD_BLE_SCANNER) or nBackedOffReq (CMD_BLE5_SCANNER) is incremented
• If an *ADV*_IND or AUX_CHAIN_IND packet is received with CRC OK and the bIgnore flag cleared, nRxAdvOk is incremented, an Rx_Ok interrupt is raised, and timeStamp is set to a timestamp of the start of the packet.
• If an *ADV*_IND or AUX_CHAIN_IND packet is received with CRC OK and the bIgnore flag set, nRxAdvIgnored is incremented and an Rx_Ignored interrupt is raised.
• If an *ADV*_IND or AUX_CHAIN_IND packet is received with CRC error, nRxAdvNok is incremented and an Rx_Nok interrupt is raised.
• If an *ADV*_IND or AUX_CHAIN_IND packet is received and did not fit in the RX queue, nRxAdvBufFull is incremented and an Rx_Buf_Full interrupt is raised.
• If a SCAN_RSP or AUX_SCAN_RSP packet is received with CRC OK and the bIgnore flag cleared, nRxScanRspOk (CMD_BLE_SCANNER) or nRxRspOk (CMD_BLE5_SCANNER) is incremented and an Rx_Ok interrupt is raised.
• If a SCAN_RSP or AUX_SCAN_RSP packet is received with CRC OK and the bIgnore flag set, nRxScanRspIgnored (CMD_BLE_SCANNER) or nRxRspIgnored (CMD_BLE5_SCANNER) is incremented and an Rx_Ignored interrupt is raised.
• If a SCAN_RSP or AUX_SCAN_RSP packet is received with CRC error, nRxScanRspNok (CMD_BLE_SCANNER) or nRxRspNok (CMD_BLE5_SCANNER) is incremented and an Rx_Nok interrupt is raised.
• If a SCAN_RSP or AUX_SCAN_RSP packet is received and did not fit in the RX queue, nRxScanRspBufFull (CMD_BLE_SCANNER) or nRxRspBufFull (CMD_BLE5_SCANNER) is incremented and an Rx_Buf_Full interrupt is raised.
• If a packet is received, lastRssi is set to the RSSI of that packet.
• If the first RX data entry in the RX queue changed state to Finished after a packet was received, an Rx_Entry_Done interrupt is raised.

A scanner operation shall end with one of the statuses listed in Table 26-153. The status field of the command structure after the operation is ended indicates the reason why the operation ended. In all cases, a Command_Done interrupt is raised. In each case, the result of TRUE, FALSE, or ABORT is indicated, which will decide the next action.