**UPGRADE YOUR BROWSER**

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- Community Forums
- :
- Forums
- :
- Design Tools
- :
- Simulation and Verification
- :
- Re: math_real integer to real conversion 2017.2 vs...

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page

ronnywebers

Scholar

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

06-25-2019 01:34 AM

133 Views

Registered:
10-10-2014

In 2017.2 I could write :

procedure generate_sinewave ( signal wave_out : out std_logic_vector; constant kFREQ_HZ : in real; -- must be > 0.0 constant kGAIN : in real; -- gain 0.0 ... 1.0, with 1.0 = full-scale ) is constant upper_limit : integer := 2**(wave_out'length) / 2; -- min value that can be held in signed vecotr constant lower_limit : integer := (-1 * upper_limit) + 1; -- max value constant amplitude : real := kGAIN * (upper_limit - 1); -- multiply with gain constant two_pi_freq : real := 2 * MATH_PI * kFREQ_HZ; -- constant factor in sine calculation

in 2018.2, when opening the same file, I get an error on the constant 'amplited' and 'two_pi_freq' calculation:

Error: found '0' definitions of operator "*", cannot determine exact overloaded matching definition for "*"

did something change from 2017.2 -> 2018.2?

I could fix this by writing :

onstant amplitude : real := kGAIN * (real(upper_limit - 1));

-> I kinda fixed this myself, but I want to double-check: looks like an explicit conversion has become required in 2018.2 vs 2017.2? Is this correct?

-> where can I find a change log of such things?

** kudo if the answer was helpful. Accept as solution if your question is answered **

1 Solution

Accepted Solutions

Highlighted
Its actually 2017.2 that was broken. Exclicit conversion should have been required but obviously wasnt.

richardhead

Scholar

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

06-25-2019 02:01 AM

124 Views

Registered:
08-01-2012

1 Reply

Highlighted
Its actually 2017.2 that was broken. Exclicit conversion should have been required but obviously wasnt.

richardhead

Scholar

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

06-25-2019 02:01 AM

125 Views

Registered:
08-01-2012