Export BLE buffers in SKD

[loftyinclination]

Describe the enhancement you're suggesting.

When sending BLE HCI commands to the STM32WB55 coprocessor (using the process laid out in Annex 5289, 14.2.2) the command body must first be written into the p_cmdBuffer. Currently, it's not possible to write to this buffer in third party applications, since it's not referenced in the SDK, and so it's not possible to build any applications that use HCI commands.

(It is currently possible to listen for the responses to these events, via use of the ble_event_dispatcher_register_svc_handler function, which I think was included because the event handling is necessary for both ACI commands (which, as they don't require touching the p_cmdBuffer, are already callable from other applications), as well as HCI commands).

Anything else?

No response

[hedger]

Issuing raw BLE HCI commands could possibly affect the state managed by the BLE subsystem. We'll consider if that feature is worth implementing, because it's current use is also quite limited due to dependance on full HCI headers being available in the SDK to parse callback results.

[loftyinclination]

Do you mean the BLE subsystem inside of the copro library, or in the flipper firmware itself?

And for HCI headers, do you mean the version of the BLE LE stack variant, or the HCI events as detailed in AN5270, section 3? Having done some reading, probably the C Header files from the STM32_copro library -- when investigating send BLE commands from within C, exposing ble_app_cmd_buffer via a method in targets/f7/ble_glue/ble_app.h bought all of the stm32wb_copro headers into the SDK, evidenced by api_symbols gaining a bunch of new entiries.