Re: Getting started with BLE device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I got a little farther. The following commands reveal something:

root@linaro-alip:/home/rmann# rfkill block bluetooth
root@linaro-alip:/home/rmann# rfkill unblock bluetooth
root@linaro-alip:/home/rmann# hciattach -t 30 /dev/ttymxc2 texas 115200 flow
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_7.6.15.bts
Loaded BTS script version 1
texas: changing baud rate to 3000000, flow control to 1
Device setup complete
root@linaro-alip:/home/rmann# hcitool scan
Scanning ...
    80:56:F2:FF:FF:5B   GRETCHEN-THINK
    9C:2A:70:86:00:25   MP_THINKPAD_6
    3C:77:E6:EE:E9:9F   MP_ACCOUNTANT
    7C:E9:D3:E6:68:4D   MP_THINKPAD_4
    60:D8:19:B6:9B:B4   FORGE


On May 2, 2014, at 12:02 , Sejo Ruiz <sejoruiz@xxxxxxxxx> wrote:

> Hi Rick.
> First of all, you should make sure that the device is recognized as a BT
> device. Run hciconfig as sudo user to see if it returns something as
> hci0. If you can see it, then you can do hciconfig hci0 up to set up the
> interface and start playing. If not, then you could try to do lsusb and
> see what devices are connected to the USB. If you cannot see your device
> there, or something goes wrong, you can always try to check what is
> going on by plugging the device off and on again and then type dmesg |
> tail. Finally, make sure the bluetooth daemon is running. You can do
> that by executing /etc/init.d/bluetoothd status (I'm not sure about this
> last one)
> NOTE: I suggest to execute all the commands with sudo.
> 


-- 
Rick



Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux