DTM test not returning any packets

[Alex Crombie]

We have the following setup:
 - Both nRF52832 and nRF52840 chips in our product

 - The nRF52832 is a module while the nRF52840 is the chip integrated directly onto our PCB

 - SDK 15.0.0 (and integrating ble_dtm.c into our test firmware)

 -  Our devices communicate quite happily over BLE with each other in all configurations (832-832, 832-840, and 840-840) (relevant a bit later)

We are looking to do certification for our devices and we need to get the packet error rate in a blocking test. I have already looked at nAN34_v1.01 and was planning to retrieve the packet error rate as in the python scripts. As the nRF52 chips are already integrated into our product we have implemented the DTM interface over I2C rather than serial.

The issue we are seeing is that we start the test by setting out of the devices to transmit with the following options followed by running the receiver test for 1-5 seconds before ending the receiver test. When the test is ended the number of received packets is reported as 0:

The transmitter is setup as follows:

- RESET: 0x0000

- Top two bytes in length to 11: 0x010c

- PHY 2M: 0x0208

- TX power -8dBm: 0xb80b

- Start Transmit PRBS9 Max length @ 2442MHz: 0x94fc

The receiver is setup as follows:

- RESET: 0x0000

- Top two bytes in length to 11: 0x010c

- PHY 2M: 0x0208

- Start Receive PRBS9 Max length @ 2442MHz: 0x54fc

- Wait 1-5 seconds

- End Test: 0xc000

For each of the operations ble_dtm.c returns the result as 0, and the ending of the receiver test always returns 32768 which should be packet report: count=0, this is irregardless of the channel selected.

A couple of questions:
1) Is there anything wrong in the setup and commands used?

2) Any Idea why ending any test always returns the packet count as 0?

[Håkon Alseth]

Hi,

 

As the nRF52 chips are already integrated into our product we have implemented the DTM interface over I2C rather than serial.

 Is there a specific reason for not using UART with DTM? How do you interface the nRF? Using a USB->I2C bridge?

 

 

1) Is there anything wrong in the setup and commands used?

Do you parse the response data from the DUT? Command-wise, this looks OK.

 

Here's the log file from entering TX/RX with your specified settings taken from nRF Connect for desktop -> direct test mode application:

Fullscreen dtm_rx_2Mbit_2442MHz.txt Download

