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 ?

[christopheMon]

that's right, I don't have the 32k, only have the 32M

However It still don't work, see the pin voltage on the scope, yellow is the Tx from computer (MCU P0.22), sending a single char and purple is the MCU TxD P0.24 (= Computer RxD). Level of MCU TxD is not good ... and not working..

How can I debug it ?

[Kenneth]

Do you have a DK for comparison? then you can just connect a wire between p0.22-p0.08 and p0.24-p0.06 to test the setup on a DK, the wires will connect the pins to the UART of the DK, and you can for instance open a virtual comport on the PC for testing.

Kenneth

[Kenneth]

Also, you can't set the pins like you have done, you need to use pin control, e.g.

&pinctrl {
	uart0_default: uart0_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 24)>;
		};
		group2 {
			psels = <NRF_PSEL(UART_RX, 0, 22)>;				
			bias-pull-up;
		};
	};

	uart0_sleep: uart0_sleep {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 24)>,
				<NRF_PSEL(UART_RX, 0, 22)>;				
			low-power-enable;
		};
	};
};

And keep pinctrl-0 = <&uart0_default>; and pinctrl-1 = <&uart0_sleep>; in &uart0.

Kenneth

[christopheMon]

I just ordered a DK, I only have our custom PCBs. And connecting the pin 6 or 8 is impossible on my PCB as it is a QFN 73...

[christopheMon]

My overlay is now as : 

/* overlay-dt.dts */

/*&uart0 {

    status = "okay";

    tx-pin = <24>;

    rx-pin = <22>;

    current-speed = <115200>;

};

*/

&radio {

    /delete-property/ dfe-supported;

};

&pinctrl {

    uart0_default: uart0_default {

        group1 {

            psels = <NRF_PSEL(UART_TX, 0, 24)>;

        };

        group2 {

            psels = <NRF_PSEL(UART_RX, 0, 22)>;            

            bias-pull-up;

        };

    };

    uart0_sleep: uart0_sleep {

        group1 {

            psels = <NRF_PSEL(UART_TX, 0, 24)>,

                <NRF_PSEL(UART_RX, 0, 22)>;            

            low-power-enable;

        };

    };

};

but still same on the pin 22 and 24 ...

How may I check if my overlay is really taken in account ?

[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