<?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>nRF52832 minimum microcontroller interface signals req&amp;#39;d</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/92148/nrf52832-minimum-microcontroller-interface-signals-req-d</link><description>I am looking at adding BLE to an existing design. The product uses an ARM micro, and currently has SPI and I2C available at daughterboard connectors. I am trying to understand the minimum interface signals that are required, between the ARM micro and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 20 Sep 2022 20:49:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/92148/nrf52832-minimum-microcontroller-interface-signals-req-d" /><item><title>RE: nRF52832 minimum microcontroller interface signals req'd</title><link>https://devzone.nordicsemi.com/thread/387173?ContentTypeID=1</link><pubDate>Tue, 20 Sep 2022 20:49:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c1a34e6-35b0-42a0-8f5e-8242b3cdedd4</guid><dc:creator>Nguyen Hoan Hoang</dc:creator><description>&lt;p&gt;Full control or not is relative to the firmware running on it. &amp;nbsp;It is up to you to write the firmware on the nRF52832 to do what you need it to do.&lt;/p&gt;
&lt;p&gt;The nRF52832 is itself an ARM M4F 64MHz 512KB Flash 64KB RAM. &amp;nbsp;Do you really need a second MCU ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>