Turn on suggestions

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

Showing results for

- Intel Community
- FPGAs and Programmable Solutions
- FPGA Intellectual Property
- Data in/out format FFT IP module

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

Altera_Forum

Honored Contributor I

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

05-02-2013
06:25 PM

787 Views

Data in/out format FFT IP module

Hello everyone!

As the title of the post states we want to use the FFT IP to program it in a Stratix III FPGA but, since this is our first time with it, we have faced some problems. So far, we have managed to run the module, that is, to get the 1024 complex vector of frequencies from a sine input signal, which was generated with a NCO (numerically controlled oscillator). The problem is that the data we get at the output is not the expected for a sinewave. The fact is that we don't really know what the format of the input signal should be (two's complement for instance). We don't either know what exactly the format of the output data (vector of frequencies) is. So the question is: is it correct to connect the output of the NCO (which we DO know is in two's complement) straight to the input of the FFT module? And also, if the module's architecture is 14 bits data resolution and the output data format is fixed point format (a total of 25 output bits for the real part and another 25 for the imaginary), what would the conversion of the following binary number 1000011110111110000111100 to signed decimal format? Thank you all and any help would be apreciated!Link Copied

0 Replies

Topic Options

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

For more complete information about compiler optimizations, see our Optimization Notice.