<?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>NRFX SPIM and Zephyr SPI</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/89434/nrfx-spim-and-zephyr-spi</link><description>I have an application where I need to trigger time critical SPI reads of accelerometer data (sample rate is very crucial and data is fed into a FFT). In my current SDK based application I use PPI timer events to trigger SPI reads. Currently we are required</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 13 Jul 2024 03:23:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/89434/nrfx-spim-and-zephyr-spi" /><item><title>RE: NRFX SPIM and Zephyr SPI</title><link>https://devzone.nordicsemi.com/thread/493731?ContentTypeID=1</link><pubDate>Sat, 13 Jul 2024 03:23:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aa1fe80f-83c7-460a-a1d8-3f0cd0385638</guid><dc:creator>Robotics Gun</dc:creator><description>&lt;p&gt;Is this sample&amp;nbsp;not applicable for 52DK_52832 ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRFX SPIM and Zephyr SPI</title><link>https://devzone.nordicsemi.com/thread/374954?ContentTypeID=1</link><pubDate>Thu, 30 Jun 2022 15:00:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9674b1b6-5c39-4645-a7c7-25288decb418</guid><dc:creator>Tristen</dc:creator><description>&lt;p&gt;Jared,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Okay&amp;nbsp; I had those kconfig options set, however I was also using the IRQ_CONNECT macro. It seems that macro is not necessary when using CONFIG_NRFX_SPIM1 and only caused build issues. I am good to go now. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRFX SPIM and Zephyr SPI</title><link>https://devzone.nordicsemi.com/thread/374932?ContentTypeID=1</link><pubDate>Thu, 30 Jun 2022 13:39:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ef684de-1105-4c87-b6ee-bead45f1699e</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;Adding&amp;nbsp;&lt;span&gt;CONFIG_SPI=y and CONFIG_NRFX_SPIM1=y will make the Zephyr API use the&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/b676d4855a86957bab6ede4ef1b3f3c4d1c64d7c/drivers/spi/spi_nrfx_spim.c#L583"&gt;nrfx Zephyr port&lt;/a&gt;&amp;nbsp;for that enabled instance. It should be &lt;/span&gt;possible to use Zephyr API for one instance, and nrfx for the other. You just need to disable SPIM instance that is going to be used with nrfx directly in the device tree. Then the Zephyr API won&amp;#39;t initialize that instance through the nrfx Zephyr port. &lt;a href="https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/boards/nrf/nrfx_prs"&gt;This example&lt;/a&gt; shows you how you can use the Zephyr API for one instance, and the nrfx driver directly for another instance for the same peripheral. It could be a good example to look at.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;best regards&lt;/p&gt;
&lt;p&gt;Jared&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>