edma_error interrupts on H264 platimun encoder

Ken Feldman

I intergrated the 2_0_0_10 H264 encoder codec into the 3_10_00_19 DVSDK and can capture and encoder video, but the CPU is much more loaded. The IRQ portion of the CPU is running around 25%. What I have noticed is the edma_error interrupt (number 17) is getting called about 40,000 times a second. With the stock h264 codec in the DVSDK I did not see this problem

Any ideas?

Thanks,

Ken

cat /proc/interrupts; sleep 10; cat /proc/interrupts
           CPU0
0:     111363       AINTC vpfe_capture0
3:          0       AINTC dm365_h3a_af
5:      55687       AINTC Imp_Sdram_Irq
6:          0       AINTC dm365_h3a_aew
8:     112730       AINTC davinci_osd
10:      55673       AINTC IRQK_Handler
12:          0       AINTC musb_hdrc
16:      86986       AINTC edma
17:   78861081       AINTC edma_error
32:     409814       AINTC clockevent
33:         10       AINTC free-run counter
39:       4293       AINTC i2c_davinci
40:          6       AINTC serial
41:      17269       AINTC serial
44:       2113 GPIO-AINTC FPGA_interrupt
52:          0       AINTC eth0
53:      26831       AINTC eth0
54:     751996       AINTC eth0
55:          0       AINTC eth0
Err:          0
           CPU0
0:     111979       AINTC vpfe_capture0
3:          0       AINTC dm365_h3a_af
5:      55995       AINTC Imp_Sdram_Irq
6:          0       AINTC dm365_h3a_aew
8:     113345       AINTC davinci_osd
10:      55981       AINTC IRQK_Handler
12:          0       AINTC musb_hdrc
16:      87467       AINTC edma
17:   79283591       AINTC edma_error
32:     412012       AINTC clockevent
33:         10       AINTC free-run counter
39:       4315       AINTC i2c_davinci
40:          6       AINTC serial
41:      17318       AINTC serial
44:       2113 GPIO-AINTC FPGA_interrupt
52:          0       AINTC eth0
53:      26914       AINTC eth0
54:     756257       AINTC eth0
55:          0       AINTC eth0
Err:          0

over 14 years ago

0 Yashwant Dutt over 14 years ago

TI__Genius 17215 points

We are looking into this issue. Will come back shortly.

regards

Yashwant

0 Yashwant Dutt over 14 years ago in reply to Yashwant Dutt

TI__Genius 17215 points

Hi,

We found the root cause of the issue and is fixed. It may take some time to reflect the updated codec package on the official download link. In case you need it at a priority, pls ask your local TI contact to get in touch with us.

regards

Yashwant

0 jan vazen over 13 years ago in reply to Yashwant Dutt

Prodigy 160 points

I have the exact same problem with the latest h264dec (02.00.00.13, also tried older versions), when I enable frame_closedloop_flag, the edma_error interrupts explode when I look at /proc/interrupts, also 45% irq cpu usage reported in top.

With the disabled frame_closedloop_flag, it works OK, no edma_error interrupts, but it takes instead of 17ms to decode 720p about 25ms. Can anyone help me?

Thanks.

0 Veeranna Hanchinal over 13 years ago in reply to jan vazen

TI__Expert 8465 points

Hi Jan,

while updating the codec are you taking "h264v_ti_dma_dm365.a" also? If not please take this also, fix is there in this library.

0 jan vazen over 13 years ago in reply to Veeranna Hanchinal

Prodigy 160 points

I have completely removed the old versions before updating.

But you gave me an idea to experiment with that file and I have tried copying this file from h264enc to h264dec, since they both use it, and now it works! No more edma_error interrupts. The problem is in that file packed with h264dec, looks like library for copying data using DMA.

How does linker deal with this during linking that these both files from h264dec and h264enc are linked to the final executable? Since they seem to contain the same symbols.

0 Veeranna Hanchinal over 13 years ago in reply to jan vazen

TI__Expert 8465 points

h264v_ti_dma_dm365.a lib is common for H264 encoder and H264 decoder. encoder and decoder codec libs will have DMA API calls which are implemented in dma lib and actual linking will happen when build application(.out or dvtb) so finally single defn of DMA call will be preset, so no clash of symbols.

And are you seeing the issue with dma lib came with decoder of version 02.00.00.13? we will check it; it should not be the case we have common DMA source code for encoder and decoder.

0 jan vazen over 13 years ago in reply to Veeranna Hanchinal

Prodigy 160 points

With this version "H264DEC.version.02.00.00.13.wizardversion.0.5.3"

If I simply copy the file from version "H264ENC.version.02.30.00.04.wizardversion.0.5.3" to the h264dec directory, it magically works.

0 Veeranna Hanchinal over 13 years ago in reply to jan vazen

TI__Expert 8465 points

Thanks, We will check dma lib in decoder release.

Can you make this post verify pass?

Thanks and regards,

Veeranna

0 jan vazen over 13 years ago in reply to Veeranna Hanchinal

Prodigy 160 points

How do I do that? I didn't create this thread, so probably can't do it.

0 Pete Eberlein over 12 years ago in reply to jan vazen

Intellectual 580 points

TI needs to hurry up and release a new H264DEC with the fixed h264v_ti_dma_dm365.a. My system is using both H264ENC and H264DEC, and the linker happened to pick the bad dma lib from H264DEC. We suffered performance issues due to the edma errors until I replaced the H264DEC bad dma lib with the good one from H264ENC.

Processors

Processors forum

edma_error interrupts on H264 platimun encoder