Vivado常見Warning問題解決方法

目錄

1、[Synth 8-2611] redeclaration of ansi port XXX is not allowed

2、[Constraints 18-619] A clock with name 'InClk' already exists

3、 [Synth 8-2611] redeclaration of ansi port InClk is not allowed

4、 [Vivado 12-1017] Problems encountered:

5、 [Constraints 18-5210] No constraint will be written out.

6、[Common 17-1548] Command failed: can't read "output_ports": no such variable

7、[filemgmt 20-2001] Source scanning failed (terminated by user) while processing fileset "sources_1" due to unrecoverable syntax error or design hierarchy issues. Recovering last known analysis of the source files.

8、[Synth 8-1849] concatenation with unsized literal; will interpret as 32 bits

9、[Constraints 18-549] Could not create 'SLEW' constraint because cell 'OBUFDS_inst' is not directly connected to top level port. 'SLEW' is ignored by Vivado but preserved inside the database.

1、[Synth 8-2611] redeclaration of ansi port XXX is not allowed

程序中重復(fù)聲明輸出端口信號

2、[Constraints 18-619] A clock with name 'InClk' already exists

描述：

在約束文件XDC（SCOPED_TO_REF、SCOPED_TO_CELLS）中使用“create_clock -name”約束時，在打開綜合設(shè)計或?qū)崿F(xiàn)設(shè)計時，或者在綜合或?qū)崿F(xiàn)期間，可以觀察到以下警告。

[Constraints 18-619] A clock with name 'InClk' already exists overwriting the previous clock with the same name. ["E:/Vivado_Project/DispTimGen/DispTimGen.srcs/constrs_1/new/DispTimGenTiming.xdc":1]

解決方案：

如果時鐘約束已存在于 IP XDC 中，則無需在頂級 xdc 中寫入約束。

clk_wiz_0.xdc文件中如下已經(jīng)約束InClk；

當(dāng)設(shè)計中有多個作用域單元/引用的實例時會顯示此警告，因此多次讀取相同的“create_clock -name”約束。

如警告消息中所示，僅最后一個讀取保留，所有其他讀取都丟失。

推薦的解決方案是從 create_clock 命令中刪除 -name 選項。

如果未使用 -name 選項，系統(tǒng)會根據(jù)網(wǎng)絡(luò)名/位置創(chuàng)建唯一名稱。

3、 [Synth 8-2611] redeclaration of ansi port InClk is not allowed

輸入端口不需要申明wire型

4、 [Vivado 12-1017] Problems encountered:

[Vivado 12-1017] Problems encountered: Failed to delete one or more files in run directory E:/Vivado_Project/DispTimGen/DispTimGen.runs/synth_1

描述：保存Project文件夾為可讀模式

解決方案：設(shè)置保存Project文件權(quán)限，設(shè)置為讀寫模式

5、 [Constraints 18-5210] No constraint will be written out.

解決方案：Vivado 中的一個已知錯誤，將在 2020.1 中修復(fù)（可以忽略）

6、[Common 17-1548] Command failed: can't read "output_ports": no such variable

描述：set_input_delay時，端口命名錯誤

解決方案：set_input_delay端口命名時，將< >去掉

7、[filemgmt 20-2001] Source scanning failed (terminated by user) while processing fileset "sources_1" due to unrecoverable syntax error or design hierarchy issues. Recovering last known analysis of the source files.

重啟軟件可解決

8、[Synth 8-1849] concatenation with unsized literal; will interpret as 32 bits

問題在了 {} 里面的 “0” 了，原來在拼接符中的0，如果不指定其位數(shù)，則軟件會將其默認為32bit，如果這個0不在高位，那么在進行賦值的時候就會形成了將一個很多位的數(shù)據(jù)賦值給了2bit的BramRst。

9、[Constraints 18-549] Could not create 'SLEW' constraint because cell 'OBUFDS_inst' is not directly connected to top level port. 'SLEW' is ignored by Vivado but preserved inside the database.

約束 [18-549] 無法創(chuàng)建“SLEW”約束，因為單元“OBUFDS_inst”未直接連接到頂級端口。Vivado 會忽略“SLEW”，但會保留在數(shù)據(jù)庫中。

注意：INBUFDS與OBUFDS這類源語言是必須要有硬件連接的In或Out接口！

審核編輯：湯梓紅