NRF52840DK error caused in app_timer2.c (error code 8)

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Nicholas_Nuti — Fri, 06 Mar 2020 18:00:05 GMT

Yeah I do get errors. I guess that comes with rushed development on a mcu I've never used before.

As for the SAADC I have it initialized in the beginning of my program but I can check it. Thank you for the suggestion. I assume the unexpected errors can be overcome with setting custom conditional statements in that ble event handler. I'm going to try it next week.

Yes, I based my project on the very most basic ble template. I forget the name currently but I can check next week. Modifications I've made: saadc, added a ble service, ble characteristic, modified the basic sleep and wake up, hold bonds on wake up, and added a static passkey. This is a very basic implementation but it's rushed. I'm at the point of where Im optimizing for battery and I started a private post. I use SDK 16. Thanks for asking.

Im not used to the... type of documentation and methods of learning how to use this device. Before I was using a scilabs device that had a plethora of documentation and it was great. It seems to be hard to find out the suggested way to do certain things for this nrf device. Might be a personal problem.

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Einar Thorsrud — Tue, 03 Mar 2020 08:06:53 GMT

Hi,

[quote user="Nicholas_Nuti"]Do you have any insight on the previous problem?[/quote]

It seems like you get errors all over the place, and not always with sensible error codes.

Regarding the specific errors you mentioned in the last few posts:

SAADC: Assuming you use SDK 16, there is an assert on line 522 in nrfx_saadc.c that will trigger if you try to sample without having the SAADC initialized. Is that the problem here?
For the peer manager error, it may be needed to debug a bit to understand what is going on. The error is essentially an assert from the peer manger, with an unexpected error.

None of the errors are expected, so I wonder what state your application is in. Have you based it on an example project? Which modifications did you to? What modifications lead to these problems? I you do not have progress, can you upload your full project here so that I can test on my side on a DK? Which SDK version do you use?

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Nicholas_Nuti — Mon, 02 Mar 2020 17:55:42 GMT

Thank you for your help Einar! I very much appreciate it.

Do you have any insight on the previous problem?

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Einar Thorsrud — Mon, 02 Mar 2020 11:16:45 GMT

Hi,

[quote user="Nicholas_Nuti"]Is there a simple way I can simply implement a static passkey?[/quote]

Yes. This is essentially the same way as you implement random passkey, just that you additionally specify the passkey by configuring the SoftDevice accordingly.

This will work smoothly if you take an unmodified GLS example, and just add this snipped at the end of the gap_params_init() function.

    memset(&opt, 0x00, sizeof(opt));
    uint8_t passkey[] = "123456";
    opt.gap_opt.passkey.p_passkey = passkey;
    err_code = sd_ble_opt_set(BLE_GAP_OPT_PASSKEY, &opt);
    APP_ERROR_CHECK(err_code);

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Nicholas_Nuti — Fri, 28 Feb 2020 19:23:26 GMT

I'm really only using this glucose example for the passkey. I don't even need a random passkey; I only need a static passkey. This seems to be more trouble than it's worth. Is there a simple way I can simply implement a static passkey?

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Nicholas_Nuti — Fri, 28 Feb 2020 19:10:44 GMT

New Update on the errors as well. If I disable LESC:

#define SEC_PARAM_LESC 0

and I pair... it seems to work fine for a short time in DEBUG mode. BUT when I go to the battery service and turn on notifications, I get another error from the SAADC:

<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
<error> app: ERROR 3735928559 [Unknown error code] at C:\Nordic\modules\nrfx\drivers\src\nrfx_saadc.c:522
PC at: 0x000320BB
<error> app: End of error report

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Nicholas_Nuti — Fri, 28 Feb 2020 19:03:04 GMT

Oh, I can't believe I didn't have that selected... Thank you so much for your help!

The error code that comes up in the terminal is:

<error> peer_manager_sm: Could not perform security procedure. smd_params_reply() or smd_link_secure() returned NRF_ERROR_INVALID_ADDR. conn_handle: 0
<error> peer_manager_handler: Unexpected fatal error occurred: error: NRF_ERROR_INVALID_ADDR
<error> peer_manager_handler: Asserting.
<error> app: ERROR 16 [NRF_ERROR_INVALID_ADDR] at C:\Nordic\components\ble\peer_manager\peer_manager_handler.c:294
PC at: 0x00039F85
<error> app: End of error report

So it seems to be a connection issue.

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Einar Thorsrud — Fri, 28 Feb 2020 18:54:09 GMT

Hi,

[quote user="Nicholas_Nuti"]Yes, I am based on an application example. I have the settings enabled in the sdk_config, but I guess the insufficient DEBUG feedback another issue for me.[/quote]

Yes. But getting debug logging is very good in this cases, as it typicaly points right at the problem. If you select the Debug build as shown by this image you get it right away:

This does not do much, but it adds DEBUG and DEBUG_NRF to the list of preprocessor definitions (which is what is relevant for logging), and it sets the optimization level to None, so that the behavior you see actually match the code. This is very important for making life easier when debugging.

[quote user="Nicholas_Nuti"]Yes I do have something you could run on an nRF52840DK but I was wondering if there is a way I could send it to you without posting it here? I would consider this program to be "company-sensitive".[/quote]

Yes. You can open a new private case where you upload the code and refer to this thread.

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Nicholas_Nuti — Fri, 28 Feb 2020 18:40:36 GMT

Yes, I am based on an application example. I have the settings enabled in the sdk_config, but I guess the insufficient DEBUG feedback another issue for me.

Yes I do have something you could run on an nRF52840DK but I was wondering if there is a way I could send it to you without posting it here? I would consider this program to be "company-sensitive".

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Einar Thorsrud — Fri, 28 Feb 2020 18:18:32 GMT

Hi,

The call stack does indicate a failure in app_timer implementation, as you write, but it would be good to know more. The fact that only "Fatal error" is printed indicates that you are not building the debug configuration, which has more extensive logging (assuming you are basing your application on an SDK example). Can you select "Debug" from the build configuration drop-down menu, rebuild and test again? What does the log say in that case?

Do you have any code that can reproduce this on a DK that I can run on my side?

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Nicholas_Nuti — Fri, 28 Feb 2020 18:13:33 GMT

Hello!

I understand, for I haven't been able to find out which function returns the error code as well. I have logging and the RTT back-end enabled too but I'm not getting the location of the error. Would the call stack be of any help?

Thank you!

RE: NRF52840DK error caused in app_timer2.c (error code 8)

Einar Thorsrud — Fri, 28 Feb 2020 12:34:50 GMT

Hi,

It is not clear to me which functions return the error code (8 = NRF_ERROR_INVALID_STATE), and the screenshot does not show it. Can you make sure to enable logging and build select "Debug" from the build configuration drop-down? That way the exact location of the error will be printed in the log so that we can know which function returned NRF_ERROR_INVALID_STATE.