DTM (direct test mode) connect fail in ncs v2.2.0

[Felix Shih]

HI,

I build project direct_test_mode and empty_app_core and connect to PC softwarre DTM v2.

If build from ncs v1.9.1, it connect ok to show standby. but if build from ncs v2.2.0, DTM show NG.

Can you help me to verify it? something wrong?

[Håkon Alseth]

Hi,

 

Which nRF device are you compiling for?

Does DTM work in nRF connect for desktop application?

 

Kind regards,

Håkon

[Felix Shih]

Hi,

1) HW is nRF5340-DK, UART is RX(P1.00), TX(P1.01)

2) I just test with nRF connect for Desktop still fail in ncs v2.2.0 image

[Håkon Alseth]

Hi,

 

I see the same behavior.

I believe this is due to this change in direct test mode, taken from the release notes (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.2.0/nrf/releases/release-notes-2.2.0.html):

On the nRF5340 development kit, the application core UART interface is used for communication with testers instead of the network core UART interface.

 

As a workaround, can you try to select the application core COM-port?

Please note that you should not use empty_app_core now, but program the RPC image (which is automatically given as a child_image in direct_test_mode)

 

I'll report this internally as a bug.

 

Kind regards,

Håkon

[Felix Shih]

Hi,

1) for ncs v2.2.0, I build direct_test_mode project, but I can not find RPC image in directory \direct_test_mode\child_image. Should I build following project to program mcu? 

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.2.0/nrf/samples/nrf5340/remote_shell/README.html#nrf5340-remote-shell

2) If I want to use ncs v1.9.1 first, my HW use P0.25 and P0.26, and have 4 antennas.

The origin overlay is:

Can I just change to 

Is it ok?

[Håkon Alseth]

Hi,

 

Felix Shih said:

1) for ncs v2.2.0, I build direct_test_mode project, but I can not find RPC image in directory \direct_test_mode\child_image. Should I build following project to program mcu? 

It is called "remote_shell" in your build-catalog.

Here's how the partition_manager_report looks for direct_test_mode in ncs v2.2.0:

  flash_primary (0x40000 - 256kB): 
+----------------------------------+
| 0x1000000: app (0x40000 - 256kB) |
+----------------------------------+

  sram_primary (0x10000 - 64kB): 
+-------------------------------------------+
| 0x21000000: sram_primary (0x10000 - 64kB) |
+-------------------------------------------+

 CPUAPP flash_primary (0x100000 - 1024kB): 
+---------------------------------------+
+---0x0: app (0x100000 - 1024kB)--------+
| 0x0: remote_shell (0x100000 - 1024kB) |
+---------------------------------------+

 CPUAPP otp (0x2fc - 764B): 
+------------------------------+
| 0xff8100: otp (0x2fc - 764B) |
+------------------------------+

 CPUAPP sram_primary (0x80000 - 512kB): 
+-----------------------------------------------+
| 0x20000000: sram_primary (0x70000 - 448kB)    |
| 0x20070000: rpmsg_nrf53_sram (0x10000 - 64kB) |
+-----------------------------------------------+

 

Felix Shih said:

2) If I want to use ncs v1.9.1 first, my HW use P0.25 and P0.26, and have 4 antennas.

The origin overlay is:

That is possible, as per the documentation, which states that atleast one must be provided:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/direct_test_mode/README.html#antenna-matrix-configuration

 

Kind regards,

Håkon