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

pc-ble-driver-py failed to open

Hello,

I am trying to use PCA10000 dongle with the pb-ble-driver-py libraries with absolutely no success, as I get a "Failed to open. Error code: 13" error.

I am running Windows 10. I installed the library using pip.

  • I installed the latest JLink software package (V614a) just to be sure.
  • I tried having the library flash the dongle (that part worked) with no success, even after unplugging and replugging the dongle
  • I tried flashing the connectivity_1.0.1_115k2_with_s130_2.0.1 firmware manually with nrfConnect, still a big nope.

Here is one of the test commands I tried and the resulting output:

C:\Python27\Lib\site-packages\pc_ble_driver_py\examples>py -2 heart_rate_collector.py NRF51 COM3
Serial port used: COM3
Traceback (most recent call last):
  File "heart_rate_collector.py", line 187, in <module>
    main(serial_port)
  File "heart_rate_collector.py", line 149, in main
    collector.open()
  File "heart_rate_collector.py", line 67, in open
    self.adapter.driver.open()
  File "C:\Python27\lib\site-packages\wrapt\wrappers.py", line 561, in __call__
    args, kwargs)
  File "C:\Python27\lib\site-packages\pc_ble_driver_py\ble_driver.py", line 126, in wrapper
    raise NordicSemiException('Failed to {}. Error code: {}'.format(wrapped.__name__, err_code))
pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: 13

Note: my dongle is working fine with Master Control Panel 3.10.0.14, although I need to unplug-replug the dongle after flashing for it to respond.

Am I doing something wrong? Is anyone else encountering this issue?

Parents
  • I've seen this issue before with my linux setup. The problem was related to the CTS (uart) line remained inactive (high) after resetting of the board. The problem started to occur with the September 2016 JLink FW and later releases. What solved it for me was to downgrade the FW to the July 2016 release.

    • Got to SEGGER dl page: www.segger.com/.../jlink
    • Find J-Link Software and Documentation Pack version 6.10. Download and install.
    • Open J-Link Configurator
    • Right click on the J-Link device and choose Replace firmware. Check that Emulator Firmware displays 2016 Jul 5 ...

    If you still have the newer J-link version installed, the FW might be updated automatically when you connect, so it might be a good idea to uninstall the newer version.

Reply
  • I've seen this issue before with my linux setup. The problem was related to the CTS (uart) line remained inactive (high) after resetting of the board. The problem started to occur with the September 2016 JLink FW and later releases. What solved it for me was to downgrade the FW to the July 2016 release.

    • Got to SEGGER dl page: www.segger.com/.../jlink
    • Find J-Link Software and Documentation Pack version 6.10. Download and install.
    • Open J-Link Configurator
    • Right click on the J-Link device and choose Replace firmware. Check that Emulator Firmware displays 2016 Jul 5 ...

    If you still have the newer J-link version installed, the FW might be updated automatically when you connect, so it might be a good idea to uninstall the newer version.

Children
Related