| ??? 01/25/05 08:50 Read: times |
#85729 - Problem code Responding to: ???'s previous message |
I don't know why you are concerned with parity checking - for the most part 8bits no parity is normally acceptable. This is not your problem at the moment. On the receive side, if your code receives a character other than an 'A' it will sit in a dead loop. Maybe you should have something like: [pre] call inchar cjne a,#'A',badchar setb p2.0 sjmp nextx badchar: clrb p2.0 sjmp nextx [/pre] [pre] NEXTX: setb p1.1 setb p1.3 setb p1.5 setb p1.7 CALL INCHAR NEXT1: CJNE A,#'A',next1 SETB P2.0 JMP nextx [/pre] Also, trying to debug two micros at one time is not a good idea! Get one micro working first, then test the second micro, then try them both otherwise if it doesn't work, how do you know which one is the problem? or it could be both? Use a MAX232 chip so you can hook your PC up the the serial from the 89C51. Use the PC with a terminal program to check the send and receive code individually. This will save you a lot of time. I don't know about this 'false detection' you speak of. False start bit detection is handled by the internals of the uart in the 89c51 - nothing you need to be concerned about. |
| Topic | Author | Date |
| Serial comms problem | 01/01/70 00:00 | |
| TxD pin | 01/01/70 00:00 | |
| Re: | 01/01/70 00:00 | |
| The problem, code (& False Detection??) | 01/01/70 00:00 | |
| Problem code | 01/01/70 00:00 | |
| Your program | 01/01/70 00:00 | |
| Progress!!!!.. But still a small Problem | 01/01/70 00:00 | |
| Progress!!! But still a small problem | 01/01/70 00:00 | |
| clutter | 01/01/70 00:00 | |
| Where TI gets initially set... | 01/01/70 00:00 | |
| Code runs away | 01/01/70 00:00 | |
| Re: | 01/01/70 00:00 | |
| wrong answer | 01/01/70 00:00 | |
| Success!!!! Thank you all | 01/01/70 00:00 | |
| I'd never do a thing like that... ;-) | 01/01/70 00:00 | |
collegue? | 01/01/70 00:00 |