2021-03-08T13:27:47.466Z INFO Application data folder: /home/hkn/.config/nrfconnect/pc-nrfconnect-dtm
2021-03-08T13:27:47.555Z DEBUG App pc-nrfconnect-dtm v1.1.7 official
2021-03-08T13:27:47.555Z DEBUG App path: /home/hkn/.nrfconnect-apps/node_modules/pc-nrfconnect-dtm
2021-03-08T13:27:47.555Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.2.0)
2021-03-08T13:27:47.555Z DEBUG nRFConnect path: /tmp/.mount_nrfcong25EQb/resources/app.asar
2021-03-08T13:27:47.555Z DEBUG HomeDir: /home/hkn
2021-03-08T13:27:47.555Z DEBUG TmpDir: /tmp
2021-03-08T13:27:48.345Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2021-03-08T13:27:48.345Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2021-03-08T13:27:48.345Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2021-03-08T13:27:48.345Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2021-03-08T13:27:48.346Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2021-03-08T13:27:48.346Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2021-03-08T13:27:48.346Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2021-03-08T13:27:48.346Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2021-03-08T13:27:48.346Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2021-03-08T13:27:48.346Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2021-03-08T13:27:48.346Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS22
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS23
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS24
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS25
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS26
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS27
2021-03-08T13:27:48.347Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS28
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS29
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS30
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS31
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS4
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS5
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS6
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS7
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS8
2021-03-08T13:27:48.348Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS9
2021-03-08T13:27:54.336Z INFO Validating firmware for device with s/n 000683340399
2021-03-08T13:27:56.742Z INFO Device selected successfully
2021-03-08T13:28:02.969Z INFO Running device setup
2021-03-08T13:28:02.969Z DEBUG DTM Transport: Create setup CMD with control: 0
2021-03-08T13:28:02.970Z DEBUG DTM Transport: Create setup CMD with parameter: 0
2021-03-08T13:28:02.970Z DEBUG DTM Transport: Create setup CMD with dc type: 00
2021-03-08T13:28:02.973Z DEBUG DTM Transport: Serialport is opened
2021-03-08T13:28:02.974Z DEBUG DTM Transport: Succeeded to open serialport
2021-03-08T13:28:02.975Z DEBUG DTM Transport: Sending data: 0x00 0x00
2021-03-08T13:28:02.982Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:28:02.983Z DEBUG DTM Transport: Create tx power CMD: 0
2021-03-08T13:28:02.983Z DEBUG DTM Transport: Sending data: 0x80 0x0B
2021-03-08T13:28:02.990Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:28:02.990Z DEBUG DTM Transport: Create setup CMD with control: 1
2021-03-08T13:28:02.990Z DEBUG DTM Transport: Create setup CMD with parameter: 0
2021-03-08T13:28:02.990Z DEBUG DTM Transport: Create setup CMD with dc type: 00
2021-03-08T13:28:02.990Z DEBUG DTM Transport: Sending data: 0x01 0x00
2021-03-08T13:28:02.997Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:28:02.997Z DEBUG DTM Transport: Create setup CMD with control: 3
2021-03-08T13:28:02.998Z DEBUG DTM Transport: Create setup CMD with parameter: 0
2021-03-08T13:28:02.998Z DEBUG DTM Transport: Create setup CMD with dc type: 00
2021-03-08T13:28:02.998Z DEBUG DTM Transport: Sending data: 0x03 0x00
2021-03-08T13:28:03.005Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:28:03.005Z DEBUG DTM Transport: Create setup CMD with control: 2
2021-03-08T13:28:03.005Z DEBUG DTM Transport: Create setup CMD with parameter: 2
2021-03-08T13:28:03.005Z DEBUG DTM Transport: Create setup CMD with dc type: 00
2021-03-08T13:28:03.006Z DEBUG DTM Transport: Sending data: 0x02 0x08
2021-03-08T13:28:03.012Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:28:03.013Z INFO Starting test
2021-03-08T13:28:03.016Z DEBUG DTM Transport: Create receiver CMD with frequency: 2442
2021-03-08T13:28:03.016Z DEBUG DTM Transport: Create receiver CMD with length: 1
2021-03-08T13:28:03.016Z DEBUG DTM Transport: Create receiver CMD with packet type: 0
2021-03-08T13:28:03.032Z DEBUG DTM Transport: Sending data: 0x54 0x04
2021-03-08T13:28:03.038Z DEBUG DTM Transport: Receiving data: 0x00 0x00

Fullscreen dtm_tx_min8dbm_2Mbit_2442MHz.txt Download

