??? 02/04/07 11:12 Read: times |
#131967 - testing two unknowns Responding to: ???'s previous message |
Why do you try and test two unknown pieces of code? How do you determine where the fault lies? If both pieces of code work - you're home free, but if there is a fault in either or both, it is near impossible to determine where the fault lies. So the question is how do you prove at least one piece of code? I'd start with the transmit fisrt. If you put a MAX232 rs232 ic onto your tx pin and the output of the max232 to the serial port of your PC, you can verify the transmit code. Another method is to use a storage oscilloscope or the sound card of your PC with the appropriate software to convert it to an oscilloscope. Once you've verified the tx code, then move onto the rx code. Have you proven your diagnostic method actually works?? That is being able to output onto P0? Never underestimate the complexity of what you're trying to do - there can be many things apart from the code that can trip you up, so don't think having us look at the code is going to solve your problem. |
Topic | Author | Date |
Bitbanging help needed | 01/01/70 00:00 | |
Because they mistyped $ | 01/01/70 00:00 | |
or use assembler with different syntax | 01/01/70 00:00 | |
Re: Because they mistyped $ | 01/01/70 00:00 | |
That's not what Jan said | 01/01/70 00:00 | |
The bit banging file | 01/01/70 00:00 | |
RE: Bitbanging | 01/01/70 00:00 | |
They are timing loops | 01/01/70 00:00 | |
they used * for a reason | 01/01/70 00:00 | |
RE:Bit banging help | 01/01/70 00:00 | |
Code for bitbanging(Modified) | 01/01/70 00:00 | |
testing two unknowns | 01/01/70 00:00 | |
A hint | 01/01/70 00:00 | |
Another hint | 01/01/70 00:00 | |
Simulate! | 01/01/70 00:00 | |
cross posted![]() | 01/01/70 00:00 |