Hi Jehudi,

On Wed, Sep 06, 2017, Laczen JMS wrote:

Running the bluetooth mesh example (samples/bluetooth/mesh/) on a
nrf51822 results in a Hard Fault. The provisioner is meshctl (bluez).
After successful provisioning I disconnect from the mesh, when
connecting again the hard fault appears:

Kernel stacks:
main (real size 512): unused 228 usage 284 / 512 (55 %)
idle (real size 256): unused 200 usage 56 / 256 (21 %)
interrupt (real size 2048): unused 1656 usage 392 / 2048 (19 %)
workqueue (real size 1024): unused 676 usage 348 / 1024 (33 %)
prio recv thread stack (real size 448): unused 144 usage 304 / 448 (67 %)
recv thread stack (real size 1396): unused 32 usage 1364 / 1396 (97 %)
***** HARD FAULT *****
Executing thread ID (thread): 0x20001f04
Faulting instruction address: 0xf63c
Fatal fault in ISR! Spinning...

If needed I can provide more info/logging...

I'd bet the recv thread stack overflowed. It's already at 97% with only
32 unused bytes based on the above log. Try increasing its size to
something bigger. The Kconfig variable is called CONFIG_BT_RX_STACK_SIZE.

Johan