<?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>Uart regressions between SDK 2.8.0 -&amp;gt; 3.3.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/129420/uart-regressions-between-sdk-2-8-0---3-3-0</link><description>Hi! We have recently upgraded nRF Connect SDK. Since this change, some of our users experience issues with uart - two nRF52840 communicating together. We have not been able to reproduce the issue and the users aren&amp;#39;t very responsive, so we unfortunately</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 16 Oct 2026 14:10:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/129420/uart-regressions-between-sdk-2-8-0---3-3-0" /><item><title>RE: Uart regressions between SDK 2.8.0 -&gt; 3.3.0</title><link>https://devzone.nordicsemi.com/thread/572320?ContentTypeID=1</link><pubDate>Fri, 16 Oct 2026 14:10:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ac2451d-0ec4-4eb6-a8b6-25a5b796b3cd</guid><dc:creator>kat829</dc:creator><description>&lt;p&gt;Hi Hung!&lt;br /&gt;&lt;br /&gt;&amp;gt;&amp;nbsp;Since it&amp;#39;s not reproducible on your desk it&amp;#39;s really hard to tell what could be wrong.&lt;br /&gt;&lt;br /&gt;I know!&amp;nbsp;&lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f61e.svg" title="Disappointed"&gt;&amp;#x1f61e;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&amp;gt;&amp;nbsp;Can you reproduce this ? What the fix was ?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Yes, with our custom board though. Didn&amp;#39;t try to reduce it to devkits.&lt;br /&gt;&lt;br /&gt;Well, more of a workaround. We detect garbage and restart the rx on 3rd such failed chunk in a row.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Uart regressions between SDK 2.8.0 -&gt; 3.3.0</title><link>https://devzone.nordicsemi.com/thread/572318?ContentTypeID=1</link><pubDate>Fri, 16 Oct 2026 13:54:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:26fede52-ccd4-4aba-afa8-682f9835f638</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Karel,&amp;nbsp;&lt;br /&gt;Since it&amp;#39;s not reproducible on your desk it&amp;#39;s really hard to tell what could be wrong.&lt;br /&gt;The customer need to provide logic analyzer trace on the UART lines.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
[quote user=""]- Limited version of similar problem can be reproduced by a simultaneous cold start of both boards. In that case, one nRF52840&amp;#39;s UARTE async receiver delivers a wrong first byte after every idle gap on the line, with no error event, until RX is disabled and re-enabled once. Fixing this doesn&amp;#39;t make the above issue go away though.[/quote]
&lt;p&gt;Can you reproduce this ? What the fix was ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>