... is that you insist it's OK to rely on someone else to do your work, your searching, and your thinking for you.

You're correct when you say that everyone needs a little help once in a while, but it's not proper to ask for help before you've done the most basic things yourself. If you want to know how to configure a voltage regulator application, it is reasonable for anyone to expect you've read the datasheets on the various available types of voltage regulators. It's reasonable for people to expect that you know what the basic terms, e.g. line-regulation, load-regulation, etc, mean, and what you input voltage and current will be, what your noise level will be, and what your requirements for, e.g. precision and accuracy of output, load dynamics, tolerable ripple, etc, are.

If you indicate you've not yet laid the groundwork, you should expect a bit of verbal abuse ... because you deserve it!

Likewise, if you want to know how to read a keypad, you should know what sort of MCU you're using, and not just say "8051" or some other generic. If you want help in selecting a chip, you should say so, and not let the responders to your query guess what your likely requirements are. If you don't know your requirements, in terms of volts and microseconds, you've not yet done the most basic work. Analysis has to precede design. If you think otherwise, you will "get what you deserve."

Part and parcel of the "groundwork" is the obligatory Google search of available "prior art" in your specific area of interest. Further, a search of the 8052.COM site should precede any posted query. After all, you're probably not the first one to encounter a given problem. While 8052.COM is difficult to search, thanks to hundreds of insufficiently-specific query titles, you should, at least, take a look. If you don't, you'll waste a lot of time. It's never a waste of YOUR time to do these things, as they're YOUR obligation. If YOU won't do that much, why should anyone help you?

RE