MENU
CLOSE
Traditionally all clocks on a chip start at a singular point, and clock architects use a variety of structures, including CTS, H-Tree and meshes, along with sophisticated techniques including staging flops, buffers, cloned gates, etc. to deliver a clock that meets the design’s performance requirements to each flop across the chip.
Clock architects have refined these techniques over the years, but they translate into tradeoffs in performance, power and area (PPA), and something that isn’t fully appreciated - TIME. As SoCs get more complicated, not only do the PPA tradeoffs become more challenging, but the implementation effort takes more and more time as a portion of the overall design cycle.
Aeonic Connect™ is an Intelligent Clock Network™ that fundamentally reimagines how clock topologies are implemented by automatically compensating for divergent clock paths through a novel closed-loop architecture. The Aeonic Connect platform continuously ensures that each flip-flop in a Aeonic domain remains synchronized with the clock source through this closed loop system.
The clock is the heartbeat of silicon design, and one of the most complex networks in an SoC, influencing every aspect of the system from timing closure to peak power demand, and from chip architecture to layout. Designs of all sizes and technology nodes experience SoC-level clock distribution challenges that lead to compromises in tapeout schedules and power challenges.
The Aeonic platform introduces the concept of an Intelligent Clock Network™ that dynamically compensates for on-chip variations (OCV) and propagation delays, lowers power consumption and simplifies timing closure. The platform is in use by an array of applications ranging from ultra-low power edge AI devices to performance-centric cloud datacenter compute and AI offerings.
Stay Connected
Stay Connected
Cookie | Duration | Description |
---|---|---|
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
Cookie | Duration | Description |
---|---|---|
__hssc | session | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hstc | session | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_F75FB76KBW | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_60322432_1 | 1 minute | Set by Google to distinguish users. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
hubspotutk | session | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |