Unable to send commands over VS studio terminal or putty due to unsatsified dependencies in Kconfig while building with nrf radio test using a custom defined nrf52833 board in nrf connect SDK 2.9.0

[Mario_Bever]

I want to use the radio test code from the nrf example library to tune the nrf52833 on a custom board. I managed to build and flash the project, but when connecting to the serial port I am not able to send any commands like "parameters_print". However, the terminal states it has a connection on the correct com port. The compiler provides also the following warning:

warning: CONSOLE_HANDLER (defined at drivers/console/Kconfig:27) was assigned the value 'y' but got
the value 'n'. Check these unsatisfied dependencies: UART_CONSOLE (=n), SERIAL_SUPPORT_INTERRUPT
(=n), CONSOLE (=n). See docs.zephyrproject.org/.../kconfig.html
and/or look up CONSOLE_HANDLER in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

I tried to add the unsattisfied dependencies to the prj.conf file and assign the value y to them but I get stuck at SERIAL_SUPPORT_INTERRUPT and CONFIG_SERIAL_HAS_DRIVER since they are not directly user-configurable.

I am quite new to this sdk so it might be something small I am missing but it would be nice if somebody is able to help me.

Thanks in advance!

[Kenneth]

Hello,

If you build the project for the nrf52833dk/nrf52833 you can use the nrf52833dk_nrf52833.dts file as reference. I expect you are for instance missing zephyr,console = &uart0;

Kenneth

[Mario_Bever]

Thanks for the fast reply. I managed to make it work for the nrf52833-dk. I used the dts and dtsi files of the nrf52833dk/nrf52833 as reference and coppied the uart0 related code. Adding CONFIG_UART_CONSOLE=y  and CONFIG_CONSOLE=y to the prj.conf file fixed the warning.

However, I still have problems. The serial number of the development kit is visible under the connected devices. When expanding, the chip name (NRF52833_xxAA_REV2) changes into NRF52833_xxAA_REV1 when the custom board is connected on debug out. However, whether the custom board is connected or not, I am only able to communicate with the DK. How can I make sure that I am connected to the custom board?

[Kenneth]

Hello,

If you normally work with the DK, and then have your own board that you want to program and use with uart, then here are some pointers:

1. Make sure to run erase or recover on the nRF52833 on the DK, this to ensure it's not running any code or forcing any pins high or low.

2. Program the external board for instance using the debug output header (connect pin 9 to GND_DETECT on the external board for the DK to know it should use an external board for programming and debugging):
https://docs.nordicsemi.com/bundle/ug_nrf52833_dk/page/UG/dk/ext_programming_support.html (So a total of 5 pins connected: VDD, GND, SWDIO, SWDCLK and GND_DETECT).

3. If you want to use forward the UART pins from the external board to the COM port of the PC, then you need to hook 4 pins (or only 2 if you don't use hardware flow control) to 4 (or 2) pins described here:
https://docs.nordicsemi.com/bundle/ug_nrf52833_dk/page/UG/dk/vir_com_port.html 

Kenneth

[Mario_Bever]

Hello,

It has been some time but your answers helped me in the right direction to be able to continue the development. Thanks a lot.