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

Connectivity Firmware from SDK17.0.2 failed for nRF52832 (PCA10040)

Hi,

I want to use connectivity firmware compiled by source, I have compiled SDK 17.0.2 connectivity project path using SES
"SDK Path\17.0\nRF5_SDK_17.0.2_d674dde\examples\connectivity\ble_connectivity\pca10040\ser_s132_uart\ses"
and make changes in pin configuration as per PCA10040 TX = 6 RX = 8 pins and HW flow control set to None.

I have load compiled hex and s132_nrf52_7.2.0_softdevice.

The issue is nRFconnect PC application version 3.6.1 gives error as below 

Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
serial port COM7 closed.
Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)
I have tried with SDK15.3 and SDK14.2 as above process but result in same error.
looks like connectivity firmware is not working or does it required additional changes in project to make PCA10040 work as dongle?
or is there any compatibility issue?
Parents
  • Hi,

    The connectivity firmware in the SDK is not compatible with the pc-ble-driver (which is used by nRF Connect for Desktop) out of the box. If you want to build it from source you need to apply a set of patches and follow the procedure described in the pc-ble-driver documentation under Compiling connectivity HEX files.

    Also please note that you cannot mix and match versions as you like. The SoftDevice version must be supported by the pc-ble-driver implementation, and currently SoftDevice API version 6 is the latest that is supported.

Reply
  • Hi,

    The connectivity firmware in the SDK is not compatible with the pc-ble-driver (which is used by nRF Connect for Desktop) out of the box. If you want to build it from source you need to apply a set of patches and follow the procedure described in the pc-ble-driver documentation under Compiling connectivity HEX files.

    Also please note that you cannot mix and match versions as you like. The SoftDevice version must be supported by the pc-ble-driver implementation, and currently SoftDevice API version 6 is the latest that is supported.

Children
No Data
Related