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

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

Paul Lin — Mon, 26 May 2025 02:54:36 GMT

Hi Håkon Alseth :

Got it.

Hope this function can be supported on the PC App recently which can be aligned with the core specification.

It would be helpful to me.

Thanks.

Best Regards.

Paul Lin

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

Håkon Alseth — Thu, 22 May 2025 10:38:07 GMT

Hi Paul Lin,

I am sorry, but there is no way to setup this without modifying for instance the radio_test sample or dtm firmware specifically to trigger this payload pattern.

Kind regards,

Håkon

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

Paul Lin — Wed, 21 May 2025 06:57:22 GMT

Hi Håkon Alseth

I knew about the tester should support to demodulate the pattern. But now I just wonder to know if any alternative way can let nRF54L15 trigger the power with pattern ALL1 for coded PHY S2/S8 to let my tester can recognize it.

Best Regards.

Paul Lin

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

Håkon Alseth — Wed, 21 May 2025 06:55:09 GMT

Hi,

At this moment, the PC software does not support this feature, but any dedicated bluetooth tester, which supports S2/S8, should.

Kind regards,

Håkon

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

Paul Lin — Wed, 21 May 2025 01:20:22 GMT

Hi Håkon Alseth

Got it.

Thank for your comment and hope the PC App. can support recently.

BTW,

it seems like the pattern can be supported but it needs to use the another way to trigger the power.

Can you advise the alternative method to achieve it?

Best Regards.

Paul Lin

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

Håkon Alseth — Tue, 20 May 2025 08:45:24 GMT

Hi Paul Lin,

Thank you for explaining.

What you are referring to is this section, in the core specification:

https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-60/out/en/low-energy-controller/direct-test-mode.html#UUID-dc52f80f-9657-877b-fd6a-0d28f1fd1120

The DTM PC application does not utilize the last packet type in the drop-down menu. I will report this internally.

Kind regards,

Håkon

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

Paul Lin — Tue, 20 May 2025 06:50:51 GMT

Hi Håkon Alseth :

Okay.

Let me describe more exact and sorry for unclear description.

You can see the below App window and the list of the packet type with four types only.

I would like to select the ALL1 for coded PHY for testing.

So my question is the feasibility of the ALL1 for coded PHY is available for not.

Best Regards.

Paul Lin

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

Håkon Alseth — Tue, 20 May 2025 06:45:50 GMT

Hi,

[quote userid="145295" url="~/f/nordic-q-a/121182/direct-test-mode-the-failed-result-of-for-nrf54l15-via-sdk-v3-0-0/536066"]The last question is how can i pick up the packet format with ALL1(11111111) for coded PHY(S2/S8)? I can`t see the option in the list of the "direct test mode" APP [/quote]

I am sorry, but I must have misunderstood you. I am not sure what you mean?

Kind regards,

Håkon

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

Paul Lin — Tue, 20 May 2025 06:41:51 GMT

Hi Håkon Alseth

I don`t get your point.

So you meant the App can`t transmit the packet format ALL1 for coded PHY under Transmission?

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

Håkon Alseth — Tue, 20 May 2025 06:08:17 GMT

Hi Paul Lin,

[quote user="Paul Lin"]The result is fine now.[/quote]

I am glad to hear this!

[quote user="Paul Lin"]

The last question is how can i pick up the packet format with ALL1(11111111) for coded PHY(S2/S8)? I can`t see the option in the list of the "direct test mode" APP

[/quote]

You use normal BLE 1 MBit mode for RX in the case of S2/S8.

Kind regards,

Håkon

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

Paul Lin — Tue, 20 May 2025 02:30:30 GMT

Hi Håkon Alseth :

I found I open the wrong file and checked dtm.c after reinstalling the SDK again which the file is with correct content which the setting power is located at Row453.

I tried to re-compile and burn again and rest to use the "direct test mode" APP to validate.

The result is fine now.

