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

Advertising and disconnection issues after porting

Hi,

I have recently ported from SDK12 to SDK14.2. We have a custom android app which connects to nRF52832.  The correct sequence of events in BLE should be

- Fast advertisement

- Slow Advertisement(if not connected for 2 mins)

- Connection

- Reading form the sensor

- Disconnection

But after porting to SDK14 we are observing the following sequence of events

- Fast advertisement

- Slow Advertisement(if not connected for 2 mins)

- Connection

- Reading form the sensor

- Fast advertisement(dont know how this happens)

- Disconnection

Also sometimes when we try to disconnect the system hangs.

Do you know why this would happen?Do we need to change something in our app related to advertisement and disconnection?

Thanks in advance

Parents
  • Hi,

    I would be surprised if it starts advertising before it has disconnected if your application is similar to the SDK example (though it would be possible). Do you see the order of events from the central device, a sniffer or the nRF? If not from the nRF, can you enable logging on the nRF side and log the BLE events there? What is the disconnect reason seen from the nRF?

    What is the state of the nRF when you write that the system hangs? Can you check with a debugger? Enabling logging could be useful to understand this as well.

Reply
  • Hi,

    I would be surprised if it starts advertising before it has disconnected if your application is similar to the SDK example (though it would be possible). Do you see the order of events from the central device, a sniffer or the nRF? If not from the nRF, can you enable logging on the nRF side and log the BLE events there? What is the disconnect reason seen from the nRF?

    What is the state of the nRF when you write that the system hangs? Can you check with a debugger? Enabling logging could be useful to understand this as well.

Children
Related