Hi Devin, Den tors 12 nov. 2020 kl 13:16 skrev Devin Bayer <dev@xxxxxxxxx>: > > On Wed, Nov 11, 2020 at 11:00:32PM +0000, Emil Lenngren wrote: > > > > It would be good to see the complete log from when the "Reset" command > > is issued, otherwise we don't know in which "state" the controller is > > in at the various commands. Also widen the command window when running > > btmon so we see the complete names. :) > > Seeing the result from "LE Read Supported States" would also be nice. > > > > Hi Emil, > > below is the complete log, starting with the the reset command. It > includes the "Supported States" call too. Let me know if there is > anything else I can do. > > ~ Devin > It's as Luiz said, you're mixing two different stacks and hence mixing legacy advertising commands with extended ones. The HCI standard says: "If, since the last power-on or reset, the Host has ever issued a legacy advertising command and then issues an extended advertising command, or has ever issued an extended advertising command and then issues a legacy advertising command, the Controller shall return the error code Command Disallowed (0x0C)." After Reset, you can see "LE Set Extended Advertising Parameters" during the `hciconfig` runs. Then later, when `python` runs, a "LE Set Advertise Enable" is sent. This is disallowed behaviour. One solution is that your python program sends a "Reset" command as the first thing, otherwise you don't know which state the controller is in. The other solution is to use BlueZ only. /Emil
