Use Shell over UART and UART ASYNC API on nRF52840

RE: Use Shell over UART and UART ASYNC API on nRF52840

Stew — Wed, 28 Sep 2022 03:15:12 GMT

Kenneth,

Thank you - your recommendations were very helpful. I was able to get them co-existing with one modification.

My .conf file:

CONFIG_SHELL=y
CONFIG_UART_0_INTERRUPT_DRIVEN=y
CONFIG_UART_0_ASYNC=n # <===================================

CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_1_ASYNC=y
CONFIG_UART_1_INTERRUPT_DRIVEN=n # <===================================

If I didn't add the 2 additional lines above (the two "...=n" lines), I got this message:

warning: UART_1_ASYNC (defined at drivers/serial/Kconfig.nrfx:161) was assigned the value 'y' but
got the value 'n'. Check these unsatisfied dependencies: (!UART_1_INTERRUPT_DRIVEN) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UART_1_ASYNC and/or look up UART_1_ASYNC 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.

With the above .conf file alterations, my larger project (not just the example code) is able to use the Shell on uart0 and the UART ASYNC API on uart1.

RE: Use Shell over UART and UART ASYNC API on nRF52840

Kenneth — Tue, 27 Sep 2022 12:10:46 GMT

You can enable both api's but then you need to explicitly specify which instance is using what (otherwise it relies on the defaults). So something like this should be ok:

CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_SHELL=y

CONFIG_UART_0_INTERRUPT_DRIVEN=y # Instance used by shell

CONFIG_UART_1_ASYNC=y #instance for other purposes supporting async api

RE: Use Shell over UART and UART ASYNC API on nRF52840

Kenneth — Tue, 27 Sep 2022 08:49:29 GMT

Hello,

I have created an internal for the developers to take a look.

Kenneth