Keywords: basncsignal, 249, Could not find, bel, F1
General Description: A case has been seen where a Spartan design failed in MAP with the fatal error:
"FATAL_ERROR:Ncd:basncsignal.c:249:18.104.22.168.2.1 - Could not find a bel for a signal on pin F1 of comp c_clk_rec_pulse/n1204<0>. Its current programmed state is : CLKX:CLK YMUX:G G3MUX:G3I G2MUX:G2I CARRY:FORCE XQMUX:QX DX:H H1:C1 SR:C3 H:#LUT:H=(H1+G)*F H0:SR H2:F G:#LUT:G=(G3+G2)+G1 F:#LUT:F=F3 CINMUX:F3 SRX:RESET Process will terminate. To resolve this error, please consult the Answers Database and other online resources at http://support.xilinx.com"
NOTE: This answer record is only a potential match for your issue if the architecture is 4K-based, and the pin mentioned is a CLB LUT input.
A basncsignal.c:249 error occurs when MAP recognizes that the external pin connectivity of a component is not consistent with the internal configuration. In this case, there is an external signal on pin F1; but internally, the F-LUT is configured to use only pin F3.
Errors of this type can often be avoided by altering the way that a component is being packed into a CLB. In this case, isolating the FMAP component involved with an XBLKNM MAP constraint resolves the problem.
A workaround is to apply the UCF constraint:
INST U2367_map XBLKNM = XLNX_WA ;
This problem is scheduled to be fixed in the next major release following 3.1i. This release is currently scheduled for July, 2001.