how to convert an integer to std_logic_vector using vhdl

[ashwin]

Hello everyone,
I am trying to divite a std_logic_vector by a std_logic_vector.
So i converted both of them into integers and divided. But how do i
convert back to std_logic_vector.


1) Is the integer type or the division" / " synthesizable in xilinx
ISE.

2) if i use integer as my output port and when i download my code onto
the fpga, does it convert back to the binary. If yes to how many bits.


I appreciate if you could answer these questions

thanks
Ashwin

 

[Andy Peters]

Hello everyone,
I am trying to divite a std_logic_vector by a std_logic_vector.
So i converted both of them into integers and divided. But how do i
convert back to std_logic_vector.

Look up numeric_std -- this is the library that has the conversion
functions you need. Do NOT use the obsolete std_logic_arith.

1) Is the integer type or the division" / " synthesizable in xilinx
ISE.

The answer is in the Xilinx XST documentation.

2) if i use integer as my output port and when i download my code onto
the fpga, does it convert back to the binary. If yes to how many bits.

Integers are 32 bit values.

-a

 

[Ralf Hildebrandt]

Andy Peters wrote:

Look up numeric_std -- this is the library that has the conversion
functions you need. Do NOT use the obsolete std_logic_arith.

Full ack.

my_int_u<=to_integer( unsigned(my_std_logic_vector) );
my_int_s<=to_integer( signed(my_std_logic_vector) );

Integers are 32 bit values.

Synthesis tools may be able to eliminate unneeded bits, IF it is clear
to the tool. Therefore it is better to specify a "range" fo integers.

In general it is not a good idea to use integers for (top level) ports,
because often synthesis tools are configured to convert avery port
signal to std_(u)logic_vector, because in reality you need a vector type
for ports.

Ralf

 

[Jaakko Varteva]

Hello everyone,
I am trying to divite a std_logic_vector by a std_logic_vector.
So i converted both of them into integers and divided. But how do i
convert back to std_logic_vector.

Try conv_std_logic_vector, see for example:
http://www.cs.sfu.ca/~ggbaker/reference/std_logic/arith/conv_std_logic_vector.html

-jv-

 

[Andy Peters]

Synthesis tools may be able to eliminate unneeded bits, IF it is clear
to the tool. Therefore it is better to specify a "range" fo integers.

Indeed, that's exactly what I do ... it's very helpful during
simulation, as the tools will complain if you try to assign an
out-of-range value.

The synthesizer simply lops off whatever bits are not needed, and it
all works well.

In general it is not a good idea to use integers for (top level) ports,
because often synthesis tools are configured to convert avery port
signal to std_(u)logic_vector, because in reality you need a vector type
for ports.

I never use integers as ports, but I've used (numeric_std's) unsigned
and signed (both of which are really std_logic_vectors in a different
dress, anyways) as ports. A big downside to using ranged integers or
naturals as ports is unsigned and signed can be assigned 'X' and 'Z'
whereas integers cannot. This is very convenient when your inputs are
from an ADC whose outputs can be tristated and you're doing math on
these values. Saves a conversion.

-a