To Xilinx guys out there - microblaze mapping problem

Hi, I have a design in which I need to instantiate two microblaze system instances (the same microblaze system in two places). I'm doing it by the following way:

1) I've created a system containing a single microblaze (in EDK) 2) I've instantiated it in my hdl code in two different places. 3) Then I merged the two bmm files into a single bmm file which looks like this:

/////////////////////////////////////////////////////////////////////////////// // // Address space 'rmac_lmb_bram' 0x00000000:0x00001FFF (8 KB). // ///////////////////////////////////////////////////////////////////////////////

ADDRESS_BLOCK rmac_lmb_bram RAMB16 [0x00000000:0x00001fff] BUS_BLOCK CORE/rmac_i/system_rmac/lmb_bram/lmb_bram/ramb16_0 [31:24] ; CORE/rmac_i/system_rmac/lmb_bram/lmb_bram/ramb16_1 [23:16] ; CORE/rmac_i/system_rmac/lmb_bram/lmb_bram/ramb16_2 [15:8] ; CORE/rmac_i/system_rmac/lmb_bram/lmb_bram/ramb16_3 [7:0] ; END_BUS_BLOCK; END_ADDRESS_BLOCK;

/////////////////////////////////////////////////////////////////////////////// // // Address space 'tmac_lmb_bram' 0x00000000:0x00001FFF (8 KB). // ///////////////////////////////////////////////////////////////////////////////

ADDRESS_BLOCK tmac_lmb_bram RAMB16 [0x00000000:0x00001fff] BUS_BLOCK CORE/tmac_i/system_tmac/lmb_bram/lmb_bram/ramb16_0 [31:24] ; CORE/tmac_i/system_tmac/lmb_bram/lmb_bram/ramb16_1 [23:16] ; CORE/tmac_i/system_tmac/lmb_bram/lmb_bram/ramb16_2 [15:8] ; CORE/tmac_i/system_tmac/lmb_bram/lmb_bram/ramb16_3 [7:0] ; END_BUS_BLOCK; END_ADDRESS_BLOCK;

4) I synthesize my design using synplify 8.1 5) I call the following script (for translate and map)

ngdbuild -a -p XC4VLX80-FF1148-10 -bm /home/motic/projects/fpga/units/mac/mac_bmax/802_16d/ublaze/rmac_tmac.bmm

-sd ../../../../syn/syn_v4/edf

-uc ../../bs_lx80.ucf bs rev1/bs.ngd;

map -cm area -p XC4VLX80-FF1148-10 -detail -o rev1/map.ncd -pr b rev1/bs.ngd rev1/bs.pcf;

The ngdbuild goes well but the mapping process has lots of errors ( it seems that the mapper tries to place the two microblaze instances on top of each other) part of the map log file (.mrp) is attached Can you please advise ? Thanks in advance, Mordehay.

Snippet of the map report file (originaly conatins 465 errors):

Release 7.1.03i Map H.41 Xilinx Mapping Report File for Design 'bs'

Design Information

------------------ Command Line : map -cm area -p XC4VLX80-FF1148-10 -detail -o rev1/map.ncd -pr b rev1/bs.ngd rev1/bs.pcf Target Device : xc4vlx80 Target Package : ff1148 Target Speed : -10 Mapper Version : virtex4 -- $Revision: 1.26.6.4 $ Mapped Date : Mon Nov 6 11:55:10 2006

Design Summary

-------------- Number of errors : 465 Number of warnings :3074

Section 1 - Errors

