The use of each type of open source license in an embedded product design imposes a unique set of obligations on the development team that is incorporating this software into their products. Because of this, some embedded computer maintain a list of open source licenses approved for use by their developers. Other companies go further, explicitly listing which specific version of each open source package has been approved for possible incorporation into the company’s embedded computer products.
Ensuring that the development team is aware of – and in compliance with – the obligations associated with each of these open source licenses takes time and effort. Tools that can help to identify and track the underlying licenses that apply and enable license obligations to be met can prove quite valuable when trying to hit aggressive solutions from product development milestones.
refer to: http://embedded-computing.com/articles/the-not-code-quality/
In all, inevitably, the embedded computer types of processors that will succeed in the future will be the SoCs that provide hardware-accelerated functions. It’s the only way that applications will be able to meet their performance-power budgets. In other words, with homogeneous SMP devices, the embedded computer performance gained by increased core count is not scalable. For example, the more cores that share a common bus structure, the more that each core must compete for memory bandwidth. This problem can be alleviated by designing chips that divide cores into clusters, where each cluster can operate autonomously if necessary.
What plans does the EEMBC have to expand its offerings in the future, and how can the industry get involved?
refer to: http://embedded-computing.com/articles/moving-qa-markus-levy-founder-president-eembc/
Also, open source software is not in the public domain and users must adhere to specific rules set forth in individual licenses that may force designers to reveal the source code to proprietary software. Even with these hurdles, open source operating systems are widely used in embedded design. Small footprint is function-handy. An added consideration when selecting an OS is the trade-off between the initial hardware footprint required and the ability to add features when updates become necessary. The OS must be scalable so that users can select just those embedded solutions or features of the software system that they need.
refer to: http://embedded-computing.com/articles/choose-right-embedded-operating-system/
10.2-Inch Display Monitor with VGA, USB Touch Screen and DC 9-32V Input for Car PC and In-Vehicle Application
1. 10.2” 16:9 wide screen
2. 600 nits LED backlight
3. VGA plus 3 video inputs
4. NTSC, PAL, SECAM automatic switch
5. Automatic switch to video input while signal present
6. Automatic dimmer
7. USB resistive touch screen
8. Optional anti-reflection coating
9. Audio input and speaker
10. All-in-One connector
11. IR remote controller
12. DC 9 to 32V power input
13. Automatic power on by VGA input
14. VESA 75 or stand mount