who has tried over clocking the at89c51 in KEIL C? how fast can it go? 10% 20% 100%? post your results.
going to another processor is not possible and i have no time for a big learning curve.
And yet you have time to faff about with overclocking - and all the weird & wonderful effects that can bring...?!
FAFF OFF
"going nowhere fast", and rude...
Ah. I happened to put pepper in the coffe instead of sugar.
Easy solution: get a new cup.
More interesting solution: try to figure out some chemical compound that will neutralize the pepper without affecting the coffe taste.
What is cheaper? Admit that the wrong processor was used and switch?
Ignore the issues and invest lots of time and still fail? And still have to switch processor in the end - but now with lots of extra time wasted trying to work around the bad design decision?
Every step further in the development process increases the costs from errors with a factor ten. So it really is imperative to make a good pre-study based on the requirements and make sure that a suitable processor is selected.
That pre-study should have considered board space + pin count + cost for having enough I/O. Often cheaper with a processor with more I/O than with I/O expansion chips.
That pre-study should have considered guestimated needs for RAM, flash, and computation speed.
That pre-study should have considered the difference between maximum optimization using hand-written assembler. Or a larger (potentially a bit more expensive but possibly not so) processor able to run the same functionality implemented in C.
That pre-study should have considered the implications of debugging using a processor with special debug hardware contra solving everything by guessing, flashing LEDs or printing to serial ports.
That pre-study should have considered availability of chips. Availability of example software (for the specific requirements - like amount of TCP/IP solutions for the specific chip). Availability of application notes. How many TCP/IP application notes did you see for your processor?
That pre-study should have looked for reference customers - other people solving simmilar problems. How many have you been in contact with (or read web pages from) that have implemented TCP/IP or display solutions with your processor?
Onverclocking will only guarantee that you will not be able to know what is a bug in your code, or a bad result from the processor not being trustworthy. That is really something you would love when trying to debug your program.
Actually what you are trying to do is near to impossible on that old 8051. You really should take a good advice and switch architecture. A big learning curve is the best that can happen to you. You are heading towards the wall of failing now.
Hey buddy, did you test it? I also want to know how much you can increment the frequency. Please tell me what you found out.