This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bluetooth Versioning

Hi,

I have some nRF52840 DK boards and want to develop a system with 5.0 BLE.

But my linux box host has older version:

Bluetooth: Core ver 2.22

My first question is this is Bluetooth 2.22, and the BLE5.0 is Bluetooth: Core ver 5.0? So we are using Core version as Bluetooth Version.

Is possible for Core ver 2.22 program (central) to scan Core version 5.0 advertisements? I believe it will not work. Let me ask in another way: Is it possible for nRF52840 to be programmed so that it can be scanned by Bluetooth 2.22 device?

Thank you,

David

Parents
  • That "Bluetooth: Core" version number tells you...

    NOTHING AT ALL.

    In fact, my Linux box has the same output in dmesg:

    [589393.748891] usb 4-3: Product: BCM20702A0
    [589393.748895] usb 4-3: Manufacturer: Broadcom Corp
    [589393.748897] usb 4-3: SerialNumber: 5CF37061A8B3
    [589394.040583] Bluetooth: Core ver 2.22
    [589394.040583] NET: Registered protocol family 31
    [589394.040583] Bluetooth: HCI device and connection manager initialized
    [589394.040583] Bluetooth: HCI socket layer initialized
    [589394.040583] Bluetooth: L2CAP socket layer initialized
    [589394.040583] Bluetooth: SCO socket layer initialized
    [589394.070820] usbcore: registered new interface driver btusb
    [589394.197798] Bluetooth: hci0: BCM: chip id 63
    [589394.220747] Bluetooth: hci0: BCM20702A
    [589394.223698] Bluetooth: hci0: BCM20702A1 (001.002.014) build 000

    But this is with a connected BT4.0 USB stick, which can talk to NRF devices via bluetooth low energy.

    We would need to know what hardware is actually in your Linux box.

Reply
  • That "Bluetooth: Core" version number tells you...

    NOTHING AT ALL.

    In fact, my Linux box has the same output in dmesg:

    [589393.748891] usb 4-3: Product: BCM20702A0
    [589393.748895] usb 4-3: Manufacturer: Broadcom Corp
    [589393.748897] usb 4-3: SerialNumber: 5CF37061A8B3
    [589394.040583] Bluetooth: Core ver 2.22
    [589394.040583] NET: Registered protocol family 31
    [589394.040583] Bluetooth: HCI device and connection manager initialized
    [589394.040583] Bluetooth: HCI socket layer initialized
    [589394.040583] Bluetooth: L2CAP socket layer initialized
    [589394.040583] Bluetooth: SCO socket layer initialized
    [589394.070820] usbcore: registered new interface driver btusb
    [589394.197798] Bluetooth: hci0: BCM: chip id 63
    [589394.220747] Bluetooth: hci0: BCM20702A
    [589394.223698] Bluetooth: hci0: BCM20702A1 (001.002.014) build 000

    But this is with a connected BT4.0 USB stick, which can talk to NRF devices via bluetooth low energy.

    We would need to know what hardware is actually in your Linux box.

Children
No Data
Related