bluetooth usecase

最新推荐文章于 2024-01-23 18:16:13 发布
最新推荐文章于 2024-01-23 18:16:13 发布
阅读量1.9k 收藏
点赞数 1
分类专栏： bluetooth 文章标签： linux kernel bluetooth
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/leougao/article/details/22741817
版权
 bluetooth4.0-usecase.txt

Keyboard:  6C:5D:63:00:93:F8    Bluetooth Keyboard
headphone: 00:0D:FD:4B:53:B6    Motorola S305

================================================================================
1  Build the rootfs with bluetooth.
================================================================================

Build wrlinux4.3 with feature/bluetooth


================================================================================
2  Start and configure bluetooth devices.
================================================================================

#:/root> vi /etc/bluetooth/main.conf ：
Name = bluez4
PageTimeout = 65535
AttributeServer = true

#:/root> (all the following commands in turn to start/restart bt)

rm -rf /var/lib/bluetooth/*
bluetoothd
hciconfig hci0 noencrypt
hciconfig hci0 piscan
hciconfig hci0 name "bluez4"
hciconfig hci0 pageto 65535
sdptool add a2snk
sdptool add a2src
sdptool add avrct
sdptool add avrtg
sdptool add hf
sdptool add hs
hciconfig hci0 class 0x200404

#:/root> hciconfig -a
hci0:    Type: BR/EDR  Bus: USB
    BD Address: C4:85:08:02:C4:0B  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:126829 acl:64 sco:0 events:17450 errors:0
    TX bytes:10046345 acl:35012 sco:0 commands:127 errors:0
    Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH HOLD SNIFF PARK
    Link mode: SLAVE ACCEPT
    Name: 'bluez4'
    Class: 0x200404
    Service Classes: Audio
    Device Class: Audio/Video, Device conforms to the Headset profile
    HCI Version: 4.0 (0x6)  Revision: 0x1ebd
    LMP Version: 4.0 (0x6)  Subversion: 0xfc00
    Manufacturer: Intel Corp. (2)

================================================================================
3  Obex Push/Recieve file
================================================================================

Bind device in PC host after start simple-agent, then enter yes to confirm.

#:/root> simple-agent
Agent registered
RequestConfirmation (/org/bluez/18475/hci0/dev_00_1A_7D_DA_71_11, 452347)
Confirm passkey (yes/no): yes

^CTraceback (most recent call last):
  File "/usr/bin/simple-agent", line 127, in <module>
    mainloop.run()
KeyboardInterrupt


#:/root> sdptool browse 00:1A:7D:DA:71:11
...
Service Name: Bluetooth Object Push
Service RecHandle: 0x10021
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 3
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100
...

#:/root> sdptool add OPUSH
OBEX Object Push service registered

#:/root> obex_test -b 00:1A:7D:DA:71:11 3
Using Bluetooth RFCOMM transport
OBEX Interactive test client/server.
> c
Tx: 80 00 10 10 00 04 00 4A 00 09 4C 69 6E 75 78 00
Connect OK!
Version: 0x10. Flags: 0x00
> p /root/test.txt test.txt
PUT file (local, remote)> name=/root/test.txt, size=11
Going to send 11 bytes
Tx: 82 00 2B C3 00 00 00 0B 01 00 15 00 74 00 65 00 73 00 74 00 2E 00 74 00 78 00
Tx: 74 00 00 49 00 0E 31 32 33 34 35 36 37 38 39 30 0A
PUT successful!
> q


================================================================================
4  A2DP
================================================================================

#:/root> vi /etc/asound.conf ：
# add  these line at the end
pcm.bluetooth{
        type bluetooth
        device 00:0D:FD:4B:53:B6
        profile "hifi"
}


#:/root> vi /etc/bluetooth/audio.conf ：

[General]
Enable=Socket
Master=true
SCORouting=PCM
AutoConnect=true

[Headset]
HFP=true
MaxConnected=2
FastConnectable=true

[A2DP]
SBCSources=1
MPEG12Sources=0


rm -rf /var/lib/bluetooth/*
bluetoothd
hciconfig hci0 noencrypt
hciconfig hci0 piscan
sdptool add a2snk
sdptool add a2src
sdptool add avrct
sdptool add avrtg
sdptool add hf
sdptool add hs
hciconfig hci0 class 0x200404

oot@WR-IntelligentDevice:/root> simple-agent hci0 00:0D:FD:4B:53:B6
RequestPinCode (/org/bluez/4624/hci0/dev_00_0D_FD_4B_53_B6)
Enter PIN Code: 0000
Release
New device (/org/bluez/4624/hci0/dev_00_0D_FD_4B_53_B6)
#:/root> bttest/test-audio connect 00:0D:FD:4B:53:B6
#:/root> hcitool con
Connections:
    < ACL 00:0D:FD:4B:53:B6 handle 35 state 1 lm SLAVE AUTH ENCRYPT
#:/root> aplay -D bluetooth Drenched.wav
Playing WAVE 'Drenched.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

================================================================================
5  HID
================================================================================

#:/root> simple-agent hci0 6C:5D:63:00:93:F8
RequestPinCode (/org/bluez/21017/hci0/dev_6C_5D_63_00_93_F8)
Enter PIN Code: 0000  (Enter and press the same code in keyboard and press enter in keyboard)
Release
New device (/org/bluez/21017/hci0/dev_6C_5D_63_00_93_F8)
#:/root> ./bttest/test-input connect 6C:5D:63:00:93:F8
#:/root> hcidump (press any key in keyboard will send ACL data)
HCI sniffer - Bluetooth packet analyzer ver 2.4
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 33 mode 0x00 interval 0
    Mode: Active
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 33 mode 0x02 interval 56
    Mode: Sniff
> ACL data: handle 33 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 0]
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 33 mode 0x00 interval 0
    Mode: Active
> ACL data: handle 33 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 0]
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 33 mode 0x02 interval 56
    Mode: Sniff
> ACL data: handle 33 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 0]
> ACL data: handle 33 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 0]
> ACL data: handle 33 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 0]
> ACL data: handle 33 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 0]
> ACL data: handle 33 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 0]
> ACL data: handle 33 flags 0x02 dlen 14
    L2CAP(d): cid 0x0041 len 10 [psm 0]

================================================================================
6  SPP
================================================================================



================================================================================
7 Low Energy
================================================================================


（remote device）

vi /etc/bluetooth/main.conf
AttributeServer = true

rm -rf /var/lib/bluetooth/*
bluetoothd
hciconfig hci0 up
hciconfig hci0 piscan
hciconfig hci0 -a
hciconfig hci0 leadv  (remote device)


（local device）
vi /etc/bluetooth/main.conf
AttributeServer = true

rm -rf /var/lib/bluetooth/*
bluetoothd
hciconfig hci0 up
hciconfig hci0 piscan
hciconfig hci0 -a
#:/root> hcitool lescan
LE Scan ...
C4:85:08:03:7A:AE (unknown)
C4:85:08:03:7A:AE (unknown)
C4:85:08:03:7A:AE (unknown)
C4:85:08:03:7A:AE (unknown)
^C
#:/root> hcitool lecc C4:85:08:03:7A:AE
Connection handle 34

#:/root> gatttool -i hci0 -b C4:85:08:03:7A:AE --interactive
[   ][C4:85:08:03:7A:AE][LE]> connect
[CON][C4:85:08:03:7A:AE][LE]> primary
[CON][C4:85:08:03:7A:AE][LE]>
attr handle: 0x0001, end grp handle: 0x0008 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0009, end grp handle: 0x000b uuid: 00001803-0000-1000-8000-00805f9b34fb
attr handle: 0x000c, end grp handle: 0x000f uuid: 00001804-0000-1000-8000-00805f9b34fb
attr handle: 0x0010, end grp handle: 0x0010 uuid: 00001801-0000-1000-8000-00805f9b34fb
attr handle: 0x0011, end grp handle: 0x0013 uuid: 00001802-0000-1000-8000-00805f9b34fb
attr handle: 0x0014, end grp handle: 0x0017 uuid: 0000a002-0000-1000-8000-00805f9b34fb
attr handle: 0x0022, end grp handle: 0x002c uuid: 0000a004-0000-1000-8000-00805f9b34fb
attr handle: 0xfffa, end grp handle: 0xfffe uuid: feee74dc-a8de-3196-1149-d43596c00a4f
[CON][C4:85:08:03:7A:AE][LE]> characteristics 0x0010 0x0010
[CON][C4:85:08:03:7A:AE][LE]>
[CON][C4:85:08:03:7A:AE][LE]> char-desc 0x0010 0x0010
[CON][C4:85:08:03:7A:AE][LE]>
handle: 0x0010, uuid: 2800
[CON][C4:85:08:03:7A:AE][LE]> char-read-uuid 2800
[CON][C4:85:08:03:7A:AE][LE]>
handle: 0x0001      value: 00 18

handle: 0x0009      value: 03 18

handle: 0x000c      value: 04 18

handle: 0x0010      value: 01 18

handle: 0x0011      value: 02 18

handle: 0x0014      value: 02 a0

handle: 0x0022      value: 04 a0
[CON][C4:85:08:03:7A:AE][LE]> disconnect
[   ][C4:85:08:03:7A:AE][LE]> exit

/*others for more test*/
#:/root> dbus-send --system --dest=org.bluez --print-reply / org.bluez.Manager.DefaultAdapter | tail -1 | sed 's/^.*"\(.*\)".*$/\1/'
#:/root> dbus-send --system --dest=org.bluez --print-reply / org.bluez.Manager.DefaultAdapter     (to get btadpter)