The last question is how can i pick up the packet format with ALL1(11111111) for coded PHY(S2/S8)? I can`t see the option in the list of the "direct test mode" APP

Best .Regards.

Paul Lin

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

Håkon Alseth — Mon, 12 May 2025 08:16:52 GMT

Hi,

I understand that you are targeting to use v3.0.0, but this comment:

[quote user="Paul Lin"]

I save the original .c file as backup and modified the dtm.c with this value of this line from 0 to 8.

But my parameter is not like yours at row 452 but 435.

Does any changed items for this dtm.c?

my NCS is V3.0.0 download by nrfutil

[/quote]

Indicates that you are not editing the correct file. Do you have several instances of ncs installed? Could it be that you selected one of the other instances?

Kind regards,

Håkon

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

Paul Lin — Mon, 12 May 2025 03:41:14 GMT

Hi Håkon Alseth

I download the NCS followed below command lines.

### 4.Run the following command to install the toolchain version for the SDK version of your choice: ###
nrfutil sdk-manager toolchain install --ncs-version version

For example:
C:\>nrfutil sdk-manager toolchain install --ncs-version v3.0.0

### 6. Specific release: To check out the v3.0.0 release, enter the following command: ###
(v3.0.0) C:\ncs\toolchains> west init -m github.com/.../sdk-nrf --mr v3.0.0 v3.0.0

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

Håkon Alseth — Fri, 09 May 2025 10:04:07 GMT

Hi,

Are you certain you are changing the correct file?

The line number 435 indicate that you are changing the file in NCS v2.7.0:

https://github.com/nrfconnect/sdk-nrf/blob/v2.7.0/samples/bluetooth/direct_test_mode/src/dtm.c#L435

Kind regards,

Håkon

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

Paul Lin — Fri, 09 May 2025 02:35:22 GMT

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

Paul Lin — Fri, 09 May 2025 02:34:20 GMT

Hi Håkon Alseth

Sorry for the missing the information.

After i modified the .c file and delete the folder "build" and compile again.

Burn into the board and trigger the power still around 0dBm not 8dBm what I set.

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

Paul Lin — Fri, 09 May 2025 02:32:34 GMT

Hi Håkon Alseth

I save the original .c file as backup and modified the dtm.c with this value of this line from 0 to 8.

But my parameter is not like yours at row 452 but 435.

Does any changed items for this dtm.c?

my NCS is V3.0.0 download by nrfutil

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

Paul Lin — Fri, 09 May 2025 02:05:31 GMT

Hi Håkon Alseth

Thanks for your feedback.

For Tx Power setting part,

I will try to modify and test on my site later.

For the pattern,

I only see the PRBS9/11110000/10101010/Constant Carrier.

So if I need the ALL1(11111111) or ALL0(00000000) this kind of pattern to test the encoded PHY S2/S8 testing how can I perform?

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

Håkon Alseth — Thu, 08 May 2025 09:13:22 GMT

Hi,

Packet pattern is selectable in the application:

[quote user="Paul Lin"]I also noticed that your picture is same as mine with can`t control power. Do you have any recommended method to solve issue?[/quote]

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:

[quote user="Paul Lin"]

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.

[/quote]

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

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

Paul Lin — Thu, 08 May 2025 07:37:28 GMT

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

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

Paul Lin — Thu, 08 May 2025 06:28:24 GMT

Hi Hakon:

BTW,

Does the packet pattern of DTM with ALL1 or ALL0?

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

Paul Lin — Thu, 08 May 2025 06:27:13 GMT

Hi Hakon:

The console print "DTM setup tx power command failed with 8 dbm"

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

Paul Lin — Thu, 08 May 2025 02:45:27 GMT

Hi Hakon:

Does any limitation for power setting of Direct Test Mode?

I noticed if I set the power under 0dBm will cause the communication failed.

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

Paul Lin — Thu, 08 May 2025 02:38:04 GMT

Hi Hakan:

I noticed that the programmer doesn`t burn into the board successfully but i noticed one issues can`t understand.

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.

But can`t see the significant power difference between these two power settings.

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

Håkon Alseth — Mon, 05 May 2025 12:57:15 GMT

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