This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Embedded C v/s C

I wouls like to know the difference between Embedded C & conventional C languages.

Parents
  • It's not about the language - it's about how you apply the language!

    "Embedded" covers a huge spectrum of systems from the tiniest 4-bitter to "embedded" PCs - so clearly there is no clear-and-simple distinction between "embedded" and "non" embedded!

    Typically, when people think of "embedded" systems in a context like this one, they're thinking of (relatively) small, microcontroller systems running on dedicated hardware specifically designed for a single task.

    Thus typical distinguishing features of "embedded" systems tend to be:

    * (relatively) resource constrained;

    * primarily concerned with interacting with hardware, rather than human users;

    * because there is no human user, has to be "autonomous"; eg, can't just display an "OK/Retry/Ignore" message if a problem occurs...!

    * the application starts when the system starts, and never ends until the system stops - there is no user to "run" the application, it does not "finish", and there is nothing to "return" to if it were to "finish".

Reply
  • It's not about the language - it's about how you apply the language!

    "Embedded" covers a huge spectrum of systems from the tiniest 4-bitter to "embedded" PCs - so clearly there is no clear-and-simple distinction between "embedded" and "non" embedded!

    Typically, when people think of "embedded" systems in a context like this one, they're thinking of (relatively) small, microcontroller systems running on dedicated hardware specifically designed for a single task.

    Thus typical distinguishing features of "embedded" systems tend to be:

    * (relatively) resource constrained;

    * primarily concerned with interacting with hardware, rather than human users;

    * because there is no human user, has to be "autonomous"; eg, can't just display an "OK/Retry/Ignore" message if a problem occurs...!

    * the application starts when the system starts, and never ends until the system stops - there is no user to "run" the application, it does not "finish", and there is nothing to "return" to if it were to "finish".

Children