nRF52 reports two JLink CDC UART Ports

RE: nRF52 reports two JLink CDC UART Ports

Michal — Tue, 20 Sep 2022 11:54:55 GMT

Hello again,

I have another solution, but it needs a DK with a chip that supports USB, so either nRF52833 or nRF52840 DK, but unfortunately not the nRF52 DK (with nRF52832). Another, cheaper option is to use the nRF52840 Dongle.

The solution is that you can use the nRF USB port. This is actually the recommended way to use the sniffer, as mentioned in the documentation. This way you can also get more data throughput.

The way you do this is by flashing the firmware normally first and then connecting the USB to the other USB port (nRF USB). You don't have to change the position of any switches for that.
nRF power source swtich is kept at VDD and nRF only switch at DEFAULT.

This way it should be possible to use a board in the sniffer even with the new J-Link chip.

Best regards,

Michal

RE: nRF52 reports two JLink CDC UART Ports

Michal — Mon, 19 Sep 2022 13:33:06 GMT

Hello Peder Olav,

Thank you for all the information. Unfortunately the nRF52DK version 3.0.0 has an nRF chip as a debugger chip, which does not support the sniffer yet.

I will try to find out if there is any way or workaround to make the sniffer work, but for now the only solution is to use an older DK with the big debugger chip.

Best regards,

Michal

RE: nRF52 reports two JLink CDC UART Ports

PederOlav — Mon, 19 Sep 2022 12:02:27 GMT

Hi Michal

At the time, I can only test with one single machine. But I have got two "new" nrf52DK, which have the same behaviour.

1) PCA 10040, 3.0.0, 2022.12, 1050306386

2) PCA 10040, 3.0.0, 2022.12, 1050377478

When I connect I get these ports up in Device Manager:

I did a reflashing with the latest FW I found on the web site (j-link-ob-sam3u128-v2-nordicsemi-170724.bin). It did not seem to change anything. Is there a way to read out the FW version of the nrf52DK?

I can program the nrf52DK with e.g. nRF Programmer 3.0.3. But when I try to use this with the nRF Sniffer, I get the following error in Wireshark:

Here is from the nRF Sniffer log file:

