Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blueooth: Controller Response COMMAND DISALLOWED #30808

Closed
LingaoM opened this issue Dec 17, 2020 · 8 comments
Closed

Blueooth: Controller Response COMMAND DISALLOWED #30808

LingaoM opened this issue Dec 17, 2020 · 8 comments
Assignees
Labels
area: Bluetooth Host Bluetooth Host (excluding BR/EDR) area: Bluetooth Mesh area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Waiting for response Waiting for author's response

Comments

@LingaoM
Copy link
Collaborator

LingaoM commented Dec 17, 2020

Describe the bug

Use nrf52832 as controller, use nrf52840 as host, use H4 transport layer.

*** Booting Zephyr OS build zephyr-v2.4.0-1367-g7d16ab50d738 **

[00:00:02.807,769] bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:02.807,800] bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:02.807,800] bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.4 Build 99
[00:00:02.825,592] bt_hci_core: Identity: e4:0c:5e:e9:04:9a (random)
[00:00:02.825,592] bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
[00:00:02.825,622] bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff
[00:00:09.433,471] bt_mesh_health_cli.health_cli_init: primary 1
[00:00:09.433,776] bt_mesh_prov_device: Device UUID: 3a2b2d51-f1a3-47ad-bb49-7c23c85219b3
[00:00:09.438,903] bt_hci_core: opcode 0x200b status 0x0c
[00:00:09.438,903] bt_mesh_adv: starting scan failed (err -5)

I did not modify any code in the host or controller. This problem occurs from time to time. However, if the host and controller are in the same chip, the problem is not found.

@LingaoM LingaoM added bug The issue is a bug, or the PR is fixing a bug area: Bluetooth area: Bluetooth Mesh area: Bluetooth Controller area: Bluetooth Host Bluetooth Host (excluding BR/EDR) labels Dec 17, 2020
@LingaoM LingaoM changed the title Blueooth: Unable start scanning Blueooth: Controller Response COMMAND DISALLOWED Dec 17, 2020
@cvinayak
Copy link
Contributor

Please provide details to reproduce like the commit, samples, configuration, build steps used, flashing steps and test procedure.

@carlescufi
Copy link
Member

carlescufi commented Jan 7, 2021

@LingaoM could you please pinpoint the exact HCI command that is getting command disallowed? This could be the set random address one, which would be different from what you analyzed.
EDIT: This is actually failing on Set Scan Parameters, so this looks like a bug in the Host itself, not Mesh or the Controller.

@carlescufi carlescufi added area: Bluetooth Host Bluetooth Host (excluding BR/EDR) and removed area: Bluetooth Controller area: Bluetooth Host Bluetooth Host (excluding BR/EDR) labels Jan 14, 2021
@carlescufi
Copy link
Member

@LingaoM could you please provide additional information here?

@LingaoM
Copy link
Collaborator Author

LingaoM commented Jan 15, 2021

Sorry for the delay, I think it may be that the controller is not reset, and the host is running on another board, resulting in an inconsistent state.

@carlescufi
Copy link
Member

Sorry for the delay, I think it may be that the controller is not reset, and the host is running on another board, resulting in an inconsistent state.

The Host should always start with an HCI Reset command after a Host reset, and that should soft-reset the controller. Any other additional information you can provide?

@LingaoM
Copy link
Collaborator Author

LingaoM commented Jan 25, 2021

Sorry, i can't provide more effective information.

@LingaoM
Copy link
Collaborator Author

LingaoM commented Jan 25, 2021

It is worth mentioning that I use auto pts to capture this problem, and it is probabilistic. If the host / controller is on the same chip, the same problem is not found.

@carlescufi
Copy link
Member

[00:00:09.438,903] bt_mesh_adv: starting scan failed (err -5)

This has likely been fixed by #31532, please reopen if that's not the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth Host Bluetooth Host (excluding BR/EDR) area: Bluetooth Mesh area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Waiting for response Waiting for author's response
Projects
None yet
Development

No branches or pull requests

6 participants