??? 03/30/06 14:40 Read: times |
#113412 - it's a LPC Responding to: ???'s previous message |
.. which allow you to configure the outputs as Push-Pull and the inputs as either open collector or weak pull-up.
You can do it either way, if you use OC inputs and active high outputs or active low outputs and pull-up inputs. for a non-LPC it still works with active low outputs (pull-ups take care of the other) and pull-up inputs. If you have a longish cable from the keypad to the uC you will want to reinforce the pullup, but if keypad and uC are in close proximity, I see no reason for that. BTW I do NOT use the key interrupt, it does not make debouncing any easier than a straight timing loop, BUT in a battery operated app it is valuable as a wake up interrupt. Erik |
Topic | Author | Date |
Pullups for reading marrix keypads. | 01/01/70 00:00 | |
it's a LPC | 01/01/70 00:00 | |
LPC modes. | 01/01/70 00:00 | |
Excellent point, I have, however, not ha | 01/01/70 00:00 | |
No problems != No Bugs. | 01/01/70 00:00 | |
believinf the data sheet | 01/01/70 00:00 | |
Dry Contact is not a condition. | 01/01/70 00:00 | |
Interface Physics | 01/01/70 00:00 | |
Brilliant analysis | 01/01/70 00:00 | |
5µm is better than 1µm | 01/01/70 00:00 | |
What a shit! | 01/01/70 00:00 | |
Maybe ... | 01/01/70 00:00 | |
Maybe ... | 01/01/70 00:00 | |
Poor Appnotes from Philips. | 01/01/70 00:00 | |
true, but not quite![]() | 01/01/70 00:00 |