Dear support team,
The release notes of Mouse Reference Design say, that "Key scanning has been replaced by GPIOn_IRQ interrupts with software filtering". What was the reason for doing this?
At the moment I see 3 ways to do debouncing of a button:
1. Decouncing in Wakeup IRQ driver, which can be enabled in wkupct_enable_irq()
2. Debouncing in GPIO driver, which can be enabled in GPIO_EnableIRQ()
3.软件decouncing(过滤)
Which method would you recommend for deboucing, when having an applications with 3 buttons connected to the DA14580?
Kind regards,
Martin Kelling
Device:
Hi mkelling,
The reason for this is that the buttons on a mouse are only 2 or 3, there is no need for key scanning. The software debouncing might be the best way to debounce your buttons.
Thanks MT_dialog