First connection using LE Privacy

[Troy Patterson]

Upon my first connection to my device with LE Privacy, first connection meaning after I've reset the firmware, I'm unable to read anything. The write characteristic works just fine, it's only the read which doesn't work. I'm not seeing any errors. But, if I disconnect and reconnect, I have expected read & write access to the device. Is there a command I'm missing after initially uploading the firmware, that I should be aware of?

[Edvin]

Hello,

I can't think of anything obvious that would cause this behavior. Do you get the interrupts on the device when you try to read read from it, on the first connection - before reconnecting?

 

Also, have you tried to sniff the connection? Anything there that could be of interest?

Are you using nRF Connect? Can you try it, as it usually gives some response when things does not work as "planned", e.g. reading/writing to a characteristic that you don't have permission to access.

 

Best regards,

Edvin

[Troy Patterson]

The current solution is to force it to subscribe twice. The hardware requires you to bond with it, and if you don't it will bond automatically when attempting to subscribe. After attempting to subscribe, making a second attempt allows me to access the device. This is a current workaround

Unfortunately the Nordic FAE and I couldn't get the sniffer to work properly.

This behaviour is exactly the same when using nRF Connect.

[Edvin]

Hello,

Do you need some specific HW to replicate this? If not, and if possible, could you send the project, so that I can try to replicate the issue here, using nRF Connect? Then I could try to sniff the connection.

 

What version of the nRF Sniffer did you try? Have you tested nRF Sniffer V2?

 

Best regards,

Edvin