Actions
Forum Thread Details
  • Replies 9 replies
  • Subscribers 472 subscribers
  • Views 797 views
  • Users 0 members are here
Related

The absolute question ... Where to start??

Former Member

Hi guys,

 

I recently discovered this website and seems pretty cool. I see people with a lot of experience with embedded systems.

As a begineer, in my career and with embedded systems i want to ask you some questions:

First, i finished the studies of an electrical engineering university, i work as a software developer mostly for industrial applications : programming PLCs (until now only small ones), intelligent modems(C/C++ over OpenAT OS), building scada applications.

 

I don't know if programming PLCs and modems means programming for embedded devices (maybe someone more experienced can clear this out), they are in essence for a one task, but when i hear about embedded i think more at microcontrollers and low level programming.

 

So...i picked up some 16F PICs, i learned a little the arhitecture, built some hello world applications, flashing leds, using ext port interrupts, etc - all these in ASM.

 

Is these the path to a embedded system developer, or should i advance to a better microcontroller, C programming?

What should i read to optimize my work?

Have any good books or trainings that can you recommend?

Where can i read about latest technologies, IDEs, etc?

My goal is to achieve a level when i trully can understand what a embedded OS is all about, what requierments are for designing one (software & hardware), etc.

 

Is this the right path? should i try to find anoher job more towards small processors ?

 

Any sugestion can help.

 

Thank you in advice!

Parents

  • This is an interesting thread. Now that you've heard from the experienced folks, I'll provide a point of view from some one not so experienced. To give you an idea of my background, at this time I am a corporate software developer. This means that I write software that takes inventories, invoices, places orders and other important processes for companies.

     

    This was not always so. At one tme I was involved with hardware and systems programming. Given the unstable job market I thought that it was time to return to these roots and play catch up with hardware, specifically embedded systems.

     

    I acquired several development boards. At this time I have an Arduino (who doesn't?), a TI LaunchPad (totally love this!), an AVR MCU based controller board (non commercial), a FreeScale i.MX53 and a Chumby (full product.

     

    Note that I decided to skip over the PIC altogether. While I believe that this technology has its applications and merits, I perceived that other technologies were a better starting point. I see AVR chips as more capable, likewise with the TI LaunchPad (MSP430).

     

    I went ahead with the Chumby and the i.MX53 because the former uses embedded Linux and is in itself a development system. The latter supports Android. I believe that it is important to know these two OSes and be able to produce software for embedded systems that use them. I perceive that Android will become an importart OS for embedded systems.

     

    The Arduino has the advantage of a large user base, painless (well almost) entry into embedded systems and has a large choice of "Shields" which are compatible expansion cards. Since it is based on an AVR MCU, I can use the recommended development system or migrate to something more advanced as another poster mentions. The wide  range of available shields let me concentrate on designing software that will interact with the environment, plus also having hardware information on how the shield works. The downside is that the Arduino is perceived as a platform for "non-programmers" and the development environment around it is more of a "toy" than a serious tool to be used by embedded systems engineers and industry. Still.the fact that uses an AVR opens many possibilities that can be exploited by a more technical crowd :-).

     

    My plan, as far as languages, is to learn assembly and C for the above mentioned platforms without neglecting other possible languages that may be available for the platform. Best regards, Salvador

Reply

  • This is an interesting thread. Now that you've heard from the experienced folks, I'll provide a point of view from some one not so experienced. To give you an idea of my background, at this time I am a corporate software developer. This means that I write software that takes inventories, invoices, places orders and other important processes for companies.

     

    This was not always so. At one tme I was involved with hardware and systems programming. Given the unstable job market I thought that it was time to return to these roots and play catch up with hardware, specifically embedded systems.

     

    I acquired several development boards. At this time I have an Arduino (who doesn't?), a TI LaunchPad (totally love this!), an AVR MCU based controller board (non commercial), a FreeScale i.MX53 and a Chumby (full product.

     

    Note that I decided to skip over the PIC altogether. While I believe that this technology has its applications and merits, I perceived that other technologies were a better starting point. I see AVR chips as more capable, likewise with the TI LaunchPad (MSP430).

     

    I went ahead with the Chumby and the i.MX53 because the former uses embedded Linux and is in itself a development system. The latter supports Android. I believe that it is important to know these two OSes and be able to produce software for embedded systems that use them. I perceive that Android will become an importart OS for embedded systems.

     

    The Arduino has the advantage of a large user base, painless (well almost) entry into embedded systems and has a large choice of "Shields" which are compatible expansion cards. Since it is based on an AVR MCU, I can use the recommended development system or migrate to something more advanced as another poster mentions. The wide  range of available shields let me concentrate on designing software that will interact with the environment, plus also having hardware information on how the shield works. The downside is that the Arduino is perceived as a platform for "non-programmers" and the development environment around it is more of a "toy" than a serious tool to be used by embedded systems engineers and industry. Still.the fact that uses an AVR opens many possibilities that can be exploited by a more technical crowd :-).

     

    My plan, as far as languages, is to learn assembly and C for the above mentioned platforms without neglecting other possible languages that may be available for the platform. Best regards, Salvador

Children
No Data