No response from master emulator

[Klaus]

I'm trying to connect my nRF51 dongle to the DK using the Master Control Panel3.10.0, but I keep getting "no response from master emulator" and failed discovery. I read the other posts regarding this issue but none helped. I flashed using the master from file. I pulled and plugged the dongle multiple times and tried changing the USB port. I tried different SDKs. Nothing has worked, what should I do since I'm a beginner ?

Best,

[Jørgen Holmefjord]

What are you using Master Control Panel for? The newer nRF Connect for Desktop can do most of things Master Control Panel can, and typically works better with later drivers/firmwares etc.

[Greg Nelson]

I'm running into the same sort of issues.  What I'm trying to do is use the dongle with the Nordic UART service as a virtual serial port to communicate with another device (with an nRF52832 module).

Apparently, the developers who originally worked on this had a solution based on MCP 3.10.0 and were able to run this, but I'm just getting the dreaded "No response from master emulator" issue regardless of whether I program the firmware on the dongle (nRF6825 Rev 1.1.0) using MCP or nRF Go Studio.

It isn't clear to me whether nRF Connect for Desktop supports the same capability of connecting, and then leaving the COM port open for other applications to use.  Do you know if this works, and if so is there documentation on it?

If not, any suggestions for where to start on getting either the nRF6825 "nRF51 Dongle" or a nRF6827 "nRF52 Development Kit" to perform this function?

[Jørgen Holmefjord]

I'm not sure I understand what you mean by this: "It isn't clear to me whether nRF Connect for Desktop supports the same capability of connecting, and then leaving the COM port open for other applications to use." Can't you just use the ble_app_uart or ble_app_uart_c examples to do this? There will be a virtual UART interface to the PC through the SEGGER chip, and anything you send on this terminal will be forwarded on the Nordic UART service (NUS) from the board. Similarly, all strings received on NUS will be relayed to the terminal.