| ??? 04/15/10 19:21 Read: times |
#175071 - Debugging Responding to: ???'s previous message |
I have found that if I do not have an emulator, the best thing is to have the code explain what it doesn't like. "Wrong Pass" is OK for the end user, but as you have seen, not good for debugging. For instance, as the code is checking the password, write the desired number and the received number to the display. It can be as simple as "11 22 33 45", where the 4 comparison received 5 instead of 4.
It may be the keypad is following the telephonic convention of sending 0x0A for 0x00, but adding the debug information will give you the answer without guessing. Also if you comment out the debug code, you can restore it in the future if a similar problem crops up. --Rich |
| Topic | Author | Date |
| Problem with succesive memory locations | 01/01/70 00:00 | |
| Debugging | 01/01/70 00:00 | |
| How can i see the code of pressed key | 01/01/70 00:00 | |
| Turn them into ASCII | 01/01/70 00:00 | |
| Or use 2 characters | 01/01/70 00:00 | |
| direct access to >80h => SFR | 01/01/70 00:00 | |
| incorrect addressing method | 01/01/70 00:00 | |
| (back to) basics - "bible" time | 01/01/70 00:00 | |
| Hal Albach's way | 01/01/70 00:00 | |
| It works | 01/01/70 00:00 | |
| You are not showing enough | 01/01/70 00:00 | |
the danger of uniformity | 01/01/70 00:00 |