<?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>nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29044/nrf-connect-for-desktop---select-serial-port-error</link><description>When using nRF connect for desktop on ubuntu I can&amp;#39;t go through the &amp;quot;Select serial port&amp;quot; step because I got the following error message:
&amp;quot;Could not open the port. Please power cycle the device and try again.&amp;quot; 
 In the log file I got this: 
 ERROR Could</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Aug 2018 23:20:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29044/nrf-connect-for-desktop---select-serial-port-error" /><item><title>RE: nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/thread/145585?ContentTypeID=1</link><pubDate>Thu, 23 Aug 2018 23:20:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50fed19a-f64c-4d2b-bfab-6f326275d079</guid><dc:creator>Eric Smith</dc:creator><description>&lt;p&gt;Thanks! I do have some udev rules for the device, but possibly they are wrong. I will try your udev rules from github and let you know. It&amp;#39;s odd that manually setting the permissions on the /dev/ttyACM&amp;lt;n&amp;gt; device to 666 wouldn&amp;#39;t be sufficient. (Without udev rules, I&amp;#39;d have to do that every time, but it should work for testing.)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/thread/144334?ContentTypeID=1</link><pubDate>Wed, 15 Aug 2018 13:01:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5de51100-716c-4625-b704-8efa746768d9</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve talked to our developers, and they were able to reproduce your issue.&lt;/p&gt;
&lt;p&gt;Installing our udev rules for nRF development kits solved the issue.&lt;br /&gt;&lt;a href="https://github.com/NordicSemiconductor/nrf-udev"&gt;https://github.com/NordicSemiconductor/nrf-udev&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Let me know if that works for you. &lt;br /&gt;Best regards, &lt;br /&gt;Joakim.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/thread/143084?ContentTypeID=1</link><pubDate>Mon, 06 Aug 2018 17:11:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:530093c4-3fcf-41e9-9039-668b2eb64567</guid><dc:creator>Eric Smith</dc:creator><description>&lt;p&gt;No, I still can&amp;#39;t get it to find the port. Other applications can find and open the port without difficulty. If I run Windows in a virtual machine and give it access to the port, nRFConnect on Windows can find and use it, but I&amp;#39;d really prefer to use it on Linux.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/thread/142149?ContentTypeID=1</link><pubDate>Tue, 31 Jul 2018 11:59:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d711b6ea-b27f-4a4d-984d-4433cd062f15</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;Sorry about the delay.&lt;/p&gt;
&lt;p&gt;Did you make any progress regarding your issue?&lt;/p&gt;
&lt;p&gt;Regards, &lt;br /&gt;Joakim.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/thread/140578?ContentTypeID=1</link><pubDate>Wed, 18 Jul 2018 21:53:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0459a258-48aa-40b1-9323-01538acc532b</guid><dc:creator>Eric Smith</dc:creator><description>&lt;p&gt;I&amp;#39;ve confirmed that I&amp;#39;m a member of the dialout group, and that the device file has read and write permission for dialout, but the port still isn&amp;#39;t showing up in nRF Connect 2.4.0.&lt;/p&gt;
&lt;p&gt;$ id&lt;br /&gt;uid=1000(eric) gid=1000(eric) groups=1000(eric),10(wheel),18(dialout) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023&lt;br /&gt;$ ls -l /dev/ttyACM*&lt;br /&gt;crw-rw----. 1 root dialout 166, 0 Jul 18 15:34 /dev/ttyACM0&lt;/p&gt;
&lt;p&gt;Even if I change the device file permissions to 666, nRFConnect 2.4.0 doesn&amp;#39;t list it.&lt;/p&gt;
&lt;p&gt;If I run nRF Connect as superuser, which I really don&amp;#39;t like to do, the device is found.&lt;/p&gt;
&lt;p&gt;If I extract the contents of the nrfconnect AppImage and run the nrfconnect binary under &amp;quot;strace -f&amp;quot;, that shows that as I try to use it, /dev/ttyACM0 is successfully opened several times. The strace output is of course quite voluminous, and I can&amp;#39;t easily spot anything obviously wrong.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/thread/115045?ContentTypeID=1</link><pubDate>Thu, 11 Jan 2018 10:02:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d10af3e3-87fe-4fe4-8a80-24df736b54bd</guid><dc:creator>flurin4</dc:creator><description>&lt;p&gt;I had to run the program as superuser, as &lt;code&gt;sudo ./nrfconnect&lt;/code&gt; (from within the corresponding folder) for it to work. Not sure this is intended, but the above command didn&amp;#39;t solve my problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/thread/115044?ContentTypeID=1</link><pubDate>Thu, 06 Oct 2016 12:44:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:890454bd-b8bd-49d7-991d-fa77da601659</guid><dc:creator>ricsilvs</dc:creator><description>&lt;p&gt;By adding serial port access permissions the problem was solved. Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for desktop - Select serial port error</title><link>https://devzone.nordicsemi.com/thread/115043?ContentTypeID=1</link><pubDate>Thu, 06 Oct 2016 12:20:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d2c65c0-ed52-4cc6-a134-ca6cdd0ed395</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;You might need to grant serial port access permissions to your user. This can be done by typing the following command to the command line:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;sudo usermod -a -G dialout &amp;lt;username&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Also make sure that you have &lt;a href="https://www.segger.com/jlink-software.html"&gt;SEGGER J-Link Software&lt;/a&gt; installed, and that you are using one of the supported devices (PCA10028, PCA10040 and PCA10031).&lt;/p&gt;
&lt;p&gt;More information about nRF Connect is available &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.tools/dita/tools/nRF_Connect/nRF_Connect_intro.html?cp=5_2"&gt;here&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>