Using radio_test sample on custom board.

[nicoled123]

Hi,

I want to run the radio_test sample on a custom board, how do I go about doing this?

The custom board uses a UBLOX NINA B401- which utilises the nRF52833 chip. Do you have any examples available for the UBLOX NINA B401 chip, including how to set up a dts for custom boards etc. 

I have the radio test sample running successfully using two nRF52840-DK boards, using nRF connect SDK on Visual Studio.

[Einar Thorsrud]

Hi,

If you do not have board files fro your device yet you can add an overlay file that re-configures the UART pins for the DK to match your hardware, and connect to those pins. You can also simply change the pin configuration in the DK pinctrl file itself, and build for the DK. If so, update the uart0 pins in zephyr/boards/nordic/nrf52833dk/nrf52833dk_nrf52833-pinctrl.dtsi.

Also, if the module does not include the DCDC componts, set CONFIG_BOARD_ENABLE_DCDC=n in prj.conf. In the same way, if it does not include the 32.768 kHz crystall, set CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y in prj.conf.

[nicoled123]

Thanks for your response! Do you have any examples available for the UBLOX NINA B401 chip and is it possible for the radio_test sample to work on it, or does it require any specific hardware that is in included in nrf52840-DK?

Is it only the UART pins i need to change in the overlay files or will there be others too?

[Einar Thorsrud]

Hi,

The radio test sample does not requer any HW that is not present on that or any othe rmodule. But I see it does not have the 32.768 kHz oscillator, so you ned to use the CONFIG_BOARD_ENABLE_DCDC=n that I specified in my previous post. You can also add CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y without any problem, though should not be needed. Then the only remaining thing is to update the UART pin configuration. I do not know which GPIO pins you have accessible for use with UART on your device, but get hold of those, and update the board file accordingly (you can just modify the DK borad file itself for simplicity), and that should be all. When you have programmed the sample you controll it via UART as explained in the sample documentation: Radio test (short-range).

[nicoled123]

I can build the radio test sample with no errors for the nrf 52840 DK. I now have a nrf52833 DK which I wanted to test the sample on before moving on to my custom board. However, i get a fatal error. do i need to do anything to make the radio test sample compatible with the nrf52833? 

ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\ce3b5ff664\opt\bin\cmake.EXE' --build 'c:\nordic\myapps\radio_test_1\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

[nicoled123]

[Einar Thorsrud]

Hi,

Which SDK version are you using here? I am not able to reprodcue with the latest release of nRF Connect SDK, which is 2.7.0.

[nicoled123]

I am using the latest version

[Einar Thorsrud]

I see. Did you make any other changes to the project than what we have discussed? Can you share the project with your modifications? Also, if you build the project without any modifications, will it build then?

[nicoled123]

I fixed this issue by including CONFIG_CORTEX_M_SYSTICK=n in proj.conf. And successfully got the radio test running on nrf52833 DK, however now when attempting on my custom board using Ublox NINA B401. I am not getting any response. 

Rather than adding overlay file, I edited the .dtsi file to match my board making it 

&pinctrl {

    uart0_default: uart0_default {

        group1 {

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

                //<NRF_PSEL(UART_RTS, 0, 5>;

        };

        group2 {

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

                //<NRF_PSEL(UART_CTS, 0, 7)>;

            bias-pull-up;

        };

    };

Note I have commented out the RTS and CTS code as I do not have these connections on my board will that be an issue?

My proj.conf is:

CONFIG_CONSOLE_HANDLER=y

CONFIG_SHELL=y

CONFIG_DYNAMIC_INTERRUPTS=y

CONFIG_NRFX_TIMER0=y

CONFIG_ENTROPY_GENERATOR=y

CONFIG_NRF_SECURITY=y

CONFIG_FEM_AL_LIB=y

CONFIG_CORTEX_M_SYSTICK=n

CONFIG_BOARD_ENABLE_DCDC=n

 

los is it possible to use the nrf connect serial terminal for chips connected via JTAG, as currently my board is not coming up in the available devices. Therefore I am using a python script currently to read the serial data, which I am not recieing any and I am expecting: 

Clock has started

[Einar Thorsrud]

Hi,

nicoled123 said:

I fixed this issue by including CONFIG_CORTEX_M_SYSTICK=n in proj.conf.

I see. It should not be needed though, and the sample builds out of the box for the nRF52833 DK on my end. Could it be that you have (inadvertedly or not) made some changes to the SDK? It could be worth wonloading the SDK and toolchain again to know that you have a good starting point.

nicoled123 said:

Note I have commented out the RTS and CTS code as I do not have these connections on my board will that be an issue?

There is no need to comment out the flow control pin configuration. The default configuration for the DK does not enable flow control as the hw-flow-control property is not present. You can verify this by looking at the generatd zephyr.dts file in the build folder. And if you have a board where it is defined you can remove it in the board file or add an overlay with the following (adjust to another uart instance if not using uart0):

&uart0 {
     /delete-property/ hw-flow-control;
};

nicoled123 said:

los is it possible to use the nrf connect serial terminal for chips connected via JTAG, as currently my board is not coming up in the available devices.

You can use PuTTY or another serial terminal of your choise as well.

Note that if you still have problems you can use Segger RTT with the radio test example, by adding the following to prj.conf if you have a Segger debugger:

CONFIG_USE_SEGGER_RTT=y
CONFIG_SHELL_BACKEND_RTT=y

But please be aware that RTT does continious access to the device which will cause noise and affect the measurements, so you should keep that in mind. 

Br,

Einar

[nicoled123]

Thanks for your help!  I reinstalled SDK and toolchains and that fixed the need for adding   CONFIG_CORTEX_M_SYSTICK=n in proj.conf.

However I am still having issues running samples on my custom board. I am currently to run the simple blinky sample and no luck. I have tried adding an overlay to nrf52833 DK to change led0 from 13 to 28 and no luck! I have also tried creating a custom board. I have attached the custom board folder and also the blinky project I am working with (I have tested on nrf52833DK and it works on it). Also please see image below for pin out of my custom board. 

I have tried flashing the board via nrf Connect VS code, programmer from nrf Connect Desktop and also JFlash.  I am using a Jlink Segger Plus to flash the board. wombat_nina.zip1526.BLINKY.zip