nRF52840 : Why BLE HCI UART implemented using Interrupt API than Asynchronous API

[Alaganraj]

Hello Nordic Team,

The sample program BLE HCI UART implemented using interrupt API, which has limitation of 1 byte Rx  per interrupt.

per document, Asynchronous API is recommend for UART,

https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-4-serial-communication-uart/topic/uart-driver/

We are interested in Asynchronous API hoping which will improve the throughput.

1. Is there any specific reason BLE HCI UART program implemented using interrupt API?
2. Do you have BLE HCI UART program based on Asynchronous API(uses eDMA)?
3. If not available, is it something Nordic can help to implement?

Regards,

Alaganraj

[Susheel Nuguru]

I haven't looked into the example deep enough to be able to answer that. Let me spend some time on it today and will try to answer you soon after that on why we used the interrupt mode for the BLE HCI UART.