Issue opening MasterEmulator

RE: Issue opening MasterEmulator

Jim Hewitt — Thu, 09 Feb 2017 06:23:36 GMT

Using pc-ble-driver and calling error_code = sd_rpc_open(m_adapter, status_handler, ble_evt_dispatch, log_handler);, I get Failed to open nRF BLE Driver. Error code: 0x0D,

RE: Issue opening MasterEmulator

bjorn-spockeli — Wed, 08 Feb 2017 13:55:12 GMT

Generally, we recommend using the pc-ble-driver, available here on our GitHub page, as it is more stable and the fact that there will not be any further development of Master Control Panel and its .dll. However, if that is not an option, then you can try to switch to the Segger J-Link v5.10n firmware as it has shown to more stable. We also have customers using the MCP dll for production testing and some have used a Yepkit USB Switchable Hub to power cycle the nRF51 Dongle from code to resolve this issue.

RE: Issue opening MasterEmulator

Jim Hewitt — Tue, 07 Feb 2017 16:06:49 GMT

@Bjørn I am testing a device that is running on an nRF52832. Basically, I'm testing with both a C# console app and a C# WPF application. The console app seems to behave better that the WPF app. The issue will occur sometimes when I restart the application. Tried Open(), Close(), Reset() variations and they don't seem to help. The only fix is to unplug/reinsert the dongle. Part of the issue may be running the application in the VS debugger and terminating the app while tracing breakpoints and then restarting. I am having better luck when running the application outside of VS.

RE: Issue opening MasterEmulator

bjorn-spockeli — Tue, 07 Feb 2017 14:20:41 GMT

Hi Jim,

May I ask what are you using the MasterEmulator for?

Its a known issue that the Master Emulator firmware running on the nRF51 dongle may freeze/hang from time to time and that a reset of the dongle is required.

When you say that you have to reset the dongle do you mean performing reset using nrfjprog -r or unplugging and reinserting the nRF51 dongle in your computer?