ERROR 12804 Multipheripheral + bonding + whitelist

[ipshiv]

Good day!

As base I used this examples:

• ble_app_multiperipheral - for connection handling
• ble_app_hids_keyboard - for whitelist and bonding

Error occurs after disconnection and resuming connection.

/**@brief Function for setting filtered device identities.
 *
 * @param[in] skip  Filter passed to @ref pm_peer_id_list.
 */
static void identities_set(pm_peer_id_list_skip_t skip)
{
    pm_peer_id_t peer_ids[BLE_GAP_DEVICE_IDENTITIES_MAX_COUNT];
    uint32_t     peer_id_count = BLE_GAP_DEVICE_IDENTITIES_MAX_COUNT;

    ret_code_t err_code = pm_peer_id_list(peer_ids, &peer_id_count, PM_PEER_ID_INVALID, skip);
    APP_ERROR_CHECK(err_code);
    NRF_LOG_INFO("IDS: %i, ID COUNT: %i", peer_ids, peer_id_count)
    err_code = pm_device_identities_list_set(peer_ids, peer_id_count);
    if (err_code != NRF_SUCCESS) {
    	NRF_LOG_INFO("Errcode is : 0x%X", err_code);
    }
    APP_ERROR_CHECK(err_code);

}

pm_device_identities_list_set - returns ERROR 12804 \ 0x3204

Any ideas in which direction should I look?

[Einar Thorsrud]

Hi,

Error 0x3204 is BLE_ERROR_GAP_DEVICE_IDENTITIES_IN_USE, which is returned from pm_device_identities_list_set when "If the device identities list is in use and cannot be set". Are you scanning or advertising using a whitelist at this point in time? If so, this error is expected.

[ipshiv]

To be sure I had to stop and start advertising again. That works fine.

How can I close that ticket?

[Shockel]

Einar, I had a similar issue here https://devzone.nordicsemi.com/f/nordic-q-a/46341/call-to-softdevice-returns-illegal-error-code-0x3204-in-current-time-service-client . 0x3204 appeared to me 'illegal' since it was hard to trace back to the proper definition. Thanks for pointing this out here.

Just as a suggestion: If it is indeed an expected result, then the demo apps as listed by the OP and the ble_app_cts_c should not treat it as an error ?

[Einar Thorsrud]

Hi,

I am glad to hear this solved the issue. You can close the case by clicking "Verify Answer" right under the answer that helped you.

[Einar Thorsrud]

I think it is correct to treat this as an error, as the device identities list will not be set. However, the example applications should not trigger this error in the first place as you described in this thread, so that should be fixed.