Subscribe by Email

Your email:

RocketBlog - a discussion about all things related to FPGA verification and debug

Current Articles | RSS Feed RSS Feed

With FPGAs, bigger is better if you have the right design tools

Share on Twitter Twitter | Submit to Digg digg it |  Add to delicious  delicious |  Submit to StumbleUpon StumbleUpon | Submit to Reddit reddit 
This week Xilinx announced the first shipments and availability of its Virtex(R)-6 LX760 device. The FPGA market leader is touting the device as the industry's largest FPGA available and says it's for designers "who need raw logic density and industry-leading I/O performance." It's impressive all right, with 1,200 I/O pins and 25,920 Kbits of Block RAM embedded memory. It's been optimized on a UMC 40-nm process which Xilinx claims helps give it 15% higher performance and 50% lower system power consumption compared to competitive 40nm FPGA offerings.

All this is great and shows that the FPGA continue to give ASIC designers a very competitive option for high-performance applications. But with this continued march forward in complexity, the verification and debug challenges will also continue to mount.

We at GateRocket are all too familiar with designers' pain when it comes to verifying and debugging complex FPGAs. Particularly with first time FPGA users (who may have migrated over from more established ASIC methodologies and flows) who struggle with debug issues related to RTL quality and unfamiliar IP. And, seemingly endless synthesis-to-place-and-route loops slow design cycles down as well.


None of this is a result of the FPGA device itself - it's simply a factor of the significantly increased complexity that these devices enable. Therefore, adopters of these mega-FPGAs are looking for more efficient approaches to verification and debug. Particularly with debugging, the complexity of FPGAs makes debugging in the lab with firmware and logic analyzer almost impossible. Enter GateRocket.


With GateRocket designers can combine conventional simulation with physical hardware and an appropriate debugging environment to detect, isolate, identify, and resolve bugs, no matter where they originated in the design flow. Our RocketDrive lets designers plug the FPGA right into the native software simulation environment - we call in ‘device native simulation.'


FPGA suppliers like Xilinx are continuing to bring out larger, more complex chips that are quickly landing in applications that would have been exclusively the domain of ASICs a few years ago. We say ‘bring it on' - even though they do present more ASIC-like challenges, with tools like GateRocket at their disposal, we're sure designers will be up to the task.


Comments

To be frank i cant see increase in size will increase the productivity,With the unlikely design routing issue's,Lack of Performance oriented RTL skills eats out space and time for prototype.and various divions like EDK/DSP/Logic conflicting for the resource's.lets have a dedicated areas defined by boundaries,Unless and until these blocks are seperated by boundaries with in the fpga i dont see any improvement. 
Posted @ Monday, January 18, 2010 12:45 PM by Ariff
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics