hciattach on rpi4 times out on first attempt
Bug #1862831 reported by
Paul Larson
This bug report is a duplicate of:
Bug #1890817: Request to include pi-bluetooth in raspi images.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Focal |
New
|
Undecided
|
Unassigned | ||
linux-raspi2 (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Eoan |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I've observed this in both armhf and arm64 on:
19.10.1-server
18.04.4-server
core18
It does not seem to happen on rpi3, only on rpi4.
If you want to use Bluetooth on rpi, one must first run:
$ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow
On RPI4, this results in a timeout on the first attempt. Reattempting it right after will work though, 100% of the times I've tried it.
In the failed attempt, the output is:
bcm43xx_init
Initialization timed out.
And the following is the only new message to show up in dmesg when this fails:
[ 270.303691] uart-pl011 fe201000.serial: no DMA platform data
tags: | added: bionic eoan |
tags: | added: rls-ff-incoming |
no longer affects: | linux-raspi (Ubuntu Eoan) |
no longer affects: | linux-raspi2 (Ubuntu Eoan) |
no longer affects: | linux-raspi (Ubuntu Eoan) |
no longer affects: | linux-raspi2 (Ubuntu Focal) |
To post a comment you must log in.
I tested raspbian on the RPI4B board, also could reproduce this problem.
steps of testing: hciattach- bak
login the raspbian, sudo mv /usr/bin/hciattach /usr/bin/
reboot
login, check the bluetooth is not up "hcitool dev"
run sudo hciattach-bak /dev/ttyAMA0 bcm43xx 921600 noflow
will timeout and fail
run sudo hciattach-bak /dev/ttyAMA0 bcm43xx 921600 noflow
it works..
And because raspbian installed pi-bluetooth package, this issue was not exposed.