No response from master emulator

RE: No response from master emulator

Jørgen Holmefjord — Tue, 13 Mar 2018 09:28:17 GMT

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.

RE: No response from master emulator

Greg Nelson — Mon, 12 Mar 2018 17:45:55 GMT

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?

RE: No response from master emulator

Jørgen Holmefjord — Fri, 16 Jun 2017 14:07:55 GMT

Did you enable bonding (Check "Perform bonding") in the security parameter settings in nRF Connect? Does the example you test with support bonding?

RE: No response from master emulator

Klaus — Fri, 16 Jun 2017 13:49:08 GMT

I did try to use the nRF connect, but I also have an issue with that since whenever I try to bond the dongle with the DK I get the error message: Authentication failed with status BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP. I tried to solve it but couldn't so I went back and tried the master control panel

RE: No response from master emulator

Jørgen Holmefjord — Thu, 15 Jun 2017 07:44:25 GMT

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.