#:/root> dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/2617/hci1/dev_78_DD_08_A3_A7_52 org.bluez.Proximity.GetProperties
method return sender=:1.62 -> dest=:1.91 reply_serial=2
array [
dict entry(
string "LinkLossAlertLevel"
variant string "none"
)
dict entry(
string "ImmediateAlertLevel"
variant string "none"
)
]

#:/root> dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/2617/hci1/dev_78_DD_08_A3_A7_52 org.bluez.Proximity.SetProperty string:LinkLossAlertLevel variant:string:mild
method return sender=:1.62 -> dest=:1.96 reply_serial=2


-------------------------------------


bluetooth-usecase.txt

bluez-hcidump-2.4-1_WR4.3.0.0.atom-a339188.rpm
btsco-0.4-1_WR4.3.0.0.atom-1a1fa81.rpm
openobex-1.3-1_WR4.3.0.0.atom-f426146.rpm

Keyboard:  6C:5D:63:00:93:F8
headphone: 00:0D:FD:4B:53:B6    Motorola S305

================================================================================
1  Build the rootfs with bluetooth.
================================================================================

Step 01: Build wrlinux4.3 with feature/bluetooth

Step 02: Rebuild the linux kernel with all the bluetooth option selected.

Step 03: Compile openobex-1.3
(configure with --enable-apps --enable-dump --enable-bluetooth --disable-usb)

