nRF52833-DK DTM test warning

[ivnn]

Hi,
Could you pls check, is it ok if these logs happened?

No firmware defined for selected device
Please make sure the device has been programmed with a supported firmware

(sdk17.0.2 dtm test, nrfConnect 3.6.1, pca10100.hex, nrf52833-dk)
Anyway seems all works fine transmit and receiving.

[ovrebekk]

Hi Ivan

As long as the test starts without reporting an error it should be fine. If the target board is not programmed correctly you won't be able to start the test. 

Can you try to press CTRL + R and do the test again?

This will reload the application, and most likely you will not see the same warning. 

Best regards
Torbjørn

[ivnn]

CTRL + R did not help, anyway looks like the application works as well!
One more question, Am I right it's impossible to see the transmitter device during the scan with nrfConnect for mobile appl? 

[ovrebekk]

Hi Ivan

ivnn said:

Am I right it's impossible to see the transmitter device during the scan with nrfConnect for mobile appl? 

That is correct. 

In DTM mode the radio is not sending full Bluetooth packets. Instead it is enabling the radio in a constant carrier mode, and the data is simply a sequence of ones and zeroes, or a sequence of pseudo random numbers. 

This will make the carrier visible to a receiver in DTM mode, or a spectrum analyzer for lab testing, but not to regular Bluetooth devices. 

Best regards
Torbjørn

[ivnn]

Hi, I need your advice, 
I prepared a dtm firmware and want to load it via dfu update on an existing device with a secure bootloader
I prepared a zip with dtm app and after flashing it seems to start but I see it appears as a DfuTarg which block dtm functionality, are there any way to block sofdevice from dtm app, sd_softdevice_disable() or so? 

[ovrebekk]

Hi Ivan

In general I would recommend opening a new ticket if you have DFU related questions, since I don't have a lot of experience with DFU., but I will try to help you out in this case

The problem might be that your DTM app is built without the SoftDevice in place, which means it will not run when a SoftDevice is present. 

If this is the problem it should be enough to build your DTM application in the same way that you build your normal applications, by setting the application flash area to start at the end of the SoftDevice region. 
As long as you don't enable the SoftDevice in the code the SoftDevice will not interfere with the operation of the DTM code, and the code should run as if the SoftDevice was not there. 

Best regards
Torbjørn