Alternative Option for ATMEL AT89S52

Hello...

I have used AT89S52 from Atmel for my project.
I have found defective Micro controller so many times while making another replica of my project.
Kindly let me know whether there are Duplicate manufactures also there with brand name Atmel. If yes, How to detect the original?

Kinldy, let me also know good alternatives for AT89s52 with different brand where we do not require to change the program written in C.

I don't think anyone will try to sell product/part with faking other company name as this may harm them. but component stockists can do anything to keep their margins high. It will be very hard to say which one is fake or true. I would recommend changing component provider.

Secondly, You have to know that all electronic components are ESD sensitive so improper handling can cause failure of the device which could also be one of the reason many of your controller chips are dying. This can happen to any other controller that you will use in future. Use proper ESD wrist strap when handling electronic boards/chips.

If you are thinking to switch from 8051 then try PIC. You have to understand that changing from 8051 to any controller will not be drop in replacement. Neither for hardware nor for code so you will have to make changes to hardware dependent part of your code to make it work, e.g. GPIO, UART.

Thank you Mr. Bhargav.
About AT89S52...
I have made one application i.e. Water Level Sensor Controller. This system has to be ON 24x7.
What I have observed is sometimes this controller goes wrong. It stops working or works abnormally. So I need to Power OFF and Then ON. I want to know why this occurs. and what to do to avoid this.
Need your suggestion on this.

About PIC...
I would appreciate if you can suggest me first pic which I should try.
10 I/O ports are enough for me.

Regards..

If your software is not written properly that means you have not done static analysis of the code properly then you software will crash after operating for some time. Do make sure your stack has enough memory to accommodate the maximum function call depth. Most of the time these crashes are connected to stacks only.