Zephyr allocation of NORDIC peripherals

[Jim Logsdon]

I'm using the Async UART API and the Enhanced ShockBurst API and my code seems unstable.   The RF Connect Debugger frequently crashes.

The ShockBurst User Guide specifies that it uses the following resources:

• Radio (NRF_RADIO)
• Timer: NRF_TIMER2, NRF_TIMER3
• PPI channels 7, 8, 9, 10, 11, 12, and 13
• Software interrupt 0

I could not find a User Guide for the Async UART API.

How can I see how Zephyr allocates resources in my application to ensure there is no conflict?

Is there an output file from the build process that provides that information?

Thank you

[Rick Cai]

If you want to see all UART API (uart_tx) Zephyr supported, you can refer to "zephyr/include/zephyr/drivers/uart.h". 

Asynchronous UART is enabled in uart drivers (/zephyr/drivers/serial).

When "CONFIG_UART_ASYNC_API=y", asynchronous APIs will be enabled. 

You can refer to "zephyr/drivers/serial/uart_nrfx_uart.c"

[Vidar Berg]

Hi,

The Async UART driver does not claim any additional HW resources by default unless the CONFIG_UART_<instance number>_NRF_HW_ASYNC symbol is enabled in the project configuration. This configuration was also made redundant after the CONFIG_UART_NRFX_UARTE_ENHANCED_RX setting was introduced.

Best regards,

Vidar

[Jim Logsdon]

Thank you