<?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>nRF5340 Issue when using Dedicated High Speed SPI pins on SDK &amp;gt; 1.5.1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/85691/nrf5340-issue-when-using-dedicated-high-speed-spi-pins-on-sdk-1-5-1</link><description>Board: nRF5340-DK 
 Version: NRF5340_xxAA_ENGD 
 SDK: 1.5.1, 1.6.1, etc 
 
 I have a Bluetooth project that also has quite a high SPI bandwidth requirement, so hence I am using the dedicated high-speed spi pins, and the SPI4 interface. 
 /* use the high</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Mar 2022 13:19:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/85691/nrf5340-issue-when-using-dedicated-high-speed-spi-pins-on-sdk-1-5-1" /><item><title>RE: nRF5340 Issue when using Dedicated High Speed SPI pins on SDK &gt; 1.5.1</title><link>https://devzone.nordicsemi.com/thread/357672?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2022 13:19:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0065c19c-95bf-42d3-b209-a59d2cc30e82</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;These pin&amp;nbsp; settings should ideally be set in the DeviceTree instead of hardcoded like that. It is being worked on, see &lt;a href="https://github.com/zephyrproject-rtos/zephyr/pull/42576"&gt;https://github.com/zephyrproject-rtos/zephyr/pull/42576&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If both the Application Core and the Network Core tries to use the same pins at the same time, it may cause errors, and I guess this is what happened in your case.&lt;/p&gt;
&lt;p&gt;Did this answer your questions?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>