This week we will discuss the simulator like debugging experience that users of the new HAPS-80 with ProtoCompiler solution get. The new solution includes built-in debug which means that the ProtoCompiler flow incorporates debug and the HAPS-80 hardware has debug capabilities physically built in. The ProtoCompiler flow ensures that the inclusion of debug it mostly seamless to the user and the HAPS-80 built in debug hardware ensures that the advanced capabilities are available without the need to purchase additional hardware.
Over the next couple of weeks I’ll blog with more details on the key capabilities of the newly available HAPS-80 with ProtoCompiler integrated solution.
Introducing HAPS-80 with Fully Integrated ProtoCompiler – Shifting the Market to an Integrated Prototyping Solution
Drum roll please…… Introducing the latest generation FPGA-based prototype, the HAPS-80 with ProtoCompiler solution is now available. Above I’m pictured introducing the new fully integrated solution to a packed room at SNUG in Taiwan. Below I’m staged in front of the physical side of the new solution, the HAPS-80 hardware itself. The unit on the right, the unit on the left sort of behind me is the previous generation the HAPS-70.
Recently I witnessed a user of our HAPS-70 systems touch the system without taking any Electrostatic Discharge, ESD, precautions. While the units are prototypes and it’s expected that they are customized with both off the shelf and custom daughter boards and of course design specific FPGA bit files, you cannot forget ESD precautions. The HAPS-70 systems utilize the Xilinx Virtex-7 2000T FPGA’s which are fabricated in a 28nm process. The smaller the geometry the more susceptible they are to ESD. You must never, never, never handle FPGA-based prototyping hardware without taking ESD precautions.
Posted in Admin and General | Comments Off on Preventing Electrostatic Discharge
Last week I posted some anonymous results from ProtoCompiler for HAPS usage on real customer designs. While I had removed the customer names and replace them with names like, consumer electronics company, which in my opinion could have implied hundreds of different HAPS customers across the globe, the greater powers in Synopsys felt the data was still too close to the customer. I should point out that Synopsys treats customer information with the highest confidentiality and I personally did not think any confidential information was being shared. I pulled the data off my blog. Anyway, this is the first and I hope last time that Synopsys has to step in and censor my blog.
Posted in ASIC Verification, Early Software Development, In-System Software Validation, Man Hours Savings, Performance Optimization, Project management | Comments Off on Customer experiences with ProtoCompiler for HAPS
Above is a picture of HAPS High Speed Time Domain Multiplexing (HAPS HSTSM) being tested across the current HAPS-70 and the new HAPS systems based on Xilinx UltraScale FPGA devices.
A long time ago in a blog since forgotten I talked about the importance of 1:1 mapping between the Xilinx FPGA Super Logic Region, SLR, to IO Bank to Connector. The result of which can be as much as 2X system performance thanks to efficient mapping of the design to the FPGA.
Everybody wants to know how much faster their FPGA-based prototype will run when they migrate to a Xilinx UltraScale VU440 based setup. This blog sets about trying to answer that very question. Sadly there is not a simple equation that can be applied as final system performance is highly design specific. Increase in performance falls into three or so buckets
Posted in UltraScale | Comments Off on Performance boost from Xilinx UltraScale based prototypes
Back in 2011 I had a vision, a vision for how users of both IP and FPGA-Based Prototypes could be more productive. The problems these users faced was not to do with bugs or lack of capabilities in the products but from the fact that the usage crossed between the two products. IP users traditionally are not experienced prototypers and prototypers lacked IP specific knowledge. Of course this was not helped by the fact that the IP did not document it’s prototyping specific needs. For example, the IP is optimized for ASIC deployment and when you prototype it the clocking, reset and rams sometimes need to be modified to fit into a FPGA environment. Another issue is that as it’s ASIC IP not all configurations can be physically supported in FPGA. For example while the IP might support up to 16 IO ports on the prototype you might only be physically implement up to 4.
Posted in DWC IP Prototyping Kits, Early Software Development, HW/SW Integration, In-System Software Validation, IP Validation, Man Hours Savings, Real Time Prototyping | Comments Off on Prototype ready IP for immediate productivity
In this blog I’m going to explain how you can run a multi-FPGA HAPS prototype at up to 100 MHz !!!!!