In with kbi when several problems: 1, ke06 kbi interrupt set is only the falling edge trigger and enable after directly into the callback function, with the oscilloscope look at the next, a enable kbi interrupt after the pin have a falling, this is what reason, and then in the callback function set to shake delay, in the main program execution scan button, the main program scanner in the first disability kbi, button scanning completed before enable kbi, the results with the prior to the same, a enable it into the interrupt. 2, set is falling interrupt, occasionally appear a problem: the release button when the rising also triggered kbi interrupt. Appear chance about 10 times have time, with the oscilloscope seen waveform, really is rising after the interrupt. Bigwigs seek solved extremely thanks
Hi 旭余,
To prevent a false interrupt request during keyboard initialization, please refer the "35.5.4 KBI initialization":
Please refer the "11.4 Input glitch filter setting" and enable the Input glitch filter:
There is a KBI example in MCUXpresso SDK, you can test that example.
Best Regards,
Robin
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi,Robin,
Thanks for your reply.I have read the contents of 35.5.4 and configured.And write 1 to KBI1_SC[KBACK] after enabled keyboard interrupt Pin.But still into the interrupt .I looked KBI1_SP register, is 0x000000, so now used to read KBI1_SP register way to determine whether a button Press, but for enable immediately after into the interrupt this point or somewhat scruples, this is normal the phenomenon of it? In official examples of on is such a phenomenon.