<?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>HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/17903/hci-controlling-interface-nrf52</link><description>Hi dear Nordic Engineers. 
 We going to move from FN-LINK (Realtek) I.C. BLE to nRF52.
FN-LINK uses HCI (UART) BLE the Interface to communicate with our embd. LINUX.
How to up HCI interface with nRF52 to move in the easiest way ?
Maybe some existing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 24 Nov 2016 09:41:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/17903/hci-controlling-interface-nrf52" /><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69039?ContentTypeID=1</link><pubDate>Thu, 24 Nov 2016 09:41:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5fa80224-e652-430a-b3f5-a21b8784b65e</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi Oleg, Glad to hear that it&amp;#39;s working! I have tested the hci_uart example from zephyr and it&amp;#39;s good to hear that nimble also works out-of-the-box!
It&amp;#39;s important to check the pinout and map this correctly, as both mynewt and zephyr defaults to the nRF52-DK pinout for UART communication.&lt;/p&gt;
&lt;p&gt;Cheers,
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69038?ContentTypeID=1</link><pubDate>Wed, 23 Nov 2016 17:35:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97150a5e-8b9a-4f49-a9ea-79b762b62c17</guid><dc:creator>Oleg</dc:creator><description>&lt;p&gt;After I modified the mynewt OS sources for our own nRF52 BOARD, NimBLE (HCI H4) works PERFECT under embedded Linux.
Tnaks you for all dear Nordic Engineers!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69037?ContentTypeID=1</link><pubDate>Wed, 23 Nov 2016 10:40:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d74e23d-7f67-4ddc-ae99-abf00151e82f</guid><dc:creator>Oleg</dc:creator><description>&lt;p&gt;NimBLE (example) does not works with blueZ , I checked with Oscilloscope , TX sends  but NO answer from nRF52... only just it&amp;#39;s blinkig LED1 project works good.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69036?ContentTypeID=1</link><pubDate>Tue, 22 Nov 2016 12:26:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:78a394e0-5a17-44b9-8213-4fd1fa7f697c</guid><dc:creator>Oleg</dc:creator><description>&lt;p&gt;OK, thanks you i&amp;#39;ll try both...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69035?ContentTypeID=1</link><pubDate>Tue, 22 Nov 2016 12:21:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c10eba2f-b0d6-4cd7-8e4f-e54e973a956f</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Note that NimBLE and zephyr are two different open-source code-bases, and therefore have differences between each other. They are not based on the SoftDevice, but on two different open-source bluetooth LE stacks.&lt;/p&gt;
&lt;p&gt;I have not tested the HCI-examples in these projects, but they are supposed to work with linux as a bluetooth LE HCI device.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69034?ContentTypeID=1</link><pubDate>Tue, 22 Nov 2016 12:14:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:524b441b-2478-43b0-b533-73af6c25a231</guid><dc:creator>Oleg</dc:creator><description>&lt;p&gt;does NimBLE ( Zemphyr ) fully supports bluez ?
We need concurrently co-existing Peripheral &amp;amp; Central roles like in FN-LINK HCI or S132.
I&amp;#39;m guessing, nRF52 abilities have more limited by SDK but not by nRF52 HW.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69033?ContentTypeID=1</link><pubDate>Tue, 22 Nov 2016 10:55:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf9c4cd9-cb06-4103-9b1e-fae05e2203be</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;The transport layer, meaning the physical layer, is supported, but the actual commands that goes over is not compatible with linux. There is a serialization protocol available from Nordic, but it is not pluggable into linux. Zephyr and NimBLE is compatible with the linux bluetooth stack bluez.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69032?ContentTypeID=1</link><pubDate>Tue, 22 Nov 2016 10:36:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a1b8c73-150b-4074-b635-0ecdf9db66d0</guid><dc:creator>Oleg</dc:creator><description>&lt;p&gt;sorry I&amp;#39;m a little confused... , Nordic does not prov. example, but DOES fully provide HCI ?
I found (in SDK 12.1.0) the HCI Transport module:&lt;/p&gt;
&lt;p&gt;QUOTE:
&amp;quot;...
HCI transport module implementation.
This module implements certain specific features from the three-wire UART transport layer, defined by the Bluetooth specification version 4.0 [Vol 4] part D.
...
&amp;quot;&lt;/p&gt;
&lt;p&gt;and from BT official spec.:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/bt4.jpg" alt="image description" /&gt;&lt;/p&gt;
&lt;p&gt;is  SDK 12xx HCI compatible with BT official UART HCI ?
does SDK12 supports HCI fully ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69040?ContentTypeID=1</link><pubDate>Tue, 22 Nov 2016 09:10:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e8812cba-87eb-4f13-8746-55f030ac9140</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi Oleg,&lt;/p&gt;
&lt;p&gt;Nordic does not provide a HCI example, but there are other options that do. In addition to the answer from Vidar, you can look at this Zephyr as well.
&lt;a href="https://gerrit.zephyrproject.org/r/gitweb?p=zephyr.git;a=summary"&gt;Zephyr&lt;/a&gt;  has included a HCI (UART) example for the nRF5-series in their upcoming v1.6.&lt;/p&gt;
&lt;p&gt;The project is located in
../samples/bluetooth/hci_uart/&lt;/p&gt;
&lt;p&gt;Cheers,
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HCI controlling interface nRF52</title><link>https://devzone.nordicsemi.com/thread/69031?ContentTypeID=1</link><pubDate>Tue, 22 Nov 2016 09:09:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06147528-3ce7-4317-8608-2150e4a0a371</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Please have a look at this &lt;a href="https://devzone.nordicsemi.com/question/103261/nrf52832-hci-firmware/?comment=103486#comment-103486"&gt;&lt;strong&gt;thread&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>