1 | |
---|
2 | pin2ucf Report File |
---|
3 | Copyright (c) 1995-2010 Xilinx, Inc. All rights reserved. |
---|
4 | Created : Fri Feb 10 18:11:10 2012 |
---|
5 | |
---|
6 | |
---|
7 | |
---|
8 | Constraint Conflicts Information |
---|
9 | ================================ |
---|
10 | |
---|
11 | This section provides information on the constraint conflicts |
---|
12 | if pin2ucf were to write a ucf file using the provided design and |
---|
13 | the existing ucf file. There are 2 types of conflicts that can |
---|
14 | occur. |
---|
15 | |
---|
16 | 1. Multiple pins could be constrained on the same net |
---|
17 | 2. Same pin could have multiple nets |
---|
18 | |
---|
19 | pin2ucf provides a list each for both. |
---|
20 | |
---|
21 | Note:- "New NET" and "New PIN" indicates the Net and Pin |
---|
22 | locations found suitable by pin2ucf for pin locking, while |
---|
23 | "Old Net" and "Old PIN" indicates the Net and Pin locations |
---|
24 | already set by the user in the ucf file, which were left |
---|
25 | untouched by pin2ucf. |
---|
26 | |
---|
27 | |
---|
28 | Net name conflicts on the pins |
---|
29 | ------------------------------- |
---|
30 | |
---|
31 | |
---|
32 | ---------------------------------------------------------------------- |
---|
33 | PIN Location New NET Old NET |
---|
34 | |
---|
35 | ---------------------------------------------------------------------- |
---|
36 | |
---|
37 | "No net name conflicts were found on pins" |
---|
38 | |
---|
39 | |
---|
40 | Pin name conflicts on the nets |
---|
41 | ------------------------------- |
---|
42 | |
---|
43 | |
---|
44 | ---------------------------------------------------------------------- |
---|
45 | NET Name New PIN Old PIN |
---|
46 | |
---|
47 | ---------------------------------------------------------------------- |
---|
48 | |
---|
49 | "No pin name conflicts were found on nets" |
---|
50 | |
---|
51 | |
---|
52 | PinLocking Successful. Constraints written to UCF File |
---|
53 | |
---|