AD535 | BIOS | Booting | Bootloader | C621 | C6211 | C6415 | C671 | C6711 | C6711DSK | C6713 | CCS | Chassaing | COFF | DAT | DM64 | DM642 | DMA | DSK671 | DSK6711 | EDM | EDMA | EMIF | Emulator | EVM | EVM620 | FFT | FIR | GPIO | Halting | HPI | HWI | IDK | JTAG | LDB | LDH | LDW | Linker | LMS | LOG_printf | Matlab | McBSP | MEM_alloc | MIPS | PCI | PCM3003 | Pipeline | Profiling | QDM | Reset | ROM | RTDX | Sampling | SDRAM | Stack | TEB | THS1206 | TMS320C621 | TMS320C6416 | TMS320C6711 | TMS320C6713 | UART | Vector Table | XBUS | XDS560

DSPers, I am working on McBSP to receive data, and map it to HWI (already use dispatcher to be able to use HWI function that was written in C), so that when McBSP interrupt, it will do the function specified in HWI. But when run, nothing happened. I would like to ask that : 1.Am I right that connect McBSP's interrupt to HWI ? 2.In main(), I wrote MCBSP_enableRcv(hMcbsp0); Is this enough ? 3.In HWI interrupt, I wrote interrupt void MyMcBSP0_Test (void) { a = MCBSP_read(hMcbsp0);} Is this enough ? Thanks In Advance, TR.

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

You can use the McBSP to generate an HWI. That is certainly an acceptable approach. That said, I would strongly recommend that you hook up a DMA channel to the McBSP and use it to process blocks at a time. You will get much more efficiency out of the DSP that way. Andrew E. At 10:53 PM 8/1/2002 -0700, Thanawach Reungnava wrote: >DSPers, > I am working on McBSP to receive data, and map it to >HWI (already >use dispatcher to be able to use HWI function that was >written in C), >so that when McBSP interrupt, it will do the function >specified in >HWI. But when run, nothing happened. I would like to >ask that : >1.Am I right that connect McBSP's interrupt to HWI ? >2.In main(), I wrote > MCBSP_enableRcv(hMcbsp0); >Is this enough ? >3.In HWI interrupt, I wrote >interrupt void MyMcBSP0_Test (void) { > a = MCBSP_read(hMcbsp0);} >Is this enough ? > Thanks In Advance, > TR. > >_____________________________________

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