• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 73 subscribers
  • Views 2271 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 119511
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issue opening MasterEmulator

Jim Hewitt

I've been testing my application and am having an issue opening MasterEmulator sometimes. I need to reseat the nfr51 dongle to clear out the errors I am seeing below. Any way I can avoid this.

2;14:43:17.8762 [MainThread] Initialize
MasterEmulator, Version=2.1.13.14, Culture=neutral, PublicKeyToken=null
3;14:43:18.0262 [MainThread] 680361820 - COM15
4;14:43:18.3362 [MainThread] Open
5;14:43:18.3462 [MainThread] 680361820 - COM15
6;14:43:18.5862 [MainThread]  - - Start of script: (2017-02-06 20:43:18) - - 
7;14:43:18.5962 [MainThread] 
<reportfile:"C:\ProgramData\Nordic Semiconductor\MasterEmulator\log.txt"/>
8;14:43:18.6262 [MainThread] Device: COM15
9;14:43:18.6362 [MainThread] HciJLinkDriver opened (COM15, 1000000-8-None-1-RequestToSend)
10;14:43:18.6562 [MainThread] 680361820 - COM15
11;14:43:20.0472 [MainThread] HCI command: BTLE_CMD_READ_BD_ADDR
12;14:43:20.0672 [MainThread] Serial port write: 01-09-10-00
13;14:43:21.6072 [MainThread] Exception: No response from master emulator
14;14:43:21.6072 [MainThread] Could not read device address.
15;14:43:21.6172 [MainThread] HCI command: NRF_CMD_GET_VERSION_INFO
16;14:43:21.6272 [MainThread] Serial port write: 01-06-FC-00
17;14:43:23.0372 [MainThread] Exception: 
18;14:43:23.0372 [MainThread] Could not read controller version info.
19;14:43:23.0572 [MainThread] HCI command: BTLE_CMD_LE_READ_BUFFER_SIZE
20;14:43:23.0672 [MainThread] Serial port write: 01-02-20-00
21;14:43:24.4873 [MainThread] Exception: 
22;14:43:24.4873 [MainThread] Could not read buffer size.
Parents
  • 0

    @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.

Reply
  • 0

    @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.

Children
No Data
Related
Terms of service