System Reset warning

RE: System Reset warning

Jared — Wed, 26 Sep 2018 13:53:20 GMT

A couple of processes is initiated once a connect event is issued. One of them is the update of connection parameters. Disconnecting too quick can therefore cause an error to be thrown. You can try stopping the connection parameter module with ble_conn_params_stop() before you disconnect. I would advise you to continue with using a delay if the error persists.

Jared

RE: System Reset warning

GK — Mon, 24 Sep 2018 09:34:26 GMT

Hi Jared,

Thank you very much for your co-operation and time.

Please find the zip file.

Line number 961 (nrf_delay_ms(250);)is commented now.

With this line commented I am getting GATT ERROR 133 on nRFConnect App.

To solve this I added the delay of 250ms( to make this, please un-comment the line on line number 961).

With this change the GATT ERROR is not coming ( but it comes very rarely), But the system resets sometimes.

Please have a look in to the code and share your comments.

with regards,

Geethadevzone.nordicsemi.com/.../Sieva_5F00_prod1_5F00_wologs.zip

RE: System Reset warning

Jared — Mon, 24 Sep 2018 08:36:05 GMT

Good that you have provided the logs, i will inspect them. Could you also share your entire project with your config file?

Cheers

Jared

RE: System Reset warning

GK — Fri, 21 Sep 2018 10:30:58 GMT

HI Jared,

I am new this nrf sniffer . So I have taken the log 3-4 times.

I am attaching all the 4 logs here.

If you want to be selective on any of the parameters, i can do that.

But please instruct me on how to do that.

Please find the attached logs.

Please let me know if you could get something from the log regarding GAT ERROR 133.

devzone.nordicsemi.com/.../log3.pcapng devzone.nordicsemi.com/.../log4.pcapng devzone.nordicsemi.com/.../5810.log2.pcapng

Please help in analysing the logs and finding the issue.

Thanking you in advance.

with regards,

Geetha

RE: System Reset warning

GK — Fri, 21 Sep 2018 04:45:01 GMT

Hi Jared,

I was trying to get a sniffer log from long time back. I was facing issues with wireshark.

I have made a query in the following thread for that https://devzone.nordicsemi.com/f/nordic-q-a/38641/wireshark-is-not-listing-the-interface-toolbars/149467#149467

I am trying with wireshark 2.4.2 now(as you suggested).

The nrf sniffer I used is from the following link

https://www.nordicsemi.com/eng/nordic/Products/nRF-Sniffer/nRF-Sniffer-v2/65225

"nrf_sniffer_2.0.0-beta-1_51296aa". Is it the correct one to use?

And I am using Windows10 .

Please share your comments.

with regards,

Geetha

RE: System Reset warning

Jared — Wed, 19 Sep 2018 13:38:09 GMT

I saw your other question here, which seems related to this one. Could you provide me with a sniffer log of the event?

Jared

RE: System Reset warning

GK — Wed, 19 Sep 2018 05:14:55 GMT

Hi Jared,

Thank you for your suggestion.

I have done it and I got the following report.

It comes from timer related APIs.

I could not figure it out where to look to solve this issue.

It comes from sd_ble_gap_conn_param_update(). THE ERROR CODE IS 08 which corresponds

to NRF_ERROR_INVALID_STATE.

Is there anything to do with the connection timeout/interval etc?

My code has the following info

#define MIN_CONN_INTERVAL               MSEC_TO_UNITS(500, UNIT_1_25_MS)        /**< Minimum acceptable connection interval (0.5 seconds). */
#define MAX_CONN_INTERVAL               MSEC_TO_UNITS(1000, UNIT_1_25_MS)       /**< Maximum acceptable connection interval (1 second). */
#define SLAVE_LATENCY                   0                                       /**< Slave latency. */
#define CONN_SUP_TIMEOUT                MSEC_TO_UNITS(4000, UNIT_10_MS)         /**< Connection supervisory timeout (4 seconds). */

Is it something we get in return from the App.?

Will you be able to help?

Is it happening due to the immediate call of "sd_ble_gap_disconnect()" from 'populate()' function?

Should I provide some delay before calling "sd_ble_gap_disconnect"?

with regards,

Geetha

RE: System Reset warning

Jared — Tue, 18 Sep 2018 14:11:16 GMT

The program resets because an error is thrown. You should set the build configuration to Debug mode to prevent it from resetting after the error handler is called so you can analyze the reason that causes the error. I recommend that you watch our series on debugging with SEGGER embedded studio: https://www.youtube.com/watch?v=uP8RYgYGRvI

Cheers

Jared