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
As you might guess we are pretty excited about the Virtual Platform development for the Zynq-7000 EPP.
The FPGA world has changed a lot from 1995 when I was an FAE at Cypress Semiconductor selling and supporting programmable logic devices. This was during the transition from schematic capture to HDLs. It was the days of PALASM and ABEL, and then the first VHDL and Verilog synthesis tools for FPGAs. Back then nobody did much simulation; after all it was a reprogrammable device (except for those anti-fuse FPGAs). How hard could it be?
One of my first jobs after college was for a server company that built a multi-processor server out of Pentium processors and small PLDs. There was some simulation, using Verilog-XL from Cadence, but the primary technique was plug-and-debug. After all, there were a finite number of combinations for each programmable device and programming took only seconds so it was just a matter of putting the right bits into each device and the system would be ready to ship. Since then I'm sure FPGA designs have become more complex and logic simulation is a required step to have any hope of getting systems to work correctly.
What about embedded software?
We currently live at a time when software is easy to change, updates are frequent, and quality is a constant challenge. One would think the combination of reprogrammable hardware and easy to change software would eliminate the need for simulation, but it has not. The introduction of an Extensible Virtual Platform for Zynq is confirmation that fast simulation for embedded software development is alive and well.
Recently, I read Paul Allen's book, Idea Man, and was intrigued to learn how he simulated the 8008 on a main frame and later PDP-10 because he didn't have hardware while he was developing BASIC. It's a great story about he took his code to New Mexico and ran it on the hardware for the first time with great success. Today, the concept is the same, the processor is a bit more complex and BASIC has turned into the Linux kernel for ARM.
A couple of months ago Linux celebrated its 20th birthday. It sounds pretty old, but Linux appears everywhere in products ranging from super computers, to servers, to consumer electronics, to mobile phones. It's likely a large number of Zynq designs will use Linux as an operating system. With its approximately 30,000 files and 10+ million lines of code it a challenge to learn and use it. Xilinx has done a great job to make it easier by providing a customized solution for Zynq, but there is still a lot to learn and a Virtual Platform is a great way to do it.
With the launch of the Zynq Virtual Platform this will be the place to learn about a number of topics related to Virtual Platform development and usage.
Some of the platform creation topics include:
Virtual Platform usage topics related to embedded software will include
One of the great things about Zynq is the Xilinx open source initiative. Almost all of the Virtual Platform projects we normally work on involve proprietary hardware designs which are not released yet and we cannot talk about any details. Zynq is a refreshing change which will greatly broaden the knowledge and usage of Virtual Platforms for simulation.
Here's the 1st Zynq Trivia question. We know that each port of ARM Linux has a unique machine identifier. All of the machines are registered in a Machine Registry.
What is the Zynq Machine ID?
Looking at the data base it could be 3343 or 3378.
Normally the boot loader places the machine ID in register r1 and one of the first steps in booting Linux is to lookup the processor type and the machine type and check that the machine type matches one of the values in the list of supported machines. The unique thing I found for Zynq Linux is that the bootloader is not required to put the right value in the register r1. For some reason it is done automatically by the kernel start-up code. Take a look at the Zynq kernel source tree and find the file arch/arm/kernel/head.S.
There is an instruction there to directly stuff the machine ID into r1. This is different than all other ARM Linux platforms I have constructed. All of the others pretty much hang during the early boot code if the machine id doesn't match the expected machine type (without much clue about why it is stuck) because the bootloader is expected to put the machine ID into r1.
The correct answer is 3343. Putting a breakpoint on start_kernel and looking at r1 will show 0xd0f
Since we saw the code setting the r1 value we can also match it to the define in the file include/generated/mach-types.h
#define MACH_TYPE_XILINX 3343
In conclusion, if you are configuring a boot loader for Zynq to run Linux there is no need to worry about the machine ID, it will all be taken care of for you and will just work, and now you know the machine ID for Zynq.
Thanks to everybody who stopped by the Xilinx booth at ARM Techcon to see the Zynq Virtual Platform demo.