Test scripts are in python. Running on version 2.1.0 and older nRF52-DK boards; but not on the new version 3.0.0 boards that have the new MCU.
Test scripts are in python. Running on version 2.1.0 and older nRF52-DK boards; but not on the new version 3.0.0 boards that have the new MCU.
Hi
The newer DK revisions open multiple COM ports when connected to the computer. So what might be happening is that your test scripts are choosing the wrong COM port and that's why you're having trouble.
If you run nrfjprog --com you should see something like this, and VCOM0 should be the COM port to the nRF52832.

Best regards,
Simon
Hi Simon,
nrfjprog --com is not a valid argument...
C:\Users\lab>nrfjprog --com
ERROR: An invalid argument was provided. Use --help for a list of valid
ERROR: arguments.
Have you installed the nRF Command Line tools on your computer, and if so, what version? I'm able to call nrfjprog --com just fine on my end.
Best regards,
Simon
Hi Simon,
Thanks! I downloaded the newest version of nrfjprog, from the link that you provided.
Indeed, the rRF52-Dk dev board did enumerate as 2 com ports.

As shown in Device Manager:

Is this a feature or a BUG?
Best Regards,
Raymond Yen
Sr. R&D Engineering Technician
Neuspera Medical
|
Hi
The two COM ports are a feature, as the new DKs have another debugger, we have an available VCOM for the debugger chip as well. You will have to change your script to choose the lower numbered VCOM port of the two to ensure that it runs on the onboard nRF52.
Best regards,
Simon