<?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>The cs pin of the spi is not working</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/109261/the-cs-pin-of-the-spi-is-not-working</link><description>I&amp;#39;m having problems with the spi api for zephyr, maybe my spi peripherals are not configured correctly, I can see normal signal outputs from the clock and mosi signal lines, but the cs line stays pulled up and doesn&amp;#39;t use any other outputs; 
 I am using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 15 Mar 2024 01:37:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/109261/the-cs-pin-of-the-spi-is-not-working" /><item><title>RE: The cs pin of the spi is not working</title><link>https://devzone.nordicsemi.com/thread/473992?ContentTypeID=1</link><pubDate>Fri, 15 Mar 2024 01:37:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:56f3bef0-9f38-4b83-96b1-a638d3fe6ccc</guid><dc:creator>emmovo</dc:creator><description>&lt;p&gt;My problem has been solved. As you said, after I mounted the spi with a special device in the device tree, the cs works fine. Thank you for your patient, professional and efficient technical support!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The cs pin of the spi is not working</title><link>https://devzone.nordicsemi.com/thread/473868?ContentTypeID=1</link><pubDate>Thu, 14 Mar 2024 13:07:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:39da5180-3d0e-43f7-a27e-b3fcf4c094e5</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Yes, correct. That is what I would expect, at least. I&amp;#39;ve never tried to use the SPI node without specifying a bus device in the DT.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The cs pin of the spi is not working</title><link>https://devzone.nordicsemi.com/thread/473867?ContentTypeID=1</link><pubDate>Thu, 14 Mar 2024 13:03:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a397f7d2-3ac4-476c-be22-ef6bcd1724d8</guid><dc:creator>emmovo</dc:creator><description>&lt;p&gt;Thanks for the reminder, what you mean is that I need to mount a specific device under the spi node of the device tree for the cs to be assigned and thus have the appropriate slice selection action; if I simply configure the spi without a specific device, the cs won&amp;#39;t have an action; am I understanding this correctly?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The cs pin of the spi is not working</title><link>https://devzone.nordicsemi.com/thread/473860?ContentTypeID=1</link><pubDate>Thu, 14 Mar 2024 12:43:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d83ab27-ae33-41b2-852c-e84e7835b1d0</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;I believe the problem in your case is that you have not specified any devices on your SPI bus, so the CS pin is not assigned to any device.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Here is an example which use the SPI API directly:&lt;/p&gt;
&lt;p&gt;&lt;a id="" href="https://github.com/too1/ncs-spi-master-slave-example/tree/master"&gt;https://github.com/too1/ncs-spi-master-slave-example/tree/master&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Notice that it defines a bus device in the overlay here:&amp;nbsp;&lt;a href="https://github.com/too1/ncs-spi-master-slave-example/blob/629db4cf8000605ddf46a5ac18936552bae3f52f/boards/nrf52840dk_nrf52840.overlay#L46"&gt;https://github.com/too1/ncs-spi-master-slave-example/blob/629db4cf8000605ddf46a5ac18936552bae3f52f/boards/nrf52840dk_nrf52840.overlay#L46&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The cs pin of the spi is not working</title><link>https://devzone.nordicsemi.com/thread/473854?ContentTypeID=1</link><pubDate>Thu, 14 Mar 2024 12:26:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c252575-7b9a-41a7-a5b1-3bb50143e78c</guid><dc:creator>emmovo</dc:creator><description>&lt;p&gt;Thank you very much for your reminder, I already know that I can directly add the st7789v node through the device tree in order to achieve the driver display, and successfully complete the display function; however, I still want to know the reason why I used the spi way cs signal line above did not work properly; I worry that if I face other zephyr device tree later when there is no preset device, I don&amp;#39;t know how to deal with it; I hope to get your support. I hope I can get your support, thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The cs pin of the spi is not working</title><link>https://devzone.nordicsemi.com/thread/473851?ContentTypeID=1</link><pubDate>Thu, 14 Mar 2024 12:16:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ae1b85b7-a31c-4df1-b221-1113609eed8e</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;If you search for &amp;#39;&lt;span&gt;st7789v&amp;#39; in the SDK, you should find multiple references to how the device can be defined in the devicetree. There&amp;#39;s also the&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.6.0/zephyr/boards/shields/st7789v_generic/doc/index.html"&gt;Generic ST7789V Display Shield&lt;/a&gt;&amp;nbsp;you can use.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Vidar&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>