I build an example of HCI-USB / HCI-UART, not fundamentally, since the result is the same. The PHY does not selects properly, and scan a LE, but I need Long Range (Coded PHY)

RE: I build an example of HCI-USB / HCI-UART, not fundamentally, since the result is the same. The PHY does not selects properly, and scan a LE, but I need Long Range (Coded PHY)

AlexandrX — Wed, 21 Apr 2021 09:03:36 GMT

Is that all technical support?

RE: I build an example of HCI-USB / HCI-UART, not fundamentally, since the result is the same. The PHY does not selects properly, and scan a LE, but I need Long Range (Coded PHY)

AlexandrX — Fri, 16 Apr 2021 07:36:49 GMT

[quote userid="2111" url="~/f/nordic-q-a/73991/i-build-an-example-of-hci-usb-hci-uart-not-fundamentally-since-the-result-is-the-same-the-phy-does-not-selects-properly-and-scan-a-le-but-i-need-long-range-coded-phy/305101#305101"]It's important CODED PHY is not set at the same time as regular 1M PHY (since it can't do both at the same time).[/quote]

Of course, I know that only one PHY can work at the moment, proper for this and there is a "phy" command in btmgmt to select an active phy, but it does not work there, only through hcitool!

Example:

[hci0]# phy LE1MTX LE1MRX
PHY Configuration successfully set

Ok, another phys:

[hci0]# phy LECODEDTX LECODEDRX
Could not set PHY Configuration with status 0x0d (Invalid Parameters)
[hci0]# phy LE2MTX LE2MRX
Could not set PHY Configuration with status 0x0d (Invalid Parameters)

- FAIL.

It's weird, isn't it? Since:

[hci0]# phy
Supported phys: LE1MTX LE1MRX LE2MTX LE2MRX LECODEDTX LECODEDRX
Configurable phys: LE2MTX LE2MRX LECODEDTX LECODEDRX

But you can only install LE1MRX/TX, why?

RE: I build an example of HCI-USB / HCI-UART, not fundamentally, since the result is the same. The PHY does not selects properly, and scan a LE, but I need Long Range (Coded PHY)

AlexandrX — Thu, 15 Apr 2021 13:24:17 GMT

"And you can confirm that CODED PHY works when using"

- works, but not pair, only find and display mac's, zephyr slack answer:

"Connection Initiation over Coded PHY is a work in progress. Double-checking with..."

and

"Yes, Connection Initiation to extended advertising is not supported, and is work in progress."

Any ideas?? )

RE: I build an example of HCI-USB / HCI-UART, not fundamentally, since the result is the same. The PHY does not selects properly, and scan a LE, but I need Long Range (Coded PHY)

Kenneth — Thu, 15 Apr 2021 12:49:39 GMT

And you can confirm that CODED PHY works when using the zephyr controller but not the softdevice controller? It's important CODED PHY is not set at the same time as regular 1M PHY (since it can't do both at the same time).

Just want to make sure I am not missing anything here.

Kenneth

RE: I build an example of HCI-USB / HCI-UART, not fundamentally, since the result is the same. The PHY does not selects properly, and scan a LE, but I need Long Range (Coded PHY)

AlexandrX — Thu, 15 Apr 2021 12:40:03 GMT

Yes, that's right, no matter what PHY I put, it only looks for BLE... It is strange that it shows that the CODED PHY is configured, but it only searches for BLE, Long Range does not even display in the results...

RE: I build an example of HCI-USB / HCI-UART, not fundamentally, since the result is the same. The PHY does not selects properly, and scan a LE, but I need Long Range (Coded PHY)

Kenneth — Thu, 15 Apr 2021 11:50:48 GMT

Regarding filtering duplicates, this is not supported (as of today at least), as described here:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrfxlib/softdevice_controller/limitations.html

However I am not sure why CODED PHY does not work, do I understand it correctly that in both your cases (hci_usb and hci_lpuart) you are actually receiving regular advertisement even if you configure CODED PHY?

RE: I build an example of HCI-USB / HCI-UART, not fundamentally, since the result is the same. The PHY does not selects properly, and scan a LE, but I need Long Range (Coded PHY)

AlexandrX — Wed, 14 Apr 2021 12:58:49 GMT

I also want to add that the example from "v1. 5. 1-rc1\nrf\samples\bluetooth\hci_lpuart" does not work. The same search curve. And if CODED_PHY is explicitly selected, it still searches only for ordinary BLE devices, BLE LR does not even see it!