================================================================================
2  Scan and Bind other bluetooth devices.
================================================================================

Step 01: Insert the Bluetooth USB dongle and check it

#:/root> hciconfig
  hci0:    Type: USB
    BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:1
    DOWN
    RX bytes:0 acl:0 sco:0 events:0 errors:0
    TX bytes:0 acl:0 sco:0 commands:0 errors:0
        
Step 02: Config hci0

#:/root> hciconfig hci0 up
#:/root> hciconfig hci0 piscan
                 

Step 03: scan devices

#:/root> hcitool scan
Scanning ...
    80:B6:86:2A:FD:53    hoxm


Step 04: start bluetooth

#:/root> vi /etc/bluetooth/rfcomm.conf
rfcomm0 {
        # Automatically bind the device at startup
        bind yes;

        # Bluetooth address of the device
        device 80:B6:86:2A:FD:53;

        # RFCOMM channel for the connection
        channel 1;

        # Description of the connection
        comment "hoxm";
}

#:/root> vi /etc/bluetooth/hcid.conf  
        security auto;  #??? user
        passkey "1234"
        
#:/root> service bluetooth start

 
Step 05: bind device  ???

Clear the bind information
#:/root> rm -rf /var/lib/bluetooth/*;
#:/root> /etc/init.d/bluetooth restart

Step 06: browse services supported

#:/root> sdptool browse local
#:/root> sdptool browse 80:B6:86:2A:FD:53

================================================================================
3  Obex Push/Recieve file
================================================================================
#:/root> obex_test -b 80:B6:86:2A:FD:53 12
Using Bluetooth RFCOMM transport
OBEX Interactive test client/server.
> c
Tx: 80 00 10 10 00 04 00 4A 00 09 4C 69 6E 75 78 00
Connect OK!
Version: 0x10. Flags: 0x00
> p /root/test.txt test.log
name=/root/test.txt, size=16
Going to send 16 bytes
Tx: 82 00 3C C3 00 00 00 10 01 00 21 00 2F 00 72 00 6F 00 6F 00 74 00 2F 00 74 00
Tx: 65 00 73 00 74 00 2E 00 74 00 78 00 74 00 00 49 00 13 0A 6F 62 65 78 20 70 75
Tx: 73 68 20 74 65 73 74 0A
PUT successful!
> q

