NRF52832 SDK 17 NUS LESC problem

[DmitrySol]

Hi.

NRF52832 is used as central for connecting with phones as peripheral.
NUS service is used. Lesc is used too.

SDK 17
SoftDevice S132 V7.0.1

I have sometimes crash of application.
I suppose it is crash of softdevice.
there aren't any logs in that time.
Application is just restarting in random times (every 1 - 15 minutes).
Breakpoint on NVIC_SystemReset() doesn't catches too.
Size of stack was increased. So i think perhaps sd has crashed in that time.

How can i find cause of that?
Thanks for any suggestions.

Another strange thing is that after resetting chip in this cases
resolving of private resolved address doesn't work (im_address_resolve).
(it is usually actual for one phone from two. phone1 is connecting successfully, another phone has not resolved address.)

[DmitrySol]

Edvin said:

My advice to you is to try to debug the application. 

Ok. I see.

Edvin said:

have sometimes crash of application.

It is solved. I wrote above. External reset signal on the reset pin was the cause.

Disconnections on old phone is another problem.

Edvin said:

Do you see any disconnect reason on the nRF?

app: BLE_GAP_EVT_DISCONNECTED: 1 , reason=0x13

And the next question:
Could you advice a variant of self testing for factory testing.
I mean testing RF part, accuracy of quartz. Perhaps do you have application note for that?

[Edvin]

DmitrySol said:

Could you advice a variant of self testing for factory testing.
I mean testing RF part, accuracy of quartz. Perhaps do you have application note for that?

 I am no HW expert. I suggest you create a new ticket for this. That way, you don't have to listen to me trying to explain something to you that a colleague told me, which I don't understand myself. 

Does that mean that the disconnect issue still remains? If so, we are back to the disconnect reason 13. I just checked, and actually, if you disconnect from the nRF yourself, you will receive a disconnect reason 0x16 (BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION), and not 0x13 (BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION).

So if you see disconnected reason 0x13 on the nRF, it means that the phone decided to disconnect. Perhaps you can try to connect to it with nRF Connect for Android/iOS, and see if it disconnects, and if so, what the reason (should be printed in the log in nRF Connect for iOS/android).

BR,

Edvin

[DmitrySol]

hi

Edvin said:

 I am no HW expert. I suggest you create a new ticket for this. That way, you don't have to listen to me trying to explain something to you that a colleague told me, which I don't understand myself. 

ok

Edvin said:

So if you see disconnected reason 0x13 on the nRF, it means that the phone decided to disconnect. Perhaps you can try to connect to it with nRF Connect for Android/iOS, and see if it disconnects, and if so, what the reason (should be printed in the log in nRF Connect for iOS/android).

0x13  is used in app code too.

The issue can be closed now.

we'll try to debug phone application later.