zephyr/doc/connectivity/bluetooth/api
Piotr Pryga c6e9b3c235 Bluetooth: hci: Extend VS fatal error for hard hault and assert
Extend current implementation of vendor-specific HCI events related
with Zephyr Fatal Error. The extended event is able to carry Zephyr
system wide fatal error as well as Controller related assertion.
That gives a possibility to use the event by bt_ctlr_assert_handle
or k_sys_fatal_error_handler to send information about unrecoverable
failures over HCI interface.

There are added two types of errors to Zephyr Fatal Error event:
- system fault error like e.g. Hard Fault. This one caries reason of
  a fault and a stack frame in the data field. The stack frame is
  defined for Corte-M SoCs only.
- Controller assert. The data field caries file name and line of code
  where an assert happened.

Except that the extended event can be used by Host, it can serve as a
debug mean to conformance testing of the Controller.

Signed-off-by: Piotr Pryga <piotr.pryga@nordicsemi.no>
2022-08-02 13:53:32 +02:00
..
mesh Bluetooth: Mesh: Add model publish support to Health Client 2022-08-01 18:04:42 +01:00
shell doc: Bluetooth: Upstream existing LE Audio shell rsts 2022-06-28 14:50:11 +02:00
audio.rst
connection_mgmt.rst
controller.rst
coordinated_sets.rst
crypto.rst
data_buffer.rst
gap.rst
gatt.rst
hci_drivers.rst
hci_raw.rst
hci.txt Bluetooth: hci: Extend VS fatal error for hard hault and assert 2022-08-02 13:53:32 +02:00
hfp.rst
index.rst doc: Bluetooth: Upstream existing LE Audio shell rsts 2022-06-28 14:50:11 +02:00
l2cap.rst
media.rst
mesh.rst
microphone.rst Bluetooth: Audio: Rename MICS to MICP 2022-07-06 10:41:52 +02:00
rfcomm.rst
sdp.rst
services.rst doc: Bluetooth: Document the services APIs 2022-05-24 17:49:17 +02:00
uuid.rst
volume.rst