Unexpected "123456" pin code value

[Thiemo van Engelen]

Hello,

In our product, we use the S132 v3 softdevice and legacy pairing with a static pin code. At startup, this pin code (that can be changed by the user) is read from flash and then passed onto the softdevice using sd_ble_opt_set(BLE_GAP_OPT_PASSKEY, &bleOptions). When a unit is shipped to the customer there is no pin stored in flash, or at least there shouldn't be. In that case, it will use "000000" as pin code and pass that to the softdevice.

We have lately encountered a few instances where a customer received a product and found out that the pin code was not "000000", but "123456". We are now wondering if there could be a situation (misconfiguration by the application, internal errors, memory corruption, etc...) in which the softdevice uses "123456" as pin code?

Has anybody else perhaps also encountered this behavior?

Kind regards,

Thiemo van Engelen

[Sigurd]

Hi,

From the documentation, it will either be the 6-digit ASCII string you set it to with sd_ble_opt_set(), or "If this is NULL, the SoftDevice will generate a random passkey if required.". So assuming this is not a one-time thing(it was 123456 just 1 random time),  I think you somehow must have set it to 123456 with sd_ble_opt_set()