2002-03-09 05:12:35 +08:00
|
|
|
.TH HCIATTACH 8 "Jan 22 2002" BlueZ "Linux System Administration"
|
|
|
|
|
.SH NAME
|
|
|
|
|
hciattach \- attach serial devices via UART HCI to BlueZ stack
|
|
|
|
|
.SH SYNOPSIS
|
|
|
|
|
.B hciattach
|
2006-06-02 02:36:20 +08:00
|
|
|
.RB [\| \-n \|]
|
|
|
|
|
.RB [\| \-p \|]
|
2009-06-27 23:01:40 +08:00
|
|
|
.RB [\| \-t
|
2006-06-02 02:36:20 +08:00
|
|
|
.IR timeout \|]
|
2002-03-09 05:12:35 +08:00
|
|
|
.I tty
|
2006-06-02 02:36:20 +08:00
|
|
|
.IR type \||\| id
|
2002-03-09 05:12:35 +08:00
|
|
|
.I speed
|
|
|
|
|
.I flow
|
2007-04-26 07:09:02 +08:00
|
|
|
.I bdaddr
|
2002-03-09 05:12:35 +08:00
|
|
|
.SH DESCRIPTION
|
|
|
|
|
.LP
|
|
|
|
|
Hciattach is used to attach a serial UART to the Bluetooth stack as HCI
|
|
|
|
|
transport interface.
|
|
|
|
|
.SH OPTIONS
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B \-n
|
2003-02-12 20:34:16 +08:00
|
|
|
Don't detach from controlling terminal.
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B \-p
|
2003-02-12 20:34:16 +08:00
|
|
|
Print the PID when detaching.
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.BI \-t " timeout"
|
2003-02-12 20:34:16 +08:00
|
|
|
Specify an initialization timeout. (Default is 5 seconds.)
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.I tty
|
2002-03-09 05:12:35 +08:00
|
|
|
This specifies the serial device to attach. A leading
|
|
|
|
|
.B /dev
|
|
|
|
|
can be omitted. Examples:
|
|
|
|
|
.B /dev/ttyS1
|
|
|
|
|
.B ttyS2
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.IR type \||\| id
|
2002-03-09 05:12:35 +08:00
|
|
|
The
|
2006-06-02 02:36:20 +08:00
|
|
|
.I type
|
2002-03-09 05:12:35 +08:00
|
|
|
or
|
2006-06-02 02:36:20 +08:00
|
|
|
.I id
|
2002-03-09 05:12:35 +08:00
|
|
|
of the Bluetooth device that is to be attached, i.e. vendor or other device
|
|
|
|
|
specific identifier. Currently supported types are
|
|
|
|
|
.RS
|
|
|
|
|
.TP
|
|
|
|
|
.B type
|
|
|
|
|
.B description
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B any
|
2002-03-09 05:12:35 +08:00
|
|
|
Unspecified HCI_UART interface, no vendor specific options
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B ericsson
|
2002-03-09 05:12:35 +08:00
|
|
|
Ericsson based modules
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B digi
|
2002-03-09 05:12:35 +08:00
|
|
|
Digianswer based cards
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B xircom
|
2002-03-09 05:12:35 +08:00
|
|
|
Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B csr
|
2002-03-09 05:12:35 +08:00
|
|
|
CSR Casira serial adapter or BrainBoxes serial dongle (BL642)
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B bboxes
|
2002-03-09 05:12:35 +08:00
|
|
|
BrainBoxes PCMCIA card (BL620)
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B swave
|
2002-03-09 05:12:35 +08:00
|
|
|
Silicon Wave kits
|
2002-11-16 09:44:53 +08:00
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B bcsp
|
2002-11-16 09:44:53 +08:00
|
|
|
Serial adapters using CSR chips with BCSP serial protocol
|
2002-03-09 05:12:35 +08:00
|
|
|
.RE
|
|
|
|
|
|
|
|
|
|
Supported IDs are (manufacturer id, product id)
|
|
|
|
|
.RS
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B 0x0105, 0x080a
|
2002-03-09 05:12:35 +08:00
|
|
|
Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.B 0x0160, 0x0002
|
2002-03-09 05:12:35 +08:00
|
|
|
BrainBoxes PCMCIA card (BL620)
|
|
|
|
|
.RE
|
|
|
|
|
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.I speed
|
2002-03-09 05:12:35 +08:00
|
|
|
The
|
2006-06-02 02:36:20 +08:00
|
|
|
.I speed
|
2002-03-09 05:12:35 +08:00
|
|
|
specifies the UART speed to use. Baudrates higher than 115.200bps require
|
|
|
|
|
vendor specific initializations that are not implemented for all types of
|
|
|
|
|
devices. In general the following speeds are supported:
|
|
|
|
|
|
|
|
|
|
.B 9600, 19200, 38400, 57600, 115200, 230400, 460800, 921600
|
|
|
|
|
|
|
|
|
|
Supported vendor devices are automatically initialised to their respective
|
|
|
|
|
best settings.
|
|
|
|
|
.TP
|
2006-06-02 02:36:20 +08:00
|
|
|
.I flow
|
2002-03-09 05:12:35 +08:00
|
|
|
If the keyword
|
2006-06-02 02:36:20 +08:00
|
|
|
.I flow
|
2002-03-09 05:12:35 +08:00
|
|
|
is appended to the list of options then hardware flow control is forced on
|
|
|
|
|
the serial link (
|
|
|
|
|
.B CRTSCTS
|
|
|
|
|
). All above mentioned device types have
|
|
|
|
|
.B flow
|
|
|
|
|
set by default. To force no flow control use
|
|
|
|
|
.B noflow
|
|
|
|
|
instead.
|
|
|
|
|
|
2007-04-26 07:09:02 +08:00
|
|
|
.TP
|
|
|
|
|
.I bdaddr
|
2009-06-27 23:01:40 +08:00
|
|
|
The
|
2007-04-26 07:09:02 +08:00
|
|
|
.I bdaddr
|
2009-06-27 23:01:40 +08:00
|
|
|
specifies the Bluetooth Address to use. Some devices (like the STLC2500)
|
|
|
|
|
do not store the Bluetooth address in hardware memory. Instead it must
|
2007-04-26 07:09:02 +08:00
|
|
|
be uploaded during the initialization process. If this argument
|
|
|
|
|
is specified, then the address will be used to initialize the device.
|
|
|
|
|
Otherwise, a default address will be used.
|
|
|
|
|
|
2002-03-09 05:12:35 +08:00
|
|
|
.SH AUTHORS
|
|
|
|
|
Written by Maxim Krasnyansky <maxk@qualcomm.com>
|
|
|
|
|
.PP
|
2003-02-12 20:34:16 +08:00
|
|
|
Manual page by Nils Faerber <nils@kernelconcepts.de>
|