2021-03-08T13:15:35.015Z INFO Application data folder: /home/hkn/.config/nrfconnect/pc-nrfconnect-dtm
2021-03-08T13:15:35.107Z DEBUG App pc-nrfconnect-dtm v1.1.7 official
2021-03-08T13:15:35.108Z DEBUG App path: /home/hkn/.nrfconnect-apps/node_modules/pc-nrfconnect-dtm
2021-03-08T13:15:35.108Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.2.0)
2021-03-08T13:15:35.108Z DEBUG nRFConnect path: /tmp/.mount_nrfcong25EQb/resources/app.asar
2021-03-08T13:15:35.108Z DEBUG HomeDir: /home/hkn
2021-03-08T13:15:35.108Z DEBUG TmpDir: /tmp
2021-03-08T13:15:35.887Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2021-03-08T13:15:35.888Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2021-03-08T13:15:35.888Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2021-03-08T13:15:35.888Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2021-03-08T13:15:35.888Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2021-03-08T13:15:35.889Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2021-03-08T13:15:35.889Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2021-03-08T13:15:35.889Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2021-03-08T13:15:35.889Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2021-03-08T13:15:35.889Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2021-03-08T13:15:35.889Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2021-03-08T13:15:35.889Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2021-03-08T13:15:35.890Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2021-03-08T13:15:35.890Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2021-03-08T13:15:35.890Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
2021-03-08T13:15:35.890Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS22
2021-03-08T13:15:35.890Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS23
2021-03-08T13:15:35.890Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS24
2021-03-08T13:15:35.891Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS25
2021-03-08T13:15:35.891Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS26
2021-03-08T13:15:35.891Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS27
2021-03-08T13:15:35.891Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS28
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS29
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS30
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS31
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS4
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS5
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS6
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS7
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS8
2021-03-08T13:15:35.892Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS9
2021-03-08T13:15:38.769Z INFO Validating firmware for device with s/n 000683340399
2021-03-08T13:15:40.925Z INFO Device selected successfully
2021-03-08T13:15:52.980Z INFO Running device setup
2021-03-08T13:15:52.980Z DEBUG DTM Transport: Create setup CMD with control: 0
2021-03-08T13:15:52.980Z DEBUG DTM Transport: Create setup CMD with parameter: 0
2021-03-08T13:15:52.981Z DEBUG DTM Transport: Create setup CMD with dc type: 00
2021-03-08T13:15:52.985Z DEBUG DTM Transport: Serialport is opened
2021-03-08T13:15:52.985Z DEBUG DTM Transport: Succeeded to open serialport
2021-03-08T13:15:52.986Z DEBUG DTM Transport: Sending data: 0x00 0x00
2021-03-08T13:15:52.995Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:15:52.995Z DEBUG DTM Transport: Create tx power CMD: 56
2021-03-08T13:15:52.995Z DEBUG DTM Transport: Sending data: 0xB8 0x0B
2021-03-08T13:15:53.003Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:15:53.003Z DEBUG DTM Transport: Create setup CMD with control: 1
2021-03-08T13:15:53.004Z DEBUG DTM Transport: Create setup CMD with parameter: 3
2021-03-08T13:15:53.004Z DEBUG DTM Transport: Create setup CMD with dc type: 00
2021-03-08T13:15:53.004Z DEBUG DTM Transport: Sending data: 0x01 0x0C
2021-03-08T13:15:53.012Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:15:53.012Z DEBUG DTM Transport: Create setup CMD with control: 3
2021-03-08T13:15:53.012Z DEBUG DTM Transport: Create setup CMD with parameter: 0
2021-03-08T13:15:53.012Z DEBUG DTM Transport: Create setup CMD with dc type: 00
2021-03-08T13:15:53.013Z DEBUG DTM Transport: Sending data: 0x03 0x00
2021-03-08T13:15:53.020Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:15:53.020Z DEBUG DTM Transport: Create setup CMD with control: 2
2021-03-08T13:15:53.021Z DEBUG DTM Transport: Create setup CMD with parameter: 2
2021-03-08T13:15:53.021Z DEBUG DTM Transport: Create setup CMD with dc type: 00
2021-03-08T13:15:53.021Z DEBUG DTM Transport: Sending data: 0x02 0x08
2021-03-08T13:15:53.027Z DEBUG DTM Transport: Receiving data: 0x00 0x00
2021-03-08T13:15:53.028Z INFO Starting test
2021-03-08T13:15:53.029Z DEBUG DTM Transport: Create transmitter CMD with frequency: 2442
2021-03-08T13:15:53.030Z DEBUG DTM Transport: Create transmitter CMD with length: 63
2021-03-08T13:15:53.030Z DEBUG DTM Transport: Create transmitter CMD with packet type: 0
2021-03-08T13:15:53.044Z DEBUG DTM Transport: Sending data: 0x94 0xFC
2021-03-08T13:15:53.053Z DEBUG DTM Transport: Receiving data: 0x00 0x00

 

Could it be that you are parsing the data in the reverse byte order?

 

2) Any Idea why ending any test always returns the packet count as 0?

Have you checked that the devices enter its respective RX and TX mode? If you do not have a spectrum analyzer, you can look at the current consumption when the nRF enters RX or TX mode.

 

Kind regards,

Håkon