type conversion in port map flagged as an error

Posted Thu, 2011-10-13 16:11 by ndhuffma

Just bringing a design into 2.0 and I'm getting a lot of lines flagged as errors where I'm doing the following:

small_st_fifo: entity work.fifo_32w_x_8d(SYN)
    port map (
        aclr              => rio_rx_rst,
        data              => std_logic_vector(st_fifo_wdata),
        rdclk             => rio_rx_clk,
        rdreq             => st_fifo_readack,
        wrclk             => av_stream_clk,
        wrreq             => st_fifo_write,
        unsigned(q)       => st_fifo_rdata,  --THIS LINE MARKED AS AN ERROR
        rdempty           => open,
        unsigned(rdusedw) => st_fifo_usedwds(2 downto 0), --THIS LINE MARKED AS AN ERROR
        wrfull            => open,
        wrusedw           => open
        );

And get this error message (only for the first mark):
"A positional association cannot follow after a named association"

but as far as I can tell, this is valid syntax and ModelSim, Quartus, and SigasiHDT 1.0 don't complain.

‹ ncsim support of sigasi Is this program made for slow people or is it just me ? ›

ticket:1758

by heeckhau (Sigasi) - 2011-10-14 08:47

Looks like a bug to me. I have logged this as ticket:1758.

Thanks for reporting,
Hendrik.

Resolved in Sigasi 2.1.1

by heeckhau (Sigasi) - 2011-11-24 16:50

Resolved in Sigasi 2.1.1

this appears to still be an issue

by ndhuffma - 2011-11-28 18:04

I upgraded this morning and did a clean and re-build and these the 1st line is still flagged with an error. The error that's flagged is reported as "A positional association cannot follow after a named association" but this is clearly still a named association.

conversion function

by heeckhau (Sigasi) - 2011-11-28 20:51

You are right, this still goes wrong. We corrected port maps for arrays and records, but it seems we forgot conversion functions.
I will reopen this ticket.

Hendrik.

thanks and another little bug

by ndhuffma - 2012-02-09 22:54

Thanks for fixing this. I did have to manually delete the .markers file in my workspace to completely remove the error. I guessed since it looked like the lingering TODO: marker bug from HDT1.0 (could save the file and see the marker go gray but it wouldn't clear the file status) and this was the work-around. After deleting the marker files for my projects and re-building this was resolved.

Post new comment

The content of this field is kept private and will not be shown publicly.
By submitting this form, you accept the Mollom privacy policy.