Hi all,
We have met a problem.
My program is based on IPNC_RDK_3.5.0.
Iif it runs over 12~24 hour, the resize stop trigger interrupt, sometimes it will print
"m3vpss ] ##################### REISZER OVERFLOW OCCURED: RESTARTING...############################" and some times not.
Our use case is something like the following:
sensor->RSZA------------------------------------------------}
RSZB->dup---->1920x1080------- ------------}->merge->encode->
|-->SCALAR->352x288 ---------------}
|-->SCALAR->720x576
(D1 for tv out, cloesed to decrease the bandwidth in normal time, open when needed)
We didn't use the H3A on chip.
camera and resize resolution:
sensor(or camera) 2336x1760(YUV422) 25fps
RSZA 2592x2048 25fps
RSZB 1920x1080 25fps
SCALAR1 352x288 25fps
encode resolution:
2592x2048(JPEG,5fps)
1920x1080(H264,25fps)
352x288(H264,25fps)
DSP: customized algorithm for vehicle recognition.
The frequency of our customized board:
L3 clk : 220MHz
IVA clk : 450MHz
ISS clk : 560MHz
DSP clk : 750MHz
DSS clk : 200MHz
ARM clk : 1000MHz
DDR clk : 533MHz
The configure of DDR controller:
total 1G bytes.
EMIF0 and EMIF 1 each has 2 16bit ddr chips.
LISA MAP :128byte interleaved.
We have noticed and read the following thread:
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/265001.aspx?pi199607=1
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/p/242555/851247.aspx#851247
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/p/163881/604055.aspx#604055
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/p/323639/1130127.aspx#1130127
and downloaded and compiled the code of new sys_pri.zip.
We have modified the script in init.sh as following:
./bin/sys_pri.out --L3-bw-reg-set HDVICP0 0 0 900 2500&
./bin/sys_pri.out --L3-bw-reg-set ISS 3 3 700 2500&
./bin/sys_pri.out --dmm-pri-set ISS 0&
./bin/sys_pri.out --dmm-pri-set HDVICP0 1&
(It seems that only HDVICP0, ISS, SGX can use --L3-bw-reg-set option, other ID will cause a bus error)
We tried the following values of PBBPR:
0xFFFFFF
0xFFFF20
0xFFFF10
0x90FF30
and tried the flollowing the clock divider values:
a.
ispPrm.clkDivM = 14;
ispPrm.clkDivN = 30;
b.
ispPrm.clkDivM = 10;
ispPrm.clkDivN = 20;
the option we have not tried:
add the vertical blanking line of sensor.
The result of test:
We have not fount a perfect solution of resize hang.
Some times our application can run over 3 days(we have three test equipment), but next time after re-power up, some of them(random) can run only 12 hours~24 hours.
this problem has confused us for a long time.
Please give me some clues for next test.
Thanks a lot.
