Eventually we got it working with the Master Control Panel again, but it will not work with our test software. I suspect a Window update change that affected links. Window7 Professional SP1 64 bit.
Eventually we got it working with the Master Control Panel again, but it will not work with our test software. I suspect a Window update change that affected links. Window7 Professional SP1 64 bit.
Need more details!
What, exactly, are the symptoms of "not working" ?
Is the dongle correctly showing up in Device Manager?
Need more details!
What, exactly, are the symptoms of "not working" ?
Is the dongle correctly showing up in Device Manager?
Originally it stopped working with the Master Control Panel interface, which is are default utility and HW troubleshooting tool. After several days and many different methods on multiple computers with different revisions of SW, the dongle started working again with the MCP program. At that point our test software could detect the dongle, but connecting to our UUT will not work. This includes LabVIEW source code software and a custom contractor build EXE interface program. So, now that the MCP works again, it rules out the hardware and the Nordic/JLink drivers to our thinking. So the Windows registry either was never part of the problem, or "fixing" the working JLink path fixed part of the problem. Now we are wondering if some Widnows 7 update may be causing issues and if new MCP (we use 3.9.0, the only version we got it to work as we needed) might be a fix.