This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AT89S52 doesn't work as exected.

Hi,

I am working on a small project, for which i have created chip code, which i have tested and it works fine in Keil IDE. But the same when uploaded to chip behaves partly expected or totally unexpected. Some times the chip doesn't reset even done hardware reset.

I have checked it with 3 chips, but no success. My programmer seems fine as it is detecting attached chip and programming chip correctly.

In my project I need serial communication, which is also not working fine. Sometime the MCU skips sending or receiving characters, or doesn't respond to command event after hardware resets.

Could you please suggest me how to resolve this?

Let me know if any further information is required.

Details
AT89S52, USB Programmer, C Programming language,

Regards,

Bhagirath

Parents
  • As the others have noted, If you expect a crude RC reset circuit to work reliably, then you are liable to be disappointed...!

    I totally agree, additionally
    the OP posted
    The reset pin is connected to 8.2k.

    If you expect only a R reset 'circuit' to work at all, then you WILL to be disappointed...!

    is the crysral and burden caps connected with traces of less than 1cm?
    are the chip decoupling caps connected with traces of less than 1cm?

    I couldn't understand your 2nd and 3rd point.
    simple questions, what is it you do not understand?

    Erik

Reply
  • As the others have noted, If you expect a crude RC reset circuit to work reliably, then you are liable to be disappointed...!

    I totally agree, additionally
    the OP posted
    The reset pin is connected to 8.2k.

    If you expect only a R reset 'circuit' to work at all, then you WILL to be disappointed...!

    is the crysral and burden caps connected with traces of less than 1cm?
    are the chip decoupling caps connected with traces of less than 1cm?

    I couldn't understand your 2nd and 3rd point.
    simple questions, what is it you do not understand?

    Erik

Children
  • but they assume familiarity with hardware design terms.

    Unfortuately, the OP has not divulged whether he designed this hardware, or understands hardware at all.

    To the OP: remember that nobody knows anything about you, your backround, your experience, your project, etc, other than what you clearly & explicitly state in your posts.