pc-ble-driver: "Failed to open nRF BLE Driver. Error code: 0x0D"

[Eliot Stock]

Hi.

I'm getting an nRF Dongle (PCA10031) set up on a Windows machine to be the BLE central that we'll use for our production line testing. To that end, I've built the pc-ble-driver code following the instructions at github.com/.../pc-ble-driver. The connectivity hex file I've flashed is connectivity_1.1.0_1m_with_s130_2.0.1.hex. I've also tried with connectivity_1.1.0_115k2_with_s130_2.0.1.

However, if I build the heart rate monitor example and try to run it, this is the result:

c:\biketracker\pc-ble-driver\examples\heart_rate_monitor\build\Debug>hrm_v2.exe
COM4
Serial port used: COM4
Info: Successfully opened COM4. Baud rate: 115200. Flow control: none. Parity: n
one.

Status: 6, message: Target Reset performed
Failed to open nRF BLE Driver. Error code: 0x0D

0x0D is a timeout:

#define NRF_ERROR_TIMEOUT                     (NRF_ERROR_BASE_NUM + 13) ///< Operation timed out

Any ideas?

[Hung Bui]

Hi Eliot,

Could you try to test with the pre-compiled pc-ble-driver such as from the pc-ble-driver-py if you see the same error ?

[Oscar J. Ariza N.]

I have the same problem with the same device (PCA10031) and I've got the same error even running the examples (heart_rate_collector and heart_rate_monitor).

[Hung Bui]

Could you try to test running the dongle with nRF Connect on PC ? nRF Connect also use pc_ble_driver in the background.

[Eliot Stock]

Although I initially said I'd tried this with both connectivity hex files, in fact it was the faster one that was causing the issue. That is, I saw this error when using:

connectivity_1.1.0_1m_with_s130_2.0.1.hex

but not when using:

connectivity_1.1.0_115k2_with_s130_2.0.1.hex

[Oscar J. Ariza N.]

I tested it and realized that I flashed the HEX file for 1M but using the wrong bitrate in the example code. Now it is working. Thanks a lot @Hung Bui.