This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Master control panel windows 10

Hello,

I've upgraded my machine to Windows 10. I can't get Master control panel to work. I keep getting the error message:

No response from master emulator

I installed all of the drivers properly. The COM port seems to be working properly since my applications work.

What I have tried:

  • both pca10028 and pca10000 dongle
  • both baud rates (115200, 1M)
  • the last three versions of the master control panel
  • Different firmware versions (10 and 11).
  • tried pressing reset, unplugging the board...

My master control panel

image description

My device manager

image description

  • Turns out it was a firmware problem on the programmer part of the boards. Not exactly sure how this happened, but the programmer (JLink) was asserting the RTS pin so the communication did not go through (NRF51422 was not responding).

    I downloaded the latest firmware from the website, flashed it and voila. Everything works as expected.

  • I've run into the same issues with my nRF51 Dongles no longer functioning after upgrading my Windows 10 system to Keil v5.18a which also seemed to upgrade some portion of my Segger JLink installation. When I plugged in my nRF51 Dongles, the Master Control Emulator software updated the JLink firmware and I now get following error in Master Control Panel:

    No response from master emulator

    How did you diagnose the issue with JLink programmer asserting the RTS pin so that communication didn't go through? Also, what specific firmware from what specific website did you flash?

    I was able to get the things going again by downgrading the JLink firmware in my nRF51 Dongle down to 4.98c but this isn't optimal as the Master Control Panel keeps wanting to upgrade the JLink firmware now to the latest. I would like to really understand what JLink versions work with which MCE version.

  • I used the latest firmware available from the Nordic download section. Its filename was "J-link OB-SAM3U128-V2-NordicSemi 160212.bin". I debugged the communication with the logic analyzer. I found the traces for the usart and connected them to the analyzer. You could clearly see that the programmer was correctly sending data, but it kept the rts pin active so the nrf did not respond. I then tried an example application where i disabled the rts/cts flow control and it worked. So as a final hail marry i tried upgrading the firmware of the programmer and that seemed to fix it. I am not sure what was my previous version of the programmer software.

    Hope you get things working again. I spent nearly a day trying to fix this.

  • OK, thanks for the details. I noticed that the latest version of Keil v5.18a forced the upgrade of all connected JLink devices to upgrade to v5.10l which broke my nRF51 Dongle from working with Master Control Panel. Using JLink Configurator v5.10d I was able to downgrade the firmware of my JLink devices to v5.10d including the nRF51 Dongle which got things working again.

    This issue is unfortunate and it looks like newer versions of the Master Control Panel firmware may be tweaked to work with the latest versions of the JLink firmware from Segger. Fortunately, the fix of downgrading the firmware worked to get me going again, but after several hours of head scratching. I'll try the new firmware you linked to see if that works as well.

    I thought I had bricked my nRF51 Dongle, but your posting put me on the track of checking the jLink firmware on the nRF51 Dongle. Thanks for the lead.

Related