<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX RT Crossover MCUs中的主题 Re: I2S Buffer not processed yet</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1733980#M27100</link>
    <description>&lt;P&gt;New twist - bit clock looks good but the frame clock is running at the same rate:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mrichardson23_0-1696457594198.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/243651iA80459D1A3D9E576/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mrichardson23_0-1696457594198.png" alt="mrichardson23_0-1696457594198.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;mrichardson23_0-1696457594198.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Oct 2023 22:13:23 GMT</pubDate>
    <dc:creator>mrichardson23</dc:creator>
    <dc:date>2023-10-04T22:13:23Z</dc:date>
    <item>
      <title>I2S Buffer not processed yet</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1733408#M27068</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am running into the error on the RT685 using the audio evaluation kit of kStatus_I2S_Busy when I attempt to transmit data on flexcomm 4.&amp;nbsp; My initialization of this bus is done at boot:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;const i2s_config_t FC4_I2S_TX_config = {
  .masterSlave = kI2S_MasterSlaveNormalMaster,
  .mode = kI2S_ModeDspWsShort,
  .rightLow = false,
  .leftJust = false,
  .sckPol = false,
  .wsPol = true,
  .divider = 2,
  .oneChannel = false,
  .dataLength = 32,
  .frameLength = 256,
  .position = 0,
  .watermark = 4,
  .txEmptyZero = true,
  .pack48 = false
};
dma_handle_t FC4_I2S_TX_TX_Handle;
i2s_dma_handle_t FC4_I2S_Tx_Handle;

static void FC4_I2S_TX_init(void) {
  /* Flexcomm I2S initialization */
  I2S_TxInit(FC4_I2S_TX_PERIPHERAL, &amp;amp;FC4_I2S_TX_config);
  /* Setup secondary channel 1 */
  I2S_EnableSecondaryChannel(FC4_I2S_TX_PERIPHERAL, kI2S_SecondaryChannel1, false, 64U);
  /* Setup secondary channel 2 */
  I2S_EnableSecondaryChannel(FC4_I2S_TX_PERIPHERAL, kI2S_SecondaryChannel2, false, 128U);
  /* Setup secondary channel 3 */
  I2S_EnableSecondaryChannel(FC4_I2S_TX_PERIPHERAL, kI2S_SecondaryChannel3, false, 192U);
  /* Enable the DMA 9 channel in the DMA */
  DMA_EnableChannel(FC4_I2S_TX_TX_DMA_BASEADDR, FC4_I2S_TX_TX_DMA_CHANNEL);
  /* Set the DMA 9 channel priority */
  DMA_SetChannelPriority(FC4_I2S_TX_TX_DMA_BASEADDR, FC4_I2S_TX_TX_DMA_CHANNEL, kDMA_ChannelPriority3);
  /* Create the DMA FC4_I2S_TX_TX_Handle handle */
  DMA_CreateHandle(&amp;amp;FC4_I2S_TX_TX_Handle, FC4_I2S_TX_TX_DMA_BASEADDR, FC4_I2S_TX_TX_DMA_CHANNEL);
  /* Create the I2S DMA handle */
  I2S_TxTransferCreateHandleDMA(FC4_I2S_TX_PERIPHERAL, &amp;amp;FC4_I2S_Tx_Handle, &amp;amp;FC4_I2S_TX_TX_Handle, NULL, NULL);
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I doing something wrong here? The clock for FC4 is attached to the audio pll and all of the pins are configured for I2S functionality.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2023 22:47:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1733408#M27068</guid>
      <dc:creator>mrichardson23</dc:creator>
      <dc:date>2023-10-03T22:47:47Z</dc:date>
    </item>
    <item>
      <title>Re: I2S Buffer not processed yet</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1733980#M27100</link>
      <description>&lt;P&gt;New twist - bit clock looks good but the frame clock is running at the same rate:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mrichardson23_0-1696457594198.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/243651iA80459D1A3D9E576/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mrichardson23_0-1696457594198.png" alt="mrichardson23_0-1696457594198.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;mrichardson23_0-1696457594198.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 22:13:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1733980#M27100</guid>
      <dc:creator>mrichardson23</dc:creator>
      <dc:date>2023-10-04T22:13:23Z</dc:date>
    </item>
    <item>
      <title>Re: I2S Buffer not processed yet</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1736845#M27186</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/221356"&gt;@mrichardson23&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;It is my understanding that you are trying to implement "TDM and DSP modes with 1 SCK pulsed WS" as seen on "Fig 73." of the Reference Manual, is this correct? If so, please refer to the "mimxrt685audevk_i2s_dma_tdm" example code from our SDK, since it exemplifies how to setup this case. If fact, from a quick look into this example, I believe it has the same initialization configuration structure, except the example changes the "tx_config.position" to "1".&lt;/P&gt;
&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 21:24:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1736845#M27186</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2023-10-10T21:24:23Z</dc:date>
    </item>
    <item>
      <title>Re: I2S Buffer not processed yet</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1736878#M27187</link>
      <description>&lt;P&gt;Thanks, &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/186731"&gt;@EdwinHz&lt;/a&gt;&amp;nbsp;.&amp;nbsp; I have done that.&amp;nbsp; I am currently building off of the playback-record example and all of that is functional.&amp;nbsp; I need to add FC4 and 5 for additional I2S busses.&amp;nbsp; So, can you tell me what might be going on where the bit clock is ticking at the expected rate but the WS clock is not right?&amp;nbsp; Could this be a hardware configuration issue?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 22:53:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1736878#M27187</guid>
      <dc:creator>mrichardson23</dc:creator>
      <dc:date>2023-10-10T22:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: I2S Buffer not processed yet</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1738770#M27211</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mrichardson23_0-1697124308836.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/244851iE71DD55DF883DD36/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mrichardson23_0-1697124308836.png" alt="mrichardson23_0-1697124308836.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;mrichardson23_0-1697124308836.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Here is the description of the Flexcomm interface from the RT-600 manual - based on this, why is the bitclock correct but the ws clock not?&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2023 15:26:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1738770#M27211</guid>
      <dc:creator>mrichardson23</dc:creator>
      <dc:date>2023-10-12T15:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: I2S Buffer not processed yet</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1738964#M27217</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/186731"&gt;@EdwinHz&lt;/a&gt;, thank you for follow-up. I will continue to follow up with Matt. Thank you.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Frank&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2023 23:17:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1738964#M27217</guid>
      <dc:creator>Frank_Kim</dc:creator>
      <dc:date>2023-10-12T23:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: I2S Buffer not processed yet</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1740607#M27240</link>
      <description>&lt;P&gt;I have checked the config and fifo registers.&amp;nbsp; In operation, they both look good.&amp;nbsp; CFG1 is 2039997 and the&amp;nbsp; FIFOCFG register is 4133.&amp;nbsp; On the board I have JP42 set to 2-3.&amp;nbsp; I can't see anything I am doing wrong here.&amp;nbsp; Could R79 be creating an issue here for me?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Oct 2023 18:17:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I2S-Buffer-not-processed-yet/m-p/1740607#M27240</guid>
      <dc:creator>mrichardson23</dc:creator>
      <dc:date>2023-10-16T18:17:13Z</dc:date>
    </item>
  </channel>
</rss>

