Sure, the traditional definition of embedded is any sort of computer system that is not a PC/notebook/server in itself but is a computer/comms element built into (embedded) in something else.
Thus the field is an all-others, catch all that includes all sorts of military systems (radars, satellites, signal intelligence, missile guidance, etc.) as well as industrial (machine vision, process control, process automation), medical (various implants or external monitors and pumps including hospital test systems and monitors) automotive (drivetrain and infotianment) and much more.
They are generally similar in that they have more hard requirements in terms of operation at broader temperature and weather conditions, need for longer use life time, rugged conditions, better real time operation (lower latency) and higher safety requirements etc. that traditional PCs.
It's an old term that may need a marketing refresh, but its still a market reality.
Could you kindly explain definitions of embedded processors and of embedded systems
Intel (computing), Freescale (communications), AMD (gaming) - they all offer embedded processors
I am quite lost in definitions used and would appreciate your guidance. Many thanks in advance.
An application using a TI ARM+DSP would never be moved to a 8-core Ivy Bridge targeted for servers. But what about a 17 Watt 4 core Ivy Bridge like that in the Macbook Air coupled with a GPGPU? And a similar Haswell processor will soon be less than 10 Watts.
It is really uncompleted description.
Even today no one produce single DSP but multi-core DSP which typically integrated with ARM devices.
There is also the issue of the prices and specifically price/performance ratio which hardly achieved using Intel Embedded devices.
note for example that TI ARM+DSP multicore based device is only about 10-25 Watt comparing to almost 90 Watt for Ivy-Bridge (8 cores).
Additional advantage is that DSP device are completely SOC (system on chip) which reduced significantly the total price for processing unit.
See HP moonshot project .
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...