------------------ ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y0) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/RAM16x1D_Reg1_Low" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I31/reg1_Data_Low) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/RAM16x1D_Reg1_Low" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I31/reg1_Data_Low) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y1) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/RAM16x1D_Reg1_High" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I31/reg1_Data_High) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/RAM16x1D_Reg1_High" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I31/reg1_Data_High) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y2) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/RAM16x1D_Reg1_Low" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I15/reg1_Data_Low) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/RAM16x1D_Reg1_Low" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I15/reg1_Data_Low) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y3) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/RAM16x1D_Reg1_High" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I15/reg1_Data_High) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/RAM16x1D_Reg1_High" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I15/reg1_Data_High) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X1Y0) which require the combination of the following symbols into a single SLICE component: LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/Reg1_Mux" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/Reg1_Mux" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data) LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/Data_Write_Mux" (Output Signal = CORE/tmac_i/system_tmac/dlmb_LMB_WriteDBus[31]) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/Data_Write_Mux" (Output Signal = CORE/rmac_i/system_rmac/dlmb_LMB_WriteDBus[31]) There are more than two function generators. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y4) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I30/RAM16x1D_Reg1_Low" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I30/reg1_Data_Low) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I30/RAM16x1D_Reg1_Low" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I30/reg1_Data_Low) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X1Y1) which require the combination of the following symbols into a single SLICE component: LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Dopb_Interface_I/OPB_Data_ Mux_I1/MUX_LUT31" (Output Signal = CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/mux_Data_Read) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Dopb_Interface_I/OPB_Data_ Mux_I1/MUX_LUT31" (Output Signal = CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/mux_Data_Read) LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/Reg2_Mux" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg2_Data) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/Reg2_Mux" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg2_Data) There are more than two function generators. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y5) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I30/RAM16x1D_Reg1_High" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I30/reg1_Data_High) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I30/RAM16x1D_Reg1_High" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I30/reg1_Data_High) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X1Y2) which require the combination of the following symbols into a single SLICE component: LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/Reg1_Mux" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/Reg1_Mux" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data) LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/Data_Write_Mux" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/raw_Data_Write) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/Data_Write_Mux" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/raw_Data_Write) There are more than two function generators. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y6) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I14/RAM16x1D_Reg1_Low" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I14/reg1_Data_Low) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I14/RAM16x1D_Reg1_Low" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I14/reg1_Data_Low) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X1Y3) which require the combination of the following symbols into a single SLICE component: LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Dopb_Interface_I/OPB_Data_ Mux_I1/MUX_LUT15" (Output Signal = CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/mux_Data_Read) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Dopb_Interface_I/OPB_Data_ Mux_I1/MUX_LUT15" (Output Signal = CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/mux_Data_Read) LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/Reg2_Mux" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg2_Data) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I15/Reg2_Mux" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg2_Data) There are more than two function generators. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y7) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I14/RAM16x1D_Reg1_High" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I14/reg1_Data_High) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I14/RAM16x1D_Reg1_High" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I14/reg1_Data_High) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X1Y4) which require the combination of the following symbols into a single SLICE component: LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I30/Data_Write_Mux" (Output Signal = CORE/tmac_i/system_tmac/dlmb_LMB_WriteDBus[30]) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I30/Data_Write_Mux" (Output Signal = CORE/rmac_i/system_rmac/dlmb_LMB_WriteDBus[30]) LUT symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I30/Reg1_Mux" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data) LUT symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I30/Reg1_Mux" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data) There are more than two function generators. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y8) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I29/RAM16x1D_Reg1_Low" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I29/reg1_Data_Low) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I29/RAM16x1D_Reg1_Low" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I29/reg1_Data_Low) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X2Y0) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/RAM16x1D_Reg2_Low" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I31/reg2_Data_Low) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I31/RAM16x1D_Reg2_Low" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I31/reg2_Data_Low) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. ERROR:Pack:679 - Unable to obey design constraints (MACRONAME=microblaze_0, RLOC=X0Y9) which require the combination of the following symbols into a single SLICEM component: RAMDP symbol

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I29/RAM16x1D_Reg1_High" (Output Signal =

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I29/reg1_Data_High) RAMDP symbol

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_ I/Register_File_Bit_I29/RAM16x1D_Reg1_High" (Output Signal =

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I /Register_File_Bit_I29/reg1_Data_High) The address signals must match exactly when using both F and G in RAM mode. Please correct the design constraints accordingly. and it continues like this ....

Reply to
me_2003
Loading thread data ...

Hi,

The problem is that the two microblazes have the exact same name. MicroBlaze is a RLOC block which requires a unique name.

In this case, I think you need to create two EDK designs which are more or less the same except for the instance name of MicroBlaze or you can also create two microblaze in one EDK design.

Göran

Reply to
Göran Bilski

Hi Goran,

Is there any way to instruct the platgen not to use RLOC for the microblaze? It is just that now (after doing what you suggested above) my mapping went well but the PAR fails - It says that a certain core (xilinx reed-solomon decoder) cannot be placed. I figured out that maybe the RLOCs of the microblaze causes this problem (my chip utilization is under 50%). Thanks in advance, Mordehay.

error snippet from par log file :

---------------------------------------------------------------------------=

----------------------------------------------- Starting Placer

Phase 1.1 ERROR:Place:346 - The components related to The RPM "CORE/RFEC_i/rs_dec_i/rs_docoder_i/rs_dec/dec/sy/nig1/ffo1/r1" can not be placed in the required relative placement form

The following components are part of this structure: SLICEM CORE/RFEC_i/rs_dec_i/rs_docoder_i/N207 SLICEL CORE/RFEC_i/rs_dec_i/rs_docoder_i/N19412 SLICEL CORE/RFEC_i/rs_dec_i/rs_docoder_i/N19411 SLICEL CORE/RFEC_i/rs_dec_i/rs_docoder_i/N19409 SLICEM CORE/RFEC_i/rs_dec_i/rs_docoder_i/N208 SLICEM CORE/RFEC_i/rs_dec_i/rs_docoder_i/N204 SLICEM CORE/RFEC_i/rs_dec_i/rs_docoder_i/N202

The reason for this issue is the following: This logic may be too large or of too irregular shape to fit on the device.

---------------------------------------------------------------------------=

-----------------------------------------------

G=F6ran Bilski wrote:

////////

////////

////////

////////

mm

_File_

File_I

_File_

File_I

_File_

File_I

_File_

File_I

_File_

File_I

_File_

File_I

_File_

File_I

_File_

File_I

_File_

)

_File_

)

_File_

_File_

_File_

File_I

_File_

File_I

_Data_

_Data_

_File_

)

_File_

)

_File_

File_I

_File_

File_I

_File_

)

