Hi Bastien, On Tue, Nov 7, 2023 at 9:47 AM Bastien Nocera <hadess@xxxxxxxxxx> wrote: > > On Mon, 2023-11-06 at 18:06 +0100, Christoph Schweers wrote: > > > > Bastien Nocera <hadess@xxxxxxxxxx> schrieb am Mo., 6. Nov. 2023, > > 15:35: > > > Hey, > > > > > > I bought the Laird Connectivity Bluetooth LE-only PTS dongle listed > > > on: > > > https://support.bluetooth.com/hc/en-us/articles/360049018492-What-is-the-difference-between-the-Profile-Tuning-Suite-PTS-Dongles > > > - > > > as I was hoping to have an easy to use Bluetooth LE only device for > > > testing. > > > > > > But the device only shows up as a serial device under kernel 6.5 > > > from > > > my distribution. > > > > > > Is there anything specific that needs to be done for that device to > > > be > > > usable as a Bluetooth adapter under Linux? Or does it only work > > > with > > > the PTS? > > > > > > I spotted the ability to run specific software on the micro- > > > controller > > > itself when powered on, but nothing specific to using it as an > > > adapter: > > > http://assets.lairdtech.com/home/brandworld/files/BL654%20USB%20Dongle%20User%20Guide%20v1_0.pdf > > > > > > Full lsusb output for that device: > > > Bus 001 Device 018: ID 1915:521f Nordic Semiconductor ASA Nordic > > > Open > > > DFU Bootloader > > > Device Descriptor: > > > bLength 18 > > > bDescriptorType 1 > > > bcdUSB 2.00 > > > bDeviceClass 0 > > > bDeviceSubClass 0 > > > bDeviceProtocol 0 > > > bMaxPacketSize0 64 > > > idVendor 0x1915 Nordic Semiconductor ASA > > > idProduct 0x521f > > > bcdDevice 1.00 > > > iManufacturer 1 Laird Connectivity > > > iProduct 2 Nordic Open DFU Bootloader > > > iSerial 3 E1BB9211FA41 > > > bNumConfigurations 1 > > > Configuration Descriptor: > > > bLength 9 > > > bDescriptorType 2 > > > wTotalLength 0x004b > > > bNumInterfaces 2 > > > bConfigurationValue 1 > > > iConfiguration 4 Default configuration > > > bmAttributes 0xc0 > > > Self Powered > > > MaxPower 100mA > > > Interface Association: > > > bLength 8 > > > bDescriptorType 11 > > > bFirstInterface 0 > > > bInterfaceCount 2 > > > bFunctionClass 2 Communications > > > bFunctionSubClass 2 Abstract (modem) > > > bFunctionProtocol 0 > > > iFunction 0 > > > Interface Descriptor: > > > bLength 9 > > > bDescriptorType 4 > > > bInterfaceNumber 0 > > > bAlternateSetting 0 > > > bNumEndpoints 1 > > > bInterfaceClass 2 Communications > > > bInterfaceSubClass 2 Abstract (modem) > > > bInterfaceProtocol 0 > > > iInterface 0 > > > CDC Header: > > > bcdCDC 1.10 > > > CDC Call Management: > > > bmCapabilities 0x03 > > > call management > > > use DataInterface > > > bDataInterface 1 > > > CDC ACM: > > > bmCapabilities 0x02 > > > line coding and serial state > > > CDC Union: > > > bMasterInterface 0 > > > bSlaveInterface 1 > > > Endpoint Descriptor: > > > bLength 7 > > > bDescriptorType 5 > > > bEndpointAddress 0x82 EP 2 IN > > > bmAttributes 3 > > > Transfer Type Interrupt > > > Synch Type None > > > Usage Type Data > > > wMaxPacketSize 0x0040 1x 64 bytes > > > bInterval 16 > > > Interface Descriptor: > > > bLength 9 > > > bDescriptorType 4 > > > bInterfaceNumber 1 > > > bAlternateSetting 0 > > > bNumEndpoints 2 > > > bInterfaceClass 10 CDC Data > > > bInterfaceSubClass 0 > > > bInterfaceProtocol 0 > > > iInterface 0 > > > Endpoint Descriptor: > > > bLength 7 > > > bDescriptorType 5 > > > bEndpointAddress 0x81 EP 1 IN > > > bmAttributes 2 > > > Transfer Type Bulk > > > Synch Type None > > > Usage Type Data > > > wMaxPacketSize 0x0040 1x 64 bytes > > > bInterval 0 > > > Endpoint Descriptor: > > > bLength 7 > > > bDescriptorType 5 > > > bEndpointAddress 0x01 EP 1 OUT > > > bmAttributes 2 > > > Transfer Type Bulk > > > Synch Type None > > > Usage Type Data > > > wMaxPacketSize 0x0040 1x 64 bytes > > > bInterval 0 > > > Device Status: 0x0001 > > > Self Powered > > > > > > Cheers > > > > This dongle must be pre-programmed with a special firmware to work as > > a PTS dongle. > > https://support.bluetooth.com/hc/en-us/articles/360049019732-How-to-upgrade-the-firmware-of-your-PTS-Dongle > > - > > > > I updated the firmware using the PTS firmware upgrader, and it still > doesn't show up as a Bluetooth adapter under Linux: > > Nov 07 15:44:11 classic kernel: usb 1-8: new full-speed USB device number 22 using xhci_hcd > Nov 07 15:44:11 classic kernel: usb 1-8: New USB device found, idVendor=1915, idProduct=521f, bcdDevice= 1.00 > Nov 07 15:44:11 classic kernel: usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > Nov 07 15:44:11 classic kernel: usb 1-8: Product: nRF52 USB Product > Nov 07 15:44:11 classic kernel: usb 1-8: Manufacturer: Nordic Semiconductor > Nov 07 15:44:11 classic kernel: usb 1-8: SerialNumber: E1BB9211FA41 > Nov 07 15:44:11 classic kernel: cdc_acm 1-8:1.0: ttyACM0: USB ACM device > > It shows up as: > Bus 001 Device 023: ID 1915:521f Nordic Semiconductor ASA nRF52 USB Product > in lsusb. Perhaps it needs to be added to be btusb if it does support a standard HCI interface. (I'm currently on vacation with limited time to assist everyone.) -- Luiz Augusto von Dentz
