BLE advertising cannot be stop without hardware crash

RE: BLE advertising cannot be stop without hardware crash

Edvin — Wed, 18 Dec 2024 12:52:18 GMT

Thank you!

Ok, so 0x10 is bit 5, and 0x12 is bit 2 and 5. The RESETREAS register, that is used for the hwinfo_get_reset_cause is retained, so it is not reset unless you do it in the application (or a power on reset).

Bit 2 = RESET_BROWNOUT
Bit 5 = RESET_DEBUG

From what I can tell, there is nothing in z_impl_hwinfo_get_reset_cause() from the file ncs\zephyr\drivers\hwinfo\hwinfo_nrf.c that can trigger bit 2 (Reset brownout), which makes sense, because there is no bit in the RESETREAS register that will indicate a brownout.

Bit 5 (RESET_DEBUG) means:

"Reset due to wake up from System OFF mode when wakeup is triggered from entering into debug interface mode"

In case of a power on reset or a brownout reset, the register should be 0x00000000, giving a reset reason = 0. But since it is cumulative, it means that all reset reasons since the last power on/brownout are added to the list.

But I am still not sure how you are able to get bit 2 set in the reset reason number. It should not be possible with an nRF, as there is no check in the hwinfo_get_reset_cause() that sets bit 2.

Best regards,

Edvin

RE: BLE advertising cannot be stop without hardware crash

iznow — Mon, 16 Dec 2024 14:39:35 GMT

uint32_t reset_cause;
int err = hwinfo_get_reset_cause(&reset_cause);

CONFIG_HWINFO=y in prj.conf

[quote userid="26071" url="~/f/nordic-q-a/117119/ble-advertising-cannot-be-stop-without-hardware-crash/515130"]unless you are done with this issue, of course. [/quote]i would prefer to understand...

will take a moment in DK... if some time to do it...

RE: BLE advertising cannot be stop without hardware crash

Edvin — Mon, 16 Dec 2024 13:54:37 GMT

[quote user="iznow"]i see the reset cause at the beginning of my app after reboot, using the reset cause api.[/quote]

Sorry, this may be obvious, but I have not seen it. Can you please specify what API that is?

[quote user="iznow"]moving settings_save_one() call before the bt_le_adv_stop() solve the crash ![/quote]

unless you are done with this issue, of course.

And if it is possible to reproduce in a DK, that would make it easier to understand what's going on.

Best regards,

Edvin

RE: BLE advertising cannot be stop without hardware crash

iznow — Mon, 16 Dec 2024 13:20:40 GMT

i see the reset cause at the beginning of my app after reboot, using the reset cause api.

settings_save_one() call is in my app and was called after the bt_le_adv_stop(). but debugger stop in bt_le_adv_stop() ????

moving settings_save_one() call before the bt_le_adv_stop() solve the crash !!

RE: BLE advertising cannot be stop without hardware crash

Edvin — Mon, 16 Dec 2024 12:56:45 GMT

Where do you see 0x12 and 0x10?

And where do you call settings_save_one()? Is this something you added to your application, or is it something that is part of the default bt_le_adv_stop() API?

Best regards,

Edvin

RE: BLE advertising cannot be stop without hardware crash

iznow — Sun, 15 Dec 2024 18:55:19 GMT

After insvestigation, it appear that a call to a settings_save_one() function just after the ble stop break the execution without explicite exception and reset cause 0x12 HARDWARE_RESET.

After disabling watchdog, the same problem reset with cause 0x10 BROWN_OUT.

Finally i manage to avoid the crash by moving the settings_save_one() call before the ble stop...

but i still do not know what's exactly going on...

i did not found any irq conflict and tried a lot a configuration variation about it...

same behaviour with all others sensors disabled and uninitilaized... maybe dts.?

i didn't try on DK for now...

RE: BLE advertising cannot be stop without hardware crash

iznow — Wed, 11 Dec 2024 08:19:10 GMT

i agree, the screenshot simply show what happend on a debug session free of breakpoints when i try to stop advertising on the main thread. The debugger stop itself without any exception i can show, but stop anyway. in vscode it stop too but line 1399. i will try in the DK.

RE: BLE advertising cannot be stop without hardware crash

Edvin — Tue, 10 Dec 2024 13:53:09 GMT

And is this something you can replicate on a DK? Preferably without the external sensors attached.

BR,
Edvin

RE: BLE advertising cannot be stop without hardware crash

Edvin — Tue, 10 Dec 2024 13:52:40 GMT

Your screenshots doesn't say anything about a crash. Please note that if you put breakpoints in the code after the BLE stack has started, you can break there to monitor parameters, but you need to restart the application after that. It is not able to continue the execution, because it has missed too many timing critical events.

Does the log say anything (if you don't set a breakpoint)?

Best regards,

Edvin

RE: BLE advertising cannot be stop without hardware crash

iznow — Tue, 10 Dec 2024 11:41:53 GMT

bt_le_adv_stop() do not return precisely because it break inside (see code in the screenshot).
no exception intercepted by debugger ... vscode or ozone the same... logs just stop and the reboot happend with reboot cause 12 (HARDWARE_RESET). i understand there is not much info but it's a very reproducable case on my side and very problematic. thanks.

RE: BLE advertising cannot be stop without hardware crash

Edvin — Tue, 10 Dec 2024 11:35:37 GMT

Hello,

I can't see anything from the information you have posted what the error might be. Does the log say anything? What value does bt_le_adv_stop() return?

Best regards,

Edvin