acrosser Technology, a world-leading In-Vehicle Computer designer and manufacturer, is pleased to introduce its latest In-Vehicle computer product, the AIV-HM76V0FL. The AIV-HM76V0FL is built for handling rugged environments. To showcase its high performance, we have created a small experiment to prove its durability in difficult situations.
One fascinating feature of AIV-HM76V0FL is its ability to support HDMI video output. This outstanding feature would satisfy those seeking for high-quality video outputs. AIV-HM76V0FL is an outstanding In-Vehicle solution for anything ranging from commercial to security issues. We have seen our clients using them on digital signage display and security IP surveillance cameras. The two key factors that allow for such high-performance graphic processing are the Intel HM76 mobile chipset and FCPGA 988 socket for 3rd generation Core i mobile computer platform.
Acrosser’s latest In-Vehicle computer product, AIV-HM76V0FL should meerit a spot on your procurement list. This product can sustain a level 2G shock and received IEC 60068-2-64 (anti-vibration) and IEC 60068-2-27 (anti-shock) certifications.
Here is the actual video demonstrating the outstanding performance of the AIV-HM76V0FL. The base vibrator simulates a mobile environment, and this is exactly how it looks like inside a moving vehicle.
AIV-HM76V0FL Features
‧ FCPGA 988 socket support Intel 3rd Generation Core i7/i5/i3 and Celeron processors
up to 45W i7-3720QM
‧ Fanless thermal design and anti-vibration industrial design
‧ HDMI/DVI/VGA video outputs
‧ Combo connector for Acrosser’s In-Vehicle monitor
An upcoming industry-standard specification that defines an interoperable mechanism for reliable, point-to-point HD video transmission between two Wi-Fi-enabled devices is expected from the in-vehicle in the second half of 2012. Although video over Wi-Fi applications have been available for quite some time, this is the industry’s first attempt to develop an interoperability specification for video distribution.
refer to: http://embedded-computing.com/articles/wireless-accelerate-
next-wave-in-vehicle-innovation/
Wind River, QNX and SDC Systems will be just a few of the vendors of embedded software that will be exhibiting and presenting at The UK Device Developers’ Conference. Delegates will get the chance to have informal embedded computer discussions with industry experts in this field and explore the very latest technologies for future projects. The UK Device Developers’ Conference is a one-day Embedded Computer conference for developers of intelligent systems and devices, taking place in Bristol (14th May), Cambridge (16th May) and Manchester (22nd May). The conference will offer engineers and embedded computing professionals a packed agenda of technical workshops, presentations and a embedded computer exhibition.
Testing and netwoking play a vital role in embedded product development. Traceability rendered via Application Life-cycle Management (ALM) software enables the team to automatically generate test cases that link back to requirements, and report defects that link back to test cases. By knowing that defects are addressed and test cases run successfully, the team can have an immediate and accurate accounting of the state of networking product requirements.
When it comes to software development, the old adage is best spun in a slightly different way: better “early” than never. Accordingly, static analysis can help those developing in Java to stay one step ahead of potential coding problems.
Today’s software development teams are under immense pressure; the market demands high-quality, secure releases at a constantly increasing pace while security threats become more and more sophisticated. Considering the high cost of product failures and security breaches, it is more important than ever to address these risks throughout the software development process. Potential problems need to be spotted early to prevent release delays or, worse, post-release failures.Fortunately, there are numerous tools to help developers manage these risks, helping to identify potential problems early in the development phase when issues are less disruptive and easier to fix. They are readily accessible to developers and easy to use within many development environments. This applies to developers programming in any language; however, we focus on Java in this discussion (see Sidebar 1).
Sidebar 1: Though Java’s mature ecosystem, numerous IDEs, and abundance of reference materials ease Java application development, they can also bestow a false sense of security upon developers, who should be watchful to mitigate Java’s weaknesses.
Static analysis helps mitigate risk
When considering static analysis tools for Java or otherwise, it is important to understand what these tools are. The term “static analysis” refers to the approach of analyzing a program without executing it. As we’ll see in the next section, static analysis tools can be used to produce reports on anything from coding standard violations to specific errors or vulnerabilities. Simply put, static analysis tools analyze source code to find information useful for managing risk.
One benefit of static analysis is that it can be performed early in the development cycle, often before the application will even execute. It is commonly integrated into an automated build, so that there is virtually no overhead to running frequent analyses. By integrating static analysis into the inner development loop, users maximize the value they get from such tools.
When used in conjunction with a well-designed development process, static analysis tools provide crucial visibility into the state of the software. This enables development teams to understand the level of risk in their code and where the risk resides so they can take action to mitigate or remove it entirely (Table 1). Individual tools generally focus on specific problems faced by software development teams, and teams often use a combination of these tools to get a comprehensive view of their development effort.
Table 1: Static analysis tools typically find specific types of issues, with each type representing a different class of risk and requiring a different type of action.
Developers have traditionally used static analysis tools via a simple IDE integration or as stand-alone tools. While the tools add significant value to the development effort, the proliferation of tools has created efficiency problems as developers spend more and more time using and maintaining different tools and sifting through more and more results. To wisely manage development resources, teams must be able to effectively manage, filter, and prioritize all those issues.
To address these problems, development testing platforms have emerged to unify and manage all of this static analysis information in one place, simplifying the user experience and increasing visibility and efficiency at larger scales while providing relevant access controls and reporting. Development testing platforms are even starting to blur the line between static analysis and other types of analysis by utilizing – during the static analysis process – artifacts generated during earlier program runs. For example, these platforms can use code coverage information from test runs during static analysis to effectively identify missing test cases automatically. The traditional approach to this problem requires significant manual effort based on simple coverage thresholds. By leveraging data from different sources, these platforms are able to significantly reduce the manual effort and time required to accomplish this with other methods.
Selecting static analysis tools for Java
The most popular, free, static analysis tools for Java are probably Checkstyle, PMD, and FindBugs. While they all fall under the “static analysis” umbrella, their strengths are so sufficiently different that many consider the tools to be complementary rather than alternatives.
Checkstyle
Checkstyle is billed as “a development tool to help programmers write Java code that adheres to a coding standard[1],” although it does not strictly limit itself to coding standard enforcement. It provides a documented API for users to define their own custom checks. Typical coding standards utilize basic rules to make code more readable and reduce the likelihood that future code changes will introduce bugs. Standards tend to define conventions about formatting (white space, bracketing, naming, commenting, and so on), inheritance, and visibility. When adequately enforced, well-designed coding standards can help developers reduce risk. Enforcement can be difficult, though, since coding standards generate a lot of violations and there can be significant pressure to ignore noisy rules. With legacy code, this can make enforcing new coding standards unfeasible. While most of the issues identified by Checkstyle do not affect code correctness, robustness, or performance, there is real value in helping developers quickly understand code written by others. It is not always obvious how to quantify the risk represented by these violations and it is problematic to measure risk directly from violation counts, but changes in those counts can be a reasonable proxy for changes in risk.
PMD
PMD is described as “…a source code analyzer. It finds unused variables, empty catch blocks, unnecessary object creation, and so forth[2].” It, too, is evolving and the current checks focus mainly on syntactic oddities that might belie developer mistakes, such as overcomplicated expressions, empty blocks, unused variables, parameters, and class members. It also has a popular module to identify duplicated code. Because it is generally reporting “suspicious code” as opposed to specific coding errors or standards violations, the user will need to carefully select the checks enabled for everyday use. Because enforced rules are selected by the user, this tool can be useful for both legacy and greenfield projects, and it is often easy to correlate these counts with risk. Unfortunately, it might not be obvious whether reported issues should be considered defects or maintenance concerns.
FindBugs
FindBugs is probably the most popular of these tools. It looks for actual bugs in the code, as well as suspicious code and standards violations. Because of the wide range of reported issues, it is important to use a configuration that includes the most relevant checks for the project. This is especially true for legacy projects, as it’s easier to keep new projects clean from the beginning. Like PMD, any team can benefit from using FindBugs and associating issue counts to risk can be straightforward.
Commercial static analysis tools show similar diversity, identifying everything from standards violations to actual defects and security vulnerabilities. To illustrate how a commercial tool might compare to a free tool, I analyzed version 1.496 of the Jenkins job management system (www.jenkins-ci.org) using a proprietary static analysis solution and version 2.0.1 of FindBugs, with all checks enabled. On this code base, 852 unique issues were identified – with only 28 issues identified by both products. The proprietary solution found 197 unique issues, with 188 of those coming from high-impact categories (security and concurrency bugs, resource leaks, and unhandled exceptions like null dereferences). FindBugs found 627 unique issues, with 29 coming from those high-impact categories. In short, each of the tools found significant high-impact issues missed by the others, so using a proprietary solution or FindBugs alone will leave significant risk undetected.
Development testing – Tying it all together
Static analysis tools are a powerful ally in the software development effort for Java developers, as these tools enable developers to gain insight into risk throughout the software development life cycle. They are typically easy to automate, enabling users to spend their time fixing problems rather than running the tools.
When it comes to managing risk, more information is generally better – as long as that information illuminates actual sources of risk that developers care about. When deciding which tools to adopt, remember to consider not just the types of issues that analysis tools identify, but how those tools can work together to provide additional value. Also, be sure to configure them appropriately so that the number of issues doesn’t overwhelm your users.
Modern development testing platforms take testing tools to another level by unifying the data in one place, simplifying the user experience, and creating opportunities to provide even more value.
A new All-in-OneGaming Board, the AMB-A55EG1. AMB-A55EG1 features AMD Embedded G-Series T56N 1.65GHz dual-core APU, two DDR3-1333 SO-DIMM, which provides great computing and graphic performance is suitable for casino gaming and amusement applications. It is designed to comply with the most gaming regulations including GLI, BMM, and Comma 6A. AMB-A55EG1 is specifically designed to be a cost competitive solution for the entry-level gaming market.
AMB-A55EG1 utilizes the functions of an X86 platform, 72-pin Gaming I/O interface, intrusion detection and also various security options, and a complete line of Application Programming Interfaces to create smoother gaming development.
For more information on AMB-A55EG1 or any other products, please contact your local acrosser sales channel or logon to our website: www.Acrosser.com
This seems to be the year for milestone events in the EDA industry, though calculations show some of the “anniversary” designations to be premature. Nevertheless, the first big EDA event of the year is the Design and Verification Conference (DVCon), held in San Jose, CA every February. DVCon celebrated its 10th anniversary this year, after a transformation from HDLcon in 2003, which followed the earlier union of theVHDLInternational User’s Forum and InternationalVerilogHDL Conference. Those predecessor conferences trace their origins back 25 years and 20 years, respectively.
After DVCon, EDA marketers quickly turn to preparations for the JuneDesign Automation Conference(DAC), perhaps with a warm-up at Design, Automation, andTestin Europe (DATE) in March. DAC is the big show, however, and this year marks the 50th such event (and its 49th anniversary). Phil Kaufman Award winner Pat Pistilli received the EDA industry’s’ highest honor for his pioneer work in creating DAC, which grew from his amusingly-named Society to Help Avoid Redundant Effort (SHARE) conference in 1964.
Milestones inevitably lead to some reflection, but also provide an opportunity to look forward to what the future will bring. In our 2nd annual EDA Digest Resource Guide, we will be asking EDA companies to share what they see as the biggest challenges facing the industry in the next five years, and how the industry will change to meet those challenges. Will future innovations be able to match the impact of the greatest past developments in EDA, which enabled the advances in electronics that we benefit from today?
AIS touchscreen displays utilize industrial grade components and are encased in steel, aluminum, or aluminum-magnesium alloys for maximum reliability and protection from shock/vibration, Wide Temperature Range Operation and harsh environmental conditions. Add-on enhancements are available such customize the LCD to perfectly fit applications such as sunlight readable touchscreen LCD enhancements, wide voltage range inputs, Anti-corrosion coatings, IP65 Water/Dustproof rating, and Touch screen integration. Several touchscreen technologies are available including resistive, capacitive, infra red (IR), surface acoustic wave (SAW), and gaming 3M MicroTouch™ DST gaming Touch System for Large size screens. Together AIS has thousands of pre-engineered, documented and tested touch screen LCD solutions at cost effective prices.
The European Telemetry Conference, also known as the Garmisch Conference, was held at its usual location in Garmisch, Germany, May 2-5. Traditionally, this conference focuses on aerospace/avionics, car racing, and similar applications. However, most presentations this year pertained to embeddedbiotelemetry. Presentations on biotelemetry embedded applications ranged from observations of birds (worldwide), salmon (in the United States), or cheetah (from Namibia) migrations to a number of human telemetry applications, including remote monitoring of patients in embedded health conditions or patients in telerehabilitation. Other applications included long-term monitoring of intracorporeal (inside the body) implants using embedded inductive powering and other telemetry applications on humans.
Given the increased complexity of processors and applications, the current generation of Operating Systems (OSs) focuses mostly on software integrity while partially neglecting the need to extract maximum performance out of the existing hardware.
Processors perform as well as OSs allow them to. A computing platform, embedded or otherwise, consists of not only physical resources – memory, CPU cores, peripherals, and buses – managed with some success by resource partitioning (virtualization), but also performance resources such as CPU cycles, clock speed, memory and I/O bandwidth, and main/cache memory space. These resources are managed by ancient methods like priority or time slices or not managed at all. As a result, processors are underutilized and consume too much energy, robbing them of their true performance potential.
Most existing management schemes are fragmented. CPU cycles are managed by priorities and temporal isolation, meaning applications that need to finish in a preset amount of time are reserved that time, whether they actually need it or not. Because execution time is not safely predictable due to cache misses, miss speculation, and I/O blocking, the reserved time is typically longer than it needs to be. To ensure that the modem stack in a smartphone receives enough CPU cycles to carry on a call, other applications might be restricted to not run concurrently. This explains why some users of an unnamed brand handset complain that when the phone rings, GPS drops.
