Peer manager causes fault due to invalid connection handle.

RE: Peer manager causes fault due to invalid connection handle.

Dmitriy L1 — Tue, 18 Sep 2018 14:02:08 GMT

I just took another example project (glucose sensor) where pairing logic is exactly what I needed, ported it to SES and adopted for my purposes. Hardfaults are still present but it likely caused by hardware so there is no point to discuss it here.

RE: Peer manager causes fault due to invalid connection handle.

haakonsh — Tue, 18 Sep 2018 12:55:14 GMT

You can leave the current post as-is. Do you mind describing what you did to solve your issue?

RE: Peer manager causes fault due to invalid connection handle.

Dmitriy L1 — Mon, 17 Sep 2018 07:50:32 GMT

I went in another way, it seems to be working well. How can I close current issue?

RE: Peer manager causes fault due to invalid connection handle.

Dmitriy L1 — Wed, 05 Sep 2018 14:27:21 GMT

Sorry for late response. Problem still exists and I need help.

Please see screenshot of debug session.

RE: Peer manager causes fault due to invalid connection handle.

haakonsh — Tue, 21 Aug 2018 11:44:44 GMT

I think 0x6B0 is the address of the hardfault handler. Do you have a dump of the CPU registers at that point?

RE: Peer manager causes fault due to invalid connection handle.

Dmitriy L1 — Fri, 17 Aug 2018 10:08:16 GMT

It looks like device crashes on the very begining of connection establishing due to some internal SoftDevice assert or error, as no event rises to application before it goes to hardfault. In debugger i see it stops on 0x000006B0 address.

I think that omitting Peer Manager and implementing simplified custom pairing/bonding logic could be an option for me. I would use pm_peer_data_bonding_store() function directly from application. Is there any restrictions or concerns?

RE: Peer manager causes fault due to invalid connection handle.

haakonsh — Fri, 17 Aug 2018 08:54:58 GMT

I would try to focus on the retrieval of the bonding information from flash by the peer manager. Find out what is different from the first to the second connection establishment attempt. How far into the process do your get on the second attempt before you crash?

Do you have any debug information from the crash?

RE: Peer manager causes fault due to invalid connection handle.

Dmitriy L1 — Thu, 16 Aug 2018 13:49:48 GMT

I tried to compare hex dumps of entire SoC memory, there were no writes at all. Later I found reason why - there were few duplicate event handlers like was described here:

https://devzone.nordicsemi.com/f/nordic-q-a/35433/configuring-peer-manager-for-bonding

Now device is able to save bonding info, but it became unstable. It can accept first connection after powering up and goes to hardfault on second attempt. I can't find were it crashes.

RE: Peer manager causes fault due to invalid connection handle.

haakonsh — Thu, 16 Aug 2018 10:53:03 GMT

I'll try to help you as best I can 🙂

First we should verify that you can write the bond information to flash. You'll need to find the address of the stored information and read out the content.

RE: Peer manager causes fault due to invalid connection handle.

Dmitriy L1 — Tue, 14 Aug 2018 13:01:54 GMT

Thanks for response!

I've been confused with connection handle 0 since function wasn't able to resolve handle to connection role and returned error.

After some playing around handlers I don't observe freezing anymore. However device doesn't keep bonding information.

Passkey popup appears each time device resumed from sleep mode. Should I create another ticket or it can be discussed here?

RE: Peer manager causes fault due to invalid connection handle.

haakonsh — Tue, 14 Aug 2018 12:45:02 GMT

Connection handle 0 is the fist connection handle to be assigned. Your first connection will always be assigned to 0.

I think the order of your event handlers are correct as well.

Do you have any more debug information ?