PeerManager error (error: 139)

RE: PeerManager error (error: 139)

Edvin — Thu, 01 Aug 2019 07:43:08 GMT

[quote user="takashina hiroki"]Can nRF Sniffer run on this device?[/quote]

No. Sorry.

[quote user="takashina hiroki"]If you delete the entire flash, other devices' bonding information will also disappear.
Therefore, this method is not preferable.[/quote]

This is not a permanent solution, but for debugging, and to find the cause of the issue.

RE: PeerManager error (error: 139)

takashina hiroki — Wed, 31 Jul 2019 23:14:46 GMT

I have the following devices.
BMD-300-EVAL (Rigado)

Can nRF Sniffer run on this device?

RE: PeerManager error (error: 139)

takashina hiroki — Wed, 31 Jul 2019 23:14:13 GMT

One device is nRF and the other is Android.
nRF needs to be bonded to multiple devices.
If you delete the entire flash, other devices' bonding information will also disappear.
Therefore, this method is not preferable.
Are there any other measures?
Also, if you know the root cause, please let me know.

RE: PeerManager error (error: 139)

Edvin — Tue, 30 Jul 2019 08:05:57 GMT

[quote user="Edvin Holmseth"]Do you use bonding when you are reproducing this?[/quote]

Are both of the devices nRF? If so, can you try to delete the entire flash of both devices, and then try again? If one of the devices is a phone, try to "forget device" to erase the bonding information (stored keys), and delete the flash on the other, so that you have a clean start.

[quote user="takashina hiroki"]I do not have nRF Sniffer.[/quote]

So do you have another DK? nRF Sniffer is only FW, which runs on another DK. It is a very useful tool for these kind of problems, and in BLE development in general.

Best regards,

Edvin

RE: PeerManager error (error: 139)

takashina hiroki — Mon, 29 Jul 2019 22:39:26 GMT

Yes, I use bonding.

I do not have nRF Sniffer.
Therefore, sniffer trace can not be performed.

Is there any other way to investigate the cause?

RE: PeerManager error (error: 139)

Edvin — Mon, 29 Jul 2019 14:32:37 GMT

Hello,

As you say, it looks like it is BLE_GAP_SEC_STATUS_DHKEY_FAILURE. Do you use bonding when you are reproducing this?

Can you do a sniffer trace of the connection when this occurs? You can use the nRF Sniffer.