_File_

)

_File_

_File_

_File_

File_I

_File_

File_I

_Data_

_Data_

_File_

)

_File_

)

_File_

File_I

_File_

File_I

_File_

_File_

_File_

)

_File_

)

_File_

File_I

_File_

File_I

_File_

File_I

_File_

File_I

_File_

File_I

_File_

File_I

Reply to
me_2003

Hi,

There is no way to tell MicroBlaze not to use RLOC. You can however tell the ISE tools to ignore RLOCs. The map needs the parameter -ir

Göran

Is there any way to instruct the platgen not to use RLOC for the microblaze? It is just that now (after doing what you suggested above) my mapping went well but the PAR fails - It says that a certain core (xilinx reed-solomon decoder) cannot be placed. I figured out that maybe the RLOCs of the microblaze causes this problem (my chip utilization is under 50%). Thanks in advance, Mordehay.

error snippet from par log file :

-------------------------------------------------------------------------------------------------------------------------- Starting Placer

Phase 1.1 ERROR:Place:346 - The components related to The RPM "CORE/RFEC_i/rs_dec_i/rs_docoder_i/rs_dec/dec/sy/nig1/ffo1/r1" can not be placed in the required relative placement form

The following components are part of this structure: SLICEM CORE/RFEC_i/rs_dec_i/rs_docoder_i/N207 SLICEL CORE/RFEC_i/rs_dec_i/rs_docoder_i/N19412 SLICEL CORE/RFEC_i/rs_dec_i/rs_docoder_i/N19411 SLICEL CORE/RFEC_i/rs_dec_i/rs_docoder_i/N19409 SLICEM CORE/RFEC_i/rs_dec_i/rs_docoder_i/N208 SLICEM CORE/RFEC_i/rs_dec_i/rs_docoder_i/N204 SLICEM CORE/RFEC_i/rs_dec_i/rs_docoder_i/N202

The reason for this issue is the following: This logic may be too large or of too irregular shape to fit on the device.

--------------------------------------------------------------------------------------------------------------------------

Göran Bilski wrote:

///////////////////////////////////////////////////////////////////////////////

///////////////////////////////////////////////////////////////////////////////

///////////////////////////////////////////////////////////////////////////////

///////////////////////////////////////////////////////////////////////////////

Reply to
Göran Bilski

Hi Goran, Thanks again for your response. when using the -ir option I managed to get my PAR right, but now I'm worried about the results of not using the RLOC constraints. Is there a danger that my design wont work properly now ? Thanks again, Mordehay.

G=F6ran Bilski wrote:

-------------------------------------------------

-------------------------------------------------

or

//////////

//////////

//////////

//////////

.bmm

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

ta)

er_File_

ta)

er_File_

er_File_

er_File_

r_File_I

er_File_

r_File_I

PB_Data_

PB_Data_

er_File_

ta)

er_File_

ta)

er_File_

r_File_I

er_File_

r_File_I

er_File_

ta)

er_File_

ta)

er_File_

er_File_

er_File_

r_File_I

er_File_

r_File_I

PB_Data_

PB_Data_

er_File_

ta)

er_File_

ta)

er_File_

r_File_I

er_File_

r_File_I

er_File_

er_File_

er_File_

ta)

er_File_

ta)

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

er_File_

r_File_I

Reply to
me_2003

No, The only thing that might happen is that you will not reach the timing constraints.

Göran

Göran Bilski wrote:

--------------------------------------------------------------------------------------------------------------------------

--------------------------------------------------------------------------------------------------------------------------

///////////////////////////////////////////////////////////////////////////////

///////////////////////////////////////////////////////////////////////////////

///////////////////////////////////////////////////////////////////////////////

///////////////////////////////////////////////////////////////////////////////

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data)

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data)

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Dopb_Interface_I/OPB_Data_

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Dopb_Interface_I/OPB_Data_

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg2_Data)

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg2_Data)

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data)

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data)

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Dopb_Interface_I/OPB_Data_

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Dopb_Interface_I/OPB_Data_

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg2_Data)

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg2_Data)

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data)

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/reg1_Data)

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/tmac_i/system_tmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

"CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_

CORE/rmac_i/system_rmac/microblaze_0/microblaze_0/Data_Flow_I/Register_File_I

Reply to
Göran Bilski

Hi G=F6ran, Thanks a lot for your support - it was realy helpful.. Best regards, Mordehay.

G=F6ran Bilski wrote:

---------------------------------------------------

---------------------------------------------------

re

ks

////////////

////////////

////////////

////////////

ac.bmm

it

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

ster_File_

Data)

ster_File_

Data)

ster_File_

ster_File_

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

/OPB_Data_

/OPB_Data_

ster_File_

Data)

ster_File_

Data)

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

ster_File_

Data)

ster_File_

Data)

ster_File_

ster_File_

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

/OPB_Data_

/OPB_Data_

ster_File_

Data)

ster_File_

Data)

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

ster_File_

ster_File_

ster_File_

Data)

ster_File_

Data)

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

ls

ster_File_

ter_File_I

ster_File_

ter_File_I

Reply to
me_2003

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.