| ??? 01/25/05 18:00 Read: times Msg Score: -1 -1 Answer is Wrong |
#85772 - Re: Responding to: ???'s previous message |
Hi Sun,
Just as Jan pointed out, your code seems to run away. In the 8051 UART when you send your data, there you check the interrupt to check if the data has been sent or not. The transmit interrupt merely means that the data was sent. It doesn't mean that the data was received by the peer. So your first data is always received. What you should do is you should design an Acknowledgement mechanism to send a stream of data. Send a data byte, and then wait for an Ack, once you receive this Ack then send the next byte. It shouldn't be much trouble in designing such mechanism. And I don't think you need parity etc. It will just complicate the problem for now... Once the simple thing starts working then you can work on the parity issue. hope this helps. -Ashish |
| 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 |