<?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>PCA10040 UART problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/16721/pca10040-uart-problem</link><description>Hi, 
 I&amp;#39;m using a PCA10040 board with the UART example provided with the v12 SDK, and the data seems to get corrupted somewhere along the way between my Ubuntu machine and the nrf52. 
 When I do: 
 pr@pr:~/nRF5/SDK_12/examples/peripheral/uart/pca10040</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 31 Mar 2017 07:09:18 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/16721/pca10040-uart-problem" /><item><title>RE: PCA10040 UART problem</title><link>https://devzone.nordicsemi.com/thread/63948?ContentTypeID=1</link><pubDate>Fri, 31 Mar 2017 07:09:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e263832d-e8ad-4a7d-b4eb-f432c5a7963d</guid><dc:creator>f.salvatore</dc:creator><description>&lt;p&gt;It affects the UART maybe because J-Link is seen like an USB storage but onestly i don&amp;#39;t why Ubuntu has this behaviour.&lt;/p&gt;
&lt;p&gt;UPDATE: i update the answer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10040 UART problem</title><link>https://devzone.nordicsemi.com/thread/63949?ContentTypeID=1</link><pubDate>Thu, 30 Mar 2017 17:45:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c6d1662e-cbd1-4f03-86ab-a3c646c511e0</guid><dc:creator>koniho</dc:creator><description>&lt;p&gt;The automount only affects the mass storage device that appears on USB connect right? Why would that affect the UART?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10040 UART problem</title><link>https://devzone.nordicsemi.com/thread/63947?ContentTypeID=1</link><pubDate>Thu, 30 Mar 2017 15:56:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2290f8f4-47e0-48ad-b289-2e0d11fb3c35</guid><dc:creator>f.salvatore</dc:creator><description>&lt;p&gt;I had the same problem. I solved changing mount settings by disabling auto-mount of devices.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;UPDATE:&lt;/strong&gt;
It seems that the problem is caused only by certain USB ports. I tried changing port and everything works. So the mount settings are not impacting on this issue. I&amp;#39;ll try to investigate.&lt;/p&gt;
&lt;p&gt;I forgot to say that i had also another issue on Ubuntu: when i connect the device to the USB a system daemon (ModemManager) sends some garbage (AT commands) to test if the device was a modem. I killed the daemon (search it with ps -aux | grep ModemManager) and everything is ok.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10040 UART problem</title><link>https://devzone.nordicsemi.com/thread/63946?ContentTypeID=1</link><pubDate>Thu, 29 Sep 2016 18:33:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7885b463-e2f1-47d0-9f58-b5b73e07cf5c</guid><dc:creator>patrick</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;the logic analyzer confirms that the nRF52 receives the data already corrupted (see attached screenshot).&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/pca10040_5F00_uart_5F00_logic_5F00_analyzer_5F00_screenshot.jpg" alt="image description" /&gt;&lt;/p&gt;
&lt;p&gt;I can&amp;#39;t seem to reproduce the problem with a Windows machine, though. So the problem must be lying with the linux driver. I&amp;#39;ve tried the latest and greatest version of cdc_acm, to no avail.&lt;/p&gt;
&lt;p&gt;Any ideas how to further investigate ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10040 UART problem</title><link>https://devzone.nordicsemi.com/thread/63945?ContentTypeID=1</link><pubDate>Thu, 29 Sep 2016 17:34:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd65de87-f5c5-40cd-869e-538a7b3e117e</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;Hi Patrick&lt;/p&gt;
&lt;p&gt;I have not used Ubuntu that much, so I don&amp;#39;t have much input there.&lt;/p&gt;
&lt;p&gt;To find out if this is a nRF52 problem or PC/Ubuntu problem, you could connect logical analyzer to the UART communication pins on the nRF52-DK (PCA10040) board and read the bytes directly from RX and TX pins.&lt;/p&gt;
&lt;p&gt;You should find the pin mapping in pca10040.h file, which are&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;#define RX_PIN_NUMBER  8
#define TX_PIN_NUMBER  6
#define CTS_PIN_NUMBER 7
#define RTS_PIN_NUMBER 5
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Which maps to pins P0.08, P0.06, P0.07, P0.05 on the PCA10040 board.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>