NRF52832 SDK 17 NUS LESC problem

RE: NRF52832 SDK 17 NUS LESC problem

DmitrySol — Mon, 21 Sep 2020 12:49:15 GMT

[quote userid="26071" url="~/f/nordic-q-a/65820/nrf52832-sdk-17-nus-lesc-problem/270062"] 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. [/quote]

[quote userid="26071" url="~/f/nordic-q-a/65820/nrf52832-sdk-17-nus-lesc-problem/270062"]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).[/quote]

0x13 is used in app code too.

The issue can be closed now.

we'll try to debug phone application later.

RE: NRF52832 SDK 17 NUS LESC problem

Edvin — Thu, 17 Sep 2020 11:40:26 GMT

[quote user="DmitrySol"]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?[/quote]

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

RE: NRF52832 SDK 17 NUS LESC problem

DmitrySol — Thu, 17 Sep 2020 09:06:08 GMT

[quote userid="26071" url="~/f/nordic-q-a/65820/nrf52832-sdk-17-nus-lesc-problem/270001"]My advice to you is to try to debug the application. [/quote]

Ok. I see.

[quote userid="26071" url="~/f/nordic-q-a/65820/nrf52832-sdk-17-nus-lesc-problem/270001"] have sometimes crash of application.[/quote]

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

Disconnections on old phone is another problem.

[quote userid="26071" url="~/f/nordic-q-a/65820/nrf52832-sdk-17-nus-lesc-problem/270001"]Do you see any disconnect reason on the nRF?[/quote]

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?

RE: NRF52832 SDK 17 NUS LESC problem

Edvin — Thu, 17 Sep 2020 08:10:53 GMT

Hello,

It is not possible to filter on a central device, unfortunately.

I assume you want to use the sniffer trace to figure out what's wrong. Please be aware that when the link is encrypted using LESC, the sniffer will not be able to sniff the connection anyway, since sniffer devices can't keep up with LESC, because of it's nature. It could keep up for some time (with undecrypted packages), but eventually it can't keep up with the channel switching, so it will loose the connection.

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

[quote user=""]I have sometimes crash of application.
I suppose it is crash of softdevice.
there aren't any logs in that time.[/quote]

Do you have logging enabled in your application at all? Are you sure it doesn't say something like "fatal error"?

Is there some way for me to replicate this on a DK?

Is it the nRF that crashes? What do you see on the phone? Does it just disconnect? Have you tried connecting via nRF Connect for Android/iOS? Does it give a disconnect reason?

Do you see any disconnect reason on the nRF? Does the disconnect event occur at all?

Best regards,

Edvin

RE: NRF52832 SDK 17 NUS LESC problem

DmitrySol — Wed, 16 Sep 2020 12:38:54 GMT

Good day! Edvin.

Thanks for your helping.

The matter is - when disconnections appears, that is cycling every few seconds.
So I can't catch address in list of wireshark.

Could I set address of central device as not private random (for debugging). and use it for filtering in wireshark?
If is it possible, how can i set that?

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?

Thanks!

RE: NRF52832 SDK 17 NUS LESC problem

Edvin — Tue, 15 Sep 2020 13:55:38 GMT

[quote user="DmitrySol"]I try to sniff rf logs by wireshark.
But i don't understand how to setup filter to catch interesting devices.
I enter passkey
But addresses are changing on every connect (they are random)[/quote]

You need to select the advertising device from this dropdown menu:

In IAR you disable optimization here:

RE: NRF52832 SDK 17 NUS LESC problem

DmitrySol — Tue, 15 Sep 2020 12:12:04 GMT

I use IAR 8

Optimisation is switched off now.

Disconnections are observed periodically.
Connection is set up. Data exchange is processed some seconds. And after that disconnect is following:
<info> app: ble_nus_c_evt_handler(): conn_handle=0x2000, evt_type=0x2
<info> app: BLE_GAP_EVT_DISCONNECTED: 1 , reason=0x13

break points on sd_ble_gap_disconnect doesn't catch.

Is it means that phone makes disconnect?

I try to sniff rf logs by wireshark.
But i don't understand how to setup filter to catch interesting devices.
I enter passkey
But addresses are changing on every connect (they are random)

RE: NRF52832 SDK 17 NUS LESC problem

Edvin — Tue, 15 Sep 2020 08:48:12 GMT

Breakpoints should catch, but the order of things may behave weird if optimization is enabled. Try to disable it. Let me knoe what IDE you are using if you are not sure how to do this.

Another thing with breakpoints: If you have hit a breakpoint, you may try to step a few steps, but the softdevice will after a while realize that it missed some time critical events, and assert. So basically, this means that you need to reset the application after a breakpoint is hit.

BR,

Edvin

RE: NRF52832 SDK 17 NUS LESC problem

DmitrySol — Tue, 15 Sep 2020 05:47:33 GMT

Hello!

Breakpoint at this place is catched sometimes.

case BLE_GATTC_EVT_TIMEOUT:
// Disconnect on GATT Client timeout event.
NRF_LOG_INFO("BLE_GATTC_EVT_TIMEOUT: %d ", conn_handle);
err_code = sd_ble_gap_disconnect(p_ble_evt->evt.gattc_evt.conn_handle,
BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
APP_ERROR_CHECK(err_code);
break;

but it is rarely.
So i hesitate that it is cause.

Breakpoints work strange sometimes.
May be so that breakpoints catch not all times?

RE: NRF52832 SDK 17 NUS LESC problem

Edvin — Mon, 14 Sep 2020 13:54:34 GMT

You still don't know who initiated the disconnect, but either the nRF or the phone decided to disconnect. Check all the places in your application that can call sd_ble_gap_disconnect, and try to set breakpoints. Alternatively, you can try to capture a sniffer trace and see which device that sends the disconnect packet.

RE: NRF52832 SDK 17 NUS LESC problem

DmitrySol — Mon, 14 Sep 2020 12:42:31 GMT

Hi!

DEBUG was present in preprocessor directives.
Reset problem is solved now. (It is described above)

I have another question.
When chip as central is connected with phone ( as peripheral)
disconnection appears sometimes:

<info> app: ble_nus_c_evt_handler(): conn_handle=0x0, evt_type=0x2
<info> app: BLE_NUS_C_EVT_DISCONNECTED: 0x0
<info> app: BLE_GAP_EVT_DISCONNECTED: 1 , reason=0x13

0x13 means:
#define BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION 0x13 /**< Remote User Terminated Connection. */

It happens on old phone (BQ-5001L ble 4.0).
I seem that another phone (more modern) doesn't has this issue.

What may be caused of that disconnection?

RE: NRF52832 SDK 17 NUS LESC problem

Edvin — Fri, 11 Sep 2020 14:11:14 GMT

Try to add DEBUG to your preprocessor definitions, and monitor the log.

If you aren't sure how to add preprocessor definitions, please let me know what IDE you are using. Segger Embedded Studio? Keil?

If you are not sure how to monitor or enable the log, let me know.

Best regards,

Edvin

RE: NRF52832 SDK 17 NUS LESC problem

DmitrySol — Fri, 11 Sep 2020 12:10:36 GMT

I am sorry.

It was reset from watchdog by host CPU.

I try now without lesc.

if It will be all right, than I will be testing lesc again.

Thanks.