pc-ble-driver-py failed to open

RE: pc-ble-driver-py failed to open

Jonathan Dukes — Mon, 22 Jan 2018 11:15:05 GMT

Thanks @Stian - that fix worked for me just now.

RE: pc-ble-driver-py failed to open

Stian Røed Hafskjold — Wed, 22 Mar 2017 11:49:33 GMT

Did you get any further on this? You can try to pull the CTS line to GND manually to see if this is actually where the problem lies.

RE: pc-ble-driver-py failed to open

Geoffrey OMWAVE — Wed, 01 Mar 2017 14:10:27 GMT

Thank you for your answer. Unfortunately I don't seem to be able to access any JLink_Windows downloads older than the V610d from October 2016.

RE: pc-ble-driver-py failed to open

Stian Røed Hafskjold — Wed, 01 Mar 2017 12:38:13 GMT

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.