| ??? 08/24/00 22:47 Read: times |
#4696 - RE: 8051 ROM lookup table |
Christian,
The madness continues... I have worked it out so that i get a different hex code for each key. For simplicity sake I have decided to read in 8 bytes for each key press (each keypress will have 8 bytes associated with it). How can I use the hex code generated by the keypress to reference the 8 bytes in ROM code. I can put it together but, I just end up with a lot of code. Here's how I decode the keypad: 8 columns X 10 rows, read in column value multiplied by 10 and added the row value, the last key ends up being 4fh. I figured that I would just have an offset in ROM of 8 bytes for each keypress (sequentially ordered). To read in the first 31 bytes is no problem I multiply the keypress hex value by 8 and use this as my offset in movc a, @a+dptr. On the 32 byte, we have a problem, when multiplied by 8,it exceeds the limit of FFh. Is there any easy way around this, ideally I am looking for the simplest approach possible. Ben |
| Topic | Author | Date |
| 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
| RE: 8051 ROM lookup table | 01/01/70 00:00 | |
RE: 8051 ROM lookup table | 01/01/70 00:00 |



