<?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>SPIS that acts as prober/sniffer</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/117956/spis-that-acts-as-prober-sniffer</link><description>I am looking into the possibility of using an nRF5340DK to probe SPI pins. For context: 
 
 There is a total of 3 devices in the system: the master and slave being used primarily for SPI, and this nRF as the prober 
 I also ensure that all devices share</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 13 Jan 2025 09:23:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/117956/spis-that-acts-as-prober-sniffer" /><item><title>RE: SPIS that acts as prober/sniffer</title><link>https://devzone.nordicsemi.com/thread/518100?ContentTypeID=1</link><pubDate>Mon, 13 Jan 2025 09:23:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ff7c56e-d0cd-4e10-92a2-c10c26c13fcc</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Interesting .. Could be many reasons&lt;/p&gt;
&lt;p&gt;If the clock signal is inverted between the master and the nRF (perhaps due to hardware or line capacitance), the nRF might interpret it as SPI Mode 2 instead of Mode 0. This could happen if there’s a delay or mismatch in clock signal propagation or probably some timing mismatches or slight delays in the signal due to some hardware components on your board at higher operating frequencies. Just guessing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPIS that acts as prober/sniffer</title><link>https://devzone.nordicsemi.com/thread/518033?ContentTypeID=1</link><pubDate>Sat, 11 Jan 2025 00:47:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:941a6726-5802-4b10-b8a8-c8221526ec0f</guid><dc:creator>esmart-engineering</dc:creator><description>&lt;p&gt;(OP replying) May have found the solutions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span style="font-size:75%;"&gt;Since the slave&amp;#39;s output goes into the nRF as an input, the MISO pin should connect to the nRF&amp;#39;s MOSI (not nRF&amp;#39;s MISO).&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span style="font-size:75%;"&gt;The nRF&amp;#39;s MISO pin also doesn&amp;#39;t need to be connected.&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span style="font-size:75%;"&gt;Changing nRF to read for SPI mode 2 (even though the master/slave agreed on SPI mode 0)&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On that note, &lt;strong&gt;are there any thoughts about why I had to switch to SPI mode 2?&lt;/strong&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>