![]() |
|
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
|
![]() |
![]() |
Answers Database
** OBSOLETE ** XNFPREP 5.20: changes "INIT=S" to lower case "init=S", which PPR 5.20 ignores![]() Record #974
Product Family: Software When XNFPREP reads in an input XNF netlist, it stores only the first instance of any string it encounters, and preserves its case. If it happens to encounter a string called "init" before it sees an "INIT" string, it will only store the string "init" and use this string when it writes out its prep'd XNF output (Ref 28734). Subsequently during the routing process, a bug in PPR 5.20 (Ref. 28692) that causes it to ignore the "init" property. One way this can happen is if you have a block in the design named "init" in lower case. When it is merged with the top level design, a HIERG record referencing this block will be written to the XNF file. These usually are found at the beginning of the XNF file, before any SYM records with INIT properties are written, so XNFPREP will encounter and store the lower case "init" first. Solution 1: Avoid naming blocks in your design "init". End of Record #974 - Last Modified: 02/26/99 17:41 |
For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips! |