13-Sep-2022 08:10:21 (+0200) INFO: --------------------------------------------------------
13-Sep-2022 08:10:21 (+0200) INFO: Software version: 4.1.0
13-Sep-2022 08:10:21 (+0200) INFO: Started PID 20796
13-Sep-2022 08:10:21 (+0200) INFO: Namespace(capture=False, extcap_interfaces=True, extcap_interface=None, extcap_dlts=False, extcap_config=False, extcap_capture_filter=None, fifo=None, extcap_control_in=None, extcap_control_out=None, extcap_version='3.6', device='', baudrate=None, only_advertising=False, only_legacy_advertising=False, scan_follow_rsp=False, scan_follow_aux=False, coded=False)
13-Sep-2022 08:10:21 (+0200) INFO: Opening serial port COM8
13-Sep-2022 08:10:21 (+0200) INFO: closing UART
13-Sep-2022 08:10:21 (+0200) INFO: Opening serial port COM8
13-Sep-2022 08:10:21 (+0200) INFO: closing UART
13-Sep-2022 08:10:21 (+0200) INFO: Opening serial port COM9
13-Sep-2022 08:10:22 (+0200) INFO: closing UART
13-Sep-2022 08:10:22 (+0200) INFO: Opening serial port COM6
13-Sep-2022 08:10:22 (+0200) ERROR: Error opening UART Cannot configure port, something went wrong. Original message: OSError(22, 'The parameter is incorrect.', None, 87)
Traceback (most recent call last):
File "C:\Users\s29298\AppData\Roaming\Wireshark\extcap\SnifferAPI\Packet.py", line 74, in __init__
self.uart = UART.Uart(portnum, baudrate)
File "C:\Users\s29298\AppData\Roaming\Wireshark\extcap\SnifferAPI\UART.py", line 130, in __init__
self.ser.baudrate = baudrate
File "C:\Python310\lib\site-packages\serial\serialutil.py", line 299, in baudrate
self._reconfigure_port()
File "C:\Python310\lib\site-packages\serial\serialwin32.py", line 222, in _reconfigure_port
raise SerialException(
serial.serialutil.SerialException: Cannot configure port, something went wrong. Original message: OSError(22, 'The parameter is incorrect.', None, 87)
13-Sep-2022 08:10:22 (+0200) INFO: Opening serial port None
13-Sep-2022 08:10:22 (+0200) INFO: Opening serial port COM6
13-Sep-2022 08:10:22 (+0200) ERROR: Error opening UART Cannot configure port, something went wrong. Original message: OSError(22, 'The parameter is incorrect.', None, 87)
Traceback (most recent call last):
File "C:\Users\s29298\AppData\Roaming\Wireshark\extcap\SnifferAPI\Packet.py", line 74, in __init__
self.uart = UART.Uart(portnum, baudrate)
File "C:\Users\s29298\AppData\Roaming\Wireshark\extcap\SnifferAPI\UART.py", line 130, in __init__
self.ser.baudrate = baudrate
File "C:\Python310\lib\site-packages\serial\serialutil.py", line 299, in baudrate
self._reconfigure_port()
File "C:\Python310\lib\site-packages\serial\serialwin32.py", line 222, in _reconfigure_port
raise SerialException(
serial.serialutil.SerialException: Cannot configure port, something went wrong. Original message: OSError(22, 'The parameter is incorrect.', None, 87)

When I use my older nRF52 DK,(PCA10040,1.2.4, 2019.19, 682250149), the device manager shows only one COM port and this DK works with the nRF Sniffer.

I have a feeling there is something with the nRF52DK MCU firmware.

Best regards

Peder Olav

RE: nRF52 reports two JLink CDC UART Ports

olgo — Thu, 15 Sep 2022 13:18:08 GMT

Sorry for stealing the ticket, just wanted to inform you all that it is a general problem.

Thanks for your input. Looking forward to hearing from you again in the matter.

/Ola

RE: nRF52 reports two JLink CDC UART Ports

Michal — Thu, 15 Sep 2022 12:43:22 GMT

Hi,

Please make a new ticket in the future.

Unfortunately, there are some issues with the nRF52840 v3.0.x, because of the new interface MCU chip. They use nRF5340, while the old DKs used a Microchip IC (sam3u128).

Which is also why you cannot flash the firmware made for the old interface MCU on the new one. The firmware for the new interface MCU is not available for download at the time.

I will ask the developers about the current status, but I know that there is an issue with nRF Sniffer and a few other things not working properly on the new DKs.

Best regards,

Michal

RE: nRF52 reports two JLink CDC UART Ports

olgo — Wed, 14 Sep 2022 20:18:17 GMT

I have the exact same problem. Jlink CDC UART Ports on both COM6 and COM7.

Tried on two different windows machines.

HW used is nRF52840 DK, version 3.0.3, serial 1050210048

Interestingly, I can still flash using segger embedded studio but nRF Sniffer does not work.

I can also not flash using the normal programmer nor rfGo Studio.

I downloaded j-link-ob-sam3u128-v2-nordicsemi-170724.bin and dropped it in the mounted drive but it does not update.

FAIL.TXT tells me that "The currently active SWD interface does not support MSD drag and drop"

RE: nRF52 reports two JLink CDC UART Ports

Michal — Tue, 13 Sep 2022 13:47:58 GMT

Hello Peder Olav,

Does this happen only on that single machine?

Just to make sure, it is the old nRF52 DK, not for example nRF52840 DK? Please also provide me with the DK version number.

What kind of errors do you get? Any screenshots?

What you could try doing is reflashing the J-Link Interface MCU firmware (as it is documented here) and see if that solves the issue.

Best regards,

Michal