<?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>nRF52 USB-UART broke, half-duplex?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29064/nrf52-usb-uart-broke-half-duplex</link><description>Hi there, 
 I have multiple PCA10040 boards, and about a year&amp;#39;s worth of experience developing code for them. I have suddenly started to have problems with USB-UART connections. Not even Nordic&amp;#39;s SDK example code (in ../examples/peripheral/uart) is dependable</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 03 Apr 2017 11:47:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29064/nrf52-usb-uart-broke-half-duplex" /><item><title>RE: nRF52 USB-UART broke, half-duplex?</title><link>https://devzone.nordicsemi.com/thread/115205?ContentTypeID=1</link><pubDate>Mon, 03 Apr 2017 11:47:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:738c2432-df5c-483b-aa20-fd086a5eee1c</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;There should not be any differences between the two rev&amp;#39;s. Have you checked if some of your kits have the &amp;quot;SB9&amp;quot; cut for current-measurement?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 USB-UART broke, half-duplex?</title><link>https://devzone.nordicsemi.com/thread/115204?ContentTypeID=1</link><pubDate>Sat, 01 Apr 2017 04:35:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:25e569ee-337d-4cb2-adc1-aad16a8f466a</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;&lt;strong&gt;EDIT, 2018-01-18:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I searched in various places for months for advice.  The folks in the SEGGER forums implied that there could be something wrong with the Linux serial drivers.  The folks over at Ubuntu Forums assured me that a problem that large would not go unaddressed for long.&lt;/p&gt;
&lt;p&gt;When I upgraded to Ubuntu 17.04, problems persisted.  When I upgraded to Ubuntu 17.10, problems disappeared.  I also have a more current version of SEGGER JLink (v6.22d), and a more current EABI from ARM, and the GTK version has changed, etc., etc.  I&amp;#39;m not sure exactly what the problem was, but with the configuration I have now, I have restored full-duplex UART capability.&lt;/p&gt;
&lt;p&gt;My old followup is below the line.  I am leaving it here for reference, but I think that I was chasing a false lead.&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;I am about to provide a partial answer to my own question, but I need further guidance.&lt;/p&gt;
&lt;p&gt;We have several nRF52 PCA10040 DK boards floating around our lab.  I have just determined that we have two slightly different versions.  The boards that are causing my UART problem are V1.1.1 boards.  All of my UART programs are working flawlessly when I flash to a V1.1.0 DK board.&lt;/p&gt;
&lt;p&gt;I am looking over the compatibility matrix documents:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52%2Fdita%2Fnrf52%2Fcompatibility_matrix%2Fnrf52832_comp_matrix.html"&gt;infocenter.nordicsemi.com/index.jsp&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I do not see any documentation that distinguishes the nRF52 1.1.0 DK boards from the 1.1.1 boards.&lt;/p&gt;
&lt;p&gt;Have I uncovered an undocumented problem?  Whether I have or not, I would appreciate any guidance.  Trying a more current SDK would seem to be the obvious next step.&lt;/p&gt;
&lt;p&gt;I will ask a more general question about the differences between the board revisions at the top level.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 USB-UART broke, half-duplex?</title><link>https://devzone.nordicsemi.com/thread/115203?ContentTypeID=1</link><pubDate>Fri, 31 Mar 2017 18:07:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8dc533d8-529e-4356-aa5a-83f9a1a01185</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Check that you are using the correct ttyUSB or ttyACM port. Newer JLinks also contain a USB2Serial capability.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 USB-UART broke, half-duplex?</title><link>https://devzone.nordicsemi.com/thread/115202?ContentTypeID=1</link><pubDate>Fri, 31 Mar 2017 18:02:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2af5e0cd-3b22-4d61-9258-e2ae297131d3</guid><dc:creator>HeS</dc:creator><description>&lt;p&gt;I have similar problem. I had to switch off hardware handshake and stop using UART interrupt while transmitting. So I have typical half-duplex. I dont know where is the problem. Maybe the cause is interchange gpio logic? Recently I figure out, that setting gpio with LED connected to high (1) switch OFF diode and oposite, setting low (0) light ON diode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>