ASSERTION FAIL [err == 0] and Error writing variable 1 (err: -116)

RE: ASSERTION FAIL [err == 0] and Error writing variable 1 (err: -116)

Zihao — Tue, 18 Jun 2024 02:56:26 GMT

Sure, thank you. That's probably because interrupt operations are not recommended to occur simultaneously with NVS write operations. I think there might be a proper solution that allows NCS to handle this time-sensitive procedure well. After directly removing the assert statement, my program seems to be running normally.

RE: ASSERTION FAIL [err == 0] and Error writing variable 1 (err: -116)

Elfving — Mon, 17 Jun 2024 13:50:47 GMT

Hello,

[quote user=""]I understand that error -116 indicates a certificate/key issue through this issue. However, I have not configured any certificates or keys. Therefore, I suspect this issue might be related to the scanning process. The scan_timeout callback function is triggered while the central device is still scanning. Interestingly, I can successfully write the variable when the central device is connected.[/quote]

You can find what all of these error codes mean in errno.h. For instance here. -116 allways means means "Connection timed out". In the context of the issue you linked to, that typically stems from certificate

or key issues, though I do not think that is the issue here.

My immediate idea on this issue is that it is related to the time-sensitive nature of this procedure. You should make sure that you do other things (ie. write to NVS) in a workqueue so that it won't hinder the connection.

Regards,

Elfving

RE: ASSERTION FAIL [err == 0] and Error writing variable 1 (err: -116)

Zihao — Thu, 13 Jun 2024 10:18:51 GMT

OK, I tried to delete the ASSERTION in WEST_TOPDIR/zephyr/subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c:476. After that, my project worked fine.

The ASSERTION is:

	if (diff > HAL_TICKER_US_TO_TICKS(EVENT_OVERHEAD_START_US)) {
		/* TODO: for Low Latency Feature with Advanced XTAL feature.
		 * 1. Release retained HF clock.
		 * 2. Advance the radio event to accommodate normal prepare
		 *    duration.
		 * 3. Increase the preempt to start ticks for future events.
		 */
		
		/*
		LL_ASSERT_MSG(false, "%s: Actual EVENT_OVERHEAD_START_US = %u",
			      __func__, HAL_TICKER_TICKS_TO_US(diff));
		*/
		
		return 1U;
	}

However, I'm not sure if this operation has any additional drawbacks. In my development experience, assertions are sometimes left in release versions, and if such assertions are not satisfied, the consequences can be fatal.

RE: ASSERTION FAIL [err == 0] and Error writing variable 1 (err: -116)

Zihao — Thu, 13 Jun 2024 07:46:17 GMT

More precise. my issue is why can't I update a variable in NVS when the k_timer is triggered？

I know it's not recommended to call a Read/Write function in a k_timer event call back function. So I defined a variable TIMEOUT_FLAG = false.

When the k_timer event occur, the TIMEOUT_FLAG well be set to true.

And in my main function:

while(1){

if(TIMEOUT_FLAG){

Write_to_NVS();

k_sleep(K_MSEC(500));

sys_reboot(0);

}

k_sleep(K_MSEC(500));

}

But the Errors still exist.

Scan timeout, no connection established. TIMEOUT...
ASSERTION FAIL [0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c:476
	lll_preempt_calc: Actual EVENT_OVERHEAD_START_US = 2990
[00:00:15.302,795] [1;31m<err> os: esf_dump: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00000001[0m
[00:00:15.302,825] [1;31m<err> os: esf_dump: r3/a4:  0x00020c29 r12/ip:  0x00000000 r14/lr:  0x00001f7b[0m
[00:00:15.302,825] [1;31m<err> os: esf_dump:  xpsr:  0x41000028[0m
[00:00:15.302,856] [1;31m<err> os: esf_dump: Faulting instruction address (r15/pc): 0x00001f86[0m
[00:00:15.302,886] [1;31m<err> os: z_fatal_error: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0[0m
[00:00:15.302,886] [1;31m<err> os: z_fatal_error: Fault during interrupt handling
[0m
[00:00:15.302,947] [1;31m<err> os: z_fatal_error: Current thread: 0x200016b0 (unknown)[0m
[00:00:15.603,393] [1;31m<err> fatal_error: k_sys_fatal_error_handler: Resetting system[0m
*** Booting Zephyr OS build v3.2.99-ncs1 ***