Direct Test Mode with nRF21540

RE: Direct Test Mode with nRF21540

Dominik Eugster — Thu, 15 Feb 2024 13:56:54 GMT

Hi Simon

Yes, the code with Zephyr is still not working, why I really have no idea and not enough time to figure it out...
The old SDK is ok and I limit the output power manually.

thanky anyway, but it seems there is a bug in the project or I make something completly wrong, possible aswell...

Have a nice day

RE: Direct Test Mode with nRF21540

Simonr — Thu, 15 Feb 2024 10:12:46 GMT

Yes, the configs look correct now Dominik. Are you still seeing the same error in the DTM app when running the Zephyr sample with these configs as well?

If you're using the nRF5 SDK, you will indeed need to set the input power manually, as we don't have specific support for the nRF21540 in the old SDK, which is why we've been trying to get it up and running on the nRF Connect SDK for you. But if you manage to set it up with the old SDK, you should be fine with that for DTM testing as well.

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Susheel Nuguru — Wed, 14 Feb 2024 06:00:23 GMT

Dominik,

Sorry for delayed response. Simon is OoO until tomorrow and will look at this right after. Thanks for your patience so far.

RE: Direct Test Mode with nRF21540

Dominik Eugster — Fri, 09 Feb 2024 17:34:44 GMT

Hi Simon

For your information: I was not able to get running the zephyr project but the old DTM project stored in :nRF5_SDK\examples\dtm\direct_test_mode\pca10056\blank\ses

I was able to get running with teh same custom made hardware. Also I checked with a spectrum analyzer the output and frequency, which is doing exactly what I set in the DTM Nordic App.

I checked some details there and I saw that I can set the transmit power to +8dBM in DTM App. In combination with the nRF21540 the Input power of the nRF21540 should be lmited to +5dBM according the datasheet / AppNote. I think I have to do this manually in the driver or what is the recommended operation in DTM? (to avoid a too high input power of the nRF21540 when the tester set +8dBm)

Thanks and have a nice weekend

RE: Direct Test Mode with nRF21540

Dominik Eugster — Fri, 09 Feb 2024 07:21:45 GMT

Update: I have a 32MHz clock connected, in the first schematic this was not visble, but yes no clock on XL1/XL2 pins and no DCDC components (inductors and cap) connected to the DCC pin

RE: Direct Test Mode with nRF21540

Dominik Eugster — Thu, 08 Feb 2024 16:47:15 GMT

Hi Simon

I did the changings in the KConfig Gui, is this correct?

Then the direct Test Mode app is still not able to connect but on the Terminal tool I got this HEX output when I switch on my device:

Am I missing something? Thanks for your effort!

RE: Direct Test Mode with nRF21540

Simonr — Thu, 08 Feb 2024 13:46:19 GMT

After a second look at your HW we see that you have no external LF clock (connected to the XL1/XL2 pins) and no DCDC components (inductors and cap) connected to the DCC pin in your HW. Have you made sure to configure your project to disable DCDC ( CONFIG_BOARD_ENABLE_DCDC = n ) and set the RC oscillator as the active LF clock source ( CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC = y and CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL = n )

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Dominik Eugster — Wed, 07 Feb 2024 14:08:07 GMT

Hi Simon

The code is working with the DK nRF21540-DK like I already wrote in the initial post. The Com-Port is not in use, this I am 100% sure. There must be a problem with the Pin configuration, but if this config overlay I sent you is correct then I have no idea what is the problem. The hardware is working correctly and the software with the original nordic DK is working, the only difference is the PIN configuration and the board, but I will solder a RS232 FTDI converter to the Pins to double check this even this all make no sense for me... Hopefully the HW engineer have an idea to get this issue solved.

Thanks

RE: Direct Test Mode with nRF21540

Simonr — Wed, 07 Feb 2024 13:53:20 GMT

The flow control seems to be disabled already in the DTM sample, so we can scratch that as an issue. It's mentioned as a note in the example that BLE DTM specifies no flow control as the standard, so that shouldn't be the issue either. From the log I'm not able to tell much either unfortunately, but it could be that the UART is already in use on another terminal when you're trying to connect, but most likely it is because of the firmware not being detected as DTM firmware correctly by the app. Can you see if you're also having issue testing with another DK as the receiver or with the Direct Test Mode terminal connection?

I'll have to discuss this with one of our HW engineers to double check that your HW looks okay and should work as intended.

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Dominik Eugster — Wed, 07 Feb 2024 09:41:40 GMT

here the log File

devzone.nordicsemi.com/.../2024_2D00_02_2D00_07T09_5F00_39_5F00_29.920Z_2D00_log.zip

RE: Direct Test Mode with nRF21540

Dominik Eugster — Wed, 07 Feb 2024 08:22:33 GMT

Hi Simon

Yes this would explain this, but I have no RTS and CTS pins connected on my board. Is it not possible to use theDTM without RTS and CTS? of course I should disable the flow control feature somewhere in the initializasion of the UART0, but where? Maybe this would be much easier to fix?

I will do the log with the logging enabled and update this log soon.

Best regards, Dominik

RE: Direct Test Mode with nRF21540

Simonr — Tue, 06 Feb 2024 10:25:33 GMT

