Login

Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.

ARM Community: Trends in Mobile Computing Applications: Part 3 - ARM Community

Jump to content

Trends in Mobile Computing Applications: Part 3

In last week’s blog I discussed how ARM introduced the ACE protocol to address the need for a hardware based cache coherency scheme. ACE enables smartphones, tablets and other mobile computing applications to continue to increase performance while simultaneously reducing power consumption—two big wins. But (and there is a but) there are clear implications associated with adding new, complex hardware functionality to systems that were complex to begin with. This blog identifies the key functional verification challenges associated with ACE-based designs and review the best practices for tackling them.

The Next Challenge: Ensuring ACE Coherency Schemes are Fully Verified
ARM has now delivered the ACE specification. That’s a great start. However, with so many processing elements and memories in today’s SoC’s, how does an engineering team go about verifying cache coherency in an ACE-based design? It’s not realistic for an engineer to simply read the ACE specification and expect to get the design right. They need specialized verification tools, known as Verification IP (VIP), to ensure their cache management scheme is correctly implemented and fully exercised.

The Keys to Verifying ACE-based, Cache Coherent Designs
There are three major capabilities necessary to verify ACE-based designs. They are:
1. Mimicking all possible scenarios to cover the full verification space
2. Ensuring coherency and system compliance with the ACE specification
3. Measuring coverage and ensuring verification completeness.

The remainder of this blog describes what to look for when considering ACE verification solutions and specifically what is required in ACE Verification IP (VIP).

Not Just Any VIP Will Do
Verifying ACE coherency is well beyond the ability of directed testing, the basic verification scheme most designers employ. Directed testing requires that engineers write a specific test for every possible scenario that could occur within the system.

Instead, a verification technique known as constrained random stimulus generation is required. The VIP must “think” through the enormous state space and generate stimuli for the engineer that will yield coverage for all the relevant scenarios. This unburdens the engineer from this humanly impossible task and enables her to focus on the key risk areas exposed by the VIP. With stimulus taken care of, the VIP must also provide a metric driven verification solution which is used to evaluate verification completeness.

The best practices in doing ACE verification are to first use the VIP to ensure that all the individual masters and slaves comply with the ACE specification. Then the VIP must be teamed with a separate interconnect monitor that checks all the traffic on the interconnect fabric. The combination of VIP and interconnect monitoring is necessary to ensure coherency of the full SoC.

Cadence Delivers First Full Solution for ACE Coherency Verification
To help engineers tackle the daunting ACE verification challenge Cadence has added the ACE Verification IP (VIP) to its broad VIP Catalog. The ACE VIP, used in tandem with the Cadence end-to-end interconnect monitor (ICM), designers have the first full solution for ACE coherency verification. The Cadence ACE VIP solution provides the stimulus, checking, and functional coverage reporting and monitoring needed to give designers the confidence that their full SoC design is truly coherent and in compliance with the ACE specification.

Attached Image


This is the result of an extensive collaboration with ARM to ensure the VIP meets with ARM’s standards. Cadence has incorporated ARM’s ACE assertions and coverage points into our regression suite to ensure there is only a single interpretation of the ACE specification. In addition, Cadence has worked with ARM’s leading Cortex-A15 customers to prove out the VIP’s value in advance of the ACE announcement to ensure its readiness for mainstream use.

You can find additional information about ARM’s ACE protocol here. For additional information regarding Cadence ACE verification IP visit the AMBA VIP web page.

Guest Partner Blogger:

Attached Image
Pete Heller is Senior Product Line Manager for Verification IP (VIP) and Interconnect at Cadence and has played a key role in the growth of Cadence's VIP business. Mr. Heller holds both a BA in Computer Science as well as an MBA from Indiana University's Kelley Graduate School of Business.

ARM welcomes its wealth of Partners in the ARM Connected Community (CC) to submit guest blogs to be published on our multiple community blogs. If interested in participating please submit email inquiries to Tell.Us@arm.com.

The ARM Connected Community (CC) is an extensive ecosystem covering all aspects of ARM processor-based design, from chip implementation through to system and device design. The CC provides a platform for collaborative innovation, with multiple types of forums for members to work with one another, and with customers, to solve industry challenges, all with the purpose of enabling designers to focus on differentiating features and an accelerated time-to-market for ARM powered solutions.
All company and product names appearing in the ARM Blogs are trademarks and/or registered trademarks of ARM Limited per ARM’s official trademark list. All other product or service names mentioned herein are the trademarks of their respective owners.

0 Comments On This Entry

Please log in above to add a comment or register for an account