<?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 Re: Set pin low every timer interval in hardware in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055364#M8175</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looking in page 78 of RT1064 reference manual, sounds like the DMA has the ability to write data to GPIO port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;• Using the GPIO ports to drive or sample waveforms&lt;BR /&gt;By configuring the DMA to transfer data to one or more GPIO ports, it is possible to&lt;BR /&gt;create complex waveforms using tabular data stored in on-chip memory. Conversely,&lt;BR /&gt;using the DMA to periodically transfer data from one or more GPIO ports, it is&lt;BR /&gt;possible to sample complex waveforms and store the results in tabular form in onchip&lt;BR /&gt;memory.&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will look into this, but also hoping to get some insight from NXP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Jul 2020 17:07:45 GMT</pubDate>
    <dc:creator>karl_fraasch</dc:creator>
    <dc:date>2020-07-17T17:07:45Z</dc:date>
    <item>
      <title>Set pin low every timer interval in hardware</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055363#M8174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am interfacing to an external ADC using the RT1064. The particular ADC supports a "Request" pin which allows the user to pull the pin low to request an ADC sample. The software will then set the pin high once the sample is read using SPI.&lt;/P&gt;&lt;P&gt;My preference is to trigger the request pin entirely in hardware, to guarantee a precise sampling rate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have experimented using the PIT routed to the XBAR to trigger an IOMUX pin. While I am able to trigger a pulse at my desired rate, the pulse matches the shape of the PIT trigger. What I need is to pull the pin low every time the timer triggers. Software will then take care of setting the pin high once the operation is complete.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From what I can tell, this is not possible using XBAR with PIT (input) and IOMUX (output). Are there other XBAR inputs or outputs that can accomplish this (QTIMER, FLEXIO)? Or are there separate modules entirely other than XBAR to accomplish this (FLEXIO)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jul 2020 15:00:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055363#M8174</guid>
      <dc:creator>karl_fraasch</dc:creator>
      <dc:date>2020-07-16T15:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Set pin low every timer interval in hardware</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055364#M8175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looking in page 78 of RT1064 reference manual, sounds like the DMA has the ability to write data to GPIO port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;• Using the GPIO ports to drive or sample waveforms&lt;BR /&gt;By configuring the DMA to transfer data to one or more GPIO ports, it is possible to&lt;BR /&gt;create complex waveforms using tabular data stored in on-chip memory. Conversely,&lt;BR /&gt;using the DMA to periodically transfer data from one or more GPIO ports, it is&lt;BR /&gt;possible to sample complex waveforms and store the results in tabular form in onchip&lt;BR /&gt;memory.&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will look into this, but also hoping to get some insight from NXP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jul 2020 17:07:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055364#M8175</guid>
      <dc:creator>karl_fraasch</dc:creator>
      <dc:date>2020-07-17T17:07:45Z</dc:date>
    </item>
    <item>
      <title>Re: Set pin low every timer interval in hardware</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055365#M8176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&amp;nbsp; Karl,&lt;/P&gt;&lt;P&gt;Hope you are doing well.&lt;/P&gt;&lt;P&gt;Based on your description I believe that if you have an output of a PWM&amp;nbsp; signal you will have better results than using a PIT interrupt. You can produce a signal that changes from high to low adequately.&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is an example using the xbar and output pwm signal in our SDK for the RT1064. Please let me know if this fits what you are looking for. If so, I can provide more information as well as other posts that go deeper in detail.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Sabina&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Jul 2020 19:12:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055365#M8176</guid>
      <dc:creator>Sabina_Bruce</dc:creator>
      <dc:date>2020-07-20T19:12:13Z</dc:date>
    </item>
    <item>
      <title>Re: Set pin low every timer interval in hardware</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055366#M8177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sabina,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any reason the method you mentioned is preferred vs doing the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using the PIT to trigger the DMA via crossbar. DMA configured to write to the GPIO DR_SET and/or DR_CLEAR registers.&lt;/P&gt;&lt;P&gt;PIT-&amp;gt;XBAR-&amp;gt;DMA-&amp;gt;GPIO DR_SET, DR_CLEAR pins?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been playing around with this and have it somewhat working. My current issue is periodically triggering the DMA transfer to GPIO DR_CLEAR register without any processor intervention.&amp;nbsp;Currently I have to reconfigure the DMA after each transfer.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jul 2020 19:36:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055366#M8177</guid>
      <dc:creator>karl_fraasch</dc:creator>
      <dc:date>2020-07-21T19:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: Set pin low every timer interval in hardware</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055367#M8178</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Karl,&lt;/P&gt;&lt;P&gt;Hope you are doing well.&lt;/P&gt;&lt;P&gt;I believe that is taking a longer route to potentially cause delays or errors in adequately triggering your external ADC. Essentially from your above description, you could use the PIT to trigger a GPIO high and low state, without going through xbar and dma. The reason I'd recommend the pwm is because you can configure the signal to produce the high and low levels on the signal directly and only needing one module, making it simple and efficient. However, there may be a reason why you are choosing to use the xbar and dma specifically. If so, could you please share the principal objective of this route you are experimenting.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Sabina&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Jul 2020 18:40:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Set-pin-low-every-timer-interval-in-hardware/m-p/1055367#M8178</guid>
      <dc:creator>Sabina_Bruce</dc:creator>
      <dc:date>2020-07-22T18:40:59Z</dc:date>
    </item>
  </channel>
</rss>