#:/root> sdptool add OPUSH
OBEX Object Push service registered
#:/root> sdptool  browse local
Browsing FF:FF:FF:00:00:00 ...
Service Name: OBEX Object Push
Service RecHandle: 0x10000
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 9
  "OBEX" (0x0008)
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100

#:/root> obex_test -b 00:1F:81:00:02:00 9
Using Bluetooth RFCOMM transport
OBEX Interactive test client/server.
> s

push file and press 's'[ENTER]  to recieve right away!

================================================================================
3  Obex FTP
================================================================================


================================================================================
3  A2DP
================================================================================

sdptool add A2SRC


================================================================================
4  HID
================================================================================
#:/root> hcitool scan
Scanning ...
    6C:5D:63:00:93:F8    Bluetooth Keyboard


================================================================================
E  hcidump debug
================================================================================
hcidump –X –V


How to Use an ESP32 as a Bluetooth Low Energy (BLE)
AI天才研究院
08-11 205
作者：禅与计算机程序设计艺术 1.简介 Bluetooth Low Energy（以下简称 BLE），是一种低功耗、低数据速率、短距离、双向通信的无线传输协议。它使用 2.4GHz 的低频率蓝牙电波进行通讯。通过引入可靠传输层协议 (RTCP)，该协议可以确保数据可靠送达，并且可以检测到接收方丢失的数据
Another How to turn your Pi in a Bluetooth Speaker Tutorial树莓派蓝牙配对 配网
最新发布
南七小僧的学海无涯
07-21 185
【代码】Another How to turn your Pi in a Bluetooth Speaker Tutorial树莓派蓝牙配对 配网。
bluetooth使用
machiner1的专栏
05-25 7315
转：https://wiki.archlinux.org/index.php/Bluetooth Bluetooth Related articles Bluez4Bluetooth mouseBluetooth headsetBlueman Bluetooth is a standard for the short-rang
android蓝牙开发——基本概念
gfdhjf的博客
01-15 607
android蓝牙开发——基本概念
magic 2.0下使用杂牌蓝牙适配器并通过手机gprs上网
Xaero的专栏
12-02 2419
一、.安装 bluez-libs 2.24 http://download.chinaunix.net/download/0001000/990.shtml bluez-utils 2.24 http://download.chinaunix.net/download/0001000/991.shtml 官方网站上有提供3.7版的下载。但经过小弟试验，好像因为3.x版的不支持kdebluetoot
Bluetooth Device Address(BD_ADDR) - 2
guoqx的专栏
01-23 1587
绑定过的设备应能处理可解析的私有地址，或者使用可解析私有地址来创建连接，然后进行接下来的蓝牙连接的身份认证过程。如果双方设备都是可绑定的，某设备为其本地地址生成一个可解析的私有地址，需要向对等设备分发其IRK值。如果设备有多个已存储的 IRK，则设备会对每个已存储的 IRK 重复上述过程，以确定接收到的可解析私有地址是否与已存储的 IRK 相关联，直到其中一个 IRK 的地址解析成功或所有IRK 都已尝试过而未解析成功。一个可解析的随机私有地址是使用与受信任设备共享的密钥而能够"可解析 "的。
hciconfig
Embeded system Development
08-19 6958
<br />hciconfig - HCI device configuration utility<br /> Usage:<br />     hciconfig<br />     hciconfig [-a] hciX [command]<br /> Commands:<br />     up                     Open and initialize HCI device<br />     down                   Close HCI dev
【安全第一】：高通Chi Usecase的数据安全保障策略全览
[【安全第一】：高通Chi Usecase的数据安全保障策略全览](https://duo.com/assets/img/blogv2/bluetooth-sm-protocol.png) 参考资源链接：[高通Chi ISP与Usecase流程深度解析]...
Android Bluetooth源码分析总结 - framework部分
CAESAR的专栏
03-04 2905
Android Bluetooth源码分析总结 -framework部分 本篇主要包括如下内容： 1. 源码目录 2. 类图 3. use case举例 蓝牙服务初始化 打开蓝牙流程 搜索蓝牙流程 4. 应用层开发总结 1，BT framework代码主要位于如下目录： android/frameworks/base/core/java/android/bluetooth andr...
harald：Bluetooth Host Elixir库
02-05
use Nerves Projekt alias Harald.HCI.Commands.LEAdvertising alias Harald.HCI.Events.LEConnectionComplete def start_link do Harald.init() Harald.LE.set_advertising_parameters() Harald.LE.start_...
Ubuntu15.10 执行sdptool add A2SNK没任何提示
02-14 3820
昨天在ubuntu 15.10 调试A2DP SNK 的时候, 执行 sdptool add A2SNK, 发现没任何错误提示， 我以为A2SNK写错了， 结果 sdptool add SP, 还是一样的问题。 执行 echo $, 输出 255(根据经验应该是 return -1),  应该是没成功了。 权限不够？ 加上sudo 还他妈的一样， sdptool del
Android/Bluetooth 初始化流程
热门推荐
为了忘却的记忆
09-10 1万+
<br />=========================Kernel Space=========================<br /> 1. Board power init<br /><br />MACHINE_START<br /> init_machine = comet_init<br /> bt_power_init<br /> bluetooth_power<br /><br /><br /> 2. HCI device/connection manager, socke
android hci设备,android-hci相关操作
weixin_36217480的博客
05-30 583
1 如果是自己手动调式蓝牙，首先将init.rc里面的dbus-daemon跟bluetoothd两个服务都自启动。也就是说将两个服务中有disabled 的部分注释掉。因为disabled的话，它不会启动，而是会在设置里面点击启动时，才会触发服务启动。2 确保这两个服务已经启动bluetooth 1670 1 1984 932800d0014 7ee111c4 S /system/...
bluetooth开发（六）------蓝牙的功能测试（二）
中华田园犬
05-08 5228
newton板已经发布了，下面接着整理我调试的一个小小的方面，蓝牙的功能实现以及测试： 转载请注明出处：http://blog.youkuaiyun.com/wang_zheng_kai 下面是我写的newton开发板中bluetooth阅读文档README的一部分。
【BTStack】BTStack 修改 CSR 4.0 dongle 蓝牙地址
helanzhiying的博客
08-19 887
为了验证电脑一拖 N 蓝牙dongle，买了几个 CSR 4.0 的 dongle，地址都是一样的，为00:1A:7D:DA:71:13，需要对此进行修改。 CSR 是一家 BT 芯片厂商，于 2015 年 8 月被 Qualcomm 收购，在 BTStack 的代码路径下： \btstack\chipset\csr\csr_set_bd_addr.c MSYS2 编译后，在路径 \btstack\port\windows-winusb 下会生成一个 exe 文件 csr_set_bd_addr.
android-bluetooth移植碰到的问题
andyhuabing的专栏
05-07 8467
前段时间移植神念系统需要使用到bluetooth功能，现将移植过程中碰到的问题简要列一下，备忘而已。 1、内核增加配置 make menuconfig -> Networking support -> Bluetooth subsystem support --> 进行选择BT选项，至少选择如下几项： CONFIG_BT=y CONFIG_BT_RFCOMM=y # # Blue
hciconfig - HCI device configuration utility
wanggongzhen1983的专栏
04-27 4035
hciconfig - HCI device configuration utilityUsage: hciconfig hciconfig [-a] hciX [command]Commands: up Open and initialize HCI device down
解决linux下连接蓝牙鼠标的灵敏度(延时问题）
卜夋
10-12 2005
今夜是个高兴的日子，前几天在天猫淘了一个华为蓝牙鼠标，上面写着HUAWEl蓝牙鼠标仅支持Microsoft Windows 10, Windows 8.1,Windows8, Mac OS 10.10,Android 5.0,Android4.4.4及以上系统。 鼠标到货后，我连接上我的 Debian10,这灵敏度慢得跟屎一样，比蜗牛还不如，咨询问客户，问售后，跟煞笔一样啥也不知道（不是我吐槽，是...
基于蓝牙的无线输液报警系统设计及应用解析
The use of Bluetooth technology enables centralized management of multiple infusion monitoring devices by a single master alarm unit, providing flexibility for healthcare workers to move the ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值