Async UART and shell module in Zephyr on nRF52480

RE: Async UART and shell module in Zephyr on nRF52480

Stew — Mon, 26 Sep 2022 17:54:59 GMT

As requested by Nordic support, I reposted my query in this new thread: Use Shell over UART and UART ASYNC API on nRF52840

RE: Async UART and shell module in Zephyr on nRF52480

Stew — Wed, 21 Sep 2022 16:01:10 GMT

AndyM, I'm glad that you were able to find an answer to your 2nd question (how to send data asynchronously over UART from a thread other than the shell), but did you get the 1st (original) question answered?

...is it possible to enable async UART support and the shell module in the same project?

I'm trying to use the shell on uart0 and the UART async API on uart1, but I'm beginning to think that these features are mutually exclusive.

When I enable UART async API support with these settings (in prj.conf),

CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y

I see these settings being applied to the project as a whole (in .config):

#
# Serial Drivers
#
CONFIG_UART_NRFX=y
CONFIG_UART_ASYNC_TX_CACHE_SIZE=8
CONFIG_UART_0_NRF_UARTE=y
CONFIG_UART_0_ENHANCED_POLL_OUT=y
CONFIG_UART_0_ASYNC=y # <======================================
# CONFIG_UART_0_NRF_PARITY_BIT is not set
CONFIG_UART_0_NRF_TX_BUFFER_SIZE=32
# CONFIG_UART_0_NRF_HW_ASYNC is not set
# CONFIG_UART_0_NRF_ASYNC_LOW_POWER is not set
CONFIG_UART_1_NRF_UARTE=y
CONFIG_UART_1_ASYNC=y # <======================================
CONFIG_UART_1_ENHANCED_POLL_OUT=y
# CONFIG_UART_1_NRF_PARITY_BIT is not set
# CONFIG_UART_1_NRF_HW_ASYNC is not set
# CONFIG_UART_1_NRF_ASYNC_LOW_POWER is not set
CONFIG_UART_ENHANCED_POLL_OUT=y
CONFIG_NRF_UARTE_PERIPHERAL=y

Note the "CONFIG_UART_0_ASYNC=y" and "CONFIG_UART_1_ASYNC=y" settings.

However, when I add shell module support with these settings (in prj.conf),

CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_SHELL=y # <======================================

I see these settings being applied to the project as a whole (in .config):

#
# Serial Drivers
#
CONFIG_UART_NRFX=y
CONFIG_UART_ASYNC_TX_CACHE_SIZE=8
CONFIG_UART_0_NRF_UARTE=y
CONFIG_UART_0_ENHANCED_POLL_OUT=y
CONFIG_UART_0_INTERRUPT_DRIVEN=y # <======================================
# CONFIG_UART_0_NRF_PARITY_BIT is not set
CONFIG_UART_0_NRF_TX_BUFFER_SIZE=32
# CONFIG_UART_0_NRF_HW_ASYNC is not set
# CONFIG_UART_0_NRF_ASYNC_LOW_POWER is not set
CONFIG_UART_1_NRF_UARTE=y
CONFIG_UART_1_INTERRUPT_DRIVEN=y # <======================================
CONFIG_UART_1_ENHANCED_POLL_OUT=y
# CONFIG_UART_1_NRF_PARITY_BIT is not set
CONFIG_UART_1_NRF_TX_BUFFER_SIZE=32
# CONFIG_UART_1_NRF_ASYNC_LOW_POWER is not set
CONFIG_UART_ENHANCED_POLL_OUT=y
CONFIG_NRF_UARTE_PERIPHERAL=y

Note the "CONFIG_UART_0_INTERRUPT_DRIVEN=y" and "CONFIG_UART_1_INTERRUPT_DRIVEN=y" settings.

With this project change, the async API function "uart_callback_set" now errors out because the define "UARTE_INTERRUPT_DRIVEN" is now defined instead of "UARTE_ANY_ASYNC" in uart_nrfx_uarte.c, line 1771 (SDK v2.1.0) since the struct element ".callback_set" no longer exists.

Is there a way to have "CONFIG_UART_0_INTERRUPT_DRIVEN=y" (the 2nd project settings window above - compatible with the shell module) while "CONFIG_UART_1_ASYNC=y" (the 1st project settings window above - compatible with the UART async API)?

FYI, I am using the DevAcademy, lesson 5, exercise 1 example code to reproduce this on an nRF52840 DK.

RE: Async UART and shell module in Zephyr on nRF52480

AndyM — Tue, 19 Jul 2022 14:33:48 GMT

Found the solution

shell_print(shell_backend_uart_get_ptr(),"%s",data);

RE: Async UART and shell module in Zephyr on nRF52480

Susheel Nuguru — Tue, 19 Jul 2022 04:53:48 GMT

It might be possible but you need to have some inter-thread communication implemented between the shell module and your thread to synchronize the access to uart in your application. There is no config to temporarily disable shell to give other threads access to uart.

RE: Async UART and shell module in Zephyr on nRF52480

AndyM — Fri, 15 Jul 2022 20:01:26 GMT

Revisiting... I have a shell module and I need to send data asynchronously over UART from a thread other than the shell. Is this possible? Is there a way to temporarily disable shell UART handlers and re-enable them when I'm done sending the data?

Thanks

RE: Async UART and shell module in Zephyr on nRF52480

AHaug — Mon, 11 Apr 2022 12:33:45 GMT

Hi,

[quote user=""]Now I need to add async UART to send some data outside the shell[/quote]

Could you check out this detailed sample using asynchronous UART in our nRF Connect SDK course to see if you have missed anything in the setup of the asynchronous UART? uart_callback_set() should only return ENOSYS if async api is not supported by the device, but this should be supported by the nRF52840, leading me to think there is something missing in your setup.

[quote user=""]Is there a way to use UART async API with the shell?[/quote]

Regarding this, I will ask around and come back with more details before Wednesday (within 2 working days). In the meanwhile, you may investigate this open ticket with a somewhat similar issue to see if you are able to spot your issue through their fix.

Let me know if these guides help you before I am able to reach back to you with additional information.

Kind regards,
Andreas