ERROR 12804 Multipheripheral + bonding + whitelist

RE: ERROR 12804 Multipheripheral + bonding + whitelist

Einar Thorsrud — Tue, 23 Apr 2019 06:57:26 GMT

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.

RE: ERROR 12804 Multipheripheral + bonding + whitelist

Einar Thorsrud — Tue, 23 Apr 2019 06:44:45 GMT

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.

RE: ERROR 12804 Multipheripheral + bonding + whitelist

Shockel — Thu, 18 Apr 2019 14:09:38 GMT

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 ?

RE: ERROR 12804 Multipheripheral + bonding + whitelist

ipshiv — Thu, 18 Apr 2019 03:06:49 GMT

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

How can I close that ticket?

RE: ERROR 12804 Multipheripheral + bonding + whitelist

Einar Thorsrud — Wed, 17 Apr 2019 12:21:34 GMT

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.