nRF8001 Security Required - Just Works configuration

[VirtualYooper]

We have a sensor product that has been in the field using the nRF8001 in no security required, just works mode for over a year. Recently, we had a request from a volume user that requires a secure connection.

In nRFGo, the settings have been changed to Security Required, Minimum key size 7, maximum key size 16, Unauthenticated, None for I/O, and Security request delay of 10 seconds. All Device Information Characteristics have been made readable regardless of security settings.

Our problem when these changes are made is this: After nRF8001 init is called, we are getting an error message of lib_aci_error_descriptor 178,255, 141 when Security Required is selected in nRFGo. The nRF8001 does not appear to finish initialization, and is not discoverable by any of our BLE tools.

Any ideas on what would be generating this error when enabling security would be greatly appreciated.

[run_ar]

Just realized that you might be using the old SDK that we had for the 8051 mcu? guessing by the numbers you posted above, you might get error 0x8D (141) ACI_STATUS_ERROR_BOND_REQUIRED. Are you doing any operations on any pipes that needs a bonded peer. E.g notifications or similar prior to the connection and bond being established? I think you should also check that you actually bonded to the peer device (by the way, what central are you using). You could try to send a bondsecurityrequest (0x1D) if needed.