Well, I wrote, but I don’t have a clue how to add it to armbian, there is some kind of command like armbian-overlay or armbian-add-overlay, maybe you need to do something else before adding, look for information, I only know how to include overlay later armbianEnv.txt: overlays = orangepi-prime-bluetooth
There may also be a problem with downloading the driver firmware, in the Armbian, some patches are doing something with the kernel, namely, with the function of searching for firmware files.
For example, I have opi-win with ap6212 and on a clean kernel, the driver downloads the file /lib/firmware/brcm/brcmfmac43430-sdio.xunlong,orangepi-win.txt what highlighted this board name from dtb, and the core armbian uses some kind of crutch in in the form of the firmware-postfix parameter and not even as an addition to what is, but as a replacement for what is. in short, see dmesg after the system is booted, it will be seen there that the driver is trying to load, what failed to load, etc.
Since the prime module is the same as on pine64, I did not change the line firmware-postfix = "pine64"; can that will load from the fact that there is in the image and immediately earn ...
1.Copy your file to:
- \ boot \ dtb \ allwinner \
- \ boot \ dtb \ allwinner \ overlay \
2. In the file \ boot \ rmbianEnv.txt introduced the line overlays = orangepi-prime-bluetooth
As a result, the file looks like this:
verbosity = 1
console = both
overlay_prefix = sun50i-h5
rootdev = UUID = d037a579-13c1-4dbb-be0b-234849d9e5b3
rootfstype = ext4
overlays = analog-codec
overlays = orangepi-prime-bluetooth
usbstoragequirks = 0x2537: 0x1066: u, 0x2537: 0x1068: u
3. Rebooted
4. But the bluetooth service was not activated:
root @ orangepiprime: # systemctl status bluetooth
в—Џ bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man: bluetoothd (8)
According to
this articleI check the presence in the bluetooth system:
root @ orangepiprime: # rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
After following the recommendations on
this articleBluetooth service is loading:
root @ orangepiprime: # modprobe btusb
root @ orangepiprime: # systemctl start bluetooth.service
root @ orangepiprime: # systemctl status bluetooth
в—Џ bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-03-14 22:58:43 MSK; 5s ago
Docs: man: bluetoothd (8)
Main PID: 2727 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
2в”Ђ2727 / usr / lib / bluetooth / bluetoothd
Mar 14 22:58:43 orangepiprime systemd [1]: Starting Bluetooth service ...
Mar 14 22:58:43 orangepiprime bluetoothd [2727]: Bluetooth daemon 5.43
Mar 14 22:58:43 orangepiprime systemd [1]: Started Bluetooth service.
Mar 14 22:58:43 orangepiprime bluetoothd [2727]: Starting SDP server
Mar 14 22:58:44 orangepiprime bluetoothd [2727]: Bluetooth management interface 1.14 initialized
But when I try to activate it, an error crashes (and everything should be ok according to
this video):
root @ orangepiprime: # bluetoothctl
[bluetooth] # power on
No default controller available
Here is
hereoffer to collect firewood yourself.
Here is
hereThe author Armbiana proposes to make similar to the Pinebook.
Here is
hereKind of like official firewood for bluetooth from linux.
Could you help me figure it out and give step-by-step instructions?
And did I understand correctly that from your dts you need to do dtb through dtc -b 0 -O dts -I dtb -o (
infa)?
Post has been editedGeremy82 - 14.03.19, 23:23