Re: Signed, Unsigned syntax issues. Please help, I'm stumped

<nitrogenocide@[EMAIL PROTECTED]
> wrote in message 
news:62d67656-1b11-4741-895b-b4741ced1a86@[EMAIL PROTECTED]
> After running "check syntax", I get the following errors.
>
> ERROR:HDLParsers:3292 - "D:/PFiles/SS08/SS08.vhd" Line 92. = has two
> or more possible definitions in this scope.  For example, parameter 2
> (string value) can be: SIGNED or UNSIGNED
> ERROR:HDLParsers:3292 - "D:/PFiles/SS08/SS08.vhd" Line 114. = has two
> or more possible definitions in this scope.  For example, parameter 2
> (string value) can be: SIGNED or UNSIGNED
> ERROR:HDLParsers:3292 - "D:/PFiles/SS08/SS08.vhd" Line 145. = has two
> or more possible definitions in this scope.  For example, parameter 2
> (string value) can be: SIGNED or UNSIGNED
>
>
> here are the lines being referred to:
>
> Line 92:    if setup_sample = "1111111" then
>
> Line 114:  curval <= countupstuff when setup_sample = "1111110";
>
> Line 145:  elsif apnea_count = "1101001101010101100100000" then
>
>
> The errors seem to be implying that I haven't specified these signals
> as either signed or unsigned.  But the following part of my code does
> specify all these signals as unsigned

But the thing you're comparing them to (i.e. "1111111" and "1111110" are 
ambiguous).  You need to tell it if it is signed or unsigned like this

unsigned'("1111110")

Note the tick mark.

KJ
>
>
>
> (these are lines 39 through 47)
>
>
> architecture Behavioral of SS08 is
>
> signal countupstuff, curval, sample, count_1khz : unsigned (15 downto
> 0);
> signal apnea_reset, alarm_out, clock1k, clock1k_int,  inc_apnea_count,
> inc_not_apnea, clock32x, clock32x_int, settozero : std_logic;
> signal apnea_count, not_apnea : unsigned (24 downto 0);
> signal count_1Mhz : unsigned (4 downto 0);
> signal setup_sample : unsigned (6 downto 0);
>
> begin
>
>
> Interesting note, I was previously running this code on ISE 9.1 and it
> didn't have a problem with it.
>
>
> Can any one shed some light on why I'm getting these errors?  It would
> be very much appreciated.  Let me know if you need any more
> information.
>
>
>
> Thanks,
>
>
>
> Jeff