I am using ncs V1.5.1 and I can run the zephyr/samples/bluetooth/peripheral sample flawlessly on an nrf52dk_nrf52832 board. I verify BLE by viewing the "Zephyr Peripheral Sample Long Name" on my Android nRF Connect App. Here is the SES debug terminal for the successful run:
[00:00:33.370,880] [0m fs_nvs: 6 Sectors of 4096 bytes[0m
[00:00:33.370,880] [0m fs_nvs: alloc wra: 0, ff0[0m
[00:00:33.370,880] [0m fs_nvs: data wra: 0, 0[0m
[00:00:33.371,002] [0m sdc_hci_driver: SoftDevice Controller build revision:
d9 e2 43 71 3b 2d c0 15 55 e1 1d c8 99 75 01 7a |..Cq;-.. U....u.z
62 85 8d 0a |b... [0m
[00:00:33.373,535] [0m bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)[0m
[00:00:33.373,535] [0m bt_hci_core: HW Variant: nRF52x (0x0002)[0m
[00:00:33.373,535] [0m bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 217.17378 Build 3224189809[0m
[00:00:33.373,870] [0m bt_hci_core: No ID address. App must call settings_load()[0m
[00:00:33.382,629] [0m sdc_crypto: key
e9 73 25 71 15 03 70 6a e4 b7 b2 79 43 c4 f0 02 |.s%q..pj ...yC...[0m
[00:00:33.382,629] [0m sdc_crypto: plaintext
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |........ ........[0m
[00:00:33.382,659] [0m sdc_crypto: enc_data
94 92 99 1d bb 07 ba 1d ff 59 98 35 6e 75 d5 47 |........ .Y.5nu.G[0m
[00:00:33.382,812] [0m bt_hci_core: Identity: F5:77:20:DF:34:57 (random)[0m
[00:00:33.382,812] [0m bt_hci_core: HCI: version 5.2 (0x0b) revision 0x11c2, manufacturer 0x0059[0m
[00:00:33.382,812] [0m bt_hci_core: LMP: version 5.2 (0x0b) subver 0x11c2[0m
[00:00:33.397,125] [0m bt_keys.keys_commit: [0m
[00:00:33.397,186] [0m sdc_crypto: key
94 92 99 1d bb 07 ba 1d ff 59 98 35 6e 75 d5 47 |........ .Y.5nu.G[0m
[00:00:33.397,186] [0m sdc_crypto: plaintext
53 c2 7b 00 00 00 00 00 00 00 00 00 00 00 00 00 |S.{..... ........[0m
[00:00:33.397,216] [0m sdc_crypto: enc_data
a7 54 56 0e d7 99 9c c8 35 d2 f8 a7 7a aa e0 f0 |.TV..... 5...z...[0m
However, when I run the same zephyr/samples/bluetooth/peripheral sample on our custom nRF52832-QFAA-R board, BLE fails to a hard fault (mpsl_init: MPSL ASSERT: 112, 2163). Here is the SES debug terminal for the failed run:
[00:00:00.012,451] [0m bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)[0m
[1;31m--- 4 messages dropped ---
[0m[00:00:00.012,451] [0m bt_hci_core: HW Variant: nRF52x (0x0002)[0m
[00:00:00.012,451] [0m bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 217.17378 Build 3224189809[0m
[00:00:00.012,756] [0m bt_hci_core: No ID address. App must call settings_load()[0m
[00:00:00.015,258] [0m sdc_crypto: key
3f c2 21 44 d7 e7 dd 99 6d 53 de 34 b6 f6 12 dc |?.!D.... mS.4....[0m
[00:00:00.015,258] [0m sdc_crypto: plaintext
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |........ ........[0m
[00:00:00.015,289] [0m sdc_crypto: enc_data
44 92 d4 28 b7 11 fb 52 a2 0e 7c 80 49 c5 e6 e0 |D..(...R ..|.I...[0m
[00:00:00.015,411] [0m bt_hci_core: Identity: FD:3A:C4:5B:33:83 (random)[0m
[00:00:00.015,441] [0m bt_hci_core: HCI: version 5.2 (0x0b) revision 0x11c2, manufacturer 0x0059[0m
[00:00:00.015,441] [0m bt_hci_core: LMP: version 5.2 (0x0b) subver 0x11c2[0m
[00:00:00.019,409] [0m bt_keys.keys_commit: [0m
[00:00:00.019,439] [0m sdc_crypto: key
44 92 d4 28 b7 11 fb 52 a2 0e 7c 80 49 c5 e6 e0 |D..(...R ..|.I...[0m
[00:00:00.019,470] [0m sdc_crypto: plaintext
a8 04 78 00 00 00 00 00 00 00 00 00 00 00 00 00 |..x..... ........[0m
[00:00:00.019,500] [0m sdc_crypto: enc_data
dc 01 0a b5 54 d8 53 86 9a 71 58 62 af 01 2d c9 |....T.S. .qXb..-.[0m
[00:00:00.030,120] [1;31m mpsl_init: MPSL ASSERT: 112, 2163[0m
[00:00:01.423,126] [1;31m os: ***** HARD FAULT *****[0m
[00:00:01.423,126] [1;31m os: Fault escalation (see below)[0m
[00:00:01.423,126] [1;31m os: r0/a1: 0x00000003 r1/a2: 0x200066b0 r2/a3: 0x00000000[0m
[00:00:01.423,126] [1;31m os: r3/a4: 0x00000013 r12/ip: 0x20000efc r14/lr: 0x00010917[0m
[00:00:01.423,156] [1;31m os: xpsr: 0x61000018[0m
[00:00:01.423,156] [1;31m os: Faulting instruction address (r15/pc): 0x0001d396[0m
[00:00:01.423,156] [1;31m os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0[0m
[00:00:01.423,187] [1;31m os: Fault during interrupt handling
[0m
[00:00:01.423,187] [1;31m os: Current thread: 0x200018e0 (unknown)[0m
[00:00:02.500,305] [1;31m fatal_error: Resetting system[0m
The custom board is very similar to the nrf52dk_nrf52832 board are very similar and I've tried running the custom board with the nrf52_nrf52832 board files and I get the same failures.
Any thoughts on how to debug this issue would be greatly appreciated.
Rich
