ENVIRONMENT
- nRF54L15 DK (CS initiator) + nRF54L15 tags (CS reflectors, 2 antennas),
3 reflectors connected concurrently
- NCS v3.4.0 (nrf @ 9955305560, SDC from that release), Zephyr v4.4.0-bf801e4e3d19
- Application: fork of nrf/samples/bluetooth/channel_sounding/ras_initiator with
multi-anchor support (BT_MAX_CONN=3), 2 antenna paths (A1_B2), mode-2 main /
mode-1 sub, ACL interval 100 ms, procedure interval 5,
CONFIG_BT_CTLR_SDC_CONN_EVENT_EXTEND_DEFAULT=n
SUMMARY
Under sustained Channel Sounding stress (three concurrent CS links, one of them
at the reception limit around -85..-95 dBm, plus periodic connect/disconnect
cycles), the SoftDevice Controller asserts and takes the system down (hard
fault -> reset). We observe roughly one assert every 20-30 minutes, in three
distinct trigger contexts:
1. "SoftDevice Controller ASSERT: 23, 587" -- fires 100-200 ms after the host
calls bt_conn_disconnect() on a CS link whose procedures are degraded
(streams of "All subevents in ranging counter N were aborted", or a CS
Procedure Enable/Disable whose Complete event never arrived). Also seen
~150 ms after disconnecting three CS links back-to-back, and once during CS
setup (right after applying procedure parameters) of a freshly connected
reflector.
2. "SoftDevice Controller ASSERT: 135, 301" -- fires WITHOUT any disconnect,
during ongoing ranging on a degraded link, shortly after a connection
parameter update (interval 100 ms -> 102.5 ms; CS procedures were disabled
with confirmed Complete event before the update and re-enabled after).
File 135 appears to be the module documented in sdc_asserts.h as
"CS results encoding failed" (documented entry is 135/261).
3. The same 23/587 assert occurred four times during real drive recordings
(17 rosbags, ~57 min total) before we had console capture -- reset reason
RESETREAS=SOFTWARE each time.
Host-side mitigation we already applied (disable CS procedures with confirmed
Complete event, then a 500 ms grace period, then disconnect) protects the paths
it covers (more than 120 protected disconnects without assert in a 2 h run),
but the asserts then surface in the remaining contexts (multiple disconnects in
a row, plain ranging, CS setup) -- so this does not look fixable from the host
side.
The assert IDs are identical across two different application builds; only the
reported PC/LR differ with the changed code layout (0x00033826 vs 0x000338e2),
so this is not specific to one image.
RELATION TO KNOWN ISSUES (checked before filing)
- We are on NCS v3.4.0, so the CS assert fixes shipped with it (DRGN-28736,
DRGN-28655, DRGN-27705) are already included in our build.
- The context of ASSERT 135,301 resembles the DRGN-28655 mechanism (results
generated faster than consumed): in the seconds before each 135,301 the
application logs thousands of "Dropped subevent results. Waiting for ranging
data from peer." messages (6000+ in a 2 h run) on the degraded link, i.e.
local subevent results keep arriving while peer data via RAS lags behind.
- We are aware of DevZone Q&A 118844 stating that Channel Sounding is primarily
qualified for single links. Our use case (vehicle localization seed) requires
three concurrent CS links on the initiator; this report is meant as concrete
field/stress data from exactly that territory.
REPRODUCTION (automated, minutes to hours)
- 1 initiator (DK), 3 reflectors; place ONE reflector at the reception limit
(-85..-95 dBm advertising RSSI, e.g. wrapped in foil).
- Loop: 45-120 s of ranging, then disconnect all three links, 10 s pause,
reconnect (we drive this via a UART command channel; equivalent to repeated
bt_conn_disconnect + re-scan/connect/CS setup).
- Expected within ~30-60 min: one of the asserts above. We can share the exact
application and the driving script on request.
FAULT DUMPS
See attached log file (nordic-bugreport-anhang.log): four excerpts, each with
~20 lines of application log context followed by the full register dump.
Line format: host epoch timestamp, then channel tag -- "D" is the application
data UART (NMEA-style lines), "L" is the Zephyr console.
Excerpt 1: ASSERT 23,587 after disconnect of a degraded CS link
Excerpt 2: ASSERT 23,587 right after disconnecting three CS links in a row
Excerpt 3: ASSERT 135,301 during ongoing ranging, no disconnect involved
Excerpt 4: ASSERT 23,587 during CS setup of a fresh connection
POSSIBLY RELATED
We have separately documented a state where, after a CS initiator disappears
abruptly (power loss mid-procedure), the reflector's link timers freeze
entirely -- supervision timeout, LL response timeout and even host-initiated
termination are all dead (verified via debugger; only a reboot recovers).
Happy to file that separately if preferred.
QUESTIONS
1. What do asserts 23/587 and 135/301 mean, and are they known issues in the
v3.4.0 SDC?
2. Is there a recommended sequence for tearing down or parameter-updating
connections with active or degraded CS procedures that avoids this? (We
already disable procedures and wait for the Complete event, plus a grace
period on timeout -- the asserts then surface in other contexts, including
plain ranging without any host action.)
3. Is a fix available or planned in a newer SDC? (We did not find a matching
entry in the main-branch changelog.)
4. Given the single-link qualification status of CS (Q&A 118844): is
multi-link CS on the initiator expected to become qualified, or should we
plan for cyclic single-link ranging as the supported operating mode?
5. Regarding the result backpressure on degraded links: is there a recommended
way to throttle local subevent result generation (short of increasing the
procedure interval) when the peer's RAS data lags?
=== Excerpt 1: ASSERT 23,587 after watchdog disconnect of a degraded CS link === === (initiator log; 'D' = data UART with $-lines, 'L' = console; epoch timestamps) === 1787648010.856 D $CSR,C2:28:69:29:B7:25,8.197,10.235,18,11.254,8.197,1,0,-71,,94,68,0,47366566,128,1,1*71 1787648010.863 D $CSR,C2:28:69:29:B7:25,7.612,,18,10.323,7.612,1,1,-71,,94,68,0,47366566,128,1,1*6B 1787648010.929 D $CSR,DF:D2:DF:DA:82:8C,7.026,15.032,16,12.380,7.026,1,0,-83,,93,67,0,47366638,153,1,2*79 1787648010.937 D $CSR,DF:D2:DF:DA:82:8C,12.296,,16,14.727,12.296,1,1,-83,,88,64,0,47366638,153,1,2*65 1787648011.009 L [00:17:00.302,294] <wrn> app_main: All subevents in ranging counter 83 were aborted 1787648011.219 L [00:17:00.512,259] <wrn> app_main: All subevents in ranging counter 154 were aborted 1787648011.356 D $CSR,C2:28:69:29:B7:25,8.490,11.601,19,11.562,8.490,1,0,-70,,98,71,0,47367066,129,1,1*70 1787648011.363 D $CSR,C2:28:69:29:B7:25,8.783,,19,10.387,8.783,1,1,-70,,98,71,0,47367066,129,1,1*64 1787648011.509 L [00:17:00.802,293] <wrn> app_main: All subevents in ranging counter 84 were aborted 1787648011.856 D $CSR,C2:28:69:29:B7:25,8.490,11.734,18,11.598,8.490,1,0,-69,,100,72,0,47367566,130,1,1*45 1787648011.864 D $CSR,C2:28:69:29:B7:25,7.905,,18,10.453,7.905,1,1,-69,,100,72,0,47367566,130,1,1*5D 1787648012.009 L [00:17:01.302,294] <wrn> app_main: All subevents in ranging counter 85 were aborted 1787648012.172 L [00:17:01.464,834] <inf> app_main: Dropped subevent results. Waiting for ranging data from peer. 1787648012.223 D $CSR,DF:D2:DF:DA:82:8C,,1.124,1,,,1,0,-76,,75,3,0,47367639,155,1,2*5C 1787648012.355 D $CSR,C2:28:69:29:B7:25,8.490,10.559,18,11.200,8.490,1,0,-70,,94,56,0,47368063,131,1,1*77 1787648012.362 D $CSR,C2:28:69:29:B7:25,8.490,,18,10.182,8.490,1,1,-70,,94,56,0,47368063,131,1,1*68 1787648012.430 L [00:17:01.718,685] <inf> app_main: Ranging data dropped as peer ranging counter doesn't match local ranging data counter. (peer: 156, local: 155) 1787648012.509 L [00:17:01.802,293] <wrn> app_main: All subevents in ranging counter 86 were aborted 1787648012.646 L [00:17:01.939,756] <wrn> app_main: All subevents in ranging counter 132 were aborted 1787648013.009 L [00:17:02.302,294] <wrn> app_main: All subevents in ranging counter 87 were aborted 1787648013.127 D $CSR,DF:D2:DF:DA:82:8C,7.026,17.482,16,12.194,7.026,1,0,-82,,93,56,0,47368636,157,1,2*74 1787648013.135 D $CSR,DF:D2:DF:DA:82:8C,12.589,,16,14.759,12.589,1,1,-82,,93,56,0,47368636,157,1,2*62 1787648013.428 D $CSR,DF:D2:DF:DA:82:8C,7.026,11.777,15,12.035,7.026,1,0,-81,,84,61,0,47369139,158,1,2*75 1787648013.435 D $CSR,DF:D2:DF:DA:82:8C,12.589,,15,14.842,12.589,1,1,-81,,81,59,0,47369139,158,1,2*6D 1787648013.609 L [00:17:02.902,294] <wrn> app_main: All subevents in ranging counter 88 were aborted 1787648013.928 D $CSR,DF:D2:DF:DA:82:8C,7.026,17.548,15,12.140,7.026,1,0,-81,,94,68,0,47369639,159,1,2*70 1787648013.935 D $CSR,DF:D2:DF:DA:82:8C,12.589,,15,14.686,12.589,1,1,-81,,93,67,0,47369639,159,1,2*63 1787648014.009 L [00:17:03.302,294] <wrn> app_main: All subevents in ranging counter 89 were aborted 1787648014.041 L [00:17:03.332,162] <wrn> app_main: D8:33:78:57:75:C3 liefert weiter nichts — trenne (3. Mal, Hungerrunde 3) 1787648014.209 L [00:17:03.502,598] <err> bt_sdc_hci_driver: SoftDevice Controller ASSERT: 23, 587 1787648014.213 L [00:17:03.502,613] <err> os: ***** HARD FAULT ***** 1787648014.219 L [00:17:03.502,619] <err> os: Fault escalation (see below) 1787648014.224 L [00:17:03.502,624] <err> os: ARCH_EXCEPT with reason 3 1787648014.224 L 1787648014.231 L [00:17:03.502,637] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x2000add0 1787648014.239 L [00:17:03.502,645] <err> os: r3/a4: 0x00000003 r12/ip: 0x00000000 r14/lr: 0x00038e41 1787648014.243 L [00:17:03.502,650] <err> os: xpsr: 0x01000000 1787648014.253 L [00:17:03.502,659] <err> os: s[ 0]: 0x0000024b s[ 1]: 0x00003332 s[ 2]: 0x00000000 s[ 3]: 0x00000000 1787648014.262 L [00:17:03.502,667] <err> os: s[ 4]: 0x000337cd s[ 5]: 0x00000000 s[ 6]: 0x20001420 s[ 7]: 0x0000089d 1787648014.272 L [00:17:03.502,676] <err> os: s[ 8]: 0x00000017 s[ 9]: 0x00003332 s[10]: 0x200057c4 s[11]: 0xffff8041 1787648014.281 L [00:17:03.502,684] <err> os: s[12]: 0x2001542c s[13]: 0x00001187 s[14]: 0x0000d959 s[15]: 0x0000d977 1787648014.285 L [00:17:03.502,689] <err> os: fpscr: 0x20008364 1787648014.292 L [00:17:03.502,694] <err> os: Faulting instruction address (r15/pc): 0x00033826 1787648014.299 L [00:17:03.502,710] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0 1787648014.305 L [00:17:03.502,724] <err> os: Current thread: 0x2000add0 (unknown) 1787648014.358 D $CSS,SEEK,0,0,dev,2,02*1C 1787648014.364 L [00:17:03.605,666] <err> fatal_error: Resetting system *** Booting nRF Connect SDK v3.4.0-99553055607b *** 1787648014.368 L *** Using Zephyr OS v4.4.0-bf801e4e3d19 *** === Excerpt 2: ASSERT 23,587 right after disconnecting three CS links (STANDBY) === 1787652383.842 D $CSR,D8:33:78:57:75:C3,7.612,,15,9.111,7.612,1,1,-64,,96,59,0,831404,169,1,3*5F 1787652383.859 D $CSR,DF:D2:DF:DA:82:8C,6.441,15.659,15,12.412,6.441,1,0,-79,,84,49,0,831521,169,1,2*7A 1787652383.866 D $CSR,DF:D2:DF:DA:82:8C,12.296,,15,14.128,12.296,1,1,-79,,100,58,0,831521,169,1,2*5C 1787652383.868 L [00:18:18.201,101] <wrn> app_main: All subevents in ranging counter 149 were aborted 1787652384.032 L [00:18:18.393,555] <wrn> app_main: All subevents in ranging counter 170 were aborted 1787652384.149 L [00:18:18.511,060] <wrn> app_main: All subevents in ranging counter 170 were aborted 1787652384.240 D $CSR,C2:28:69:29:B7:25,,15.027,2,,,1,0,-68,,100,13,0,831915,150,1,1*66 1787652384.539 L [00:18:18.901,059] <wrn> app_main: All subevents in ranging counter 151 were aborted 1787652384.725 > STANDBY 1787652384.744 D $ACK,1015,STANDBY*1B 1787652384.747 D $CSS,STANDBY,3,832,dev,0,02*5B 1787652384.753 L [00:18:19.112,538] <inf> app_main: STANDBY: gebe D8:33:78:57:75:C3 frei 1787652384.759 L [00:18:19.112,709] <inf> app_main: STANDBY: gebe DF:D2:DF:DA:82:8C frei 1787652384.766 L [00:18:19.112,870] <inf> app_main: STANDBY: gebe C2:28:69:29:B7:25 frei 1787652384.771 L [00:18:19.113,021] <inf> app_main: STANDBY (Lease 600 s) 1787652384.940 L [00:18:19.301,469] <err> bt_sdc_hci_driver: SoftDevice Controller ASSERT: 23, 587 1787652384.944 L [00:18:19.301,483] <err> os: ***** HARD FAULT ***** 1787652384.950 L [00:18:19.301,488] <err> os: Fault escalation (see below) 1787652384.954 L [00:18:19.301,494] <err> os: ARCH_EXCEPT with reason 3 1787652384.954 L 1787652384.962 L [00:18:19.301,507] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x2000add0 1787652384.970 L [00:18:19.301,515] <err> os: r3/a4: 0x00000003 r12/ip: 0x00000000 r14/lr: 0x00038efd 1787652384.974 L [00:18:19.301,520] <err> os: xpsr: 0x01000000 1787652384.984 L [00:18:19.301,528] <err> os: s[ 0]: 0x0000024b s[ 1]: 0x00003332 s[ 2]: 0x00000000 s[ 3]: 0x00000000 1787652384.993 L [00:18:19.301,537] <err> os: s[ 4]: 0x00033889 s[ 5]: 0x00000000 s[ 6]: 0x20001420 s[ 7]: 0x0000089d 1787652385.002 L [00:18:19.301,545] <err> os: s[ 8]: 0x00000017 s[ 9]: 0x00003332 s[10]: 0x200057c4 s[11]: 0xffff8026 1787652385.012 L [00:18:19.301,553] <err> os: s[12]: 0x20015438 s[13]: 0x00001187 s[14]: 0x0000d959 s[15]: 0x0000d977 1787652385.016 L [00:18:19.301,558] <err> os: fpscr: 0x20008364 1787652385.023 L [00:18:19.301,562] <err> os: Faulting instruction address (r15/pc): 0x000338e2 1787652385.030 L [00:18:19.301,579] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0 1787652385.035 L [00:18:19.301,593] <err> os: Current thread: 0x2000add0 (unknown) 1787652385.090 D $CSS,SEEK,0,0,dev,1,02*1F 1787652385.096 L [00:18:19.404,489] <err> fatal_error: Resetting system *** Booting nRF Connect SDK v3.4.0-99553055607b *** === Excerpt 3: ASSERT 135,301 during ongoing ranging, NO disconnect involved === === (conn param update 100->102.5 ms ~2.5 s earlier, CS procedures were disable/re-enabled around it) === 1787657142.758 D $CSR,DF:D2:DF:DA:82:8C,15.224,,15,17.723,15.224,1,1,-87,,56,41,0,592931,82,1,2*54 1787657143.041 L [00:26:02.472,754] <wrn> app_main: All subevents in ranging counter 83 were aborted 1787657143.331 L [00:26:02.765,281] <inf> app_main: CS procedures enabled: 1787657143.333 L - config ID: 0 1787657143.336 L - antenna configuration index: 4 1787657143.338 L - TX power: 0 dbm 1787657143.340 L - subevent length: 16000 us 1787657143.342 L - subevents per event: 1 1787657143.344 L - subevent interval: 0 1787657143.346 L - event interval: 2 1787657143.348 L - procedure interval: 5 1787657143.350 L - procedure count: 0 1787657143.353 L - maximum procedure length: 640 1787657143.364 L [00:26:02.792,078] <inf> app_main: C2:28:69:29:B7:25: ACL zurueck auf 100 ms — Ankerpunkt wird umgesetzt (Versuch 2) 1787657143.432 L [00:26:02.862,319] <inf> app_main: Dropped subevent results. Waiting for ranging data from peer. 1787657143.440 L [00:26:02.862,820] <wrn> app_main: All subevents in ranging counter 65 were aborted 1787657143.637 L [00:26:03.062,854] <inf> app_main: Ranging data dropped as peer ranging counter doesn't match local ranging data counter. (peer: 66, local: 65) 1787657143.829 L [00:26:03.262,675] <inf> app_main: CS procedures disabled. 1787657144.341 L [00:26:03.772,787] <wrn> app_main: All subevents in ranging counter 85 were aborted 1787657144.535 L [00:26:03.964,813] <inf> app_main: Dropped subevent results. Waiting for ranging data from peer. 1787657144.633 L [00:26:04.062,810] <inf> app_main: Ranging: ACL 102 ms, Prozedur-Intervall 5 (512 ms), Antennen 0x04 1787657144.738 D $CSR,C2:28:69:29:B7:25,6.654,12.170,16,10.338,6.654,1,0,-71,,100,72,0,594423,61,1,1*76 1787657144.746 D $CSR,C2:28:69:29:B7:25,5.371,,16,10.259,5.371,1,1,-71,,100,72,0,594423,61,1,1*6A 1787657144.758 L [00:26:04.168,509] <inf> app_main: Ranging data dropped as peer ranging counter doesn't match local ranging data counter. (peer: 62, local: 61) 1787657144.845 D $CSR,DF:D2:DF:DA:82:8C,14.583,20.823,12,20.725,14.583,1,0,-87,,97,70,0,594931,86,1,2*48 1787657144.852 D $CSR,DF:D2:DF:DA:82:8C,14.638,,12,19.800,14.638,1,1,-87,,51,37,0,594931,86,1,2*57 1787657145.041 L [00:26:04.472,782] <wrn> app_main: All subevents in ranging counter 87 were aborted 1787657145.095 D $CSS,SEEK,3,595,dev,3,02*17 1787657145.241 L [00:26:04.672,231] <err> bt_sdc_hci_driver: SoftDevice Controller ASSERT: 135, 301 1787657145.245 L [00:26:04.672,245] <err> os: ***** HARD FAULT ***** 1787657145.251 L [00:26:04.672,251] <err> os: Fault escalation (see below) 1787657145.255 L [00:26:04.672,256] <err> os: ARCH_EXCEPT with reason 3 1787657145.256 L 1787657145.263 L [00:26:04.672,269] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x2000add0 1787657145.271 L [00:26:04.672,277] <err> os: r3/a4: 0x00000003 r12/ip: 0x2001543c r14/lr: 0x00038efd 1787657145.275 L [00:26:04.672,282] <err> os: xpsr: 0x01000000 1787657145.285 L [00:26:04.672,291] <err> os: s[ 0]: 0x0000012d s[ 1]: 0x00353331 s[ 2]: 0x00000000 s[ 3]: 0x00000000 1787657145.294 L [00:26:04.672,299] <err> os: s[ 4]: 0x00033889 s[ 5]: 0x00000000 s[ 6]: 0x200074ca s[ 7]: 0x0000089d 1787657145.304 L [00:26:04.672,307] <err> os: s[ 8]: 0x00000087 s[ 9]: 0x00353331 s[10]: 0x00000012 s[11]: 0x00000000 1787657145.313 L [00:26:04.672,316] <err> os: s[12]: 0x20015438 s[13]: 0x0000d96d s[14]: 0x20006eac s[15]: 0x20015438 1787657145.317 L [00:26:04.672,321] <err> os: fpscr: 0x20006eac 1787657145.324 L [00:26:04.672,325] <err> os: Faulting instruction address (r15/pc): 0x000338e2 1787657145.331 L [00:26:04.672,341] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0 1787657145.337 L [00:26:04.672,356] <err> os: Current thread: 0x2000add0 (unknown) 1787657145.393 D $CSS,SEEK,0,0,dev,4,02*1A 1787657145.399 L [00:26:04.775,774] <err> fatal_error: Resetting system *** Booting nRF Connect SDK v3.4.0-99553055607b *** === Excerpt 4: ASSERT 23,587 during CS setup of a fresh connection === 1787658915.684 D $CSR,C2:28:69:29:B7:25,6.787,10.405,17,10.193,6.787,1,0,-71,,100,60,0,1346612,103,1,1*7F 1787658915.691 D $CSR,C2:28:69:29:B7:25,5.514,,17,9.597,5.514,1,1,-71,,98,59,0,1346612,103,1,1*62 1787658915.697 D $CSR,DF:D2:DF:DA:82:8C,,16.489,4,,,1,0,-85,,100,11,0,1346627,111,1,2*5F 1787658915.951 L [00:55:35.392,650] <inf> app_main: Dropped subevent results. Waiting for ranging data from peer. 1787658915.975 L [00:55:35.417,849] <wrn> app_main: All subevents in ranging counter 104 were aborted 1787658916.123 L [00:55:35.560,346] <inf> app_main: Ranging data dropped as peer ranging counter doesn't match local ranging data counter. (peer: 119, local: 120) 1787658916.197 D $CSR,DF:D2:DF:DA:82:8C,3.513,24.125,9,18.525,3.513,1,0,-86,,73,53,0,1347127,112,1,2*70 1787658916.204 D $CSR,DF:D2:DF:DA:82:8C,2.635,,9,14.747,2.635,1,1,-86,,59,43,0,1347127,112,1,2*6C 1787658916.688 D $CSR,DF:D2:DF:DA:82:8C,,18.937,3,,,1,0,-85,,90,10,0,1347627,113,1,2*64 1787658916.738 L [00:55:36.175,378] <inf> app_main: Ranging data dropped as peer ranging counter doesn't match local ranging data counter. (peer: 120, local: 122) 1787658916.936 L [00:55:36.380,766] <wrn> app_main: Procedure 126 aborted 1787658916.987 L [00:55:36.430,351] <wrn> app_main: All subevents in ranging counter 114 were aborted 1787658917.038 L [00:55:36.482,740] <inf> app_main: CS procedures disabled. 1787658917.429 L [00:55:36.870,364] <inf> app_main: Dropped subevent results. Waiting for ranging data from peer. 1787658917.479 D $CSR,C2:28:69:29:B7:25,6.789,12.326,15,10.339,6.789,1,0,-71,,100,61,0,1348112,106,1,1*76 1787658917.487 D $CSR,C2:28:69:29:B7:25,5.467,,15,10.052,5.467,1,1,-71,,100,61,0,1348112,106,1,1*63 1787658917.687 L [00:55:37.124,275] <inf> app_main: Ranging data dropped as peer ranging counter doesn't match local ranging data counter. (peer: 107, local: 106) 1787658917.759 L [00:55:37.200,412] <inf> app_main: Ranging: ACL 100 ms, Prozedur-Intervall 5 (500 ms), Antennen 0x04 1787658917.975 L [00:55:37.417,847] <wrn> app_main: All subevents in ranging counter 108 were aborted 1787658918.260 > STANDBY 1787658918.278 D $ACK,1157,STANDBY*1C 1787658918.282 D $CSS,STANDBY,3,1349,dev,5,02*68 1787658918.288 L [00:55:37.728,543] <inf> app_main: STANDBY: gebe D8:33:78:57:75:C3 frei 1787658918.294 L [00:55:37.728,718] <inf> app_main: STANDBY: gebe C2:28:69:29:B7:25 frei 1787658918.301 L [00:55:37.728,879] <inf> app_main: STANDBY: gebe DF:D2:DF:DA:82:8C frei 1787658918.306 L [00:55:37.729,031] <inf> app_main: STANDBY (Lease 600 s) 1787658918.358 L [00:55:37.802,844] <inf> app_main: CS procedures enabled: 1787658918.359 L - config ID: 0 1787658918.362 L - antenna configuration index: 4 1787658918.364 L - TX power: 0 dbm 1787658918.366 L - subevent length: 16000 us 1787658918.368 L - subevents per event: 1 1787658918.370 L - subevent interval: 0 1787658918.372 L - event interval: 2 1787658918.374 L - procedure interval: 5 1787658918.376 L - procedure count: 0 1787658918.379 L - maximum procedure length: 640 1787658918.388 L [00:55:37.830,744] <err> bt_sdc_hci_driver: SoftDevice Controller ASSERT: 23, 587 1787658918.392 L [00:55:37.830,758] <err> os: ***** HARD FAULT ***** 1787658918.398 L [00:55:37.830,763] <err> os: Fault escalation (see below) 1787658918.402 L [00:55:37.830,769] <err> os: ARCH_EXCEPT with reason 3 1787658918.402 L 1787658918.410 L [00:55:37.830,782] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x2000add0 1787658918.418 L [00:55:37.830,789] <err> os: r3/a4: 0x00000003 r12/ip: 0x00000000 r14/lr: 0x00038efd 1787658918.422 L [00:55:37.830,794] <err> os: xpsr: 0x01000000 1787658918.432 L [00:55:37.830,803] <err> os: s[ 0]: 0x0000024b s[ 1]: 0x00003332 s[ 2]: 0x00000000 s[ 3]: 0x00000000 1787658918.441 L [00:55:37.830,811] <err> os: s[ 4]: 0x00033889 s[ 5]: 0x00000000 s[ 6]: 0x20001420 s[ 7]: 0x0000089d 1787658918.450 L [00:55:37.830,820] <err> os: s[ 8]: 0x00000017 s[ 9]: 0x00003332 s[10]: 0x200057c4 s[11]: 0xffff804a 1787658918.460 L [00:55:37.830,828] <err> os: s[12]: 0x20015438 s[13]: 0x00001187 s[14]: 0x0000d959 s[15]: 0x0000d977 1787658918.464 L [00:55:37.830,833] <err> os: fpscr: 0x20008364 1787658918.471 L [00:55:37.830,837] <err> os: Faulting instruction address (r15/pc): 0x000338e2 1787658918.478 L [00:55:37.830,853] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0 1787658918.483 L [00:55:37.830,868] <err> os: Current thread: 0x2000add0 (unknown) 1787658918.540 D $CSS,SEEK,0,0,dev,6,02*18 1787658918.547 L [00:55:37.933,761] <err> fatal_error: Resetting system *** Booting nRF Connect SDK v3.4.0-99553055607b *** 1787658918.550 L *** Using Zephyr OS v4.4.0-bf801e4e3d19 ***
