赛灵思
直播中

h1654155275.5916

7年用户 993经验值
私信 关注
[问答]

为什么BUFG到DCM时钟定时错误?

大家好。
BUFG资源和DCM / PLL模块在许多FPGA线路上使用专用时钟布线资源。
对于SerDes应用,我们使用BUFIO2来获得DDR SerDes IOCLK,SerDes Strobe和DIVCLK(这很好)。
在SerDes输入之前,DIVCLK由BUFG缓冲(参见UG382 p32)。
然后它也可用于Fabric逻辑。
在我的应用程序中,我们需要使用这种结构DIVCLK并使用DCM重新计时,更新频率并生成4个阶段(0,90,180和270)。
但是,MAP报告BUFG和DCM之间的网络无法进入专用时钟线,因此建议使用。
DCM gore生成器向导已将IPCore配置为使用BUFG作为其输入时钟,因此我不确定这里存在什么问题。
DCM和BUFG是专用时钟资源的一部分,目前在.ucf中没有放置约束(我知道它们需要在同一个时钟区域内)。
有谁知道它为什么没有使用这些专用路径。
信号路径是:
GCLK输入> BUFIO2_2CLK> BUFG> DCM> Fabric。
提前致谢。
埃德

以上来自于谷歌翻译


以下为原文

Hi All.

BUFG resources and DCM/PLL blocks use dedicated clock routing resources on many FPGA lines.

For a SerDes application we use a BUFIO2 to obtain DDR SerDes IOCLK, SerDes Strobe and DIVCLK (this works fine). DIVCLK is buffered by a BUFG prior to SerDes input (See UG382 p32). It is then also available to the Fabric logic.

In my application we need to take this fabric DIVCLK and use a DCM to re-time, chnage frequency and generate 4 phases (0, 90, 180 and 270).

However, MAP reports that the net between the BUFG and DCM cannot go on the dedicated clock lines and therefore suggests use of . The DCM gore generator wizard has configured the IPCore to use a BUFG as its input clock so I'm not sure what the problem is here.

The DCM and BUFG are part of the dedicated clock resources and there are currently no placement constrainsts in the .ucf (I know they need to be within the same clock region).

Does anyone know why it is failing to use those dedicated paths.

The signal path is:

GCLK input > BUFIO2_2CLK > BUFG > DCM > Fabric.

Thanks in advance.
Ed

回帖(3)

李铃华

2019-7-30 10:55:05
要做的第一件事是检查翻译消息,看看是否由于某种原因你的约束被忽略了。
顺便说一句,错误消息将约束括在尖括号中,但那些不应该进入UCF文件。
约束应如下所示:NET“sensor_video_1_iClock_pin”CLOCK_DEDICATED_ROUTE = FALSE
谢谢和RegardsBalkrishan -----------------------------------------------
---------------------------------------------请将帖子标记为
一个答案“接受为解决方案”,以防它有助于解决您的查询。如果一个帖子引导到解决方案,请给予赞誉。

以上来自于谷歌翻译


以下为原文

The first thing to do is check the translate messages to see if for some reason your constraint has been ignored.  By the way, the error message encloses the constraint in angle brackets, < ... >, but those should not go into the UCF file.  The constraint should look like:



NET "sensor_video_1_iClock_pin" CLOCK_DEDICATED_ROUTE = FALSEThanks and Regards
Balkrishan
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
举报

陈光琦

2019-7-30 11:11:54
不幸的是,这个问题没有给出合适的答案。
我不想摆脱将其降级为警告的错误,我想实际使用时钟资源,实际上我们希望保留DEDICATED_ROUTE =“TRUE”
我已经修改了设计以遵循以下路径: 
- >面料 
|
GCLK> BUFIO2> BUFG> SerDes 

- > DCM> Fabric
这已经清除了错误,但是当BUFG(UG382 p32)之后的Fabric DIVCLK点击然后用于T触发器(在这种情况下为negedge SERDES_DIVCLK)时,已经创建了类似的DEDICATED_ROUTE =“FALSE”问题,报告了
BUFG之后的网络无法使用专用时钟分配,即将DIVCLK线路进入SerDes模块关闭专用路由。
干杯。
埃德

以上来自于谷歌翻译


以下为原文

Unfortunatly that didn't really give a suitable answer to the issue. I don't want to get rid of the error downgrading it to a warning, I want to actually use the clock resources, in effect we are looking to retain DEDICATED_ROUTE = "TRUE"
 
I've since modified the design to follow the path:
    
                                                -> Fabric
                                               |
GCLK > BUFIO2 > BUFG > SerDes
                               |
                               -> DCM > Fabric
 
This has now cleared the error, but has created a similar DEDICATED_ROUTE = "FALSE" problem when the Fabric DIVCLK tap after the BUFG (UG382 p32) is then used in a T Flip-Flop (in this case negedge SERDES_DIVCLK), reporting that the net after the BUFG cannot use dedicated clock distribution, i.e. taking the DIVCLK line going into the SerDes blocks off the dedicated routing.
 
Cheers.
Ed
 
 
举报

潘晶燕

2019-7-30 11:24:24
E,
简单的问题:你不能从这里到达那里。
DCM输入必须来自IBUFG,BUFG或常规互连。
我还将GCLK放在BUFG上,以便能够到达DCM。
只有这么多方法允许客户路由。
你拥有的那个不存在。
Austin Lesea主要工程师Xilinx San Jose

以上来自于谷歌翻译


以下为原文

e,
 
Simple problem:  you cannot get there from here.  DCM input must come from an IBUFG, BUFG, or over regular interconnect.
 
I would also put the GCLK on a BUFG so it is able to reach the DCM.

Only so many ways to allow a customer to route.  The one you have doesn't exist.
 
 
Austin Lesea
Principal Engineer
Xilinx San Jose
举报

更多回帖

发帖
×
20
完善资料,
赚取积分