Bluetooth

[skelosParticipant]

Hello,
I would to use bloetooth in cubox-i 4×4.
I staart the service but when I looking for devices near my mobile I can’t find noting: no device are seen.

Could you indicate me how I can create a link between cubox and my mobile?

[Warped RudiModerator]

Generally spoken: Bluetooth sucks on the Cubox-i. I think nobody has ever got it working properly. Actually, it appears to kill WiFi. Not just the built-in, it seems to really jam the communication in the whole neighbourhood !!! So be warned…

Nevertheless, I recently changed our package layout to harmonize it with RaspberryPi3. So if you don’t already did so, please remove the package “brcm-patchram-plus” and install “firmware-bluetooth-brcm43xx” instead. Then unmask “bluetooth-setup.service” and start it:

root@geexbox:~# systemctl unmask bluetooth-setup
Removed symlink /etc/systemd/system/bluetooth-setup.service.
root@geexbox:~# systemctl start bluetooth-setup
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI Three-wire UART (H5) protocol initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
root@geexbox:~# 
root@geexbox:~# systemctl status bluetooth-setup -l
● bluetooth-setup.service - Load Broadcom 43xx bluetooth firmware and enable HCI device
   Loaded: loaded (/usr/lib/systemd/system/bluetooth-setup.service; disabled; vendor preset: enabled)
   Active: active (exited) since Sat 2016-04-30 06:59:49 BST; 11s ago
  Process: 3342 ExecStart=/usr/bin/brcm43xx-bt-attach (code=exited, status=0/SUCCESS)
 Main PID: 3342 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/bluetooth-setup.service
           └─3446 hciattach /dev/ttymxc3 bcm4329 3000000 flow -
Apr 30 06:59:45 geexbox brcm43xx-bt-attach[3342]: Found chip version 0x4329.
Apr 30 06:59:49 geexbox brcm43xx-bt-attach[3342]: bcm43xx_init
Apr 30 06:59:49 geexbox brcm43xx-bt-attach[3342]: Flash firmware /lib/firmware/brcm/BCM4329B1.hcd
Apr 30 06:59:49 geexbox brcm43xx-bt-attach[3342]: Set Controller UART speed to 3000000 bit/s
Apr 30 06:59:49 geexbox brcm43xx-bt-attach[3342]: Device setup complete
root@geexbox:~# hcitool scan
Scanning ...
root@geexbox:~# hcitool scan
Scanning ...
        F4:06:69:19:46:D6       Sirius-0   <--- my Linux PC
root@geexbox:~#
root@geexbox:~# hciconfig
hci0:   Type: BR/EDR  Bus: UART
        BD Address: 43:29:B0:00:2F:DD  ACL MTU: 1021:6  SCO MTU: 64:1
        UP RUNNING PSCAN INQUIRY
        RX bytes:4057 acl:0 sco:0 events:64 errors:0
        TX bytes:1221 acl:0 sco:0 commands:39 errors:0
root@geexbox:~#

But if you got that far, it doesn’t mean that you got “a link between cubox and your mobile”. You did not say what kind of link that would be (audio, file transfer, calendar sync, serial port emulation, ethernet emulation) and depending on that there are a bunch of other protocols/components necessary, which we most likely do not have…
The only Bluetooth device we (i.e. @tomlohave) have tried is the WiiRemote. However, I *think* he uses a generic USB-attached Bluetooth radio instead of the Cubox-i built-in.

Note that the logs are from an early CuBox-i. Newer units use a BCM4330, which might work a little bit better. But not much.

[tomlohaveModerator]

Not just the built-in, it seems to really jam the communication in the whole neighbourhood

Yes, it kills my wifi internet box ….
as children say “Dad, what did you do with internet ? …” :p

the only way to recover this is to poweroff the box , so It’s not a good idea to use it.
Now, it works quite well if you don’t use the built-in wifi at the same time, ie do not use bluetooth and wifi, only bluetooth.

The only Bluetooth device we (i.e. @tomlohave) have tried is the WiiRemote. However, I *think* he uses a generic USB-attached Bluetooth radio instead of the Cubox-i built-in.

Yes for quick tests I use a dongle with a wiiRemote.
But as already said, it works well using only built-in bluetooth on cuboxi or utilite devices

[Author]

Posts