M
MM
Guest
This is a more generic question following up my previous question on
translation failing because of the IOBs instantiated in one of the EDK
cores. I was wondering if there is a way (short of hacking the core) to
either disable IOB instantiation in EDK altogether or vice-versa to disable
IOB instantiation in ISE, but only for those pins, which already have IOBs
instantiated by EDK. I tried implementing the latter idea by assigning
synthesis iob attribute for these pins and setting it to FALSE, but got an
INTERNAL_ERROR in XST... I can't believe there is no simple solution... In
the past ISE somehow managed to figure this out. I also vaguely remember
that at some point long ago I had a similar problem and did something with
some of the cores, but can't remember what... In any case latest MPMC core
has these IOB instantiations scattered through many files and hacking them
all doesn't appear to be a nice solution.
Any ideas will be highly appreciated!
/Mikhail
translation failing because of the IOBs instantiated in one of the EDK
cores. I was wondering if there is a way (short of hacking the core) to
either disable IOB instantiation in EDK altogether or vice-versa to disable
IOB instantiation in ISE, but only for those pins, which already have IOBs
instantiated by EDK. I tried implementing the latter idea by assigning
synthesis iob attribute for these pins and setting it to FALSE, but got an
INTERNAL_ERROR in XST... I can't believe there is no simple solution... In
the past ISE somehow managed to figure this out. I also vaguely remember
that at some point long ago I had a similar problem and did something with
some of the cores, but can't remember what... In any case latest MPMC core
has these IOB instantiations scattered through many files and hacking them
all doesn't appear to be a nice solution.
Any ideas will be highly appreciated!
/Mikhail