??? 09/13/08 22:41 Read: times |
#158252 - Why would you conclude that, Erik? Responding to: ???'s previous message |
First of all, he hasn't stated whether he's using external program memory, so how can you reach the conclusion that he's having the problem in question under those circumstances? Secondly, if he inserts the 89C52 where the 89C51 previously was, in the same circuit, /EA should remain unchanged. According the datasheets, this affects both MCU's in the same way.
I agree, in that, if /EA were to be unconnected, unpredictable effects would result. The /EA signal would, presumably, start out as "low", meaning "use external program memory," then, after a time, would charge up to a "high" level. On the next RESET, the signal would, being in a "high" state now, the /EA signal would tell the MCU to execute its internal code. There's no indication that that's the case, however. Further, if that were the case, he'd experience the same problem with the 89C31 as with the 89C32. I'd guess, having no information to the contrary, the problem lies with the fact that one or both MCU's are from ATMEL. RE |
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 |