aht2000 Posted March 5, 2023 Posted March 5, 2023 I am new to this. I have an H96Max Android TV box which I flashed successfully with Armbian 23.02.2 Bullseye with Linux 5.15.93-rockchip64the latest armbian image. Wifi is running fine. However, I failed to activate bluetooth. I read several post around the same topic with no luck. I am attaching several logs I collected and hope it can clarify more the case, so someone can help resolving this. =============================================== root@rk3318-box:/# dmesg | egrep -i 'blue|firm' [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 6.838446] Bluetooth: Core ver 2.22 [ 6.838756] NET: Registered PF_BLUETOOTH protocol family [ 6.838775] Bluetooth: HCI device and connection manager initialized [ 6.838804] Bluetooth: HCI socket layer initialized [ 6.838821] Bluetooth: L2CAP socket layer initialized [ 6.838868] Bluetooth: SCO socket layer initialized [ 9.513260] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43342-sdio.rockchip,rk3318-box.bin failed with error -2 [ 9.525849] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43342-sdio.rockchip,rk3318-box.txt failed with error -2 [ 9.693623] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43342/1 wl0: Oct 18 2016 17:43:42 version 6.25.134.25 (r662387) FWID 01-281dd9d9 [ 38.183427] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 38.183447] Bluetooth: BNEP filters: protocol multicast [ 38.183468] Bluetooth: BNEP socket layer initialized ========================= root@rk3318-box:/# rfkill ID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked ============================================= root@rk3318-box:/# systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-03-05 19:55:27 +04; 28min ago Docs: man:bluetoothd(8) Main PID: 1867 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4587) Memory: 2.5M CPU: 97ms CGroup: /system.slice/bluetooth.service └─1867 /usr/libexec/bluetooth/bluetoothd Mar 05 19:55:27 rk3318-box systemd[1]: Starting Bluetooth service... Mar 05 19:55:27 rk3318-box bluetoothd[1867]: Bluetooth daemon 5.55 Mar 05 19:55:27 rk3318-box systemd[1]: Started Bluetooth service. Mar 05 19:55:27 rk3318-box bluetoothd[1867]: Starting SDP server Mar 05 19:55:27 rk3318-box bluetoothd[1867]: Bluetooth management interface 1.21 initialized =============================== root@rk3318-box:/# bluetoothctl Agent registered [bluetooth]# power on No default controller available ========================= root@rk3318-box:/# lsmod ========================= Module Size Used by bnep 32768 2 ir_nec_decoder 20480 0 nft_chain_nat 16384 4 xt_MASQUERADE 20480 1 nf_nat 49152 2 nft_chain_nat,xt_MASQUERADE nft_counter 16384 3 xt_state 16384 0 xt_conntrack 16384 1 nf_conntrack 163840 4 xt_conntrack,nf_nat,xt_state,xt_MASQUERADE nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack nft_compat 20480 2 nf_tables 212992 15 nft_compat,nft_counter,nft_chain_nat nfnetlink 20480 2 nft_compat,nf_tables lz4hc 16384 0 lz4 16384 0 brcmfmac 385024 0 brcmutil 28672 1 brcmfmac cfg80211 876544 1 brcmfmac snd_soc_spdif_tx 16384 1 hantro_vpu 118784 0 rockchip_vdec 32768 0 gpio_ir_recv 16384 0 rc_core 57344 3 gpio_ir_recv,ir_nec_decoder snd_soc_hdmi_codec 24576 1 snd_soc_rockchip_spdif 16384 2 v4l2_h264 16384 2 rockchip_vdec,hantro_vpu snd_soc_rk3328 16384 1 rockchip_rga 28672 0 videobuf2_vmalloc 20480 1 hantro_vpu snd_soc_simple_card 24576 4 snd_soc_simple_card_utils 28672 1 snd_soc_simple_card rockchip_iep 20480 0 snd_soc_rockchip_i2s 24576 4 snd_soc_rockchip_pcm 16384 1 snd_soc_rockchip_i2s snd_soc_core 262144 8 snd_soc_spdif_tx,snd_soc_rockchip_pcm,snd_soc_hdmi_codec,snd_soc_rockchip_spdif,snd_soc_rk3328,snd_soc_simple_card_utils,snd_soc_rockchip_i2s,snd_soc_simple_card videobuf2_dma_sg 24576 1 rockchip_rga videobuf2_dma_contig 24576 3 rockchip_vdec,hantro_vpu,rockchip_iep v4l2_mem2mem 40960 4 rockchip_vdec,hantro_vpu,rockchip_rga,rockchip_iep videobuf2_memops 20480 3 videobuf2_vmalloc,videobuf2_dma_contig,videobuf2_dma_sg videobuf2_v4l2 32768 5 rockchip_vdec,hantro_vpu,rockchip_rga,rockchip_iep,v4l2_mem2mem videobuf2_common 65536 10 rockchip_vdec,videobuf2_vmalloc,videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_dma_sg,rockchip_iep,v4l2_mem2mem,videobuf2_memops snd_pcm_dmaengine 20480 1 snd_soc_core videodev 262144 7 rockchip_vdec,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_common,rockchip_iep,v4l2_mem2mem snd_pcm 131072 3 snd_soc_hdmi_codec,snd_soc_core,snd_pcm_dmaengine mc 61440 6 rockchip_vdec,videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem snd_timer 40960 1 snd_pcm snd 94208 12 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm cpufreq_dt 20480 0 soundcore 16384 1 snd zram 40960 3 btusb 65536 0 btrtl 24576 1 btusb btbcm 28672 1 btusb btintel 40960 1 btusb bluetooth 638976 11 btrtl,btintel,btbcm,bnep,btusb rfkill 36864 6 bluetooth,cfg80211 sunrpc 581632 1 ip_tables 32768 0 x_tables 49152 5 xt_conntrack,nft_compat,xt_state,ip_tables,xt_MASQUERADE autofs4 49152 2 dwmac_rk 28672 0 stmmac_platform 24576 1 dwmac_rk stmmac 237568 2 stmmac_platform,dwmac_rk dw_hdmi_cec 16384 0 pcs_xpcs 24576 1 stmmac dw_hdmi_i2s_audio 16384 0 lima 61440 0 gpu_sched 40960 1 lima gpio_syscon 20480 1 adc_keys 16384 0 0 Quote
jock Posted March 6, 2023 Posted March 6, 2023 To debug the problem, it is better to paste the link coming from armbianmonitor -u ; also photos of the board are very useful to identify which board you have. Also this is the reference thread for rk3318 boxes 0 Quote
aht2000 Posted March 6, 2023 Author Posted March 6, 2023 (edited) Thank you. Following is the link. https://paste.armbian.com/xemihiquqo Attached is a photo of the board Edited March 6, 2023 by aht2000 Added the photo for the board 0 Quote
aht2000 Posted December 2, 2023 Author Posted December 2, 2023 (edited) This is an old thread. I made some progress by running the rk3318-config and accepting the default. Using bluetoothctl I see it works, and I can scan on. However, either it scans very few devices or none. Following is the dmesg outcome. It complains about a missing patch for BCM43342A. How can I add this patch? dmesg | grep -i blue [ 10.361265] Bluetooth: Core ver 2.22 [ 10.361501] NET: Registered PF_BLUETOOTH protocol family [ 10.361514] Bluetooth: HCI device and connection manager initialized [ 10.361545] Bluetooth: HCI socket layer initialized [ 10.361559] Bluetooth: L2CAP socket layer initialized [ 10.361607] Bluetooth: SCO socket layer initialized [ 10.432142] Bluetooth: HCI UART driver ver 2.3 [ 10.432184] Bluetooth: HCI UART protocol H4 registered [ 10.432193] Bluetooth: HCI UART protocol BCSP registered [ 10.432374] Bluetooth: HCI UART protocol LL registered [ 10.432397] Bluetooth: HCI UART protocol ATH3K registered [ 10.432489] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 10.432863] Bluetooth: HCI UART protocol Intel registered [ 10.435956] Bluetooth: HCI UART protocol Broadcom registered [ 10.436076] Bluetooth: HCI UART protocol QCA registered [ 10.436085] Bluetooth: HCI UART protocol AG6XX registered [ 10.441003] Bluetooth: HCI UART protocol Marvell registered [ 10.820901] Bluetooth: hci0: BCM: chip id 83 [ 10.821724] Bluetooth: hci0: BCM: features 0x0f [ 10.823414] Bluetooth: hci0: BCM43342A [ 10.823458] Bluetooth: hci0: BCM (001.002.003) build 0000 [ 10.823836] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 10.823862] Bluetooth: hci0: BCM: 'brcm/BCM.rockchip,rk3318-box.hcd' [ 10.823869] Bluetooth: hci0: BCM: 'brcm/BCM.hcd' [ 18.309192] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.309238] Bluetooth: BNEP filters: protocol multicast [ 18.309273] Bluetooth: BNEP socket layer initialized [ 18.357504] Bluetooth: MGMT ver 1.22 [ 56.740638] Bluetooth: RFCOMM TTY layer initialized [ 56.740700] Bluetooth: RFCOMM socket layer initialized [ 56.740747] Bluetooth: RFCOMM ver 1.11 The outcome link from armbianmonitor -u is: https://paste.armbian.com/qusikoqege Edited December 2, 2023 by aht2000 0 Quote
aht2000 Posted December 16, 2023 Author Posted December 16, 2023 Thank you very much. Yes it did. After creating the symbolic link, Bluetooth is now working successfully and I am able to pair and connect to my Airpods. 0 Quote
MattWestB Posted October 13 Posted October 13 For your version of RK3318_V1.4 (without display) its needs the configure file as you was doing OK. For other users its the command "ln -s /usr/lib/firmware/brcm/BCM43342.hcd /usr/lib/firmware/brcm/BCM.hcd" And its stop using different BT MAC-addresses after every reboot so can being used with BT devices. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.