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

hi,

i'm using c6414 connected to MPC8250 by HPI.

i have a problem with the HPI bus (or with the EDMA transaction
triggered by HPI). it happens occasionally when the DSP is under work
load.

after an HPI write (32 bit), the PQSR bit of the HPI's priority queue
(urgent in my case) stays '0', and the data is not written to the
destination?
after 8 writes like that the HRDY stays busy, and the MPC8250 gets a
machine check exception.

maybe this situation rings a bell for someone?
thanks
nir




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

Nir-

> i'm using c6414 connected to MPC8250 by HPI.
>
> i have a problem with the HPI bus (or with the EDMA transaction
> triggered by HPI). it happens occasionally when the DSP is under work
> load.
>
> after an HPI write (32 bit), the PQSR bit of the HPI's priority queue
> (urgent in my case) stays '0', and the data is not written to the
> destination?
> after 8 writes like that the HRDY stays busy, and the MPC8250 gets a
> machine check exception.

What's the "workload"? Is DSP code using DMA channels? If so how many?

Also, what is the destination address; i.e. HPIA value?

-Jeff





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