OpenCores
no use no use 1/1 no use no use
Re: A Virtex-5 slice utilization problems
by UmairSiddiqui on Nov 14, 2007
UmairSiddiqui
Posts: 21
Joined: Aug 13, 2005
Last seen: Sep 19, 2016
lut packing is performed after "map"... Design Summary -------------- Number of errors: 0 Number of warnings: 2 Slice Logic Utilization: Number of Slice LUTs: 5 out of 138,240 1% Number used as logic: 5 out of 138,240 1% Number using O6 output only: 5 Slice Logic Distribution: Number of occupied Slices: 2 out of 34,560 1% Number of LUT Flip Flop pairs used: 5 Number with an unused Flip Flop: 5 out of 5 100% Number with an unused LUT: 0 out of 5 0% Number of fully used LUT-FF pairs: 0 out of 5 0% On 11/14/07, Umair Siddiqui umairsiddiqui84 at gmail.com> wrote:
According Virtex 5 User Guide (ug190.pdf):
-----------------------------------------------------
Each slice has an F8MUX. F8MUX combines the outputs of F7AMUX and
F7BMUX to form a combinatorial function up to 27 inputs (or a 16:1
MUX). Only one 16:1 MUX can be implemented in a slice, as shown in
Figure 5-23.
===========================================
Now I code

module mux16
(
input clk,
input [3:0] sel,
input [15:0] in,
output reg q
);

always @(posedge clk) begin
case (sel)
4'd0 : q 4'd1 : q 4'd2 : q 4'd3 : q 4'd4 : q 4'd5 : q 4'd6 : q 4'd7 : q 4'd8 : q 4'd9 : q 4'd10 : q 4'd11 : q 4'd12 : q 4'd13 : q 4'd14 : q 4'd15 : q default: q endcase
end

endmodule
===========================================
I'm getting following result using Xilinx ISE 9.2.02i (IO buffers are
not required) => 6 slices

and also notice there is no F8MUX!

================================
* Final Report *
================================
Final Results
RTL Top Level Output File Name : mux16.ngr
Top Level Output File Name : mux16
Output Format : NGC
Optimization Goal : Area
Keep Hierarchy : NO

Design Statistics
# IOs : 22

Cell Usage :
# BELS : 7
# LUT3 : 1
# LUT6 : 4
# MUXF7 : 2
# FlipFlops/Latches : 1
# FD : 1
=================================


Device utilization summary:
---------------------------

Selected Device : 5vlx220tff1738-2


Slice Logic Utilization:
Number of Slice Registers: 1 out of 138240 0%
Number of Slice LUTs: 5 out of 138240 0%
Number used as Logic: 5 out of 138240 0%

Slice Logic Distribution:
Number of Bit Slices used: 6
Number with an unused Flip Flop 5 out of 6 83%
Number with an unused LUT: 1 out of 6 16%
Number of fully used Bit Slices: 0 out of 6 0%
Number of unique control sets: 1

IO Utilization:
Number of IOs: 22
Number of bonded IOBs: 0 out of 680 0%

