<?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>S110 serialization based on Linux</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/3878/s110-serialization-based-on-linux</link><description>Please, 
 We want to develop our BLE related application on PC and we find that &amp;quot;GAP/GATT driver for windows&amp;quot; is a good way to achieve that. While our system is based on Linux (Ubuntu 12.04) and currently the &amp;quot;GAP/GATT driver for Linux&amp;quot; is unavailable</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Sep 2014 09:01:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/3878/s110-serialization-based-on-linux" /><item><title>RE: S110 serialization based on Linux</title><link>https://devzone.nordicsemi.com/thread/13952?ContentTypeID=1</link><pubDate>Wed, 24 Sep 2014 09:01:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:766f679d-65f2-4a09-9077-3d55b748ae10</guid><dc:creator>Nicole</dc:creator><description>&lt;p&gt;Problem has solved!&lt;/p&gt;
&lt;p&gt;In fact, we found that it it because serial port can&amp;#39;t accept the full serial data for Linux. Now we can control EK based on serial packages.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 serialization based on Linux</title><link>https://devzone.nordicsemi.com/thread/13951?ContentTypeID=1</link><pubDate>Tue, 23 Sep 2014 08:58:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:91a9de7f-1846-46f2-bcdc-20b3a768542a</guid><dc:creator>Nicole</dc:creator><description>&lt;p&gt;Thanks jezule,&lt;/p&gt;
&lt;p&gt;Just now we try &amp;quot;uart_example&amp;quot; project (only uart communication related) with EK board. It works well on Linux.
And then according to your advice, we use EK&amp;#39;s uart port directly, which changes to ttyUSB0 port. But there are no data replying. And also we find that no waveform on TX pin when EK sends &amp;quot;0x04 0x00 0x00 0x60 0x01 0x00&amp;quot; through oscilloscope.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 serialization based on Linux</title><link>https://devzone.nordicsemi.com/thread/13950?ContentTypeID=1</link><pubDate>Mon, 22 Sep 2014 15:43:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:327b0772-079a-4e3b-93a5-c1d2f626c24e</guid><dc:creator>jezule</dc:creator><description>&lt;p&gt;I would say that that happens because you are dealing with ttyACMx instead of a ttyUSBx port. ttyACMx is a modem for Linux so it is probably adding some AT commands which are confusing the dongle. If you type lsmod you will read something like cdc, right? Ideally, you should force the right driver to be used instead (usbserial, I think to remember) but not sure how this can be achieved if the dongle is introducing itself as a CDC device. Maybe using udev rules?&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>