Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I just noticed when I used the fallTime function as described in the OCEAN documentation 6.1.5 - January 2012, it actually returns me the value of the riseTime.
The example in the documentation is pretty clear though :
fallTime( v( "/net8" ) 9 nil 1 nil 10 90 )
Computes the fall time for the waveform representing the voltage of "/net8" from 9 to 1.
It seems to actually compute the rise time on my waveform. If I want the falltime, either I have to swap '9 nil 1' to '1 nil 9' or swap '10 90' to '90 10'
Is that "normal" ?
Thanks a lot,
Which precise subversion are you using? There were some issues with fallTime/riseTime in certain ISRs of IC615.
In reply to Andrew Beckett:
My current subversion is : IC6.1.5-64b.500.9 (64-bit addresses)
Could you tell me a bit more about the issue and in which subversion it was fixed and the best workaround while waiting for an update on my side ?
In reply to The Setlaz:
It was broken in ISR8 - something changed which meant that the order of the arguments was different from what it said (if you specify the high value then the low value, then it should be 10 90 as the first threshold is 10 percent of the way between the high and the low, and the second threshold is 90 percent between the high and the low).
It was fixed in ISR12 (may have been ISR11, but I see an integration notice for ISR12 too). This was as a result of CCR 972729. There's another related CCR because we weren't really happy about the fact that riseTime and fallTime would actually detect the opposite if the arguments were specified the other way around - they are essentially doing the same thing at the end of the day. I believe it's more clearly documented from ISR12 onwards (I didn't check just now as I'm on vacation today and only taking a brief look).
In the affected versions, you could use the attached code. Use:
(the file is password encrypted, and the second argument is the password). Only use this in IC615 ISR8-ISR11, after which it is unnecessary.
Thanks a million for the explanations and the SKILL fix !
Have a great day,