The nRF Connect Desktop v4.0.0 and Direct Test Mode app v2.0.4 does not work with some USB-UART controller ICs.

[enoch.park]

Deer,

The Direct Test Mode(v2.0.4)  app in nRF connect Desktop(v4.0.0) recognizes COM PORT by the cypress USB-UART controller IC,
but the device selection is not successful and cannot DTM test proceed.

In the previous version(v2.0.3), it was confirmed that it works OK.
nRFgo STUDIO also recognized and operated OK.

I have other USB-UART controller ICs such as FTDI, SiLabs, CMSIS-DAP, etc. were recognized and selected successful.

Please let me know how to downgrade the DTM app within nRF Connect Desktop or how I can work around this.

[Hieu]

Hi enoch.park,

Let me ask the engineers behind the DTM app if downgrade is possible and feedback to you.

Hieu

[Hieu]

Hi enoch.park,

Could you please let me know if there are any error logs when you select the Cypress Device? Even if there is no error, what does the app's log says?

I am not familiar with the tool on the second screenshot you posted, where the test is running. Is this on the nRFgo STUDIO app or a different app?

Hieu

[enoch.park]

Hi, Hieu

Hi Hieu,

1) No log is displayed when selecting Cypress Device. I attached the system report in About > support is as follows.
COM13: DAPLink CMSIS-DAP
COM12: FTDI
COM16: SiLabs
COM4: Cypress (<-- )

2) The second screen shot is the interface that appears when selecting the Direct Test Mode item from the Bluetooth item in the Feature tab on the left after running the nRFgo STUDIO program.

Hieu

Fullscreen nrfconnect-system-report-2023-03-31T06-43-41.298Z.txt Download

# nRFConnect System Report - 2023-03-31T06-43-41.298Z

- System:     SAMSUNG ELECTRONICS CO., LTD. 800G5M/800G5W
- BIOS:       American Megatrends Inc. SECCSD - 1072009
- CPU:        1 x Intel Core™ i7-7700HQ 2.8 GHz 8 cores (4 physical)
- Memory:     23.7 GB free of 31.9 GB total
- Filesystem: C: (NTFS) 237.3 GB 46.8% used

- OS:         Microsoft Windows 10 Pro (10.0.19045) Windows ia32

- Versions
    - kernel: 10.0.19045
    - git: 
    - node: 16.17.1
    - python: 
    - python3: 
    - nrf-device-lib-js: 0.5.0
    - nrf-device-lib: 0.13.11
    - nrfjprog DLL: 10.18.2
    - JLink: JLink_V7.66a

- Connected devices:
    - 310400000f150f5b00000000000000000000000097969902 : COM13
    - AK00CZPL : COM12
    - {A56C4638-83AB-5F71-A871-5E1AF53C0AF5} : COM16
    - null : COM4

- Current device:
    - name:          undefined
    - serialNumber:  null
    - cores:         Unknown
    - website:       Unknown

[Hieu]

Thank you for the information.

The app team has confirmed that there currently is no way to downgrade the app to an earlier version.

I have forwarded the new information you sent to our app team. As you could see, nothing specific about COM4 is shown, so I am not sure if this would be all it takes to pinpoint the issue. Let's wait for their response.

Please also note that it's Easter holiday next week, so responses from them and us support engineers are likely delayed until after Monday 10 April at the earliest.

[Hieu]

Hi enoch.park,

Thank you for your patience. My apology for the long wait.
Our app team feedbacked on Wednesday, soon after the holiday. However, I am then partially out of office, resulted in some extra lead time. 

Unfortunately, they don't see anything outstanding; and without a similar hardware, they cannot reproduce it to debug the issue.

There is one last thing we can try. Could you try turning on Verbose Logging? It is under the Support card of the About pane.
After that, please click on Restart with verbose logging button then reproduce the issue with your Cypress device and send us the logs from clicking the Open Log File button, which is located at the bottom of the log window.

Hopefully there is something obvious in the verbose log that could help tell us what is wrong.