can't find board nrf52833dk_nrf5283 in bluetooth DTM sample

[christopheMon]

Hello,

I have a project in Visual studio code and Nrf connect.

MCU is a NRF 52833.

For the certicications, the lab request me the DTM mode.

I tried the use the Sample - Direct-test-mode Firmware

However I'm not able to find eht board "nrf52833dk_nrf5283" in the NCS folder.

I tried to install several SDKs (2.2.0 / 2.3.0 / 2.4.2 / 2.7.0 / 2.9.2 / 3.2.4 ) but none includes the 833 board. I can find and compile with the 840, but no options for the 833.

Please can sombody help me ? I need to use and compile the DTM for the 52833.

Thanks in advance

[Kenneth]

Hi,

If you choose Nordic Kits you can build for nRF52833dk like this:

But I assume you are not using direction finding, so you need to disable it by either adding to app.overlay:

&radio {
	/delete-property/ dfe-supported;
};

Or build as described here: 
https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/direct_test_mode/README.html#disabling_direction_finding_feature 

Kenneth

[christopheMon]

hello, thanks for your reply, however, with the Nordic Kit selection, (and not the Compatible), impossible to compile the code...

I can compile selecting the nRF52840 only...

how to get just a simple code for DTM for the 833 ?

Also don't you have example with the USB communication ?

I can't understant how all people using nrf devices have to certificate them then every body have to use the DTM too... nothing is proposed for this ? I mean PC software - USB control and DTM for most nrf devices ?

So in my case, I need to create a new board to use with the DTM as the 52833 is not available...right ?

[Kenneth]

In the build folder you can check zephyr.dts file.

Kenneth

[christopheMon]

3652.build.zip

herer is my build folder, in the zephyr.dts, I can't find the configuration....

Maybe it is the issue not ?

[christopheMon]

after checking, the pin 0.22 is not configured.

No pull-up configured. without connections to the external FTDI device, the pin is always 0V.

[Kenneth]

Try a pristine build, or manually delete the build folder before building.

Kenneth

[christopheMon]

each time I build I do that... first I delete build then I build a new... the issue is not here... but my overlay seems still not taken in account