meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux:bluetooth:bluez:btattach [2025/04/11 08:30] – niziaklinux:bluetooth:bluez:btattach [2025/04/11 12:23] (current) – niziak
Line 1: Line 1:
 ====== btattach ====== ====== btattach ======
  
-Is not working in ''3wire'' aka ''H:5'' mode.+hci/btattach flow: 
 +  * bluez (bluetoothd service) is running 
 +  * ''hciattach'' 
 +  * ''hci0'' interface appears 
 +  * bluez is configuring it 
 +    * NOTE: w/o blues try to call ''hciconfig hci0 up'' returns error: ''Can't init device hci0: Cannot assign requested address (99)'' 
 +  * now possible put inteface up: 
 +    * ''hciconfig hci0 up'' or  
 +    * ''bluetoothctl -- power on'' 
 + 
 +===== EUNATCH (Protocol driver not attached) ===== 
 + 
 +Search tags:  
 +  * ''EUNATCH (Protocol driver not attached)'' 
 +  * ''Failed to get device id: Protocol driver not attached) = 54'' 
 +  * ''No controller attached) = 23'' 
 + 
 +Btattach is not working in ''3wire'' aka ''H:5'' mode.
  
 <code bash> <code bash>
Line 49: Line 66:
 write(1, "Device setup complete\n", 22Device setup complete) = 22 write(1, "Device setup complete\n", 22Device setup complete) = 22
 </code> </code>
 +
 +===== Headline =====
 +
 +It is not working since 2017 :(
 +  * [[https://www.spinics.net/lists/linux-bluetooth/msg72050.html|btattach and 3wire doesn't work]]
 +
 +Issue was posted on mailing list but without any deep look from developer.
 +Problem is not related to connected nrF52 device. 
 +It can be reproduced on any UART. Problem is during UART configuration before any data transmission!
 +
 +