<?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: kdsk - how to access hardware, say GPIO, inside and outside interrupts? in Kinetis Software Development Kit</title>
    <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631073#M6720</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok.&amp;nbsp; So your saying GPIO_WritePinOutput() is reentrant?&amp;nbsp; If yes, seen an documentation confirming this? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Jan 2017 02:19:21 GMT</pubDate>
    <dc:creator>petero</dc:creator>
    <dc:date>2017-01-24T02:19:21Z</dc:date>
    <item>
      <title>kdsk - how to access hardware, say GPIO, inside and outside interrupts?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631071#M6718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class=""&gt;&lt;P&gt;Using ksdk on a Cortex M4. Using kdsk if your accessing hardware from inside and outside interrupts do you need to add disable and enable interrupts around the hardware access in the main thread?&amp;nbsp; see //### below&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Like this:&lt;BR /&gt; void main(void)&lt;BR /&gt; {&lt;BR /&gt;&amp;nbsp; GPIO_PinInit();&amp;nbsp;&amp;nbsp; //init some kdsk hardware&lt;BR /&gt;&amp;nbsp; enableInterruptXYZ();&lt;BR /&gt;&amp;nbsp; while (1)&lt;BR /&gt;&amp;nbsp; {&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; disableInterruptXYZ();&amp;nbsp; //### need this line?&lt;BR /&gt;&amp;nbsp; &amp;nbsp; GPIO_WritePinOutput(); //access some kdsk hardware&lt;BR /&gt;&amp;nbsp; &amp;nbsp; enableInterruptXYZ();&amp;nbsp; //### also need this line?&lt;BR /&gt;&amp;nbsp; &amp;nbsp; //do other stuff&lt;BR /&gt;&amp;nbsp; }&lt;BR /&gt; }&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;InterruptXYZ-Handler()&lt;BR /&gt; {&lt;BR /&gt;GPIO_WritePinOutput(); //access the same kdsk hardware&lt;BR /&gt; }&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2017 02:51:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631071#M6718</guid>
      <dc:creator>petero</dc:creator>
      <dc:date>2017-01-20T02:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: kdsk - how to access hardware, say GPIO, inside and outside interrupts?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631072#M6719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Peter,&lt;/P&gt;&lt;P&gt;I think it is unnecessary to disable interrupt when&amp;nbsp; you want to set or clear a GPIO pins no matter whether the setting/clearing GPIO pin is inside main loop or ISR. when you run the code GPIO_WritePinOutput(); the GPIO pin logic changes immediately.&lt;/P&gt;&lt;P&gt;Hope it can help you&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;XiangJun Rong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jan 2017 02:03:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631072#M6719</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2017-01-24T02:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: kdsk - how to access hardware, say GPIO, inside and outside interrupts?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631073#M6720</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok.&amp;nbsp; So your saying GPIO_WritePinOutput() is reentrant?&amp;nbsp; If yes, seen an documentation confirming this? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jan 2017 02:19:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631073#M6720</guid>
      <dc:creator>petero</dc:creator>
      <dc:date>2017-01-24T02:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: kdsk - how to access hardware, say GPIO, inside and outside interrupts?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631074#M6721</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 think GPIO_WritePinOutput() is reentrant function.&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;xiangjun Rong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jan 2017 02:13:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/kdsk-how-to-access-hardware-say-GPIO-inside-and-outside/m-p/631074#M6721</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2017-01-25T02:13:55Z</dc:date>
    </item>
  </channel>
</rss>

