Bluetooth: Mesh: Provisioning state doesn't always get properly re-initialized when doing reset #14928
Assignees
Labels
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Milestone
Comments
jhedberg
added
bug
jhedberg
pushed a commit
to jhedberg/zephyr
that referenced
this issue
Mar 28, 2019
If both PB-ADV and PB-GATT are supported, we need to properly re-initialize variables such as link.rx.prev_id and (particularly importantly) link.rx.buf. If we don't do this it may lead to the following fault when trying to reprovision again: ***** USAGE FAULT ***** Illegal use of the EPSR ***** Hardware exception ***** Current thread ID = 0x20001f10 Faulting instruction address = 0x0 Fatal fault in thread 0x20001f10! Aborting. Fixes zephyrproject-rtos#14928 Signed-off-by: Johan Hedberg <[email protected]>
jhedberg
pushed a commit
that referenced
this issue
Mar 28, 2019
If both PB-ADV and PB-GATT are supported, we need to properly re-initialize variables such as link.rx.prev_id and (particularly importantly) link.rx.buf. If we don't do this it may lead to the following fault when trying to reprovision again: ***** USAGE FAULT ***** Illegal use of the EPSR ***** Hardware exception ***** Current thread ID = 0x20001f10 Faulting instruction address = 0x0 Fatal fault in thread 0x20001f10! Aborting. Fixes #14928 Signed-off-by: Johan Hedberg <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If both PB-ADV and PB-GATT are supported and the node is reset after provisioning, there are several parts of the provisioning state that do not get correctly re-initialized and result in the following fault:
The text was updated successfully, but these errors were encountered: