<?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, WS2812, I2S</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127287/nrf5340-ws2812-i2s</link><description>Hello. 
 I&amp;#39;m trying to use WS2812 leds with I2S. I&amp;#39;m using two boards for testing: an NRF5340DK and my board based on the HOLYIOT-21069-5340 module. 
 I&amp;#39;m using a zephyr/samples/drivers/led/led_strip as an example. 
 I need the control signal to be on</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 10 Mar 2026 09:49:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127287/nrf5340-ws2812-i2s" /><item><title>RE: NRF5340, WS2812, I2S</title><link>https://devzone.nordicsemi.com/thread/562899?ContentTypeID=1</link><pubDate>Tue, 10 Mar 2026 09:49:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d75643b6-d4c7-4f08-922e-6ca54571600c</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Did you try scoping the pins to see if there is a difference between the two solutions?&lt;/p&gt;
&lt;p&gt;Could it be that there is a soldering issue or a routing issue on your custom board? Did you try to use other pins for your custom board?&lt;/p&gt;
[quote user="D233374"]As far as I understand, the I2C unit is clocked from the 32 MHz bus, not the 32 kHz bus. Therefore, switching the 32 kHz bus to the RC source didn&amp;#39;t help.[/quote]
&lt;p&gt;You have not provided a schematic for your custom board, but having a 32k source is mandatory for the rtos. If you do not have an external 32k (default in nRF5340-DK), you need to set the source to internal 32k RC oscillator.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF5340, WS2812, I2S</title><link>https://devzone.nordicsemi.com/thread/562768?ContentTypeID=1</link><pubDate>Sun, 08 Mar 2026 15:40:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd6746b0-0ea6-43d9-b565-39a8604c2c6c</guid><dc:creator>D233374</dc:creator><description>&lt;p&gt;The I2S settings allow to select a clock source (&lt;a href="https://docs.zephyrproject.org/latest/build/dts/api/bindings/i2s/nordic%2Cnrf-i2s.html)."&gt;docs.zephyrproject.org/.../nordic,nrf-i2s.html).&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As far as I understand, the I2C unit is clocked from the 32 MHz bus, not the 32 kHz bus. Therefore, switching the 32 kHz bus to the RC source didn&amp;#39;t help.&lt;/p&gt;
&lt;p&gt;I tried all the available options (&lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;PCLK32M&lt;/span&gt;&lt;/code&gt;&lt;span&gt;,&amp;nbsp;&lt;/span&gt;&lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;PCLK32M_HFXO&lt;/span&gt;&lt;/code&gt;), but the result was exactly the same. I checked the debugger, and the error appears starting&amp;nbsp;&lt;span style="font-family:inherit;"&gt;with the second attempt to send. This means, for some reason, the first attempt to send never completes.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;It&amp;#39;s possible there really is a clocking issue, but I don&amp;#39;t see what could be wrong. On this board, the UART, SPI, and BLE are working. This means the high-frequency bus is clocked.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF5340, WS2812, I2S</title><link>https://devzone.nordicsemi.com/thread/562731?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 13:34:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:48f9b109-bbd2-49cf-a7c0-da7dde5c8a7a</guid><dc:creator>D233374</dc:creator><description>&lt;p&gt;It&amp;#39;s the exact same code. The same .hex file. I don&amp;#39;t recompile the project, I just upload it to both boards.&lt;/p&gt;
&lt;p&gt;I tried selecting different pins, and there were always no error messages on the NRF5340DK, but on my board, I get the same error messages every time I try to send it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF5340, WS2812, I2S</title><link>https://devzone.nordicsemi.com/thread/562721?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 12:31:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4e4cd9e3-6811-4882-9474-efd563014dd9</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you done any changes to the .c file? Do you use the exact same .hex for the DK as for your board?&lt;/p&gt;
&lt;p&gt;This indicates that the module is draining its transfer:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;&amp;lt;err&amp;gt; i2s_nrfx: Cannot write in state: 3&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;as state=3 means&amp;nbsp;I2S_STATE_STOPPING, indicating that a former transfer is on-going when triggering a new one.&lt;/p&gt;
&lt;p&gt;I would recommend that you scope the I2S pins in both working scenario and non-working scenario, and see if there is a specific difference.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF5340, WS2812, I2S</title><link>https://devzone.nordicsemi.com/thread/562709?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 10:03:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:20bcaf98-8652-463c-a806-5a61ba13374c</guid><dc:creator>D233374</dc:creator><description>[quote userid="2115" url="~/f/nordic-q-a/127287/nrf5340-ws2812-i2s/562662"]&lt;p&gt;Does your custom board include both DCDC inductors and an external LF clk?&lt;/p&gt;
&lt;p&gt;If not, you will need to&amp;nbsp;&lt;span&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;[/quote]
&lt;p&gt;I added to prj.conf:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_CLOCK_CONTROL=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;But there are no changes, I still get messages on my board:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;[00:00:00.000,335] &amp;lt;inf&amp;gt; main: Found LED strip device ws2812@0
[00:00:00.000,366] &amp;lt;inf&amp;gt; main: Displaying pattern on strip
[00:00:00.053,161] &amp;lt;err&amp;gt; i2s_nrfx: Cannot write in state: 3
[00:00:00.053,192] &amp;lt;err&amp;gt; ws2812_i2s: Failed to write data: -5
[00:00:00.053,192] &amp;lt;err&amp;gt; main: couldn&amp;#39;t update strip: -5
&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF5340, WS2812, I2S</title><link>https://devzone.nordicsemi.com/thread/562662?ContentTypeID=1</link><pubDate>Thu, 05 Mar 2026 15:20:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ecdf3d52-2aca-4be8-afb3-b7a0c2d0d525</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]&lt;p&gt;If I use pin P1.00, nothing works — the pin stays high all the time. If I use P1.01 or P1.13, everything works.&lt;/p&gt;
&lt;p&gt;P1.00 is listed in the description as a &amp;quot;General purpose I/O.&amp;quot; Nothing seems to be connected to it on the board either. Why can&amp;#39;t I use it?&lt;/p&gt;[/quote]
&lt;p&gt;Try disabling the gpio pin forwarder to the network core by adding this to your overlay:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;&amp;amp;gpio_fwd {
	status = &amp;quot;disabled&amp;quot;;
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]&lt;p&gt;The second problem occurs when I try to use my board. The board is based on a &lt;span&gt;HOLYIOT-21069-5340&lt;/span&gt; module with&amp;nbsp;nRF5340 QKAA.&lt;/p&gt;
&lt;p&gt;I use the exact same code without rebuilding it.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m just doing a &amp;quot;west flash,&amp;quot; but instead of a &lt;span&gt;NRF5340DK&lt;/span&gt; board, I&amp;#39;m connecting my &lt;span&gt;HOLYIOT-21069-5340&lt;/span&gt;&lt;span&gt;&amp;nbsp;module&lt;/span&gt;. And for some reason, the driver stops working, and I get the following messages in debug:&lt;/p&gt;[/quote]
&lt;p&gt;Does your custom board include both DCDC inductors and an external LF clk?&lt;/p&gt;
&lt;p&gt;If not, you will need to&amp;nbsp;&lt;span&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kind regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Håkon&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>