anil kumar wrote:
-------------------------------
iam not really into hardware,so i dont know much about the circuits.

regards,
anil


The 8051/8052 type microcontrollers, the preferred types for discussion at this particular forum, are used largely in a product classification called the "embedded system". The engineers and aspiring engineers who work in the field of "embedded system" design, development, testing, coding, validation and so forth really needs to have a solid basic understanding of a number of skills in order to be successful. The list of these skills can be made....I will start it here. And I am sure that others can add to it.

1) Understanding of basic DC type electronics including ohms law, calculating power, how resistors work, how capacitors work, familiarity with tranasistors, diodes, FETs and LEDs.

2) The ability to be able to locate data sheets for the parts needed in a design. Locating skills these days focus primarily on internet usage and knowing how to get the most out of Google.

3) The ability to be able to read a component data sheet.

4) A basic understanding of how simpler logic parts function and how to put them into a circuit sucessfully. These days it is getting more and more rare to need basic logic parts in a design, but the experience with it is irreplacable in understanding how things work.

5) The ability of conceive a design for solving a problem. This skill is really important. Aspiring engineers that lack this skill only know how to say "Give to me", "Where do I start", "Please send ASAP". The conception process will often include skills with block diagrams, flow charts, drawing on napkins at restaurants, and carrying around a pocket full of magic marking pens of 5 colors. :-)

6) Skills with schematics, reading them and drawing them. There is an important aspect here too, there is much of a spread here. There are good wonderful schematics and there are horrible lousey schematics.

7) Skills with prototyping and fabricating circuits.

8) Ownership or access to a minimal tool set for debugging embedded circuits. I suggest as a mimimum an analog type of oscilloscope, a digital volt-ohm-meter, test clips and leads, and a logic probe.

9) Ownership or access to a software development and testing tool set and knowlwdge of how to use them.

10) The ability to read a manual. Include in this the software tool manuals and the microcontroller users manual and the instruction set definition manual.

11) You will need skills with programming a microcontroller AT THE ASSEMBLY LANGUAGE LEVEL. This includes the skills to use the basic tools including a PC, an editor, and an assembler. In some cases depending on the tool set there may also be a linker involved. NOTE It is my strong inclination to say that no person getting into the programming of embedded systems should be allowed to by pass this skill. Start here, learn here, and only then can you move on to a high level language like C or BASIC.

12) You will need skills with debugging and solving hardware AND software problems. A pretty schematic will often have marks all over it by the time the first circuit works. Software that looks perfect on the screen in the text editor is often less than perfect when you try to run it on a piece of target hardware. If your the type of person that at the point that the hardware or software does not work right off and you are clueless about how to go about finding the problems then quit right now and find another profession. In close to 30 years in embeded electronics I know that this skill is ESSENTIAL and either you have it or you don't. If you try to pretend that you have the debug and fixing skills when in fact you are indeed clueless you will only cause problems for yourself, those you try to work for and those around you in general. (Beleive me...I have seen and tried to work with university trained engineers that lacked this ability. They are better suited for a career that may still be considered engineering but not in embedded systems work).

13) Skills on PC board artwork creation and in PC board techniques are essential to todays embeeded engineers. Even if you don't make artwork directly it is necessary to understand the process so you can guide the task for the person that does make your artwork. If you do not do this then your design may many times not work.

14) Most of the rest of what it takes to become a seasoned professional comes from... listening... asking intellegent questions... willingness to admit you make mistakes... looking at ready made examples... learning from experience... fixing a problem right away when you become aware of it... willingness to tear up an approach you have started on and starting over,.. and finally being able to learn to look at something and be able to say "this is a good solution" or "this solution has its problems" or "this solution sucks".

15) Finally and most important....the skill of being able to recoginze when a project is done and meets the needs of the original conception. With this comes the need to be able to pat your own self on the back for a job well done becasue many times there will be no acknowlwdgement from anywhere else. It is my firm belief that a significantly important attribute of the successful embedded systems worker is to come to the finished point on each project. If you don;t finish the first it is more than likely that you will also not finish the 2nd 3rd or 4th ones either. Also know when enough is enough. I have seen projects where the engineers worked on them for years and never came to and kind of finalization or closure.....they were frustrated individuals to say the least.



Michael Karas