??? 09/15/08 15:03 Modified: 09/15/08 15:10 Read: times |
#158285 - No good news... Responding to: ???'s previous message |
Dilip,
what you observe might be an indication that your project isn't properly designed and is working unreliable, such unreliable, that it works with the one micro, but quits with a nearly identically working one. This is often observed, for instance, when using a board not containing a solid ground plane, etc. Yes, even a change of cable routing to your board can make your device suddenly stop working properly then. So, what you observe need not necessarily have to do with the "migration" to the AT89C52 at all, but can demonstrate, that there's something wrong with your basic design. I have seen this in my career many times. The only escape is to fully analyze the performance of your system by the help of a good scope and many many small test programs. It can mean, that you must redesign the layout, or enhance the filtering or whatsoever. Good luck, Kai |
Topic | Author | Date |
89C51 works but 89C52 does not | 01/01/70 00:00 | |
/EA not connected | 01/01/70 00:00 | |
89c51 works 89c52 does not | 01/01/70 00:00 | |
Why would you conclude that, Erik? | 01/01/70 00:00 | |
More detail, please. Where does the code reside? | 01/01/70 00:00 | |
i faced the same problem...... | 01/01/70 00:00 | |
wong direction | 01/01/70 00:00 | |
Try Other 89C52 Part | 01/01/70 00:00 | |
No good news... | 01/01/70 00:00 | |
wrong spot ... | 01/01/70 00:00 | |
but your problem was with 89c52 | 01/01/70 00:00 |