<?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>Application Controller Interface (ACI) or similar for SPI communications to nrf53811</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50489/application-controller-interface-aci-or-similar-for-spi-communications-to-nrf53811</link><description>In the past we had a C based product that communicated from our Host processor over SPI to an nrf8001 peripheral using an Application Controller Interface (ACI) provided as part of 
 a Nordic SDK (the \Nordic\ble-sdk-efm32-master.) 
 This allowed us to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 01 Aug 2019 13:37:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50489/application-controller-interface-aci-or-similar-for-spi-communications-to-nrf53811" /><item><title>RE: Application Controller Interface (ACI) or similar for SPI communications to nrf53811</title><link>https://devzone.nordicsemi.com/thread/201919?ContentTypeID=1</link><pubDate>Thu, 01 Aug 2019 13:37:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3b5218a-af62-4e45-b103-67950f27051b</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;One of our American FAEs has written a short guide on getting started with serialization. Attached here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-f4392da99c334a378a126faca01519b0/Serialization-Port-Information-V0.3.2.docx"&gt;devzone.nordicsemi.com/.../Serialization-Port-Information-V0.3.2.docx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It is written for an older SDK version, which didn&amp;#39;t have the S112 softdevice, but it may still be relevant. I can recommend reading through it.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Application Controller Interface (ACI) or similar for SPI communications to nrf53811</title><link>https://devzone.nordicsemi.com/thread/201899?ContentTypeID=1</link><pubDate>Thu, 01 Aug 2019 13:01:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88ca630c-2bbc-4267-998c-cee8ee2b615f</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I believe the &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.3.0%2Flib_serialization.html&amp;amp;cp=5_1_3_42"&gt;Serialization Library&lt;/a&gt;&amp;nbsp;may be what you are looking for. When you use the nRF as a connectivity chip, the only thing running on it is the softdevice, and the serial interface over which it receives commands on what softdevice calls to do. This is designed as a radio and BLE stack slave to be controlled by another MCU, such as the STM32.&lt;/p&gt;
&lt;p&gt;It requires some porting to run the application from the STM, but there are several others that have done something similar.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I see that the S112, which is the softdevice for nRF52811 has an SPI project as the connectivity chip (slave), but we don&amp;#39;t have any projects that uses this. There is a project for the application chip using the HCI (uart), the SDK15.3.0\examples\ble_peripheral\ble_app_hrs\pca10040\ser_s112_hci, but it shouldn&amp;#39;t be too much of a job to change the hci transport layer with a SPI.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>