FPGA Central - World's 1st FPGA / CPLD Portal

FPGA Central

World's 1st FPGA Portal

 

Go Back   FPGA Groups > NewsGroup > FPGA

FPGA comp.arch.fpga newsgroup (usenet)

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 12-29-2005, 11:24 PM
Guest
 
Posts: n/a
Default Virtex 4 desing : ChipScope insertion impacts my timing problem debug

Hi,
I am working on a Virtex4 FX design, when the system clock runs at
100MHz, the memory controller core does not work correctly. Then I
inserted ChipScope trying to identify the problem, but once it is
inserted, the problem is gone!

I know it is of timing problem since if I lower the system clock to
50MHz, there is no problem either.

It looks like that after the chipscope is inserted, somehow the
routing is altered in favor of the memory controller.

I just wonder if there are any trick so that Chipscope insertion does
not impact design routing?

Reply With Quote
  #2 (permalink)  
Old 12-30-2005, 06:56 PM
mike_la_jolla
Guest
 
Posts: n/a
Default Re: Virtex 4 desing : ChipScope insertion impacts my timing problem debug


[email protected] wrote:
> Hi,
> I am working on a Virtex4 FX design, when the system clock runs at
> 100MHz, the memory controller core does not work correctly. Then I
> inserted ChipScope trying to identify the problem, but once it is
> inserted, the problem is gone!
>
> I know it is of timing problem since if I lower the system clock to
> 50MHz, there is no problem either.
>
> It looks like that after the chipscope is inserted, somehow the
> routing is altered in favor of the memory controller.
>
> I just wonder if there are any trick so that Chipscope insertion does
> not impact design routing?


No.

Reply With Quote
  #3 (permalink)  
Old 12-31-2005, 05:39 PM
John Adair
Guest
 
Posts: n/a
Default Re: Virtex 4 desing : ChipScope insertion impacts my timing problem debug

Generally the answer is that Chipscope always has some effect. However you
can minimise the effect by pre-registering signals used as inputs to
chipscope. This reduces the raw fight for resources between where design
elements need to be and where Chipscope needs to be with the chip.

The problem you describe does sound like timing. Have you set proper timing
constraints? Have you considered the implementation where any clock
boundaries that are crossed?


John Adair
Enterpoint Ltd. - Home of MIN-CAN. The Spartan-3 CAn Bus Development Board.
http://www.enterpoint.co.uk


<[email protected]> wrote in message
news:[email protected] oups.com...
> Hi,
> I am working on a Virtex4 FX design, when the system clock runs at
> 100MHz, the memory controller core does not work correctly. Then I
> inserted ChipScope trying to identify the problem, but once it is
> inserted, the problem is gone!
>
> I know it is of timing problem since if I lower the system clock to
> 50MHz, there is no problem either.
>
> It looks like that after the chipscope is inserted, somehow the
> routing is altered in favor of the memory controller.
>
> I just wonder if there are any trick so that Chipscope insertion does
> not impact design routing?
>



Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
chipscope pro problem CMOS FPGA 0 10-17-2005 07:40 AM
Chipscope pro : timing constraint? Pasacco FPGA 9 08-19-2005 06:11 PM
Spartan-3E, ISE 7.1 some issues - solved (BUFG insertion problem) Antti Lukats FPGA 2 07-09-2005 02:59 PM
chipscope pro problem (par) Yttrium FPGA 19 11-11-2004 08:20 PM
Problem with timing in post PAR with Xilinx Virtex II Steven FPGA 0 09-09-2004 08:30 PM


All times are GMT +1. The time now is 09:19 PM.


Powered by vBulletin® Version 3.8.0
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Copyright 2008 @ FPGA Central. All rights reserved