<?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: KBI OF KINETIS EA in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930560#M54089</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bright&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is generally a difficulty when &lt;EM&gt;more that one key&lt;/EM&gt; (with the KBI) is used due to the fact that if one is in an active state no other can be detected until this first one has been released again.&lt;/P&gt;&lt;P&gt;In my opinion the KBI design is flawed and so is often not usable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is an external interrupt module that has one single interrupts that supports rising/falling and level sensitive interrupts (on only one of a few selectable inputs) which allows 2 interrupt inputs to be flexibly handed (one on KBI and one on IRQ).&lt;/P&gt;&lt;P&gt;Unfortunately the basic KE and KEA series doesn't support the flexible port interrupts that most other parts allow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally I would use an approx. 50ms polling technique for HMI key inputs since this will allow adequate response with little processor overhead and no de-bouncing requirements. The interrupt method is only really necessary for very fast input handling.&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;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;Complete Kinetis solutions for professional needs, training and support:http://www.utasker.com/kinetis.html&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;uTasker: supporting &amp;gt;1'000 registered Kinetis users get products faster and cheaper to market&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Request Free emergency remote desk-top consulting at &lt;A href="http://www.utasker.com/services.html" target="test_blank"&gt;http://www.utasker.com/services.html&lt;/A&gt;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 31 May 2019 11:40:47 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2019-05-31T11:40:47Z</dc:date>
    <item>
      <title>KBI OF KINETIS EA</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930557#M54086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HELLO&lt;/P&gt;&lt;P&gt;HERE'S A PROBLEM WITH KBI MODULE. AS WE KNOW KBI CAN BE SET UP FOR RISING EDGE / FALLING EDGE TRIGGER. BUT IF I USE KBI FOR A SWITCH WITH SETUP OF ACTIVE LOW HOW CAN I KNOW WHEN USER RELEASE THE SWITCH? I MEAN WHEN USER IS PUSHING BUTTON WE CAN THROUGH INTERRUPT FLAG TO CONFIRM THE STATUS BUT CANNOT RECOGNIZE THE RELEASE FROM BUTTON.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE DON'T WANT TO USE A METHOD OF FOR LOOP BY POLLING. IT WASTE THE PERFORMANCE OF CHIP. WE WANT HARDWARE DETECTION LIKE FTM CAPTURE IN.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2019 10:26:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930557#M54086</guid>
      <dc:creator>alighieri</dc:creator>
      <dc:date>2019-05-31T10:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: KBI OF KINETIS EA</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930558#M54087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you have detected the button being pressed reprogram the interrupt to react to rising edge and then you will get a second interrupt when it is released.&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;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2019 10:35:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930558#M54087</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2019-05-31T10:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: KBI OF KINETIS EA</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930559#M54088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HELLO MARK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I Know This But The Problem May Be Using Such A Method Will Result In Unusable Of The Other Pins With KBI Due To Debouncing Time Disturbance. Is That Another Way? We Need To Guarantee Each Time Allow At Least 3 GPIOs (Button) Configured With KBI Mods Are Enough Sensitive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bright&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2019 10:42:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930559#M54088</guid>
      <dc:creator>alighieri</dc:creator>
      <dc:date>2019-05-31T10:42:57Z</dc:date>
    </item>
    <item>
      <title>Re: KBI OF KINETIS EA</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930560#M54089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bright&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is generally a difficulty when &lt;EM&gt;more that one key&lt;/EM&gt; (with the KBI) is used due to the fact that if one is in an active state no other can be detected until this first one has been released again.&lt;/P&gt;&lt;P&gt;In my opinion the KBI design is flawed and so is often not usable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is an external interrupt module that has one single interrupts that supports rising/falling and level sensitive interrupts (on only one of a few selectable inputs) which allows 2 interrupt inputs to be flexibly handed (one on KBI and one on IRQ).&lt;/P&gt;&lt;P&gt;Unfortunately the basic KE and KEA series doesn't support the flexible port interrupts that most other parts allow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally I would use an approx. 50ms polling technique for HMI key inputs since this will allow adequate response with little processor overhead and no de-bouncing requirements. The interrupt method is only really necessary for very fast input handling.&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;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;Complete Kinetis solutions for professional needs, training and support:http://www.utasker.com/kinetis.html&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;uTasker: supporting &amp;gt;1'000 registered Kinetis users get products faster and cheaper to market&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Request Free emergency remote desk-top consulting at &lt;A href="http://www.utasker.com/services.html" target="test_blank"&gt;http://www.utasker.com/services.html&lt;/A&gt;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2019 11:40:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBI-OF-KINETIS-EA/m-p/930560#M54089</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2019-05-31T11:40:47Z</dc:date>
    </item>
  </channel>
</rss>

