> I've sent a v3 with a couple of updates so it should now use the > advertisement interval rather than just assuming 200ms would cover all > intervals. Awesome! > So we will probably need to fix that before we can apply it, I suspect > we are getting more events than anticipated causing the steps to go > into negative which probably is why it hangs, anyway it should have > stopped when it reached the end. I think that I've fixed that in v4. The case is that sometimes the ext adv parameters are set with min/max advertisement intervals set to 0 (which is not valid I think ?). Because of that, the broadcast timer (with timeout 0) blocks everything and the test hangs. I've fixed it by providing a default advertising interval (according to the Bluetooth Core Spec), and checking for invalid values. Also, in case of high duty cycle advertising (direct advertising), the timeout is set to non-zero (10ms) in order not to hang everything. I've verified that with mgmt-tested and everything passes (except one test which always fails with my setup). Regards, Arek
