Softdevice crashes/disappears after connection speed test

[schef]

Hi guys, i was testing the connection speed from android in conjunction with advertisement time to see what will work better in my production code.

The result were:

• ~3s on 100ms adv time
• ~7s on 300ms adv time

I have some other sensor readings, adc, flash and timer. I was monitoring firmware status over RTT and what happend was:

after 100 connections the device was unvisible but the code on RTT side was further executing. No reboot or any sign of crash.

This happend multiple times. Do you have any suggestions? Is there somekind of watchdog for Softdevice? Or am i totaly looking at the wrong rabbits hole?

Thanks

[FormerMember]

From what I understand, you are measuring the time it takes to connect when a device is advertising.

1) The longer a connection interval is, the longer time it will take for a scanner to pick up the signals. Especially if the scanner is not scanning continuously. It is hard to know if Android is scanning continuously. To create a continuous scanner, you can for example use pc-ble-driver.

2) How does the production code work? Does it disconnect immediately after a connect? And after 100 connections, the devices stop to advertise?

[FormerMember]

Yes, that's true. When the chip is not in debug mode and an error is caught by APP_ERROR_CHECK, the chip should reset.

Could you upload your code so that we can test it here? Which version of the SDK and S132 do you use? If you don't want your code to be public, you can create a new support case on myPage from www.nordicsemi.com, upload the code there, and link to this thread.