<?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>Is a 3-bit synchronous (3 data lines + Clock) parallel input at 16.368 MHz feasible?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38808/is-a-3-bit-synchronous-3-data-lines-clock-parallel-input-at-16-368-mhz-feasible</link><description>I&amp;#39;m evaluating the nRF52840 for a new project. 
 I have read a number of previous posts that show that I can&amp;#39;t achieve what I want, but I want to be sure as the 840 is ideal for our application aside from this limitation. 
 My problem is that I need to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 24 Sep 2018 12:05:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38808/is-a-3-bit-synchronous-3-data-lines-clock-parallel-input-at-16-368-mhz-feasible" /><item><title>RE: Is a 3-bit synchronous (3 data lines + Clock) parallel input at 16.368 MHz feasible?</title><link>https://devzone.nordicsemi.com/thread/150041?ContentTypeID=1</link><pubDate>Mon, 24 Sep 2018 12:05:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0e752d2-da20-4a1e-8f62-7f480cf8681d</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;I&amp;#39;ll talk to some guys tomorrow, and see what they say.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;You might be able to use some external shift registers to capture the bitstreams.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is a 3-bit synchronous (3 data lines + Clock) parallel input at 16.368 MHz feasible?</title><link>https://devzone.nordicsemi.com/thread/150028?ContentTypeID=1</link><pubDate>Mon, 24 Sep 2018 11:40:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:43d64b56-2b06-4329-901b-0ccab2dcd114</guid><dc:creator>sadara</dc:creator><description>&lt;p&gt;1) I realize&amp;nbsp;I can&amp;#39;t use the radio without a 32Mhz HSE, I should be able to switch HSE frequencies in the future (with the MCU stopped obviously)&lt;/p&gt;
&lt;p&gt;2) The sensor is under NDA. There is not really a protocol for the sensor, the data interface is just a 3-bit ADC sampled at&amp;nbsp;&lt;span&gt;16.384Mhz.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;After powering up the sensor, it starts outputting 3 bit signed data over a simple parallel interface (3 data lines and a clock line). There is no control protocol, just one way raw data on this bus. After taking a small sample of the data (2ms), cut power to the sensor. It&amp;#39;s not like SPI interface or a UART protocol, just raw data.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is a 3-bit synchronous (3 data lines + Clock) parallel input at 16.368 MHz feasible?</title><link>https://devzone.nordicsemi.com/thread/149949?ContentTypeID=1</link><pubDate>Mon, 24 Sep 2018 08:21:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a8528ffd-3b3f-4bab-b123-141973418323</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;1) No, I don&amp;#39;t think so. I think you might be able to run&amp;nbsp;the the MCU off an external 32.768MHz crystal, but&amp;nbsp;a&amp;nbsp;radio protocol is out of the question. Either way it&amp;#39;s outside the specifications.&lt;/p&gt;
&lt;p&gt;2) I need more information on the protocol and the sensor device in order to answer this one.&lt;/p&gt;
&lt;p&gt;3) I do not think this is possible. At 16MHz you&amp;#39;re at 1/4 the CPU speed which means that you only have 4 CPU cycles to read the state of a single pin,&amp;nbsp;store it, and then clear the interrupt. I&amp;#39;ll need to find the delay from the clock interrupt fires until you can start to execute an ISR as well as the time from a GPIO state change until the registers update, etc.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;We need to know what sensor and protocol you&amp;#39;re asking for.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>