I don't know about the getting started guide, but here is how I got bluetooth working for my project:
rfkill unblock bluetooth
hciconfig hci0 up
you can use the command 'rfkill list' to show the state of the various RF interfaces.
Note: the above assumes you are using linux image ww28 or later!
Bluetooth: How scan and connect a device
- First you have to enable bluetooth as described, it is needed a simple command:root@edison:~# bcm_bluetooth_control on --> from WW28 this has been replaced by just 'rfkill unblock bluetooth'
- Now enter the BlueZ command line utilityroot@edison:~# bluetoothctl
[NEW] Controller 43:34:1B:00:1F:AC edison [default] --> this will indicate you that the bluetooth controller has been found
- you can register an agent and set it as default one (an agent let handle all actions like pairing when user interaction is needed); option are 'KeyboardDisplay', 'DisplayOnly', 'DisplayYesNo', 'KeyboardOnly', 'NoInputNoOutput'. This settings will let emulate different capabilities of the application developped by end user for bluetooth using Edison board.[bluetooth]# agent KeyboardDisplay --> better register agent with I/O cap to be able to enter PIN or display passkey to enter on peer device like keyboardAgent registered
Default agent request successful
- now you can perform a scan (eventually you can stop it or not after you get desired device listed)[bluetooth]# scan onDiscovery started
[CHG] Controller 43:34:1B:00:1F:AC Discovering: yes
[NEW] Device 70:F3:95:C7:C7:2D 70-F3-95-C7-C7-2D
[NEW] Device E0:2A:82:CB:62:9B E0-2A-82-CB-62-9B
[NEW] Device 70:F3:95:C7:C5:0C cedric-linux-0
[NEW] Device 70:F3:95:7D:48:EF MONTEILX-MOBL
[NEW] Device F4:B7:E2:F7:14:FD AZOUAOUI-MOBL
[NEW] Device 10:68:3F:57:90:4F Nexus 4
[bluetooth]# scan off
- you can pair the desired device (a confirmation will be needed on peer device, please be sure to have set agent in step 3)[bluetooth]# pair 10:68:3F:57:90:4FAttempting to pair with 10:68:3F:57:90:4F
[CHG] Device 10:68:3F:57:90:4F Connected: yesPairing successful
[CHG] Device 10:68:3F:57:90:4F Modalias: bluetooth:v000Fp1200d1436
[CHG] Device 10:68:3F:57:90:4F UUIDs has unsupported type
[CHG] Device 10:68:3F:57:90:4F Paired: yes
[CHG] Device 10:68:3F:57:90:4F Connected: no
- and trigger connection[bluetooth]# connect 10:68:3F:57:90:4FAttempting to connect to 10:68:3F:57:90:4F
[CHG] Device 10:68:3F:57:90:4F Connected: yes
NOTE: bluetooth connection is established at profile level so the involved devices have to support profiles (and roles if applicable) that let them connect. Currently in release 1 we have validated PAN and HID so connection will work only on this profile. For HID there is not need to register the profile at application layer (HID host in implemented at kernel level) so a basic 'discovery' + 'pair' + 'connect' to an HID peripheral device will lead to a connection. For PAN we have validated GN and NAP role so to have a connection we need first to register this profile at application layer (for instance using bluez scripts as described) and then connect to a device supporting PAN user role (like the 'Nexus 4 ' example in this page)
- you may additionally check supported service on peer device[bluetooth]# info 10:68:3F:57:90:4FDevice 10:68:3F:57:90:4F
Name: Nexus 4
Alias: Nexus 4
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: PANU (00001115-0000-1000-8000-00805f9b34fb)
UUID: NAP (00001116-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
- to check additional capabilities of BlueZ command line check its help[bluetooth]# help
- once done you can exit from the utility[bluetooth]# exit
Great work, just need a little help. When I get to the "scan on" bit nothing is displaying in here. I made the default-agent to NoInputNoOutput and KeyboardDisplay and both have no luck.
This may be a month to late, but I ran into the same issue you did when trying to pair the Edison with my Galaxy Note.
Make sure the Bluetooth is discoverable on the device you are attempting to pair with the Edison. This was why the Edison was unable to see anything when doing a scan.
@MPayne can you help me?