<?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>Does zephyr Bluetooth Stack route to nRF BLE stack APIs internally..?!</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/84872/does-zephyr-bluetooth-stack-route-to-nrf-ble-stack-apis-internally</link><description>Hi, 
 
 I want to understand that in nCS, where do have BLE abstraction layer..? 
 As in zephyr device driver model, if you use any peripheral driver API, it internally routes to nordic driver API. 
 Is similar the case with zephyr Bluetooth Stack..?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 07 Mar 2022 17:07:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/84872/does-zephyr-bluetooth-stack-route-to-nrf-ble-stack-apis-internally" /><item><title>RE: Does zephyr Bluetooth Stack route to nRF BLE stack APIs internally..?!</title><link>https://devzone.nordicsemi.com/thread/356703?ContentTypeID=1</link><pubDate>Mon, 07 Mar 2022 17:07:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d77281e7-1a6b-4eb1-817c-2890b5a929ce</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The second path contains &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.8.0/nrf/libraries/index.html"&gt;libraries developed by Nordic&lt;/a&gt; for the exclusive use in nRF Connect SDK. Some of these libraries may use APIs for the Zephyr libraries, but that may not be true for all. The APIs in&amp;nbsp;&lt;strong&gt;zephyr\subsys\bluetooth&lt;/strong&gt;&amp;nbsp;is part of the Zephyr RTOS, which may be developed by Nordic or other contributors to the open source project.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does zephyr Bluetooth Stack route to nRF BLE stack APIs internally..?!</title><link>https://devzone.nordicsemi.com/thread/356472?ContentTypeID=1</link><pubDate>Mon, 07 Mar 2022 07:09:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e125840-d5c5-4ace-bf27-c4f17a596d95</guid><dc:creator>Ubaid_M</dc:creator><description>&lt;p&gt;Hello &lt;a class="internal-link view-user-profile" href="https://devzone.nordicsemi.com/members/joh2"&gt;J&amp;oslash;rgen Holmefjord&lt;/a&gt;,&lt;/p&gt;
[quote userid="14926" url="~/f/nordic-q-a/84872/does-zephyr-bluetooth-stack-route-to-nrf-ble-stack-apis-internally/353836#353836"]Bluetooth stack is split into two parts[/quote]
&lt;p&gt;Thanks for the suggest, I was able to understand this.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;And also found that there are two directory paths for nCS Stack as in below:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. v1.8.0\zephyr\subsys\bluetooth&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2.&amp;nbsp;v1.8.0\nrf\lib&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The first path(&lt;strong&gt;v1.8.0\zephyr\subsys\bluetooth&lt;/strong&gt;) provides all BLE &amp;amp; Mesh related operational APIs,&lt;br /&gt;While the second path (&lt;strong&gt;v1.8.0\nrf\lib&lt;/strong&gt;) provides application APIs using the APIs provided at the first path (&lt;strong&gt;v1.8.0\zephyr\subsys\bluetooth&lt;/strong&gt;).&lt;br /&gt;&lt;br /&gt;Kindly Confirm the above.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks,&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does zephyr Bluetooth Stack route to nRF BLE stack APIs internally..?!</title><link>https://devzone.nordicsemi.com/thread/353836?ContentTypeID=1</link><pubDate>Fri, 18 Feb 2022 12:25:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94ffe522-2c1d-4a97-b701-f4078ddace79</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;In nRF Connect SDK/Zephyr, the Bluetooth stack is split into two parts (see&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.0/zephyr/guides/bluetooth/bluetooth-arch.html"&gt;Bluetooth Stack Architecture&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.0/zephyr/guides/bluetooth/bluetooth-arch.html#host"&gt;BLE Host&lt;/a&gt;, which implements the higher-level protocols and profiles, and provides a high-level API to the application.&lt;/li&gt;
&lt;li&gt;A link-layer BLE controller, which implements the lower layers.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can read more about this in these documentation chapters:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.0/nrf/ug_ble_controller.html"&gt;Bluetooth LE Controller&lt;/a&gt;&amp;nbsp;(nRF Connect SDK)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.0/zephyr/guides/bluetooth/index.html"&gt;Bluetooth&lt;/a&gt;&amp;nbsp;(Zephyr)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.0/nrfxlib/softdevice_controller/README.html"&gt;SoftDevice Controller&lt;/a&gt;&amp;nbsp;(nrfxlib)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>