[Direct Test Mode] The failed result of for nRF54L15 via SDK v3.0.0

[Paul Lin]

Hi Support team:

I am new for using the Nordic Design kit of nRF54L15-DK. 

And I would like to use the app "Direct Test Mode" v2.4.2 built-in the "nRF Connect for Desktop" v5.1.0 on my Windows OS.

But I followed up the instruction to install the SDK with v3.0.0 and burn the .hex into the board and power-on still show the error message.

Cannot communicate with the device. Make sure it is not in use by another application, that the correct serial port has been selected, and that it uses firmware compatible with Direct Test Mode.

[Håkon Alseth]

Hi,

 

Thank you for sharing the .hex file that you use. 

I was able to run this on my end, but I needed to try both COM-ports. Could you check if the other enumerated COM port, by selecting it in the top-left corner?

 

Kind regards,

Håkon

[Paul Lin]

Hi Hakon:

BTW, 

Does the packet pattern of DTM with ALL1 or ALL0?

[Håkon Alseth]

Hi,

 

Packet pattern is selectable in the application:

 

Paul Lin said:

I also noticed that your picture is same as mine with can`t control power. Do you have any recommended method to solve issue?

Does it always fail, or is it only one specific combination that fails?

It runs on my side, with 8 dBm, with your .hex file:

 

Paul Lin said:

No matter the transmit power set 0dBm or 8dBm why my test instrument get the same measured power around 0dBm?

I use the test probe to touch the connector MM8130-2600 and connect to my instrument CMW-270 to check.

Changing the TX power is not a part of the bluetooth core spec, but we have added this as a "vendor specific" implementation, meaning that generic testers do not change the tx_power.

If you want the TX power to default to 8 dBm, you can change this line to 8:

https://github.com/nrfconnect/sdk-nrf/blob/v3.0.0/samples/bluetooth/direct_test_mode/src/dtm.c#L452

ie. .txpower = 8,

 

Kind regards,

Håkon