Hi, looking for some advice on an error that has started occuring in FPGA compiler. I haven't use LV for quite a few months and came back to try a very simple analog to frequency circuit using cRIO and got the error. Everything was working fine last time I used it.
I made a vi with just a while loop and tried compiling that and same thing happened so I'd be reasonably sure it isn't a problem with the vi. Couldn't find any other info on the error code on the web. Also tried doing a repair of all LV software from the add/remove panel but no improvement. I haven't done a mass compile yet tho. Using WinXPSP2 and LV8.1 on a Dell dual-core notebook.
The last few lines of the compile report are as follows, I can supply the whole report if needbe.
Thanks,
Andy.
#----------------------------------------------#
# Starting program map
# map -o toplevel_gen_map.ncd -intstyle xflow toplevel_gen.ngd toplevel_gen.pcf
#----------------------------------------------#
Using target part "2v1000fg456-4".
Mapping design into LUTs...
Running directed packing...
Running delay-based LUT packing...
Running related packing...
Design Summary:
Number of errors: 0
Number of warnings: 92
Logic Utilization:
Number of Slice Flip Flops: 304 out of 10,240 2%
Number of 4 input LUTs: 337 out of 10,240 3%
Logic Distribution:
Number of occupied Slices: 249 out of 5,120 4%
Number of Slices containing only related logic: 249 out of 249 100%
Number of Slices containing unrelated logic: 0 out of 249 0%
*See NOTES below for an explanation of the effects of unrelated logic
Total Number 4 input LUTs: 340 out of 10,240 3%
Number used as logic: 337
Number used as a route-thru: 3
Number of bonded IOBs: 148 out of 324 45%
Number of GCLKs: 2 out of 16 12%
Total equivalent gate count for design: 4,688
Additional JTAG gate count for IOBs: 7,104
Peak Memory Usage: 119 MB
NOTES:
Related logic is defined as being logic that shares connectivity - e.g. two
LUTs are "related" if they share common inputs. When assembling slices,
Map gives priority to combine logic that is related. Doing so results in
the best timing performance.
Unrelated logic shares no connectivity. Map will only begin packing
unrelated logic into a slice once 99% of the slices are occupied through
related logic packing.
Note that once logic distribution reaches the 99% level through related
logic packing, this does not mean the device is completely utilized.
Unrelated logic packing will then begin, continuing until all usable LUTs
and FFs are occupied. Depending on your timing budget, increased levels of
unrelated logic packing may adversely affect the overall timing performance
of your design.
Mapping completed.
See MAP report file "toplevel_gen_map.mrp" for details.
#----------------------------------------------#
# Starting program par
# par -w -ol std -intstyle xflow toplevel_gen_map.ncd toplevel_gen.ncd
toplevel_gen.pcf
#----------------------------------------------#
ERROR:Xflow - Program par returned error code -1073741515. Aborting flow
execution...