I want to add that I can trigger this behaviour if I send 0x2000 as an Opcode without parameters to the chip, e.g using hcitool on raspberry pi:
sudo hcitool cmd 0x08 0x00
Minor comment: in the log, there are HCI Event with non-Bluetooth event codes 0x40 and higher - these are used internally by the stack and are not received from the Bluetooth Controller.
Hi CaAs_4607266 ,
I am sorry , we don't have an public released document for the vendor specific commands.
Are you still facing this issue ? If then, please provide the logs and steps / commands which you tried.