56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Has anyone successfully used Motorola's split56.asm or split563.asm macros for unscrambling the data after using a N/2-point complex FFT to transform N real data points? I always get garbage out (running on a 56311), whereas my own (much slower) split routine works fine. It would be nice to have some confidence that the Motorola code is OK so I can look for the problem elsewhere... Chris

______________________________
Start your Android Ice Cream Sandwich development on TI's AM35x Sitara ARM Cortex-A8 processor today.



(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

I know this is a very old question, but the same issue just got me as a half-clueless(ful) beginner in this area. I made a few observations about this macro: - it expects a few modulo registers to be left as cfft563 left them (check the references to r? with no initialization of m?) - it expects the IDATA to be the original FFT's input data, and is the _destination_ of the data from this macro. Notice its companion cfft563 is not done in place. To make it work with an inplace complex fft, make a copy of your input data before running the FFT. You could reschedule FFT time away from making the copy by having the data collection write to two areas as the samples come in. Still seems like unnecessary computations though. I'd like to find a good in place real valued FFT. I've seen very good ones in C, but I'm new to 56K assembly. --- In motoroladsp@y..., "cmkessell" <C_Kessell@t...> wrote: > Has anyone successfully used Motorola's split56.asm or split563.asm > macros for unscrambling the data after using a N/2-point complex FFT > to transform N real data points? I always get garbage out (running > on a 56311), whereas my own (much slower) split routine works fine. > > It would be nice to have some confidence that the Motorola code is OK > so I can look for the problem elsewhere... > > Chris

______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )