<?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: How to enable GPIOs which are DISABLED after reset in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853649#M51252</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark, thanks for your time and response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried uTasker as you suggested, but I couldn't manage to make it compile, it had too many things to adjust and modify, so I started again from the very beginning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, "haste is a waste", cause is I did not pay attention to schematic drawings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Victor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Apr 2019 08:01:03 GMT</pubDate>
    <dc:creator>VictorLorenzo</dc:creator>
    <dc:date>2019-04-01T08:01:03Z</dc:date>
    <item>
      <title>How to enable GPIOs which are DISABLED after reset</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853647#M51250</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm creating a project with the MKE04Z64VLD4 microcontroller with MCEXpresso (v10.3.1 [Build 2233]) and its built-in Pins and Clocks tools. I've downloaded the MCUXpresso SDK (2.5.0) from nxp using MCUXpresso SDK Builder.&lt;/P&gt;&lt;P&gt;Problem is I try to use pins 36, 37 (PTC7,PTC6) as GPIO outputs but writing to them has no effect on the pin.&lt;/P&gt;&lt;P&gt;The BOARD_InitPins() function created by the Pins tool includes calls to GPIO_PinInit() for each pin, but calls to GPIO_PinWrite() seem not having effects on the output.&lt;/P&gt;&lt;P&gt;Is there any other step required for using those pins?&lt;/P&gt;&lt;P&gt;Victor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Mar 2019 10:28:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853647#M51250</guid>
      <dc:creator>VictorLorenzo</dc:creator>
      <dc:date>2019-03-26T10:28:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable GPIOs which are DISABLED after reset</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853648#M51251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Victor&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is nothing special to be done (apart from avoiding enabling peripheral functions on pins you want to use as GPIO).&lt;BR /&gt;If you continue to have problems try the uTasker open source project at &lt;A href="https://github.com/uTasker/uTasker-Kinetis" target="test_blank"&gt;https://github.com/uTasker/uTasker-Kinetis&lt;/A&gt; since it supports your device and has chip simulation which increases efficiency over generation tools and guessing whether they are correct or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;Complete Kinetis solutions, training and support:http://www.utasker.com/kinetis.html&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Kinetis KE:&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;- &lt;A href="http://www.utasker.com/kinetis/FRDM-KE02Z.html" target="test_blank"&gt;http://www.utasker.com/kinetis/FRDM-KE02Z.html&lt;/A&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;- &lt;A href="http://www.utasker.com/kinetis/FRDM-KE02Z40M.html" target="test_blank"&gt;http://www.utasker.com/kinetis/FRDM-KE02Z40M.html&lt;/A&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;- &lt;A href="http://www.utasker.com/kinetis/FRDM-KE04Z.html" target="test_blank"&gt;http://www.utasker.com/kinetis/FRDM-KE04Z.html&lt;/A&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;- &lt;A href="http://www.utasker.com/kinetis/FRDM-KE06Z.html" target="test_blank"&gt;http://www.utasker.com/kinetis/FRDM-KE06Z.html&lt;/A&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;- &lt;A href="http://www.utasker.com/kinetis/FRDM-KE15Z.html" target="test_blank"&gt;http://www.utasker.com/kinetis/FRDM-KE15Z.html&lt;/A&gt;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Mar 2019 14:56:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853648#M51251</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2019-03-26T14:56:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable GPIOs which are DISABLED after reset</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853649#M51252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark, thanks for your time and response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried uTasker as you suggested, but I couldn't manage to make it compile, it had too many things to adjust and modify, so I started again from the very beginning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, "haste is a waste", cause is I did not pay attention to schematic drawings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Victor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Apr 2019 08:01:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853649#M51252</guid>
      <dc:creator>VictorLorenzo</dc:creator>
      <dc:date>2019-04-01T08:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable GPIOs which are DISABLED after reset</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853650#M51253</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Victor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you verify if your program includes the BOARD_InitDebugConsole(); in the main.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know,&lt;/P&gt;&lt;P&gt;Sabina&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2019 18:19:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853650#M51253</guid>
      <dc:creator>Sabina_Bruce</dc:creator>
      <dc:date>2019-04-04T18:19:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable GPIOs which are DISABLED after reset</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853651#M51254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sabina,&lt;/P&gt;&lt;P&gt;No need to check BOARD_InitDebugConsole(). The answer was in my previous response.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 12 Apr 2020 19:02:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-enable-GPIOs-which-are-DISABLED-after-reset/m-p/853651#M51254</guid>
      <dc:creator>VictorLorenzo</dc:creator>
      <dc:date>2020-04-12T19:02:13Z</dc:date>
    </item>
  </channel>
</rss>

