<?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>topic Clarification on eDMA use with LPSPI watermark in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Clarification-on-eDMA-use-with-LPSPI-watermark/m-p/735308#M114439</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, I am using IAR with an RT1050 SDK, version&amp;nbsp; &lt;SPAN class=""&gt;2.3.0&lt;/SPAN&gt; (2017-11-16).&amp;nbsp; I have been working with the scatter gather example and trying to adapt it to a double-buffered reader of LPSPI data.&amp;nbsp; I am looking for clarification on some things I am seeing in the reference manual:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;21.1.3&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;Periodic Trigger mode&lt;BR /&gt;In this mode, a DMA source may only request a DMA transfer, such as when a&lt;BR /&gt;transmit buffer becomes empty or a receive buffer becomes full, periodically.&lt;BR /&gt;Configuration of the period is done in the registers of the periodic interrupt timer&lt;BR /&gt;(PIT). This mode is available only for channels 0 to 3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;21.4.1 DMA channels with periodic triggering capability&lt;BR /&gt;Besides the normal routing functionality, the first 4 channels of the DMAMUX provide a&lt;BR /&gt;special periodic triggering capability that can be used to provide an automatic mechanism&lt;BR /&gt;to transmit bytes, frames, or packets at fixed intervals without the need for processor&lt;BR /&gt;intervention.&lt;BR /&gt;The trigger is generated by the periodic interrupt timer (PIT); as such, the configuration&lt;BR /&gt;of the periodic triggering interval is done via configuration registers in the PIT. See the&lt;BR /&gt;section on periodic interrupt timer for more information on this topic.&lt;BR /&gt;Note&lt;BR /&gt;Because of the dynamic nature of the system (due to DMA&lt;BR /&gt;channel priorities, bus arbitration, interrupt service routine&lt;BR /&gt;lengths, etc.), the number of clock cycles between a trigger and&lt;BR /&gt;the actual DMA transfer cannot be guaranteed.&lt;BR /&gt;Chapter 21 Direct Memory Access Multiplexer (DMAMUX)&lt;BR /&gt;i.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;38.1 Chip-specific LPSPI information&lt;BR /&gt;NOTE&lt;BR /&gt;The "Output Triggers" section is not applicable for this device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;38.3.5.1 Output Triggers&lt;BR /&gt;The LPSPI generates two output triggers that can be connected to other peripherals on the&lt;BR /&gt;device. The frame output trigger asserts at the end of each frame (when PCS negates) and&lt;BR /&gt;remains asserted until PCS next asserts. The word output trigger asserts at the end of each&lt;BR /&gt;received word and remains asserted for one LPSPI_SCK period.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the statements above and other experimentation, I am getting the impression that LPSPI eDMA transactions can not be triggered or paced from an LPSPI RX FIFO watermark event.&amp;nbsp; Section 21.1.3 seems to suggest that the recommended way of doing this is to periodically trigger a transfer of a given number of bytes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to trigger an RT1050 eDMA transfer from an LPSPI FIFO hitting a given watermark of is the PIT polling process the only way?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Jan 2018 17:43:16 GMT</pubDate>
    <dc:creator>ryanshuttlewort</dc:creator>
    <dc:date>2018-01-18T17:43:16Z</dc:date>
    <item>
      <title>Clarification on eDMA use with LPSPI watermark</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Clarification-on-eDMA-use-with-LPSPI-watermark/m-p/735308#M114439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, I am using IAR with an RT1050 SDK, version&amp;nbsp; &lt;SPAN class=""&gt;2.3.0&lt;/SPAN&gt; (2017-11-16).&amp;nbsp; I have been working with the scatter gather example and trying to adapt it to a double-buffered reader of LPSPI data.&amp;nbsp; I am looking for clarification on some things I am seeing in the reference manual:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;21.1.3&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;Periodic Trigger mode&lt;BR /&gt;In this mode, a DMA source may only request a DMA transfer, such as when a&lt;BR /&gt;transmit buffer becomes empty or a receive buffer becomes full, periodically.&lt;BR /&gt;Configuration of the period is done in the registers of the periodic interrupt timer&lt;BR /&gt;(PIT). This mode is available only for channels 0 to 3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;21.4.1 DMA channels with periodic triggering capability&lt;BR /&gt;Besides the normal routing functionality, the first 4 channels of the DMAMUX provide a&lt;BR /&gt;special periodic triggering capability that can be used to provide an automatic mechanism&lt;BR /&gt;to transmit bytes, frames, or packets at fixed intervals without the need for processor&lt;BR /&gt;intervention.&lt;BR /&gt;The trigger is generated by the periodic interrupt timer (PIT); as such, the configuration&lt;BR /&gt;of the periodic triggering interval is done via configuration registers in the PIT. See the&lt;BR /&gt;section on periodic interrupt timer for more information on this topic.&lt;BR /&gt;Note&lt;BR /&gt;Because of the dynamic nature of the system (due to DMA&lt;BR /&gt;channel priorities, bus arbitration, interrupt service routine&lt;BR /&gt;lengths, etc.), the number of clock cycles between a trigger and&lt;BR /&gt;the actual DMA transfer cannot be guaranteed.&lt;BR /&gt;Chapter 21 Direct Memory Access Multiplexer (DMAMUX)&lt;BR /&gt;i.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;38.1 Chip-specific LPSPI information&lt;BR /&gt;NOTE&lt;BR /&gt;The "Output Triggers" section is not applicable for this device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;38.3.5.1 Output Triggers&lt;BR /&gt;The LPSPI generates two output triggers that can be connected to other peripherals on the&lt;BR /&gt;device. The frame output trigger asserts at the end of each frame (when PCS negates) and&lt;BR /&gt;remains asserted until PCS next asserts. The word output trigger asserts at the end of each&lt;BR /&gt;received word and remains asserted for one LPSPI_SCK period.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the statements above and other experimentation, I am getting the impression that LPSPI eDMA transactions can not be triggered or paced from an LPSPI RX FIFO watermark event.&amp;nbsp; Section 21.1.3 seems to suggest that the recommended way of doing this is to periodically trigger a transfer of a given number of bytes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to trigger an RT1050 eDMA transfer from an LPSPI FIFO hitting a given watermark of is the PIT polling process the only way?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jan 2018 17:43:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Clarification-on-eDMA-use-with-LPSPI-watermark/m-p/735308#M114439</guid>
      <dc:creator>ryanshuttlewort</dc:creator>
      <dc:date>2018-01-18T17:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: Clarification on eDMA use with LPSPI watermark</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Clarification-on-eDMA-use-with-LPSPI-watermark/m-p/735309#M114440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; According to Chapter 22 [Enhanced Direct Memory Access (eDMA)] &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;of i.MX RT1050 Processor Reference Manual, Rev. 0, 10/2017, &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;there are two options to request channel service:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;• Software: setting the TCDn_CSR[START].&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;• Hardware: slave device asserting its eDMA peripheral request signal.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;The DMAMUX should be used in Normal mode.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;“In this mode, a DMA source is routed directly to the specified DMA channel. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;The operation of the DMAMUX in this mode is completely transparent to the &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;system.”&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Yuri&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jan 2018 07:44:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Clarification-on-eDMA-use-with-LPSPI-watermark/m-p/735309#M114440</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2018-01-19T07:44:50Z</dc:date>
    </item>
    <item>
      <title>Re: Clarification on eDMA use with LPSPI watermark</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Clarification-on-eDMA-use-with-LPSPI-watermark/m-p/735310#M114441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Customers can use&amp;nbsp;&lt;A class="link-titled" href="https://www.nxp.com/webapp/sps/download/license.jsp?colCode=i.MXRT1050-EX-CODE-AND-HW-GUIDE&amp;amp;appType=file2&amp;amp;location=null&amp;amp;DOWNLOAD_ID=null" title="https://www.nxp.com/webapp/sps/download/license.jsp?colCode=i.MXRT1050-EX-CODE-AND-HW-GUIDE&amp;amp;appType=file2&amp;amp;location=null&amp;amp;DOWNLOAD_ID=null"&gt;i.MXRT1050 EVK Extended Feature Example Code and HW guide&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yuri.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2018 06:11:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Clarification-on-eDMA-use-with-LPSPI-watermark/m-p/735310#M114441</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2018-01-24T06:11:05Z</dc:date>
    </item>
  </channel>
</rss>

