Hardfault after reboot

RE: Hardfault after reboot

tesc — Fri, 01 Dec 2023 10:26:06 GMT

Hi,

In order to ensure valid address handles, you should use dsm_address_get_all() for fetching the handles into a list of handles, and the p_count will reflect the number of valid handles in that list after the call to dsm_address_get_all() returns.

Regards,
Terje

RE: Hardfault after reboot

Simsim — Thu, 30 Nov 2023 06:37:11 GMT

Hi, Terje

I could find out what called the hardfault, i was printing all the Adresses form the DSM

 dsm_address_get(alladressHandle, &localaddress);

which points to non valid memory.

By enlarge the DSM_SUBNET_MAX from 4 to 40 the hardfault does no more occure.

But i think this is not the real soultion for this, while i use only one subnet, so i will post here if i find the root of this.

Regards

Simon

RE: Hardfault after reboot

tesc — Thu, 23 Nov 2023 16:57:56 GMT

Hi,

There is no strong connection to the SoftDevice with flash storage used for provisioning data in the nRF5 SDK for Mesh. In fact, the SoftDevice does not directly handle Bluetooth Mesh either.

Bluetooth Mesh is built on top of BLE, so the provisioning (which is purely a Bluetooth Mesh concept) is part of the Bluetooth Mesh stack, which is provided as source code form in the SDK and compiled into the application.

In the Bluetooth Mesh stack, data storage is handled by the Device State Manager module, which again uses the Flash manager module (also part of nRF5 SDK for Mesh) for the actual storage.

The Flash manager module then does the direct flash operations, and uses the SoftDevice API for that (since the SoftDevice because of time critical operation needs to control when (time consuming) flash operations are scheduled.)

Regards,
Terje

RE: Hardfault after reboot

Simsim — Thu, 23 Nov 2023 07:06:59 GMT

Hi Terje

Thanks for the insights, i could pin down with ozone the Error, it comes from a not enabled Busfault which rises a hardfault.

So i had to look deeper into the code.

Can you give me some information about storing of the provisioner data into the softdevice (not the mesh config file ) since i had disabled them and it seems that the Softdevice still starts up provisioned and load configuration of handels and dsm addreses and so on. So i guess there is another memory for the configuration of this part.

Regards

Simon

RE: Hardfault after reboot

tesc — Wed, 22 Nov 2023 19:57:23 GMT

Hi,

Step by step debugging is not expected to work as long as there is a SoftDevice involved, since then a hardfault is expected. (The SoftDevice faults if it detects that certain timing constraints are not held.) Even though the Bluetooth Mesh stack in the nRF5 SDK does not use the SoftDevice for the ADV bearer, it does use the SoftDevice for the GATT bearer. Therefore, there is a SoftDevice involved.

What this means, is, if doing a debug session, you can only do one breakpoint. When that breakpoint is reached and code execution is halted, the stack is expected to crash once resumed. Debug options are therefore limited. Print debugging may in many instances be more effective.

When provisioning fails, do you get log output of the devices involved? (Both provisionee and provisioner.) There is not much to go on there, apart from the step debugging (expectedly) failing with hardfault. The error is most likely elsewhere.

Regards,
Terje