unlike software such as Matlab, embedded software/hardware is much harder to deb
ID: 3820141 • Letter: U
Question
unlike software such as Matlab,embedded software/hardware is much harder to debug. Explain why this is the case (think about using PI + Navio when it is fully embedded in the quadcopter ... i.e. no live connection ).
unlike software such as Matlab,
embedded software/hardware is much harder to debug. Explain why this is the case (think about using PI + Navio when it is fully embedded in the quadcopter ... i.e. no live connection ).
embedded software/hardware is much harder to debug. Explain why this is the case (think about using PI + Navio when it is fully embedded in the quadcopter ... i.e. no live connection ).
Explanation / Answer
Embedded systems are electronically controlled system, where hardware and software are combined. These are computers incorporeted in consumer products or other devices to perform application-specific functions. The end user is usually not even be aware of their existence. Embedded systems can contain a variety of computing devices, such as microcontrollers, application-specific integrated circuits and digital signal processors. Most systems used in a real life as home appliances, air traffic control station, routers ,robotics ,smart cards and cellular phone are example of embedded system.
There is a strong interaction between hardware and software in their failure and diagnosis, as in other aspects of system performance. System failures often involve defects in both hardware and software. Software does not "break" in the traditional sense, however it can perform inappropriately due to faults in the underlying hardware, as well as specification or design flaws in either the hardware or the software. At the same time , the software can be exploited to test for and respond to the presence of faults in the underlying hardware. It is necessary to understand the imprtance of the testing of embedded system, as its functions have been complicated. However the studies related to embedded system test are not adequate.
Test methdologies and test goals differ in the hardware and software domains. Embedded software development uses specialized compilers and development software that offer means for debugging. Developers build application software on more powerful computers and eventually test the application in the target processing environment.
In contrast, hardware testing is concerned mainly with functional verification and self-test after chip is manufactured. Hardware developers use tools to simulate the correct behavior of circuit models. Vendors design chips for self-test, which mainly ensures proper operation of circuit models after their implementation. Test enginners test the integrated systems.
At a higher abstraction level, executable specification languages provide an excellent means to assess embedded system designs. Developers can test system-level prototypes with either formal verification techniques or simulation. A current shortcoming of many approaches is, however , that the transition from tetsing at the system level to esting at the implementation level is largely ad hoc.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.