<?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: Hardware trigger with ADC2 in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/1349830#M16559</link>
    <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/167132"&gt;@kurt_staubli&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It helped me with the same problem on RT1024.&lt;/P&gt;&lt;P&gt;Solution - change the default value of&amp;nbsp;enableTSCBypass from "true" to "false";&lt;/P&gt;</description>
    <pubDate>Mon, 04 Oct 2021 01:57:00 GMT</pubDate>
    <dc:creator>ohmjke</dc:creator>
    <dc:date>2021-10-04T01:57:00Z</dc:date>
    <item>
      <title>Hardware trigger with ADC2</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929192#M3767</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As &lt;A _jive_internal="true" href="https://community.nxp.com/thread/482078"&gt;others &lt;/A&gt;I struggle with hardware trigger of ADCs.&lt;/P&gt;&lt;P&gt;My base was NXP's example adc_etc_hardware_trigger_conv. It works as expected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Next I tried to do the same but use ADC2 instead of ADC1. I&amp;nbsp; didn't get any interrupts. I used trigger 4 instead of trigger 0 and I added an interrupt handler for ADC_ETC_ERROR. I received periodically&amp;nbsp;ADC_ETC_ERROR but no&amp;nbsp; ADC_ETC_IRQ0/1 as expected.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Oct 2019 11:49:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929192#M3767</guid>
      <dc:creator>kurt_staubli</dc:creator>
      <dc:date>2019-10-17T11:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger with ADC2</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929193#M3768</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" data-content-finding="Community" data-userid="342483" data-username="kurt.staubli@zub.ch" href="https://community.nxp.com/people/kurt.staubli@zub.ch"&gt;Kurt Staubli&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;Thank you for your interest in NXP Semiconductor products and &lt;BR /&gt;the opportunity to serve you.&lt;BR /&gt;To provide the fastest possible support, I'd like to suggest you refer to the post which is a similar question on our NXP community.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/514844"&gt;i.MXRT1060 ADC external trigger (ADC_ETC) for ADC 2&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIC&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Oct 2019 01:45:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929193#M3768</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2019-10-18T01:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger with ADC2</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929194#M3769</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN class=""&gt;&lt;A _jive_internal="true" data-content-finding="Community" data-userid="213424" data-username="jeremyzhou" href="https://community.nxp.com/people/jeremyzhou"&gt;jeremyzhou&lt;/A&gt; &lt;span class="lia-inline-image-display-wrapper" image-alt="Mitarbeiter"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/123686i130F8DE6A6AE32B2/image-size/large?v=v2&amp;amp;px=999" role="button" title="Mitarbeiter" alt="Mitarbeiter" /&gt;&lt;/span&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thank you for your answer.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" data-containerid="11760" data-containertype="14" data-content-finding="Community" data-objectid="514844" data-objecttype="1" href="https://community.nxp.com/thread/514844"&gt;i.MXRT1060 ADC external trigger (ADC_ETC) for ADC 2&lt;/A&gt; &lt;/P&gt;&lt;P&gt;did not help me, since its solution (use XBAR1, instead of XBAR0) was already implemented in the original example adc_etc_hardware_trigger_conv and I did not change it.&lt;/P&gt;&lt;P&gt;Kurt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Oct 2019 06:25:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929194#M3769</guid>
      <dc:creator>kurt_staubli</dc:creator>
      <dc:date>2019-10-18T06:25:31Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger with ADC2</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929195#M3770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class=""&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" data-containerid="-1" data-containertype="-1" data-content-finding="Community" data-objectid="342483" data-objecttype="3" href="https://community.nxp.com/people/kurt.staubli@zub.ch"&gt;Kurt Staubli&lt;/A&gt;,&lt;/P&gt;Thanks for your reply.&lt;BR /&gt;I was wondering if you can share a compile-able demo that can replicate the issue, as I'd like to do some testing by myself.&lt;BR /&gt;&lt;P&gt;TIC&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Oct 2019 06:24:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929195#M3770</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2019-10-22T06:24:26Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger with ADC2</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929196#M3771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN class=""&gt;&lt;A _jive_internal="true" class="" data-content-finding="Community" data-userid="213424" data-username="jeremyzhou" href="https://community.nxp.com/people/jeremyzhou"&gt;jeremyzhou&lt;/A&gt; &lt;span class="lia-inline-image-display-wrapper" image-alt="Mitarbeiter"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/123687iF299CD92E4093B69/image-size/large?v=v2&amp;amp;px=999" role="button" title="Mitarbeiter" alt="Mitarbeiter" /&gt;&lt;/span&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I have solved the problem.&lt;/P&gt;&lt;P&gt;The orignial example is adc_etc_hardware_trigger_conv. I have just the changed files in the attachment. As hardware I am using EmbeddedArtist's RT1060 Evaluation board. The difference to NXP's evaluation board is that EA's board has much more IOs for the user. &lt;/P&gt;&lt;P&gt;Kurt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Oct 2019 09:48:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/929196#M3771</guid>
      <dc:creator>kurt_staubli</dc:creator>
      <dc:date>2019-10-22T09:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger with ADC2</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/1349830#M16559</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/167132"&gt;@kurt_staubli&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It helped me with the same problem on RT1024.&lt;/P&gt;&lt;P&gt;Solution - change the default value of&amp;nbsp;enableTSCBypass from "true" to "false";&lt;/P&gt;</description>
      <pubDate>Mon, 04 Oct 2021 01:57:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Hardware-trigger-with-ADC2/m-p/1349830#M16559</guid>
      <dc:creator>ohmjke</dc:creator>
      <dc:date>2021-10-04T01:57:00Z</dc:date>
    </item>
  </channel>
</rss>

