problem with CTE packets on nrf5340

RE: problem with CTE packets on nrf5340

Simonr — Mon, 04 Jan 2021 12:53:52 GMT

Hi again

The nRF5340 DK has only been tested with the Programmer app. The DTM app should support any device following the BLE DTM specification (the version from the nRF5 SDK). So you'll need to modify and program this DTM firmware onto the nRF5340 in order to run it on the nRF Connect application.

One of our developers tested the DTM example for the nRF5340 using an RF tester and found that the CTE worked as intended. The duration of the CTE is also required. The issue could you're seeing could be specific to NCS v1.4.0 (if that's the version you're using), where an incorrect SHORT was set up in the Radio. This was fixed with the following commit (see GitHub link here). It is recommended to rebase on top of the sdk-nrf master or use the Development tag (v1.4.99-dev1).

Best regards,

Simon

RE: problem with CTE packets on nrf5340

Simonr — Mon, 07 Dec 2020 14:01:58 GMT

Hi Mohammad

I have contacted the developers of this project with a request asking how we can make the CMW detect these packets (either by making some changes to the project or by some other clever solution). Thank you for your patience and explanations thus far. I will get back to you as soon as I hear from the devs.

Best regards,

Simon

RE: problem with CTE packets on nrf5340

Mohammad Ranjbar — Fri, 04 Dec 2020 19:03:27 GMT

Hi Simon,

The description of the DTM project is in the following link:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/direct_test_mode/README.html

This project is included in nrf connect SDK v1.4.0

RE: problem with CTE packets on nrf5340

Simonr — Thu, 03 Dec 2020 12:00:26 GMT

Hi Mohammad

Okay, that makes more sense, thank you for explaining. But can you explain what DTM firmware you are referring to?

Best regards,

Simon

RE: problem with CTE packets on nrf5340

Mohammad Ranjbar — Wed, 02 Dec 2020 17:37:33 GMT

Hi Simon,

sorry for the confusion; maybe I did not explain the problem clearly. I am using Direct Test Mode (DTM) for BLE tests. For BLE tests under DTM mode, the tester (in my case CMW500) sends command through UART to the DUT (nrf5340) on what kind of packet it should send. Then the DUT responds to the command (sent by tester) and transmits the requested BLE packet to the tester. For example for Frequency Offset and Drift test for CTE packets, the requested packet has PDU length of 37 bytes with pattern 11110000, CTE length of 20 bytes (customizable). The tester receives this packet, detects it and does some calculation on it and gives us the test result. The tester that I use (CMW 500) uses power trigger to detect the start of the received packets. But the DTM firmware that I downloaded using nrf connect transmits packets with CTE in a way that we have always transmit power even in between packets, so CMW500 can not detect the packets.

RE: problem with CTE packets on nrf5340

Simonr — Wed, 02 Dec 2020 14:07:42 GMT

Hi Mohammad

This doesn't make much sense to me, can you try to explain this in a bit more detail? An unmodulated carrier isn't a packet, and won't contain any information. The direct test mode has specified when the packets will be sent, so you shouldn't have to trig this on your end.

If you only want to use unmodulated carrier to verify if the DUT is transmitting or not, you should be only to just turn the spectrum on without a trig on the CMW500 (I think).

Best regards,

Simon