MCP / nrfConnect issues

[OskarM]

Dear Nordic Team,

I can't launch Sniffer on PCA10000 using MCP nor on PCA10040 using nrfConnect. In case of MCP I get "No response from master emulator" and in nrfConnect "Error occurred opening serial port. (NRF_ERROR_TIMEOUT)".

The PCA10000 works on my collegue PC, so I assume FW is correct. On the PCA10040 I downloaded the "s132" hex using nRFGostudio.

I tried newest JLink USB drivers, different ports etc. - no difference. In both cases I see that whatever USB socket I plug boards in they preserve their COM numbers (like COM12 or COM18) which is a bit strange.

My system is Win7 Pro 64b

Please advise what to do. regards

[Hung Bui]

@OskarM: Please clarify, do you want to run a Sniffer or you want to start a Master emulator. They are not the same.

If you simply want to run Master emulator (nRFMCP or nRF Connect) you need to flash the correspondent firmware on the dongle or the DK.

In MCP you click File -> Flash programming and select one of the firmware in the two option MEFW.

In nRF Connect the firmware will be flashed automatically, do you see the pop up message asking to update the firmware ?

[OskarM]

Sorry- I mean Master emulator in both cases. I flashed firmware on PCA10040 using hex from nrfConnect "hex" folder (s132). When I erase the chip and run nRFConnect it prompts for upgrading "connectivity" firmware to 1.0. Logs:

11:20:55.3190 Connectivity firmware version 1.0.0 detected 11:20:55.3210 Opening adapter connected to COM12 11:20:55.3460 Successfully opened COM12. Baud rate: 115200. Flow control: none. Parity: none. 11:20:55.3480 Reset performed on adapter COM12 11:20:57.3470 Error occurred opening serial port. (NRF_ERROR_TIMEOUT)

I have upgraded SEGGER debugger & USB drivers to latest vesrion (V612) and issue persists.

[Hung Bui]

Have you done any modification on the board ? for example with solder bridges ?
If you test COM 12 port with PC terminal and a UART test firmware from the SDK would it work ?

[OskarM]

I did have some external devices connected to the board. After getting back to "bare board" it started to work. Thanks for hint, I got this board from a collegue and I assumed it worked with the setup.

[Hung Bui]

I'm glad that it works now. :)