Problem about compiling code with ISE on different computers

I met a stranger problem.
I compile (systhesis , place and route) by ISE in one coumputer.
And download resualt in FPGA. It work correctly.
But, I compile the same source code in the another computer.
And download the resualt into FPGA. It work incorrectly.

Anybody meets this condition?

Re: Problem about ISE

Hi,
i have encoutered such problems using the ISE software.
Are the ISE versions exactly the same? If not try to use
for both PCs the version which programs the FPGA correctly...
Sometimes just an ISE update makes difference...

pmat

Re: Problem about ISE

this is, why you should not use any GUI to work on a project that you want to re-use on a different pc at a different location later-on. Use scripting instead (a software developers do, too). Using a GUI makes it really difficult to re-produce all the settings you used @ the original PC.

To you 'problem': differences between GUI-setting definately will result in a different implementation - but...

If your design is functionall correct, meets all timing constraints, the timing-constraints are 'complete' (don't forget I/O-timing !) and you descibed all your clock-domain-crossings correctly, then your design 'should' work independently from the machine you used. (experience from more than 5 years using ISE).
Whenever we had issues like the one you described, one of the conditions above was violated.

(It's of cause much easier to blame the tool)

Re: Problem about ISE

Hi, pmat.
Thank for your help.
I make sure the ISE version is the same in the two computer. (release version 8.2i, application version I.31).

Added after 10 minutes:

Hi, JFrensch.
Thanks for your help.
I agree with you "It's of cause much easier to blame the tool", especially the source code are the same.

I check the warning messages in each step (no error message). I cannot find the difference.

Could you give me some information about scripting flow for ISE?
I want to try it.

Re: Problem about ISE

Hi kjtom,

think, you are going into the wrong direction and scipting on it's own won't probably solve your issue !
Sometime, we see those problems too - but in 90% of all cases the root cause is
a) missing constraints
b) wrong constraints (=> check your timing-report after PAR)
c) false clock-domain crossing

Scripting is done for "reproducability" in general, but unlike will solve an issue like yours

Good luck
Jochen