• State Not Answered
  • Replies 5 replies
  • Subscribers 93 subscribers
  • Views 991 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 331038
Options

Switching from UART_INTERRUPT_DRIVEN to UART_ASYNC_API in USB CDC ACM Sample Leads to Fatal Error

Omar

Hello,

I am working with the USB CDC ACM Sample Application from NCS V2.1.0 on nRF52840DK and have encountered an issue when attempting to replace the UART_INTERRUPT_DRIVEN API with the UART_ASYNC_API.

Steps Taken:

  1. I took the standard USB CDC ACM Sample Application from the NCS V2.1.0 samples.
  2. I modified the code to switch from using UART_INTERRUPT_DRIVEN to UART_ASYNC_API.

Problem:

After making the changes and using the uart_tx() function, I encountered a fatal error. Below are the details:

Here are the screenshots showing the code differences and the specific error messages encountered:



PS: i defined uart_cb() above, and i just put a switch case and some comments, and for the tx_buf[] i initialized it with some text.


And here are the prj.conf changes



Error Message:

I would appreciate any insights or guidance on why switching to UART_ASYNC_API is causing this issue and how to resolve it. Specifically, I am looking for:

  1. Correct procedure to transition from UART_INTERRUPT_DRIVEN to UART_ASYNC_API for the USB CDC ACM application.
  2. Any known issues or considerations when using UART_ASYNC_API in this context.

Thank you for your assistance!

Related
Terms of service