Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
Verification 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.
The Cadence Academic Network helps build strong relationships between academia and industry, and promotes the proliferation of leading-edge technologies and methodologies at universities renowned for their engineering and design excellence.
Participate in CDNLive
A huge knowledge exchange platform for academia to network with industry. We are looking for academic speakers to talk about their research to the industry attendees at the Academic Track at CDNLive EMEA and Silicon Valley.
Come & Meet Us @ Events
A huge knowledge exchange platform for academia. We are looking for academic speakers to talk about their research to industry attendees.
Americas University Software Program
Join the 250+ qualified Americas member universities who have already incorporated Cadence EDA software into their classrooms and academic research projects.
EMEA University Software Program
In EMEA, Cadence works with EUROPRACTICE to ensure cost-effective availability of our extensive electronic design automation (EDA) tools for non-commercial activities.
Apply Now For Jobs
If you are a recent college graduate or a student looking for internship. Visit our exclusive job search page for interns and recent college graduate jobs.
Cadence is a Great Place to do great work
Learn more about our internship program and visit our careers page to do meaningful work and make a great impact.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
Overview All Courses Asia Pacific EMEANorth America
Instructor-led training [ILT] are live classes that are offered in our state-of-the-art classrooms at our worldwide training centers, at your site, or as a Virtual classroom.
Online Training is delivered over the web to let you proceed at your own pace, anytime and anywhere.
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.
Get email delivery of the Cadence blog featured here
One of the great benefits of working with simulation (RTL, SystemC, or any Virtual Platform) is the ability to provide non-intrusive interactive software debugging. Interactive software debugging provides the control and data access needed to inspect the state of the hardware and software in a running system. Because everything is simulated, it is easy to read and write memory without any actual simulation. This is in contrast to working with hardware. With hardware there is usually no way to peek into memory without stopping the CPU and performing instructions to read memory or use JTAG sequences to insert instructions into the CPU pipeline to access memory. In summary, working with real hardware results in an intrusive debugging environment where debugging results in extra system activity that would not be there if debugging were not being done. In the simulated world, debugging activity can be non-intrusive because the simulation can be stopped and a debugging tool can directly inspect the values in memory without any simulation occurring.
One thing that should be obvious, but should be reviewed, is that software debugging is memory intensive, mostly memory read intensive. The primary operation performed by a software debugger is reading memory and CPU registers. Scrolling the debugger’s memory window or source code window requires large quantities of memory data. It's also important to review that there are two kinds of memory accesses that occur:
Software debuggers read both CPU registers and memory data to display the current context of the software. Many debugger commands require access to memory to display useful information. The debugger can even change the program or data values to change software and system behavior.
In an RTL simulation environment tools can use backdoor accesses to memory for debug reads and writes, but the memory map of the design must be specified or declared somehow. Different tools have different ways to do it, but generally the flow consists of specifying a range of addresses as seen by the software running on the CPU (a memory map) and linking this set of addresses to the memory models in the design.
data_bus_width 32byte_order littleendianname TBplatform.uPlatform.uProcSubSys.uIRAM.addr 0x40010000start_bit 0last_bit 31
With SystemC TLM-2.0 provisions were made for separating debug accesses from regular memory accesses. The debug transport interface can be used to provide backdoor memory reads and writes to be done with no simulation. Or as the TLM-2.0 specification says, "the debug interface is for debug access free of the delays or side-effects associated with regular transactions".
To date, it has been my general assumption that non-intrusive debugging is best and intrusive debugging is usually better than nothing, but less desirable. Recently, I heard an engineer explain that he preferred intrusive debugging, even in a simulation environment. I'm not sure why running simulation with bus traffic to satisfy debug memory reads and writes would be better, but I agree that if backdoor accesses cannot be used then running simulation is a must to retrieve the memory data. To me this would be a last resort if the memory map is too complex to describe. Furthermore, this engineer made a case for intrusive debugging because it makes sure the design doesn't use any techniques that have strange side-effects such as register bits that automatically clear after the register is read (although stumbling upon such a register during debugging is probably not a good idea either).
In conclusion, the best solution seems to be one that allows backdoor accesses for non-intrusive debugging (like TLM-2.0 does), but still allows the use of simulation cycles to run bus transactions in cases where backdoor access is not practical or is not implemented. Any comments on intrusive vs. non-intrusive debugging are welcome.
As I pondered this topic it occurred to me that the only reason such a discussion exists is because there is no single debugging tool that understands the hardware AND software. For example, SimVision understands very well a hardware design running in the Incisive Simulator and can display all hardware values (and memory contents) automatically. A software debugger like gdb knows very well how to display the information about the software as long as it can access register and memory values. You can probably guess that for engineers working across the hardware/software boundary a single debugger that understands both the hardware and software would be an ideal solution compared to trying to operate a hardware debugger and a software debugger, both of which have the ability to start and stop execution. Stay tuned for more information on this topic.
This discussion doesn't cover the other type of debugging, tracing. There are really two ways to debug, interactive and tracing. Tracing can range from something as simple as printf() statements to something more complex like dedicated hardware used to capture instruction traces from a CPU, but tracing vs. interactive debugging is a a topic for another time. Another topic not covered today is using backdoor accesses to run faster by not simulating transactions generated by the software running on the CPU. Again, SystemC TLM-2.0 provides an example with the direct memory interface (DMI), but this is also a good topic for the future. If you cannot wait for future posts you can find additional information in my (somewhat outdated, but still relevant) book, Co-Verification of Hardware and Software for ARM SoC Design.
Good luck with all your debugging.