If I invoke "hci_le_set_advertise_enable(0)" after advertising via "hci_le_set_advertise_enable(1)", I can no longer communicate with CPU2 and the C2DS bit inside PWR_EXTSCR is no longer set which indicates it didn't go into a low power state (and that CPU2 likely stuck somewhere).
Has anyone else seen this bug, or can reproduce it? I'm running custom firmware on a custom product and haven't tried to modify any of the examples to do exhibit this on a stock product, but have successfully been scanning for advertising packets (and enabling/disabling scanning) without issue.
This is against v1.11.1 on a STM32WB5x and I can reproduce with:
- stm32wb5x_BLE_HCILayer_fw.bin
- stm32wb5x_BLE_Stack_full_fw.bin
- stm32wb5x_BLE_Stack_light_fw.bin
