| ??? 08/03/05 13:53 Read: times |
#98764 - it is always a bad idea to make a port p Responding to: ???'s previous message |
it is always a bad idea to make a port pin part of an operation such as the above.
If the compiler reduces to XOR P1,a you complement the read from the port latch, if it reduces to mov a,P1; xor a,#; mov p1,a; you complement the read of the port pin and you will never know which of these two is done by the compiler Of course, in your case, if you have no outputs connected to p1.3 it will work as coded since the latch and pin is the same in that particular case. Try disconnecting anything connected to p1.3 and then check. Erik |
| Topic | Author | Date |
| 16KHz generation | 01/01/70 00:00 | |
| Code ? | 01/01/70 00:00 | |
| Code & mistake | 01/01/70 00:00 | |
| it is always a bad idea to make a port p | 01/01/70 00:00 | |
| Solved | 01/01/70 00:00 | |
| once bitten, twice shy T2OUT and the PCA | 01/01/70 00:00 | |
Timer2 | 01/01/70 00:00 |