[nRF Connect SDK](Urgent)Assert after DFU via OTA

[Tim Hwang]

Target nRF52832(nrf52dk_nrf52832)
SDK NCS v1.9.1

Normally OTA works well.
I found unexpected assert after OTA is done.
Can you please review my assert code with my elf.

00> I: SoftDevice Controller build revision:
00> I: 0e e7 c5 66 67 18 3c ac |...fg.<.
00> I: b3 d2 cc 81 a3 dc f1 c0 |........
00> I: c0 36 02 22 |.6."
00> I: No ID address. App must call settings_load()
00> E: ***** MPU FAULT *****
00> E: Stacking error (context area might be not valid)
00> E: Data Access Violation
00> E: MMFAR Address: 0x20006190
00> E: r0/a1: 0x00000000 r1/a2: 0x000347f9 r2/a3: 0x00000000
00> E: r3/a4: 0x000347f9 r12/ip: 0xec7ff16f r14/lr: 0x29302810
00> E: xpsr: 0x38132000
00> E: Faulting instruction address (r15/pc): 0xf2e63a6d
00> E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
00> E: Current thread: 0x20002350 (unknown)
00> E: Resetting system

6165.build.7z

[Tim Hwang]

Aug 08- 2022

Hello. 

In my test I found I already had ring buffer(provided by zephyr) assert issue.
Recently I update NCS version to 2.0.0.  And it looks good in my test.
I found lots of changes. so please review my stack size is affordable in my attached config.
It it is fine, I will use NCS2.0 instead.

My SW	NCS	OTA assert	Ringbuffer test	Result
V1.3.6:	1.9.1	NG(sometime happened)	assert (within 48 hours)	NG
V1.3.7	1.9.1	Increase stack size So far so good	assert (within 48 hours)	NG
V1.4.0	2.0	Increase stack size So far so good	No Ringbuffer assert (so far so good)	Need your review

NCS2.0_build.7z

[Simon]

Tim Hwang said:

I found lots of changes. so please review my stack size is affordable in my attached config.
It it is fine, I will use NCS2.0 instead.

It is hard to comment on the stack sizes just by looking at it. As mentioned in Memory footprint Optimizations-->General recommendations, you can analyze the stack usage in each thread of your application by using the Thread analyzer. Reduce the stack sizes where possible.

Best regards,

Simon