I'm currently developing a BLE Long Range application based on Zephyr and the v2.8.0 version of the nRF Connect SDK. The app is based on the following nRF samples: central_hr_coded, peripheral_hr_coded, central_uart and peripheral_uart. BLE LR is used to establish communication between a Central and Peripheral node. The Central node scans for compatible devices while the Peripheral advertises itself. Once the Central node finds the Peripheral node they connect immediately and exchange messages periodically through NUS (Nordic UART Service).
The app was tested succesfully using two nRF52840dks. However, the aim of this project is to establish such communication between two BL654PA_dk (nRF52840 SoC based Dev Kit). Such board contain a PA/LNA for radio communication with a sky66112 (Skyworks) FEM for PA/LNA drive. When testing the app on two BL654PA_dk nodes (Central and Peripheral) connection cannot be established. However communcationation can be established succesfully between a BL654PA_dk node and a nRF52840_dk node (working as central and peripheral respectively, and vice versa).
The following images show how the FEM is supported on the devicetree and at a prj.conf level. The devicetree shown is the one provided by Ezurio on \ncs\v2.8.0\zephyr\boards\ezurio\bl654_dvk\bl654_dvk_nrf52840_pa.dts, which at the same time corresponds too Nordic´s indications for FEM support here.
I´m not seeing why two BL654PA_dk boards cant´t connect to each other, while a BL654PA_dk and a nRF52840_dvk connect succesfully.
The following was done as to debug the problem:
- SoC transmision power modification: it was increased through CONFIG_BT_CTLR_TX_PWR_PLUS_8=y. It was also decreased throguh CONFIG_BT_CTLR_TX_PWR_MINUS_8=y.
- Instructions on this ticket were followed.
- settle-times were modified.
- UART and Logging were disabled as suggest on another ticket.
When doing any of the above mentioned, communcation between a BL654PA_dk and a nRF52840_dvk remain successful and communcation between two BL654PA_dks remain unsuccessful.
Additionally, logs of the BT module where activated through CONFIG_BT_LOG_LEVEL_DBG=y but no errors where shown. On the BL654pa_dk scanning and advertising functions are correclty executed.