| ??? 07/20/06 20:57 Read: times |
#120722 - confidence Responding to: ???'s previous message |
Ashwin,
Congratulations to get the code right. I am quite confident you can find the problem now yourself. Please, tell us, how did you find what was wrong. Did the remarks of the members here help you? JW PS. Carefully try to short directly on the chip the pins P1.4-P1.7 to P1.1, so you can rule out or confirm hardware problem with your keyboard. |
| Topic | Author | Date |
| hex key pad code not working | 01/01/70 00:00 | |
| Explanation | 01/01/70 00:00 | |
| what, how | 01/01/70 00:00 | |
| each line of code must be justified | 01/01/70 00:00 | |
| correction made, still not workin | 01/01/70 00:00 | |
| Lookup table | 01/01/70 00:00 | |
| hyperlink | 01/01/70 00:00 | |
| of course not, | 01/01/70 00:00 | |
| shall I spoil the fun? | 01/01/70 00:00 | |
| code workin partially | 01/01/70 00:00 | |
| be specific | 01/01/70 00:00 | |
| specific | 01/01/70 00:00 | |
| check it in the simulator | 01/01/70 00:00 | |
| Use serial port for debugging | 01/01/70 00:00 | |
| confidence | 01/01/70 00:00 | |
| I wouldn't do that | 01/01/70 00:00 | |
| problem with find_num subroutine? | 01/01/70 00:00 | |
| Code presentation | 01/01/70 00:00 | |
| sorry it's 'hyper terminal' | 01/01/70 00:00 | |
| Problem solved | 01/01/70 00:00 | |
| which conclusion, please tell | 01/01/70 00:00 | |
| Problem is NOT solved. | 01/01/70 00:00 | |
| Post the solution please | 01/01/70 00:00 | |
| solution | 01/01/70 00:00 | |
| a 'killer solution' | 01/01/70 00:00 | |
| killer???? | 01/01/70 00:00 | |
you 'eat' the main | 01/01/70 00:00 |