editor's blog
Subscribe Now

Virtualizer and HAPS Shake Hands

Numerous systems tend to get used for verifying SoCs, and, with software now in the picture, the range is extended even further. We’ve talked before about the use of simulation, virtual prototypes, emulation, and prototyping as ways of getting both hardware and software to work, and to work together. Including their unification.

Synopsys recently took a move towards unification by bringing their Virtualizer virtual platform tool and their HAPS prototyping tool closer together. What this is means is that a design can be implemented with some parts in Virtualizer and some in HAPS and the two systems can talk to each other while running.

They actually run the SCE-MI 2 interface (traditionally found in the emulator-to-host connection), running over their UMRBus. This allows transactors to speed the interchange of data.

The architecture is very AMBA-centric; much of their DesignWare catalog relies on AMBA, and AMBA is popular, so this isn’t a big surprise. They’re open to other busses on an “ask us and we’ll consider it” basis.

The actual use of the tools isn’t so integrated. The two sides have separate programs that you run to manage them – there isn’t one unified interface that can talk to both sides. But this is partly due to the fact that they don’t traditionally see one person doing the whole thing. In the early stages, system integrators/architects would use the Virtualizer side and FPGA guys would implement the HAPS side; they would tag-team to get it up and running. Once that’s all done, then software programmers could use it (using computers more moderate than those required for the FPGA-building tools, for instance). So a single console might not have an associated use case.

The design partitioning process is also manual (although they could see the future possibility of tagging a design to automatically build the virtual and FPGA sides). Cross-triggering between the two sides is rudimentary.

This capability will be generally available in August. Why announce when they did? I’m guessing because they couldn’t talk the DAC guys into rescheduling the conference to August…

You can find more info in their release


Leave a Reply

featured blogs
Jul 17, 2018
In the first installment, I wrote about why I had to visit Japan in 1983, and the semiconductor stuff I did there. Today, it's all the other stuff. Japanese Food When I went on this first trip to Japan, Japanese food was not common in the US (and had been non-existent in...
Jul 16, 2018
Each instance of an Achronix Speedcore eFPGA in your ASIC or SoC design must be configured after the system powers up because Speedcore eFPGAs employ nonvolatile SRAM technology to store the eFPGA'€™s configuration bits. Each Speedcore instance contains its own FPGA configu...
Jul 12, 2018
A single failure of a machine due to heat can bring down an entire assembly line to halt. At the printed circuit board level, we designers need to provide the most robust solutions to keep the wheels...