difference between components/libraries/uart and drivers_nrf/uart

[Florian Zierer]

Hi there,

I am starting with nrf52 and SDK 9.0.2 and am struggling with the SDK structure.

Can anyone please explain the difference between

components/libraries/uart and drivers_nrf/uart

Why are there two different UART drivers? What should be used? They differ e.g. in app_uart_init:

// drivers_nrf/uart/app_uart.c
uint32_t app_uart_init(const app_uart_comm_params_t * p_comm_params,
                         app_uart_buffers_t *     p_buffers,
                         app_uart_event_handler_t event_handler,
                         app_irq_priority_t       irq_priority,
                         uint16_t *               p_app_uart_uid)


// libraries/uart/app_uart.c
uint32_t app_uart_init(const app_uart_comm_params_t * p_comm_params,
                       app_uart_buffers_t           * p_buffers,
                       app_uart_event_handler_t       event_handler,
                       app_irq_priority_t             irq_priority)

Is there an introduction of the different parts and folders of the SDK and the intended use?

[Krzysztof Chruscinski]

The drivers in drivers_nrf/uart (app_uart.c and app_uart_fifo.c) are legacy implementation and are left there by accident and will be gone in next release. The idea is that in components/drivers_nrf folder you will find peripheral driver (one for each peripheral) and in components/libraries you will find modules build on top peripheral drivers. In case of uart, we have nrf_drv_uart (peripheral driver) and app_uart build on top of the peripheral driver.

[Florian Zierer]

Ok, I understand. Thanks for the explanation