1HCIATTACH(1) Linux System Administration HCIATTACH(1)
2
3
4
6 hciattach - attach serial devices via UART HCI to BlueZ stack
7
9 hciattach [OPTIONS] <tty> <type|id> [speed] [flow] [sleep] [bdaddr]
10
11 hciattach -1
12
14 hciattach(1) is used to attach a serial UART to the Bluetooth stack as
15 HCI transport interface.
16
18 -i Send break
19
20 -n Don't detach from controlling terminal.
21
22 -p Print the PID when detaching.
23
24 -t timeout
25 Specify an initialization timeout. Default is 5 seconds.
26
27 -s speed
28 Specify an initial speed instead of the hardware default.
29
30 -l List all available configurations.
31
32 -r Set the HCI device into raw mode. The kernel and bluetooth dae‐
33 mon will ignore it.
34
35 -h, --help
36 Show help options
37
39 show This specifies the serial device to attach. A leading /dev can
40 be omitted.
41
42 Examples: /dev/ttyS1 ttyS2
43
44 type|id
45 The type or id of the Bluetooth device that is to be attached,
46 i.e. vendor or other device specific identifier. Currently sup‐
47 ported types are
48
49 ┌─────────┬────────────────────────────┐
50 │type │ Description │
51 ├─────────┼────────────────────────────┤
52 │any │ Unspecified HCI_UART in‐ │
53 │ │ terface, no vendor spe‐ │
54 │ │ cific options │
55 ├─────────┼────────────────────────────┤
56 │ericsson │ Ericsson based modules │
57 ├─────────┼────────────────────────────┤
58 │digi │ Digianswer based cards │
59 ├─────────┼────────────────────────────┤
60 │xircom │ Xircom PCMCIA cards: │
61 │ │ Credit Card Adapter and │
62 │ │ Real Port Adapter │
63 └─────────┴────────────────────────────┘
64
65
66
67 │csr │ CSR Casira serial adapter │
68 │ │ or BrainBoxes serial don‐ │
69 │ │ gle (BL642) │
70 ├─────────┼────────────────────────────┤
71 │bboxes │ BrainBoxes PCMCIA card │
72 │ │ (BL620) │
73 ├─────────┼────────────────────────────┤
74 │swave │ Silicon Wave kits │
75 ├─────────┼────────────────────────────┤
76 │bcsp │ Serial adapters using CSR │
77 │ │ chips with BCSP serial │
78 │ │ protocol │
79 ├─────────┼────────────────────────────┤
80 │ath3k │ Atheros AR300x based se‐ │
81 │ │ rial Bluetooth device │
82 ├─────────┼────────────────────────────┤
83 │intel │ Intel Bluetooth device │
84 └─────────┴────────────────────────────┘
85
86 ┌──────────────────────────────┬────────────────────────────┐
87 │Supported ID │ Description │
88 │(manufacturer id, product id) │ │
89 ├──────────────────────────────┼────────────────────────────┤
90 │0x0105, 0x080a │ Xircom PCMCIA cards: │
91 │ │ Credit Card Adapter and │
92 │ │ Real Port Adapter │
93 ├──────────────────────────────┼────────────────────────────┤
94 │0x0160, 0x0002 │ BrainBoxes PCMCIA card │
95 │ │ (BL620) │
96 └──────────────────────────────┴────────────────────────────┘
97
98 speed The speed specifies the UART speed to use. Baudrates higher than
99 115200bps require vendor specific initializations that are not
100 implemented for all types of devices. In general the following
101 speeds are supported:
102
103 Supported vendor devices are automatically initialised to their
104 respective best settings.
105
106 ┌───────┐
107 │9600 │
108 ├───────┤
109 │19200 │
110 ├───────┤
111 │38400 │
112 ├───────┤
113 │57600 │
114 ├───────┤
115 │115200 │
116 ├───────┤
117 │230400 │
118 ├───────┤
119 │460800 │
120 ├───────┤
121 │921600 │
122 └───────┘
123
124 flow If the flow is appended to the list of options then hardware
125 flow control is forced on the serial link (CRTSCTS). All above
126 mentioned device types have flow set by default. To force no
127 flow control use noflow instead.
128
129 sleep|nosleep
130 Enables hardware specific power management feature. If sleep is
131 appended to the list of options then this feature is enabled. To
132 disable this feature use nosleep instead. All above mentioned
133 device types have nosleep set by default.
134
135 Note: This option will only be valid for hardware which support
136 hardware specific power management enable option from host.
137
138 bdaddr The bdaddr specifies the Bluetooth Address to use. Some devices
139 (like the STLC2500) do not store the Bluetooth address in hard‐
140 ware memory. Instead it must be uploaded during the initializa‐
141 tion process. If this argument is specified, then the address
142 will be used to initialize the device. Otherwise, a default ad‐
143 dress will be used.
144
146 http://www.bluez.org
147
149 linux-bluetooth@vger.kernel.org
150
152 Maxim Krasnyansky <maxk@qualcomm.com>, Nils Faerber <nils@kernelcon‐
153 cepts.de>
154
156 Free use of this software is granted under ther terms of the GNU Lesser
157 General Public Licenses (LGPL).
158
159
160
161
162BlueZ Jan 22, 2002 HCIATTACH(1)