<?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: Using Ceedling with SDK2.3.0 in MCUXpresso General</title>
    <link>https://community.nxp.com/t5/MCUXpresso-General/Using-Ceedling-with-SDK2-3-0/m-p/833328#M1041</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I am not familiar with the ceedling, and never use it before.&lt;/P&gt;&lt;P&gt;&amp;nbsp; But, about the SIM_SOPT2_USBSRC and SIM_SOPT2_PLLFLLSEL&amp;nbsp; error, actually, from IAR, MDK, MCUXPresso IDE, you also can find it is defined in the MK64F12.h.&lt;/P&gt;&lt;P&gt;&amp;nbsp; So, the code should not have the problem, I think it should still in the ceedling side, maybe you can contact with ceedling engineer, let them help you whether you have lost some configuration in that tool. From the nxp side, we highly recommend you to use the official recommended IDE:IAR , MDK, MCUXPresso IDE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wish it helps you!&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Kerry&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 10 Aug 2018 02:37:53 GMT</pubDate>
    <dc:creator>kerryzhou</dc:creator>
    <dc:date>2018-08-10T02:37:53Z</dc:date>
    <item>
      <title>Using Ceedling with SDK2.3.0</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Using-Ceedling-with-SDK2-3-0/m-p/833327#M1040</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to incorporate Ceedling as a unit-testing tool for my K64 project. I am struggling to get the source code to compile with gcc when trying to execute tests with Ceedling.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specifically, I am trying to test a module that makes use of many of the fsl drivers (fsl_pit, fsl_dac, fsl_ftm, etc.). When compiling the driver headers, I get errors regarding many of the custom typedefs and macros that are defined in "MK64F12.h". I am #include-ing the processor header (&lt;SPAN&gt;"MK64F12.h")&amp;nbsp;&lt;/SPAN&gt;in my test_module.c source code, so these typedefs and macros should be defined (and they work fine when I compile the code from MCUXpresso).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a concrete example, here is the first error that I run into when compiling the test_myModule.c from Ceedling:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;In file included from drivers/fsl_common.h:173,&lt;BR /&gt; from drivers/fsl_pit.h:37,&lt;BR /&gt; from src/myModule.c:5:&lt;BR /&gt;drivers/fsl_clock.h:341:25: warning: implicit declaration of function 'SIM_SOPT2_USBSRC' [-Wimplicit-function-declaration]&lt;BR /&gt; kCLOCK_UsbSrcPll0 = SIM_SOPT2_USBSRC(1U) | SIM_SOPT2_PLLFLLSEL(1U), /*!&amp;lt; Use PLL0. */&lt;BR /&gt; ^~~~~~~~~~~~~~~~&lt;BR /&gt;drivers/fsl_clock.h:341:48: warning: implicit declaration of function 'SIM_SOPT2_PLLFLLSEL' [-Wimplicit-function-declaration]&lt;BR /&gt; kCLOCK_UsbSrcPll0 = SIM_SOPT2_USBSRC(1U) | SIM_SOPT2_PLLFLLSEL(1U), /*!&amp;lt; Use PLL0. */&lt;BR /&gt; ^~~~~~~~~~~~~~~~~~~&lt;BR /&gt;drivers/fsl_clock.h:341:5: error: enumerator value for 'kCLOCK_UsbSrcPll0' is not an integer constant&lt;BR /&gt; kCLOCK_UsbSrcPll0 = SIM_SOPT2_USBSRC(1U) | SIM_SOPT2_PLLFLLSEL(1U), /*!&amp;lt; Use PLL0. */&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;SIM_SOPT2_USBSRC and SIM_SOPT2_PLLFLLSEL are both #define'd in "MK64F12.h", so I don't understand what's happening here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Aug 2018 00:21:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Using-Ceedling-with-SDK2-3-0/m-p/833327#M1040</guid>
      <dc:creator>aberger</dc:creator>
      <dc:date>2018-08-09T00:21:06Z</dc:date>
    </item>
    <item>
      <title>Re: Using Ceedling with SDK2.3.0</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Using-Ceedling-with-SDK2-3-0/m-p/833328#M1041</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I am not familiar with the ceedling, and never use it before.&lt;/P&gt;&lt;P&gt;&amp;nbsp; But, about the SIM_SOPT2_USBSRC and SIM_SOPT2_PLLFLLSEL&amp;nbsp; error, actually, from IAR, MDK, MCUXPresso IDE, you also can find it is defined in the MK64F12.h.&lt;/P&gt;&lt;P&gt;&amp;nbsp; So, the code should not have the problem, I think it should still in the ceedling side, maybe you can contact with ceedling engineer, let them help you whether you have lost some configuration in that tool. From the nxp side, we highly recommend you to use the official recommended IDE:IAR , MDK, MCUXPresso IDE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wish it helps you!&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Kerry&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Aug 2018 02:37:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Using-Ceedling-with-SDK2-3-0/m-p/833328#M1041</guid>
      <dc:creator>kerryzhou</dc:creator>
      <dc:date>2018-08-10T02:37:53Z</dc:date>
    </item>
  </channel>
</rss>

