This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bonding problem

Hello guys,

I'm working in a project which requires from me to bond to certain devices and refuse the bonding from others, I mean at certain input, connect to anyone and accept pairing from any device and at certain input, connect only to previously paired devices only, My problem is that the behaviour of the development kit is good but when I'm using this module PTR51822A, I faced a lot of issues and I cannot understand why its doing like that and it's totally random,it's not depending on the condition I'm putting because when I checked it with ble sniffer, it gives me weird results , for example: image description

image description

image description

why the telephone keeps sending too much packets with no waiting for the module to respond to it? these cases never ever happened with the development kit and it's the same code running in both chips.

and also sometimes after trying to bond, master is not responding to the slave and after timeout it looses the connection and start advertising again which is not expected to do.

I'm saying it's really weird because all my devices are able connecting to the same module and they are also at certain time with the same conditions, didn't connect to the module, I don't know why but I'm attaching six sniffer files, one is the working case and the others are not working for different reasons.

snifferResults.rar

I'm trying my module with LG , Hauwei mediapad m2, Iphone 4s, Ipad 10.

thanks for help.

Regards,

Mohamed Osama

  • Hi Hung bui, I tried proxmity application with nrf connect, it code is a little bit different because I depend on the bonding between the ble and phone, I mean you proxmity application didn't pop up window asking for pairing, I should go and press on "bond" to start bonding process, and also I've dfu in my application which is different than proxmity application,

    anyways, I tried the code more and more & finished the debugging with that coclusion: if you've any problem with pairing, it crash, for example : you're connecting to the firmware, a pop up window asking you to pair or cancel, if you pressed on cancel, it will crash, I'm not doing any change in the device_manager_peripherial code & revised my code with the ble_app_hrs with dfu and found no difference.

    the crash was at assembly command called DCW and behind it was written 2E2E the error code is very weird, it was 0x00000089

  • @Mohamed: It's not a black box, all the code are open, if it crash, it should be possible to figure out why it crashes and where.

    I won't be able to help you if can't provide enough information on the issue or reproduce the issue on our example code.

Related