J
Jon Elson
Guest
Hello, all,
I'm using Xilinx Ise 10.1 on a Linux system, and ran into a crazy problem.
I took a previous design and stripped out a bunch of stuff to make a
skeleton of that project to test something, leaving over a bunch of pins
that became unused. I then removed the unused pins from the top-level VHDL
file's port list, and removed those LOC definitions from my .ucf file.
Now, when I try to implement that, I get a bunch of messages that there were
constraints that didn't match a signal name. I edited the .ucf file again,
deleted it from the project and re-added it, but it still finds these
constraints. If I open the .ucf in the text editor, they are not there,
but if I open constraints in the constraint editor - port page, they do
show up.
Anybody know where these are coming from, or what I can do to refresh ise to
get rid of this stale data?
(There used to be a button to "remove implementation data" that would clear
out this sort of thing, but I can't find it in 10.1.)
Thanks,
Jon
I'm using Xilinx Ise 10.1 on a Linux system, and ran into a crazy problem.
I took a previous design and stripped out a bunch of stuff to make a
skeleton of that project to test something, leaving over a bunch of pins
that became unused. I then removed the unused pins from the top-level VHDL
file's port list, and removed those LOC definitions from my .ucf file.
Now, when I try to implement that, I get a bunch of messages that there were
constraints that didn't match a signal name. I edited the .ucf file again,
deleted it from the project and re-added it, but it still finds these
constraints. If I open the .ucf in the text editor, they are not there,
but if I open constraints in the constraint editor - port page, they do
show up.
Anybody know where these are coming from, or what I can do to refresh ise to
get rid of this stale data?
(There used to be a button to "remove implementation data" that would clear
out this sort of thing, but I can't find it in 10.1.)
Thanks,
Jon