<?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>nRF54H20 SPI CS assert issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123882/nrf54h20-spi-cs-assert-issue</link><description>Hi I&amp;#39;m trying to communicate with ICM45686 using nRF54H20 and SPI CLK, MISO, MOSI state appear correct but CS pin is not asserting/deasserting following it the scope capture, Yellow CS, Green Clock, Blue MOSI, Purple is MISO. Note: this is only one capture</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 02 Nov 2025 12:10:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123882/nrf54h20-spi-cs-assert-issue" /><item><title>RE: nRF54H20 SPI CS assert issue</title><link>https://devzone.nordicsemi.com/thread/553091?ContentTypeID=1</link><pubDate>Sun, 02 Nov 2025 12:10:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3174cd64-93cc-40d0-a011-43107194ece7</guid><dc:creator>Anuj Pathak</dc:creator><description>&lt;p&gt;The issue is resolved, it turns out to be a pin conflict issue during board migration&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54H20 SPI CS assert issue</title><link>https://devzone.nordicsemi.com/thread/546720?ContentTypeID=1</link><pubDate>Tue, 26 Aug 2025 08:15:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb3e35d6-c4e3-4a60-9ea0-c5d624248997</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Anuj,&lt;/p&gt;
&lt;p&gt;Could you try to test the CS pin on other&amp;nbsp;GPIOs ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;On the DK pin 2.7 is used for RTS UART136, have you checked if UART136 is not active and the pin is not used by UART ?&amp;nbsp;&lt;br /&gt;Could you send us your board&amp;#39;s device tree files ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you try to reproduce using one of our spim sample for example nrfx_spim/blocking ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>