App crashes after manual disconnection from mobile application.

[AthulValsan]

There is a custom bootloader in the flash having a address of 0x27000 immediately after the soft device occur, the bootloader code jumps directly to our beacon application having a flash address of 0x30100. The beacon application works fine.

Then we connected a mobile with the beacon and disconnected. After disconnection we didn't see any beacon broadcast from the device(nrf52833). Please help me to find the reason.    

[Simonr]

Hi

I think we need some more information on what your application actually does upon a disconnect event. What SDK are you using for development, the nRF5 SDK or the nRF Connect SDK?

What happens in your application when the BLE_GAP_EVT_DISCONNECTED or the disconnected() callback is trigged (depending on the SDK you're using)?

 

Best regards,

Simon

[AthulValsan]

hi,

I am developing ibeacon application using nRF5 SDK with nrf52833 board. It will advertise beacon data every 100ms. it supports connection from central device. 

In our case mobile app is central device.

I am connected to my ibeacon using  mobile app. After forceful disconnection from mobile app. our nrf52833 based beacon application disconnected successfully. After few seconds of disconnection i can't see broadcast from beacon. This issue happens when I am combining custom bootloader. Without bootloader there is no issue after forceful disconnection. 

[Simonr]

Hi

By either logging ordebugging, are you able to see what the application does after a disconnection event both with and without a bootloader? Does the application jump to some other part of the code, in the bootloader for example? Normally, the bootloader is set to the "top" addresses of the flash memory instead of straight after the SoftDevice. Could you try moving the application address to 0x27000 instead and the bootloader address a bit higher (0x70000 for example)?

Best regards,

Simon