Sign in
Search c54x
Subscribe to c54x
c54x by Keywords
5409 | 5416 | AD5 | ADC | BIOS | Boot | Booting | Bootloader | C540 | C5402 | C5409 | C5416 | CCS | Codec | DMA | Dmad | DSK | DSKPlus | Dsplib | EVM | FFT | FIR | Flash | GPIO | HPI | Initialization | Interrupt | JTAG | LOG_printf | MCBSP | RFFT | RTDX | Sampling | STLM | UART | VC540
Ads
Discussion Groups
Discussion Groups | TMS320C54x | Q: problem about dsplib real fft
Technical discussions about the TI C54x DSPs (including the c5401, c5402, c5402a, c5404, c5407, c5409, c5409a, c5410, c5410a, c5416, c5420, c5421, c5441, c549, c5470 and c5471).
Q: problem about dsplib real fft - jamesztyou - Aug 13 12:37:00 2002
|
I had searched the former msgs, but can not find answer. so I post a help message again. follow is the test code where FFTSZ is a const integer 256, noscale defined as 0, scale defined as 1; and rfftws is an Uns array header, pointed to a 256 elements' Uns array, rfftws equals 0x1200(cording to myout.map), data are in Q15 format. //rfft cbrev( rfftws, rfftws, FFTSZ/2 ); rfft ( rfftws, FFTSZ, noscale ); //do actual processing. //rifft cbrev( rfftws, rfftws, FFTSZ/2 ); rifft( rfftws, FFTSZ, scale ); and here is the question, the result is quite different from the former datas... help.. |
(You need to be a member of c54x -- send a blank email to c54x-subscribe@yahoogroups.com )