Hello, this is my current setup:
- nRF52840 acting as NUS peripheral, with properly configured coded phy (nRF SDK)
- nRF5340 acting as NUS central, with properly configured coded phy (nRF Connect SDK)
I have those testing devices:
- OnePlus 6T
- another nRF52840 using NUS central with properly configured coded phy (nRF SDK)
The problem:
I'm trying to connect with nRF5340 via coded phy to nRF52840 NUS service. nRF5340 finds the nRF52's advertising, but connection fails:
*** Booting Zephyr OS build v2.4.99-ncs2 *** [00:00:00.418,457] [0m<inf> fs_nvs: 2 Sectors of 4096 bytes[0m [00:00:00.418,457] [0m<inf> fs_nvs: alloc wra: 0, fd8[0m [00:00:00.418,457] [0m<inf> fs_nvs: data wra: 0, 1c[0m [00:00:00.441,802] [1;33m<wrn> bt_hci_core: ECC HCI commands not available[0m [00:00:00.441,802] [0m<inf> bt_hci_core: No ID address. App must call settings_load()[0m [00:00:00.441,802] [0m<inf> central_uart: Bluetooth initialized[0m [00:00:00.444,732] [0m<inf> central_uart: Scan module initialized[0m [00:00:00.444,732] [0m<inf> central_uart: NUS Client module initialized[0m Starting Bluetooth Central UART example [00:00:00.448,883] [0m<inf> central_uart: Scanning successfully started[0m [00:00:00.482,482] [0m<inf> central_uart: Filters matched. Address: F9:XX:4A:XX:XX:XX (random) connectable: 1[0m [00:00:03.485,382] [0m<inf> central_uart: Failed to connect to F9:XX:4A:XX:XX:XX (random) (2)[0m
So I decided to make following tests:
- nRF52840 (peripheral) <===> nRF52840 (central) (nRF SDK, no Zephyr) - works absolutely good
- nRF52840 (peripheral) <===> OnePlus 6T (central) - bit hard to connect, but else good (phone's fault)
- nRF52840 (peripheral) <===> nRF5340 (central) but using normal PHY (no coded) - works good
Thus, I see the problem is in nRF5340 configuration. In attachment, I'm sending my edited UART NUS central code + .config for app and HCI RPMSG.
In those configs, I enabled coded phy support and also extended advertising support
8304.sample.zip
Thanks,
with regards,
Marek Kraus
