<?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: Bug Report - CADC Peripheral Configuration in MCUXpresso Config Tools</title>
    <link>https://community.nxp.com/t5/MCUXpresso-Config-Tools/Bug-Report-CADC-Peripheral-Configuration/m-p/1083898#M1040</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Patrick,&lt;/P&gt;&lt;P&gt;Yes, you are right. They are typo. These error are not new in SDK2.8 only. They are inherited from SDK2.2. I'll report them to software team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Jul 2020 07:25:23 GMT</pubDate>
    <dc:creator>jingpan</dc:creator>
    <dc:date>2020-07-27T07:25:23Z</dc:date>
    <item>
      <title>Bug Report - CADC Peripheral Configuration</title>
      <link>https://community.nxp.com/t5/MCUXpresso-Config-Tools/Bug-Report-CADC-Peripheral-Configuration/m-p/1083897#M1039</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Project is for the KV46 device.&amp;nbsp; SDK version 2.8.0 (366 2020-07-21).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Two typos found...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;There appears to be a typo in the fsl_cadc.h file for the zero crossing enumerations.&amp;nbsp; The 'Crossing" is misspelled as "Corssing" (lines 125 through 128).&amp;nbsp; This causes an error in the generated code when it populates the sample configuration structure in peripherals.c&amp;nbsp; In the auto-generated peripherals.c, the correct spelling is used (i.e. kCADC_Zero&lt;STRONG&gt;Crossing&lt;/STRONG&gt;Disabled).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;typedef enum _cadc_zero_crossing_mode&lt;BR /&gt;{&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; kCADC_Zero&lt;STRONG&gt;Corssing&lt;/STRONG&gt;Disabled&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 0U, /*!&amp;lt; Zero Crossing disabled. */&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; kCADC_Zero&lt;STRONG&gt;Corssing&lt;/STRONG&gt;ForPtoNSign&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 1U, /*!&amp;lt; Zero Crossing enabled for positive to negative sign change. */&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; kCADC_Zero&lt;STRONG&gt;Corssing&lt;/STRONG&gt;ForNtoPSign&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 2U, /*!&amp;lt; Zero Crossing enabled for negative to positive sign change. */&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; kCADC_Zero&lt;STRONG&gt;Corssing&lt;/STRONG&gt;ForAnySignChanged = 3U, /*!&amp;lt; Zero Crossing enabled for any sign change. */&lt;BR /&gt;} cadc_zero_crossing_mode_t;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;There appears to be a typo in the fsl_cadc.h file for the cadc_config_t typdef structure.&amp;nbsp; The 'DMATriggerSource" element is misspelled as "DMATriggerSoruce" (line 148).&amp;nbsp; This causes an error in the generated code when it populates the ADC configuration structure in peripherals.c&amp;nbsp; In the auto-generated peripherals.c, the correct spelling is used (i.e. .DMATrigger&lt;STRONG&gt;Source&lt;/STRONG&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This typo also exists in fsl_cadc.c on line 153 and line 187.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;typedef struct _cadc_config&lt;BR /&gt;{&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; cadc_dual_converter_scan_mode_t dualConverterScanMode; /*!&amp;lt; Dual converter's scan mode. */&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; bool enableSimultaneousMode;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /*!&amp;lt; Using Simultaneous mode. */&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; cadc_dma_trigger_source_t DMATrigger&lt;STRONG&gt;Soruce&lt;/STRONG&gt;;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /*!&amp;lt; DMA trigger source. */&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; cadc_idle_work_mode_t idleWorkMode;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /*!&amp;lt; Converter's work mode when in idle. */&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; uint16_t powerUpDelay; /*!&amp;lt; Delay clock count to wait for the clock is stable. Available range is 0-63.*/&lt;BR /&gt;} cadc_config_t;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jul 2020 22:50:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-Config-Tools/Bug-Report-CADC-Peripheral-Configuration/m-p/1083897#M1039</guid>
      <dc:creator>Kirilian</dc:creator>
      <dc:date>2020-07-23T22:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: Bug Report - CADC Peripheral Configuration</title>
      <link>https://community.nxp.com/t5/MCUXpresso-Config-Tools/Bug-Report-CADC-Peripheral-Configuration/m-p/1083898#M1040</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Patrick,&lt;/P&gt;&lt;P&gt;Yes, you are right. They are typo. These error are not new in SDK2.8 only. They are inherited from SDK2.2. I'll report them to software team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2020 07:25:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-Config-Tools/Bug-Report-CADC-Peripheral-Configuration/m-p/1083898#M1040</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2020-07-27T07:25:23Z</dc:date>
    </item>
  </channel>
</rss>

