Direct Test Mode v2.4.1 GUI does not work with third party boards

[lx_brz]

Using nRF Connect for Desktop on Ubuntu 24.04 LTS I am trying to use the Direct Test Mode v2.4.1 software with our own custom board.

On https://docs.nordicsemi.com/bundle/nrf-connect-direct-test-mode/page/index.html you wrote:

> The application also supports third-party devices that are programmed with the DTM standard protocol and expose access to it through a serial port.

But it is not possible. Trying to select the FTDI based UART and running clicking "Start test" I see the following error:

At the same time I am connected to the board via RTT to view logs and don't see any communication.

On the contrast when I use cutecom to send commands as hex codes directly, everything works as expected:

And I see the expected communication activity on the RTT logs:

Help would be much appreciated. It would be much more convenient to use your GUI based Direct Test Mode tool instead of sending and decoding the DTM commands as hex manually.

There are no problems by the way using a nrf52840DK. It only does not work with the custom board, connected via UART, although you explicitly write:

> The application also supports third-party devices that are programmed with the DTM standard protocol and expose access to it through a serial port.

Thanks

Alex

[lx_brz]

Forgot to attach the system report:

# nRFConnect System Report - 2024-09-24T06-20-04.455Z

- System: LENOVO 20UD0013GE
- BIOS: LENOVO R1BET80W(1.49 )
- CPU: 1 x AMD Ryzen 7 PRO 4750U with Radeon Graphics 1.7 GHz 16 cores (8 physical)
- Memory: 21.5 GB free of 30.6 GB total
- Filesystem: /dev/mapper/vgroot-lvroot (ext4) 914.3 GB 63.3% used

- OS: Ubuntu (24.04.1 LTS) linux x64

- Versions
- kernel: 6.8.0-45-generic
- git: 2.43.0
- node: 20.14.0
- python: 3.12.5
- python3: 3.12.5
- nrfutil-nrfutil-device: 2.1.1
- Connected devices:
- FT5TXPWV : /dev/ttyUSB0
- 000260105857 : undefined

[lx_brz]

Interestingly enough I just found this project: https://github.com/olleheugene/nRF-DTM/?tab=readme-ov-file#download-the-latest-version

This seems to work without problems. Using it I can start transmitter tests and see the communication happening in RTT logs.

[lx_brz]

Umm, sorry? I got the email notification that "A support engineer has been assigned to your ticket" and then the ticket was closed without comment, suggesting that the answer above, which links to an unofficial project is the "verified answer"?

This is hard to understand? Could you please at least explain your motivation for closing this ticket and suggesting the above as the "verified answer"?

It does not make sense to me that the official documentation from nordic reads as

> The application also supports third-party devices that are programmed with the DTM standard protocol and expose access to it through a serial port.

but when it does not work and you file a ticket for that it will just be closed pointing to some random persons private project as a solution?