Problem Loading Bonding Info From Flash

[Eric]

Unless manually set the value of bond_init_data.bonds_delete to true in the function bond_manager_init to clear bonded masters, I end up in the HardFault_handler. The last call I can trace is line 641 in pstorage.c,memcpy (p_dest, (((uint8_t *)p_src->block_id) + offset), size); From that code it doesn't look like a memcpy is ever expected to fail.

The example I'm primarily working on is the experimental ble_app_ancs, but it occurs in other examples as well. I am using the latest SDK and soft device, but this has happened with the previous version as well.

I suspect this is related to my target setup, but I'm just using the defaults from the example project - nrf51822_xxaa_s110 (256). I've had a look at the Dev Kit User Guide, but those numbers seem to be different.

How do I go about finding the source of this issue?

Thanks, Eric

[Eric]

Attached is a screen shot with the stack at HardFault, also a stack just before the memcpy that causes the HardFault.

I get this fault with all the ble projects at the moment. Those screen shots are from an unmodifed copy of ble_app_proximity (well I changed the optimisation so the stack trace has more info for the second screen shot).

ble_app_proximity.7z

[Ole Morten]

I just tried to reproduce this, with the project and hex you uploaded, but I'm not able to. The values for the memcpy() parameters also looks good in your screenshot, but I find it strange that you don't get a backtrace from your HardFault. Can you please make sure that you use softdevice 6.0.0, which is required for SDK 5.0.0? Also, can you please read off the laser markings on your chip, and post them?