<?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のトピックadc_etc hardware trigger example has the problem</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/adc-etc-hardware-trigger-example-has-the-problem/m-p/836766#M1615</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I used MCUXpresso IDEv10.3.0 [Build 2200] [2018-12-03] with RT1050 sdk v2.5 to try adc_etc hardware trigger example. I found that the adc_etc interrupt is nor taken place (adc value always 0) and adc_etc software trigger example is OK. Has anyone been the same problem?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Screenshot from 2018-12-27 12-40-29.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/71034iC5F26B48DCCA8125/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot from 2018-12-27 12-40-29.png" alt="Screenshot from 2018-12-27 12-40-29.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Dec 2018 04:41:59 GMT</pubDate>
    <dc:creator>zhongshen</dc:creator>
    <dc:date>2018-12-27T04:41:59Z</dc:date>
    <item>
      <title>adc_etc hardware trigger example has the problem</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/adc-etc-hardware-trigger-example-has-the-problem/m-p/836766#M1615</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I used MCUXpresso IDEv10.3.0 [Build 2200] [2018-12-03] with RT1050 sdk v2.5 to try adc_etc hardware trigger example. I found that the adc_etc interrupt is nor taken place (adc value always 0) and adc_etc software trigger example is OK. Has anyone been the same problem?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Screenshot from 2018-12-27 12-40-29.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/71034iC5F26B48DCCA8125/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot from 2018-12-27 12-40-29.png" alt="Screenshot from 2018-12-27 12-40-29.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Dec 2018 04:41:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/adc-etc-hardware-trigger-example-has-the-problem/m-p/836766#M1615</guid>
      <dc:creator>zhongshen</dc:creator>
      <dc:date>2018-12-27T04:41:59Z</dc:date>
    </item>
    <item>
      <title>Re: adc_etc hardware trigger example has the problem</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/adc-etc-hardware-trigger-example-has-the-problem/m-p/836767#M1616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;refer to the readme:&lt;/P&gt;&lt;P&gt;Board settings&lt;BR /&gt;==============&lt;BR /&gt;ADC0_IN15 and ADC0_IN0 are ADC inputs. Please sample voltage by J23-1 and J23-2 pins.&lt;/P&gt;&lt;P&gt;&amp;nbsp;pls check if your board settings are correct or not.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2019 08:48:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/adc-etc-hardware-trigger-example-has-the-problem/m-p/836767#M1616</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2019-01-03T08:48:18Z</dc:date>
    </item>
    <item>
      <title>Re: adc_etc hardware trigger example has the problem</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/adc-etc-hardware-trigger-example-has-the-problem/m-p/836768#M1617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for you reply. The connection is not wrong. I found that the print info is on the console not on the uart port. The software&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;trigger example&lt;SPAN&gt;&amp;nbsp;is correct and the print info is on the uart port. And I delete the hardware&amp;nbsp;&lt;SPAN style="background-color: #ffffff;"&gt;trigger example&lt;SPAN&gt;&amp;nbsp;and import it again, build it. This time, the print info is on the uart port and adc is working correct. Could you advise me the reason, print info on console or uart port?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Jan 2019 08:18:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/adc-etc-hardware-trigger-example-has-the-problem/m-p/836768#M1617</guid>
      <dc:creator>zhongshen</dc:creator>
      <dc:date>2019-01-05T08:18:36Z</dc:date>
    </item>
  </channel>
</rss>

