<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>USB CDC ACM:uart tx unable to trigger interrupt</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/103581/usb-cdc-acm-uart-tx-unable-to-trigger-interrupt</link><description>I have a USB CDC ACM module that works with other uarts that are asynchronous. In other words, when I reset the program, other uarts will directly output some initialization information to the terminal when they are turned on. However, cdc acm is interrupted</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 04 Oct 2023 11:35:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/103581/usb-cdc-acm-uart-tx-unable-to-trigger-interrupt" /><item><title>RE: USB CDC ACM:uart tx unable to trigger interrupt</title><link>https://devzone.nordicsemi.com/thread/448808?ContentTypeID=1</link><pubDate>Wed, 04 Oct 2023 11:35:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5bc43716-c2ba-47a0-a8d8-cc004837b0a3</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi Reskyllr,&lt;/p&gt;
&lt;p&gt;Thanks for your patience while I was gone.&lt;/p&gt;
&lt;p&gt;It is possible that the current async uarte usage with USB CDC ACM be written in a way that is relying on the rx aswell to complete the first transaction. Maybe you can rewrite the application that the order of initialization and the first transaction does not rely on rx being enabled?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;OR&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Do you see that his is something specific to how the drivers are handling the initialization?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: USB CDC ACM:uart tx unable to trigger interrupt</title><link>https://devzone.nordicsemi.com/thread/447342?ContentTypeID=1</link><pubDate>Mon, 25 Sep 2023 06:16:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d5e41ee-8265-49c3-8761-5ffe14eef13d</guid><dc:creator>Reskyllr</dc:creator><description>&lt;p&gt;Hi, Maria&lt;/p&gt;
&lt;p&gt;I have conducted reproducible experiments and read relevant documents, and learned that USB CDC ACM works in interrupt mode by default.&lt;br /&gt;No changes are required, my requirement is to receive data from uart_tx without sending any uart instructions, as long as this can be achieved (so that uart information can be received when our reset starts).&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Reskyllr&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: USB CDC ACM:uart tx unable to trigger interrupt</title><link>https://devzone.nordicsemi.com/thread/446935?ContentTypeID=1</link><pubDate>Wed, 20 Sep 2023 15:34:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bec5549-9c74-4a3e-b828-66bd756f8ad5</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Hi Reskyllr,&lt;/p&gt;
&lt;p&gt;I have started to look at this, but I am unsure if I have all the requirements to reproduce.&lt;/p&gt;
&lt;p&gt;Have you reproduced on the nRF5340 DK?&lt;/p&gt;
&lt;p&gt;Which modifications have you done for the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/peripheral_uart/README.html"&gt;Peripheral UART sample&lt;/a&gt;? I assume you &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/peripheral_uart/README.html#activating-sample-extensions"&gt;build with prj_cdc.conf and adding usb.overlay&lt;/a&gt;, but are there others changes?&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Maria&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: USB CDC ACM:uart tx unable to trigger interrupt</title><link>https://devzone.nordicsemi.com/thread/445977?ContentTypeID=1</link><pubDate>Thu, 14 Sep 2023 05:49:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9d61379-abe9-48f3-83c5-9191a4c1b40e</guid><dc:creator>Reskyllr</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;emm,There is one more url above).&lt;/p&gt;
&lt;p&gt;&lt;a id="" href="https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/peripheral_uart"&gt;https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/peripheral_uart&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;just try it,You just need to run cdc uart in it.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Reskyllr&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: USB CDC ACM:uart tx unable to trigger interrupt</title><link>https://devzone.nordicsemi.com/thread/445591?ContentTypeID=1</link><pubDate>Tue, 12 Sep 2023 10:36:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:be2b9197-b0e0-460c-89cd-0ed6c647337c</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Reskylir,&lt;/p&gt;
&lt;p&gt;I am not able to access the git repo you linked. It says access is denied.&lt;/p&gt;
&lt;p&gt;Can you please fix the access to AryanNordic and give me steps to reproduce this with the USB CDC ACM. I can then try to see what the actual block here is and suggest you something.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: USB CDC ACM:uart tx unable to trigger interrupt</title><link>https://devzone.nordicsemi.com/thread/445228?ContentTypeID=1</link><pubDate>Sat, 09 Sep 2023 03:45:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e86e2539-ff69-4f44-9b52-5757cec62faf</guid><dc:creator>Reskyllr</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Sorry, my English is not very good.&lt;br /&gt;Please refer to this sample (&lt;a href="https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/peripheral_uart)"&gt;github.com/.../peripheral_uart)&lt;/a&gt;. There is a uart_async_adapter that converts usb cdc acm to the same API as asynchronous uart.&lt;br /&gt;But it seems that it cannot be separated from the interruption. When my com is open, the tx data does not appear on my terminal. Only if I send a message (uart rx) from the terminal, the tx data can be displayed on the terminal.&lt;br /&gt;But this will not be the case with asynchronous uart. As long as my com is open, the tx data will be output directly.&lt;br /&gt;My purpose is to make USB CDC ACM work like other asynchronous UART.&lt;br /&gt;If you need more information, I can provide relevant test demos.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Reskyllr&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: USB CDC ACM:uart tx unable to trigger interrupt</title><link>https://devzone.nordicsemi.com/thread/445104?ContentTypeID=1</link><pubDate>Fri, 08 Sep 2023 10:24:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8766d8a3-bec7-44d5-b8d1-580f7b532ee6</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi Reskyllr,&lt;/p&gt;
&lt;p&gt;I am having a bit of a struggle to understand the below thing you wrote.&lt;/p&gt;
[quote user=""]However, cdc acm is interrupted and cannot be used for asynchronous work. I can only store the information that needs to be output in the buffer, and then manually get the initialization information from the console when the terminal rx triggers an interrupt.[/quote]
&lt;p&gt;I do not know what this limitation is. Why do you have to buffer the data before it is sent to the output. Can you show me which API you are using so that I can try to understand the limitations that comes with it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>