hciattach(1)
π hciattach(1) β attach serial devices via UART HCI to BlueZ stack π
From the <pink>Linux System Administration</pink> shelf, bestie. This is the hciattach(1) manual page, and it's lowkey iconic for one very specific job: hooking a serial UART into the Bluetooth stack. π¦
β¨ Name β¨
hciattach β attach serial devices via UART HCI to BlueZ stack.
πΈ SYNOPSIS πΈ
hciattach [OPTIONS] <tty> <type|id> [speed] [flow] [sleep] [bdaddr]
hciattach -1
π DESCRIPTION π
Okay so hciattach(1) is used to attach a serial UART to the Bluetooth stack as HCI transport interface. That's the whole vibe: serial device meets Bluetooth stack, and hciattach is the main character making the introduction. π
π« OPTIONS π«
-iβ Send break.-nβ Don't detach from controlling terminal.-pβ Print the PID when detaching.-ttimeout β Specify an initialization timeout. Default is5seconds.-sspeed β Specify an initial speed instead of the hardware default.-lβ List all available configurations.-rβ Set the HCI device into raw mode. The kernel and bluetooth daemon will ignore it.-h,--helpβ Show help options.
π§ ARGUMENTS π§
showβ This specifies the serial device to attach. A leading/devcan be omitted.- Examples:
/dev/ttyS1ttyS2
- Examples:
type|idβ The type or id of the Bluetooth device that is to be attached, i.e. vendor or other device specific identifier. Currently supported types are:anyβ UnspecifiedHCI_UARTinterface, no vendor specific optionsericssonβ Ericsson based modulesdigiβ Digianswer based cardsxircomβ Xircom PCMCIA cards: Credit Card Adapter and Real Port Adaptercsrβ CSR Casira serial adapter or BrainBoxes serial dongle (BL642)bboxesβ BrainBoxes PCMCIA card (BL620)swaveβ Silicon Wave kitsbcspβ Serial adapters using CSR chips with BCSP serial protocolath3kβ AtherosAR300xbased serial Bluetooth deviceintelβ Intel Bluetooth device
Supported ID (manufacturer id, product id):
0x0105,0x080aβ Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter0x0160,0x0002β BrainBoxes PCMCIA card (BL620)
speedβ The speed specifies the UART speed to use. Baudrates higher than115200bpsrequire vendor specific initializations that are not implemented for all types of devices. In general the following speeds are supported:9600192003840057600115200230400460800921600
Supported vendor devices are automatically initialised to their respective best settings.
flowβ If the flow is appended to the list of options then hardware flow control is forced on the serial link (CRTSCTS). All above mentioned device types have flow set by default. To force no flow control usenoflowinstead.sleep|nosleepβ Enables hardware specific power management feature. Ifsleepis appended to the list of options then this feature is enabled. To disable this feature usenosleepinstead. All above mentioned device types havenosleepset by default.
Note: This option will only be valid for hardware which support hardware specific power management enable option from host.
bdaddrβ Thebdaddrspecifies the Bluetooth Address to use. Some devices (like theSTLC2500) do not store the Bluetooth address in hardware memory. Instead it must 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.
π RESOURCES π
π REPORTING BUGS π
<linux-bluetooth@vger.kernel.org>
π Author π
Maxim Krasnyansky <maxk@qualcomm.com>, Nils Faerber <nils@kernelconcepts.de>
π Copyright π
Free use of this software is granted under the terms of the GNU Lesser General Public Licenses (LGPL).
Source/version: BlueZ Β· Date: Jan 22, 2002 Β· Page: hciattach(1) β mwah, bestie πβ¨
π¦ where this page comes from
- arch rolling: bluez-deprecated-tools 5.87-2 Β· GPL-2.0-only
- nixpkgs unstable: bluez 5.87
- ubuntu stonking: bluez 5.87-4 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms