Full compulation for large IO pins

--- Quote Start ---

Hi

I would like to perform full compilation for component (not the Top Level) that has large IO pins. Im looking at over thousands bits in output bits. But I need to know the total LEs and Fmax of the that particular component. Any ways to do so? apparently there would not be any device that can provides such large pins. Thanks

--- Quote End ---

To compile a design, you have to select a particular architecture (ie, CycloneV, for example) and a specific device and package within that architecture. You can't compile for a device that does not physically exist. Can you explain further what you are attempting to do?

--- Quote Start ---

IF you're just getting resource estimations for a block, then simply create a new project containing the block and sub-modules you need to compile it. In the assignments editor, create an assignment for Virtual_pins, and assign it to *. That will then ensure all IOs for that module are assigned virtual pins allowing you to compile your module and get logic usage. You will still need to pick a device - I suggest using the same device as your eventual target.

--- Quote End ---

Yes you are right. That is exactly what I wanted to do. And later I found out that the full compilation took a very long time and has yet to be successful. I found this message on the console:

Warning (16618): Fitter routing phase terminated due to routing congestion. Congestion details can be found in Chip Planner.

any advice?

Without seeing the code, I cannot really say alot.

But long compiliation times for idividual modules (eg >30 mins) is likely a problem in the code and the easiest way to kill it is to have a large ram that gets inferred as registers instead of Ram blocks because the behaviour is incorrect.

Can you post your code?

--- Quote Start ---

Without seeing the code, I cannot really say alot.

But long compiliation times for idividual modules (eg >30 mins) is likely a problem in the code and the easiest way to kill it is to have a large ram that gets inferred as registers instead of Ram blocks because the behaviour is incorrect.

Can you post your code?

--- Quote End ---

Basically the top module is as such:

module KC(clk, reset, in, out);

input clk;

input reset;

input [575:0] in;

output [511:0] out;

wire [1599:0] r0, r1, r2, r3, r4, r5, r6, r7, r8, r9, r10,r11;

wire [1599:0] r12,r13,r14,r15,r16,r17,r18,r19,r20,r21,r22,r23;

assign out = r23[1599:1599-511];

mKC

round0 ( clk, reset, 8'h01, {in, 1024'b0 } , r0);

mKC

round1 ( clk, reset, 8'h32, r0, r1);

mKC

round2 ( clk, reset, 8'hba, r1, r2);

.

.

.

.

.

.

.

--basically there are 23 identical portmap as above

endmodule

and each of the mKC module contains several logical expression with output is registered.

Why are those busses so huge? what are you trying to do?

What is this block?

--- Quote Start ---

Is there any reason you're not doing this using ram?

--- Quote End ---

For now, I just want to explore various implementation methodology. Initially, I was thinking to customized some optimization of the function but seems like my approach is not practical for implementation