2013年4月29日 星期一

We introduce you a pleasant embedded platform


State of the industry
Wide adoption of several of these key standards has resulted in commercially viable COTS building blocks – hardware and software – that address various functional layers in a network-ready system quickly and cost effectively (Figure 1). This embedded approach is being broadly employed by various industry players, and such platforms have been successfully embedded in networks worldwide. A few critical challenges, however, still remain:

2013年4月16日 星期二

Clouding your mind inception


Industrial pc, Console server, networking appliance



Pentek (www.pentek.com) signal processing products have found embedded computer homes in U.S. Navy Signals Intelligence (SIGINT) systems. Pentek products score high with the Navy acquisition system: reducing development time, and acquisition and maintenance costs. The open architecture standards used in these embedded computer enable easier new technology insertion so that the latest technology is available to key Navy programs.
CES – Creative Electronic Systems (www.ces.ch) develops scalable systems, using COTS principles, with modular functional units. These modules are widely used in commercial, military, and unmanned aerial vehicles for test, simulation, airborne mission, and primary flight computer systems.


refer to: http://vita-technologies.com/articles/embedded-trends-high-flying-design-wins/

2013年4月1日 星期一

Experimental static analysis for embedded system

Industrial pc, Console server, networking appliance
About Embedded System:

Continuous Integration-Time (CI) static analysis
After running integration-time static analysis, software engineers should have a stronger sense of potential systemic problems in the code. The next step is to run CI static analysis to enforce the coding policy outlined in the planning phase. This prevents the types of defects discovered during integration-time analysis.
For every issue discovered in static analysis, there are at least 10 more of the exact same thing in other places in the code. Static analysis is the ideal tool for addressing all violations of the same kind at the same time. This is opposed to chasing every possible path through the code. It’s far better to find the systemic problems in order to create an environment in which bugs cannot survive.
When we talk about static analysis, in many cases we mean anti-pattern analysis. A positive pattern is something that should be in the code. For example, a policy that requires engineers to use a typedef when declaring function pointers is a positive pattern static analysis rule[1]. This is in contrast to a policy that, for example, prohibits the use of the data() member function from a string class when interfacing with the standard C library.
refer to: http://embedded-computing.com/articles/getting-leveraging-right-static-analysis/