<?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 ADC Conversion timing issue in S32K</title>
    <link>https://community.nxp.com/t5/S32K/ADC-Conversion-timing-issue/m-p/1928219#M39111</link>
    <description>&lt;DIV&gt;Hi Team,&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;1. In S32K146, I have an issue where ADC0 (total 8 channels) one-shot conversion takes ~600 microsec for a single group using StartGroup() &amp;amp; ReadGroup() Apis and this is causing timing delays for the 1ms App scheduler.&amp;nbsp;&lt;BR /&gt;What could be the reason for this timing behaviour?&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;2. When I changed the config to Continuous mode , the time delay was ~120ms for getting the expected ADC value increased compared&amp;nbsp;to one-shot where it took less than 50msec, is this expected behaviour.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;3.After analyzing the timing for the internal ADC functions , it was found that the Adc_Ipw_ConfigurePdbConversion(), ADC_Ip&lt;/SPAN&gt;&lt;I&gt;_&lt;/I&gt;&lt;SPAN&gt;ConfigChannel() is taking 130 us, 120 us which causes overall timing delay.&lt;/SPAN&gt;&lt;/DIV&gt;</description>
    <pubDate>Thu, 08 Aug 2024 10:46:25 GMT</pubDate>
    <dc:creator>S32k1</dc:creator>
    <dc:date>2024-08-08T10:46:25Z</dc:date>
    <item>
      <title>ADC Conversion timing issue</title>
      <link>https://community.nxp.com/t5/S32K/ADC-Conversion-timing-issue/m-p/1928219#M39111</link>
      <description>&lt;DIV&gt;Hi Team,&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;1. In S32K146, I have an issue where ADC0 (total 8 channels) one-shot conversion takes ~600 microsec for a single group using StartGroup() &amp;amp; ReadGroup() Apis and this is causing timing delays for the 1ms App scheduler.&amp;nbsp;&lt;BR /&gt;What could be the reason for this timing behaviour?&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;2. When I changed the config to Continuous mode , the time delay was ~120ms for getting the expected ADC value increased compared&amp;nbsp;to one-shot where it took less than 50msec, is this expected behaviour.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;3.After analyzing the timing for the internal ADC functions , it was found that the Adc_Ipw_ConfigurePdbConversion(), ADC_Ip&lt;/SPAN&gt;&lt;I&gt;_&lt;/I&gt;&lt;SPAN&gt;ConfigChannel() is taking 130 us, 120 us which causes overall timing delay.&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 08 Aug 2024 10:46:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/ADC-Conversion-timing-issue/m-p/1928219#M39111</guid>
      <dc:creator>S32k1</dc:creator>
      <dc:date>2024-08-08T10:46:25Z</dc:date>
    </item>
  </channel>
</rss>

