Turning towards Embedded

The definition of embedded system has broadened over the years. The initial definition said that an embedded system is anything that is application-specific, but, today, an embedded device like a mobile phone can do much more than just calling—it can play FM radio, click

pictures and so on.

Embedded means Implanting (an idea) within something else so it becomes an essential characteristic of it.

.i.e Processing System embedded into a larger product

for beginners (Read:non EC Engineers) itcan be defined as a Combination of hardware and software to perform a specific function.  

               Embedded systems are becoming more and more complex and so is the skill set of an embedded engineer.Whenever there comes in any additional feature,an embedded system will always be resource-constrained. The challenge to design with limited power, limited processing speed, limited memory and limited input/output (I/O).Embedded engineers always need to optimise what they are doing.

              Here are some suggestions for those who aspire to become an embedded engineer and also for those who are already embedded engineers.

Be an all-rounder

               An embedded engineer needs to be an all-rounder. “He has to know much more than just writing the code. He has to understand the hardware, how it interacts with the environment, how  to use controls, sensors and actuators, and how to integrate all together.

                Today’s education system will  teach you either hardware in Electrical Engineering or software in computer  Engineering. None of  engineering branches  cover embedded  systems completely.  Hence Embedded engineers  need a broader set of educational  qualification. Cross-functional curriculum  for the embedded discipline  tailored to embedded career will be  useful for budding Engineers esp ones in EC domain.

Buy a development board

             It’s said that if a kid can take a thing  apart and then put it back together  such that it still works, he will become an engineer. Engineering  is a lot about self-learning  through experimentation. You need to buy a development board and play with it. Program it, and get one LED to blink. Then program it to blink fast and slow. Learn how to connect it to your computer.

Playing with electronics teaches you a lot. Doing actual stuff is very important. For those who are still confused about buying a Development board, try out some simulators. Proteus is a very good IDE (Integrated Development Environment) to begin with. 

           Lately, open source hardware has become very popular in the hobbyist community. Beagle board, Arduino, Panda board, Raspberry Pi and many such boards help you to create a new project altogether.

A special tip for final year students: Choosing the right set of projects is very important. The project  

you choose should 

be influenced by the 

application domain 

in which you want to 

become an expert.

Work on multiple projects

           You need to have hands-on controllers(atleast a few basic 8-bit controllers like 8051, PIC, AVR etc) You need to take up as many projects as possible to gain expertise in an area. The projects need to be of similar nature or using similar components. It should not be that ultimately you end up being "J

ack of 

all and master of none".

          The projects need to be of similar nature or using similar components. If you become an

expert in that, you certainly have the capability to pick up another domain and become expert in something else.

Produce quality work

           Quality testing is very important. Earlier, there were just a few hundred lines of code and now there are millions of lines of code.

Experience at least three generations of the same product

               Newer technologies are shortening the life-cycle of embedded products. The life-cycle of a technology or product could be up to three years. Take the example of Apple’s iPhone. You will not see anyone buying iPhone of the first generation or even second when the fourth-generation is already in the market. The engineer should see and experience designs of at least three generations of the same product in order to become fairly knowledgeable in that domain.