D
Duth
Guest
On Mar 19, 6:59 am, "Homuncilus" <Sha.Cr...@gmail.com> wrote:
Hi,
This is something that was supposed to be supported in ISE XST in
9.1i, although the change did not make it in time.
Thanks
Duth
On Mar 19, 11:00 am, "John McGrath" <tail...@gmail.com> wrote:
On Mar 16, 11:28 pm, "Ulsk" <a...@ljs.com> wrote:
I noticed XST 9.1 still doesn't support multi-dim arrays in an always @*
block.
Here's a (perhaps poor) example:
reg signed [15:0] table [0:255];
reg signed [23:0] sum;
integer i;
always @*
begin
sum = 0;
for ( i =0; i < 256; i = i + 1 )
sum = sum + table; // yes, I know this will synthesize a suboptimal
imbalanced adder-tree!
end
Correct me if I'm wrong, but I believe that this is not valid verilog
- you cannot use an array as a term in the always() sensitivity list,
and the always* implies that the array is in the sensitivity list. I
know that the ncverilogsimulatorwarns about this (but does work). It
states that this is non-portable verilog. Synopsys DC does indeed
synthesize this correctly, but it's not a good idea to use non-
standard verilog statements.ISEseems to err on the side of adhering
to the strict rules of the verilog language. I could be wrong about
this, but from the warning given by ncverilog, I believe this to be
the case. Maybe try a verilog linting tool? formality/conformal should
set you straight, if you have them.
Cheers
John
I think the wrong isn't due to the sensitivity list. Do you sure the
error inISEis caused by that?
Hi,
This is something that was supposed to be supported in ISE XST in
9.1i, although the change did not make it in time.
Thanks
Duth