I think you also need the CTS and RTS pins configured on the custom board for the DTM app to work correctly, and these doesn't seem to be included in your overlay. Can you also enable verbose logging and upload the log file from the DTM app here so I can take a look at that? Go to the ABOUT tab, enable and restart with verbose logging, try selecting the custom board in the DTM app and open and upload the log file here on DevZone.

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Dominik Eugster — Mon, 05 Feb 2024 11:36:09 GMT

Hi Simon

The nrfConnect app is working with the nRF21540-DK connected over USB. If I connect my custom made board (which is working with the original custom made code) and download the same project with the overlay file I posted, then the nrf connect app is not able to connect.

Can you tell me if the definition in the G3.overlay is correct for my board, which has the RX and TX connected like this?

I'm working on Win10Pro.

&uart0_default {
	group1 {
		psels = <NRF_PSEL(UART_TX, 0, 20)>, <NRF_PSEL(UART_RX, 0, 24)>;
	};
};

custom board:

The overlay file I did with the DeviceTree

RE: Direct Test Mode with nRF21540

Simonr — Mon, 05 Feb 2024 10:13:47 GMT

I tested on an nRF21540 DK on my end, and the nRF Connect for Desktop DTM app runs without issues on my end there. Can you confirm that the DTM app is running if you build your custom board with the nRF5 SDK DTM project with the J-Link adapter as connector. Are you working on a Windows or Linux machine? I'm just trying to narrow down what the issue can be.

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Dominik Eugster — Fri, 02 Feb 2024 15:19:07 GMT

It is connected over the UART from the J-Link adapter, the same port which I use for our standard software. This port is working 100%, only with the zephyr there is something wrong and I can't find what it is. Honestly, I'm not used to the zephyr and VS Code environment, but the PIN configuration is correct and I can't see why this is not running with the DTM app.

RE: Direct Test Mode with nRF21540

Simonr — Fri, 02 Feb 2024 08:45:43 GMT

How is your device connected to your computer exactly? The DTM app uses a serial interface to communicate with the board, so if it is only connected to the J-Link device and the SWD pins, you won't be able to use the DTM app, and might want to do testing with a certified tester or another of the Testing options.

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Dominik Eugster — Thu, 01 Feb 2024 15:06:03 GMT

I changed the overlay file, now I can compile and flash my board. If I use the Direct Test Mode App there is communication error, this means the config or code is not working on my board or is there a possible other reason?

devzone.nordicsemi.com/.../8204.G3.overlay

RE: Direct Test Mode with nRF21540

Simonr — Fri, 26 Jan 2024 11:46:11 GMT

From a look at your .overlay file, it seems like you're missing the pinctrl defines that is necessary when setting up a custom board. Please check out the Custom boards documentation here, and the Pin Control documentation here.

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Dominik Eugster — Thu, 25 Jan 2024 13:59:15 GMT

Ok thank you for the information.

I added a own overlay file but got this error, can you please take a look what is wrong in this file?

devzone.nordicsemi.com/.../G3.overlay

RE: Direct Test Mode with nRF21540

Simonr — Tue, 23 Jan 2024 07:27:00 GMT

This has been confirmed by the devs and been fixed in the master branch. The next release of the VS Code extension will have this issue fixed. For pin configs for your custom board you should add that to an overlay file where you define your pin assignments for the peripherals you want to use.

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Dominik Eugster — Mon, 22 Jan 2024 14:53:00 GMT

Ok, thank you for this information.

Regarding the DTM test sample: Where do I made the pin definition settings for the custom hardware board?

In the dtm_hw_config.h the define NRF52840_XXAA is made somewhere but I cant find the reference.

Thank you

RE: Direct Test Mode with nRF21540

Simonr — Mon, 22 Jan 2024 08:54:01 GMT

Hi Dominik

I'm able to reproduce this as well, so this is a bug either in the VS code extension or the sample itself. I have reported it internally and the devs will investigate.

Thank you for reporting this. For now, I'd recommend just building it from scratch if you need to make any changes to the build configuration and not use the "Edit build configuration" button.

Best regards,

Simon

RE: Direct Test Mode with nRF21540

Dominik Eugster — Fri, 19 Jan 2024 16:51:48 GMT

Update:

If I add a new build config and build it, I got only 3 problems:

Then I go to Edit build config, DON'T cahnge anything and press again on build I got Errors, this is more than strange. I can remove the actual buld config and add a new one and it's working again... Can somebody explain this?

RE: Direct Test Mode with nRF21540

Dominik Eugster — Fri, 19 Jan 2024 12:43:29 GMT

Then the build is not possible, I didn't wrote this argument, its getting generated automatically if I select use build system default and build:

If I select the prj.conf I have more errors and no HEX Output...

Is there a documentation how to set this build config correctly to get a clean output without warnings and errors? The project DTM in samples for sure is ok, so the problem will come from the build config or missing CMake arguments.

Thanks a lot

RE: Direct Test Mode with nRF21540

Simonr — Fri, 19 Jan 2024 12:22:31 GMT

There seem to be a lot of problems indeed here. The only build configuration difference I can see is that you have -DBOARD_ROOT="." in your CMake arguments. Can you try removing this to see if it changes anything? But if the application is working as intended problems in terms of "warnings" and "info" in NCS can be ignored.

Best regards,

Simon