nRFConnect 3.0.0 unsupported device "serialport"

[Dave_couling]

I updated to nRF Connect 3.0 today and its seemed to causes issues with any Dongles I connect to my PC.  I get the following error:

ERROR Unsupported device with serial number 'CD28EC9EE85A' and traits ["serialport"]

I tried uninstalling and reverting to 2.7 but the issue seems to persist.  I've tested on 3 dongles and I get the same error everytime.  

[Hung Bui]

Hi Dave, 

I'm sorry for the delayed response. We are on reduced staff during the summer. 

When I tested on my computer, on the first run after programming the board I saw the exact same error code but then nRF Connect showed an error regarding LibUSB and asking for reset of the software. After that the dongle worked as expected. 

Could you try to put the dongle into bootloader mode (press the reset button on the dongle, red LED should breath) and program the chip using nRFConnect ? 

Could you update the Jlink driver to latest version ? 

If the issue remains, I would suggest to use a NRF52 DK instead of the Dongle. You will have more control for programming the chip compare to the Dongle. 

[Dave_couling]

Hi Hung,

I had tried this, but programming seem to fail.  When the device would reset, my computer would be assigning it a COM port number.  Somehow this process causes issues with the FW updates.  I plugged my dongles into another computer which successfully programmed them.  They work fine back on my machine, but I am concerned of this occuring in the future.  Atleast I know a fix, but want to post this in cases other experienced the same issue when upgrading to nRF Connect V3.0.0

[Dave_couling]

This is still a problem with the latest nRF Connect v3.2.0.  

[Dave_couling]

Shows similar except without the "USB: Nordic Semiconductpr nRF52 Connectivity"

This suggests to me that the firmware in the dongle isn't working properly.  I let the nRF Connect attempt to update the firmware once in bootloader mode, but the FW updates always fail.

Here is the log:

2019-11-07T19:14:02.662Z VERBOSE Could not fetch serial number for serial port at COM10
2019-11-07T19:14:02.662Z VERBOSE Could not fetch serial number for serial port at COM9
2019-11-07T19:14:02.662Z VERBOSE Could not fetch serial number for serial port at COM8
2019-11-07T19:14:02.662Z VERBOSE Could not fetch serial number for serial port at COM7
2019-11-07T19:15:56.001Z INFO Validating connectivity firmware for device with serial number D1370E346EFE...
2019-11-07T19:16:26.381Z ERROR Error while setting up device D1370E346EFE: Timeout while waiting for device D1370E346EFE to be attached and enumerated

I have tested on all available USB port with the same result.

[tesc]

Hi,

Thanks for the update.

You mentioned earlier that a workaround was to program the dongle on a different computer. Was that a computer with an earlier version of nRF Connect for Desktop, or was there another difference between the two?

Regards,
Terje

[Dave_couling]

Yes that other computer had a much earlier version

[tesc]

Hi,

Can you try to program a different hex file onto the Dongle through the nRF Connect Programmer app first? (An SDK example for the PCA10059, so that you can validate that the computer is able to program the Dongle with an application. Also, so that the new application for the DFU performed by the BLE app is different from the one already present on the board, for next step.)

Then, try pressing the button for putting the Dongle into bootloader mode (red light pulsating) before selecting it in the nRF Connect BLE app?

By the way, we just recently released nRF Connect for Desktop v3.3.0, and Bluetooth Low Energy app v2.3.2.

Regards,
Terje

[Dave_couling]

v3.3 seems to fix the issue however it now causes issues with the PCA10031 dongles

[tesc]

Hi,

What are the issues that you see with PCA10031 Dongles?

Regards,
Terje