<?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>nRF52833 i2s problem.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/86821/nrf52833-i2s-problem</link><description>Hello. 
 Is there any difference between i2s hardware in nRF52840 and nRF52833? I made WS2812B i2s driver and working very good on nRF52840. The same code (project is adjusted to nRF52833) doesn&amp;#39;t work on nRF52833. I discovered that there is small oversight</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Apr 2022 07:56:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/86821/nrf52833-i2s-problem" /><item><title>RE: nRF52833 i2s problem.</title><link>https://devzone.nordicsemi.com/thread/363782?ContentTypeID=1</link><pubDate>Wed, 20 Apr 2022 07:56:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88ab62db-2306-4d1e-bcc6-275359ef4a91</guid><dc:creator>PW</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Problem was solved. I used P1.11 in nRF5233 as i2s sck pin. But&amp;nbsp;there is no P1.11 in nRF5233 &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;. Thanks for code.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Piotr&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52833 i2s problem.</title><link>https://devzone.nordicsemi.com/thread/362880?ContentTypeID=1</link><pubDate>Mon, 11 Apr 2022 13:39:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7367b33-220c-4a60-ae9a-b09c8e6a8159</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I agree that the workaround should be applied for the nRF52833 as the Errata has also been &lt;a href="https://infocenter.nordicsemi.com/topic/errata_nRF52833_Rev2/ERR/nRF52833/Rev2/latest/anomaly_833_194.html?cp=4_1_1_0_1_14"&gt;listed &lt;/a&gt;in the errata list for that IC. But I don&amp;#39;t think that is causing your issue as the errata is related to the the current draw of the peripheral. Have you tried the I2S example in the SDK? I&amp;#39;ve attached the example folder from the SDK which contains a ported version that works on the nRF52833, see the PCA10100 folder.&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;
&lt;p&gt;Jared&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/i2s.7z"&gt;devzone.nordicsemi.com/.../i2s.7z&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52833 i2s problem.</title><link>https://devzone.nordicsemi.com/thread/362852?ContentTypeID=1</link><pubDate>Mon, 11 Apr 2022 12:26:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:07947618-5a15-43ac-bb65-b10b26dbcbe4</guid><dc:creator>PW</dc:creator><description>&lt;p&gt;About SDK. I didn&amp;#39;t express myself clearly. I wrote about definition which is in the beginning of file nrfx_i2s.c.&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/46660.png" /&gt;&lt;/p&gt;
&lt;p&gt;Shouldn&amp;#39;t there be extra definition for nRF52833? (I added&amp;nbsp;it in my code and enabled workaround for i2s_stop anomaly)&lt;/p&gt;
&lt;p&gt;Project is built correctly. BLE, i2c master, i2c slave and SPI works good, exactly like in nRF52840 version. The problem is only i2s. After start i2s, signal isn&amp;#39;t generated. Then after next start i2s, programm goes to &amp;quot;app_error_fault_handler&amp;quot;. Between starts there is of cource &amp;quot;i2s_stop&amp;quot;. I though there is some new issue with i2s in nRF52833, which can explain this&amp;nbsp;kind of action :(&lt;/p&gt;
&lt;p&gt;Piotr&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52833 i2s problem.</title><link>https://devzone.nordicsemi.com/thread/362822?ContentTypeID=1</link><pubDate>Mon, 11 Apr 2022 11:28:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:76837e28-5bfc-4ad9-9cb6-ad586d9bae6c</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t think there is any difference HW wise between the two in regards to the I2S peripheral.&amp;nbsp;&lt;/p&gt;
[quote user=""]discovered that there is small oversight in SDK17.1.0. In &lt;span style="color:rgba(0, 0, 0, 1);font-family:inherit;"&gt;nrfx_i2s_stop &lt;/span&gt;missing definition about nRF52833 which repair USE_WORKAROUND_FOR_I2S_STOP_ANOMALY&amp;nbsp;(file nrfx_i2s.c).&amp;nbsp;I try to find some differences in manuals, but I can&amp;#39;t see.&amp;nbsp;&amp;nbsp;[/quote]
&lt;p&gt;Can you elaborate a bit more on this? Maybe show me the difference in the driver?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you also describe how it doesn&amp;#39;t work on the nRF52833? Does the project build successfully? Does it assert during runtime?&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;
&lt;p&gt;Jared&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>