<?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>How can I pull down a MOSI pin in SPI?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97313/how-can-i-pull-down-a-mosi-pin-in-spi</link><description>I am using a nRF5340 with two SPI (master) outputs configured. I am only concerned with the MOSI line on both SPIs because I am driving WS2814 Addressable LED Strips and they are driven only using SPI MOSI lines. The issue I am having is one of my MOSI</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 10 Mar 2023 17:38:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97313/how-can-i-pull-down-a-mosi-pin-in-spi" /><item><title>RE: How can I pull down a MOSI pin in SPI?</title><link>https://devzone.nordicsemi.com/thread/414730?ContentTypeID=1</link><pubDate>Fri, 10 Mar 2023 17:38:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4172aa4-0bdb-4f91-84ae-fc168933cade</guid><dc:creator>jacobbluhm</dc:creator><description>&lt;p&gt;Setting the last bit I send over MOSI to 0 made it so the default state of the MOSI pin is 0. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How can I pull down a MOSI pin in SPI?</title><link>https://devzone.nordicsemi.com/thread/413660?ContentTypeID=1</link><pubDate>Mon, 06 Mar 2023 23:02:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5d5345d4-3a49-4ef8-9f6e-79ed97ba3864</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I suspect that the MOSI line is just left wherever the last bit ended. Could that be the case? Are you sending the same data when using SPI1 and SPI4?&lt;/p&gt;
&lt;p&gt;Perhaps you can try to attach a 0xFF or 0x00 at the end of the bytes you are trying to send? That should set it high or low, if that is the case.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I must admit I have not seen anyone doing this in NCS/Zephyr, but I see that there are quite a lot of posts on the nRF5 SDK + neopixel LEDs. Have you checked out any of those? I am not saying you need to use the nRF5 SDK, but perhaps you can find someone with a similar issue.&lt;/p&gt;
&lt;p&gt;BR,&lt;br /&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>