===========================================
Problem is that I need to make a arbiter handling 64 requesters @ 250
Mhz. I was estimating that 64 bit 64:1 (with registered intermediate
stages) should take 64*5=320 slices. I've not yet started coding...but
it seems useless :-(


Re: A Virtex-5 slice utilization problems
by UmairSiddiqui on Nov 14, 2007
UmairSiddiqui
Posts: 21
Joined: Aug 13, 2005
Last seen: Sep 19, 2016
Area & timing requirement is strict...please tell me whether it is a acheiveable target (64 bit 64:1 mux struct @ 250Mhz) or not..I'm getting skeptical... On 11/14/07, Umair Siddiqui umairsiddiqui84 at gmail.com> wrote:
lut packing is performed after "map"... Design Summary -------------- Number of errors: 0 Number of warnings: 2 Slice Logic Utilization: Number of Slice LUTs: 5 out of 138,240 1% Number used as logic: 5 out of 138,240 1% Number using O6 output only: 5 Slice Logic Distribution: Number of occupied Slices: 2 out of 34,560 1% Number of LUT Flip Flop pairs used: 5 Number with an unused Flip Flop: 5 out of 5 100% Number with an unused LUT: 0 out of 5 0% Number of fully used LUT-FF pairs: 0 out of 5 0% On 11/14/07, Umair Siddiqui umairsiddiqui84 at gmail.com> wrote:
> According Virtex 5 User Guide (ug190.pdf):
> -----------------------------------------------------
> Each slice has an F8MUX. F8MUX combines the outputs of F7AMUX and
> F7BMUX to form a combinatorial function up to 27 inputs (or a 16:1
> MUX). Only one 16:1 MUX can be implemented in a slice, as shown in
> Figure 5-23.
> ===========================================
> Now I code
>
> module mux16
> (
> input clk,
> input [3:0] sel,
> input [15:0] in,
> output reg q
> );
>
> always @(posedge clk) begin
> case (sel)
> 4'd0 : q > 4'd1 : q > 4'd2 : q > 4'd3 : q > 4'd4 : q > 4'd5 : q > 4'd6 : q > 4'd7 : q > 4'd8 : q > 4'd9 : q > 4'd10 : q > 4'd11 : q > 4'd12 : q > 4'd13 : q > 4'd14 : q > 4'd15 : q > default: q > endcase
> end
>
> endmodule
> ===========================================
> I'm getting following result using Xilinx ISE 9.2.02i (IO buffers are
> not required) => 6 slices
>
> and also notice there is no F8MUX!
>
> ================================
> * Final Report *
> ================================
> Final Results
> RTL Top Level Output File Name : mux16.ngr
> Top Level Output File Name : mux16
> Output Format : NGC
> Optimization Goal : Area
> Keep Hierarchy : NO
>
> Design Statistics
> # IOs : 22
>
> Cell Usage :
> # BELS : 7
> # LUT3 : 1
> # LUT6 : 4
> # MUXF7 : 2
> # FlipFlops/Latches : 1
> # FD : 1
> =================================
>
>
> Device utilization summary:
> ---------------------------
>
> Selected Device : 5vlx220tff1738-2
>
>
> Slice Logic Utilization:
> Number of Slice Registers: 1 out of 138240 0%
> Number of Slice LUTs: 5 out of 138240 0%
> Number used as Logic: 5 out of 138240 0%
>
> Slice Logic Distribution:
> Number of Bit Slices used: 6
> Number with an unused Flip Flop 5 out of 6 83%
> Number with an unused LUT: 1 out of 6 16%
> Number of fully used Bit Slices: 0 out of 6 0%
> Number of unique control sets: 1
>
> IO Utilization:
> Number of IOs: 22
> Number of bonded IOBs: 0 out of 680 0%
>
> ===========================================
> Problem is that I need to make a arbiter handling 64 requesters @ 250
> Mhz. I was estimating that 64 bit 64:1 (with registered intermediate
> stages) should take 64*5=320 slices. I've not yet started coding...but
> it seems useless :-(
>



Re: A Virtex-5 slice utilization problems
by Unknown on Nov 14, 2007
Not available!
On Wed, 14 Nov 2007 18:22:22 +0500 "Umair Siddiqui" umairsiddiqui84 at gmail.com> wrote:
Area & timing requirement is strict...please tell me whether it is a
acheiveable target (64 bit 64:1 mux struct @ 250Mhz) or not..I'm
getting skeptical...


A much better place to ask this sort of question is comp.arch.fpga...


/Mikhail

Re: A Virtex-5 slice utilization problems
by Unknown on Nov 15, 2007
Not available!

This question would be better posed to your local Xilinx application
engineer.

Clint

On Wed, 14 Nov 2007, Umair Siddiqui wrote:

Area & timing requirement is strict...please tell me whether it is a acheiveable target (64 bit 64:1 mux struct @ 250Mhz) or not..I'm getting skeptical... On 11/14/07, Umair Siddiqui umairsiddiqui84 at gmail.com> wrote:
lut packing is performed after "map"... Design Summary -------------- Number of errors: 0 Number of warnings: 2 Slice Logic Utilization: Number of Slice LUTs: 5 out of 138,240 1% Number used as logic: 5 out of 138,240 1% Number using O6 output only: 5 Slice Logic Distribution: Number of occupied Slices: 2 out of 34,560 1% Number of LUT Flip Flop pairs used: 5 Number with an unused Flip Flop: 5 out of 5 100% Number with an unused LUT: 0 out of 5 0% Number of fully used LUT-FF pairs: 0 out of 5 0% On 11/14/07, Umair Siddiqui umairsiddiqui84 at gmail.com> wrote:
According Virtex 5 User Guide (ug190.pdf):
-----------------------------------------------------
Each slice has an F8MUX. F8MUX combines the outputs of F7AMUX and
F7BMUX to form a combinatorial function up to 27 inputs (or a 16:1
MUX). Only one 16:1 MUX can be implemented in a slice, as shown in
Figure 5-23.
===========================================
Now I code

module mux16
(
input clk,
input [3:0] sel,
input [15:0] in,
output reg q
);

always @(posedge clk) begin
case (sel)
4'd0 : q 4'd1 : q 4'd2 : q 4'd3 : q 4'd4 : q 4'd5 : q 4'd6 : q 4'd7 : q 4'd8 : q 4'd9 : q 4'd10 : q 4'd11 : q 4'd12 : q 4'd13 : q 4'd14 : q 4'd15 : q default: q endcase
end

endmodule
===========================================
I'm getting following result using Xilinx ISE 9.2.02i (IO buffers are
not required) => 6 slices

and also notice there is no F8MUX!

================================
* Final Report *
================================
Final Results
RTL Top Level Output File Name : mux16.ngr
Top Level Output File Name : mux16
Output Format : NGC
Optimization Goal : Area
Keep Hierarchy : NO

Design Statistics
# IOs : 22

Cell Usage :
# BELS : 7
# LUT3 : 1
# LUT6 : 4
# MUXF7 : 2
# FlipFlops/Latches : 1
# FD : 1
=================================


Device utilization summary:
---------------------------

Selected Device : 5vlx220tff1738-2


Slice Logic Utilization:
Number of Slice Registers: 1 out of 138240 0%
Number of Slice LUTs: 5 out of 138240 0%
Number used as Logic: 5 out of 138240 0%

Slice Logic Distribution:
Number of Bit Slices used: 6
Number with an unused Flip Flop 5 out of 6 83%
Number with an unused LUT: 1 out of 6 16%
Number of fully used Bit Slices: 0 out of 6 0%
Number of unique control sets: 1

IO Utilization:
Number of IOs: 22
Number of bonded IOBs: 0 out of 680 0%

===========================================
Problem is that I need to make a arbiter handling 64 requesters @ 250
Mhz. I was estimating that 64 bit 64:1 (with registered intermediate
stages) should take 64*5=320 slices. I've not yet started coding...but
it seems useless :-(

_______________________________________________ http://www.opencores.org/mailman/listinfo/cores


no use no use 1/1 no use no use
© copyright 1999-2026 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.