ISE build dependencies

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View
In ISE 6.2i, I compile a design off a mapped drive at a foreign site(ie I
did not install the software and do not have administrative privileges).
For example, I try to run Map, sometimes it completes with a green check
mark, and sometimes it completes with no green check mark.  Sometimes when
it compiles with a green check mark, and I hit the Map Report, it reruns all
the tools again (like xst, ngcbuild, map) as though a source hdl file had
been changed. but no source files have been changed.  Its maybe like the
filesystems are running off two different timestamp clocks?

Any ideas?

-Newman



Re: ISE build dependencies

Quoted text here. Click to load it

The timestamp thing can be a problem for make-based dependency checking
(which ISE uses).

But if all the design files are stored on the same computer, I would think
that the timestamp would be consistent across all of them.

As a practical matter, would it be possible for you to simply check the
time on all relevant computers? The first step to corrective action is to
determine what the problem is. Inconsistent time is one hypothesis, now
you should test it. If the time is consistent, then you will have to come
up with a new hypothesis.

--Mac


Re: ISE build dependencies

Quoted text here. Click to load it
Well,  the files are stored on a remote computer. Looking at the file
timestamps in an explorer window, I did notice that when I refreshed the
window, some of the working files were later than the time displayed on the
local computer (where the compilation takes place).  I did bump up the local
time by a couple of minutes in order to guess an approximate equal time for
both computers, but I still experienced the same problem.

-Newman



Re: ISE build dependencies

Quoted text here. Click to load it

If you want to solve this problem, here is what I suggest. First, devise a
simple, repeatable test which identifies the problem.

Then, formulate a hypothesis about what is causing the problem, and take
appropriate steps (according to the hypothesis) to make the problem go
away. Then perform the simple repeatable test to see if the problem is
fixed. If it is fixed, then, just to be sure, undo the fix, and perform
the test again to make sure the problem comes back. Sometimes I go back
and forth like this several times to really convince myself that I have
solved the problem.

If the potential solution doesn't work, undo it, and try another potential
solution. And so on.

In this case, the question you should ask yourself is, did you synchronize
the clocks or not? Do you feel that you have ruled out clock
differences as a potential cause of the behavior you are seeing or
not? If you haven't ruled it out, then keep messing around until you can.

I would think the one thing you DON'T want to have, is files with
modification times in the future, so if you can't sync the clocks exactly,
at least try to make the clock on the system running the compiler slightly
faster than the one storing the data.

Good luck.

--Mac


Re: ISE build dependencies

Quoted text here. Click to load it
site(ie I
Quoted text here. Click to load it
privileges).
Quoted text here. Click to load it
green check
Sometimes
reruns
file had
like the
checking
would think
check the
action is to
Quoted text here. Click to load it
hypothesis, now
to come
file
refreshed the
displayed on the
Quoted text here. Click to load it
the local
time for
devise a
take
go
is
perform
back
have
potential
synchronize
can.
exactly,
slightly


There's another possible problem, if your systems are not set up for
the
same time zone.  In this case if the computers have the same time the
file system will think the dates are off by the time zone differential.

Also I know it's a pain but the simplest workaround is to right click
on
the report file in the process window and "open without updating".  If
you
need to generate a new report or re-synthesize you can use the
right-click
"rerun" or "rerun all" to force a new build.

Good Luck
Gabor


Site Timeline