This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM368+DDR2+TVP5151+Capture_get() == misunderstanding

Other Parts Discussed in Thread: TVP5151, TVP5150

We have DM365EVM, DVSDK4.02 and slightly modified encode demo (output stream broadcating over udp/ip). It works pretty good with PAL input signal.

After we've designed our custom board: davinci dm368, tvp5151 decoder, ddr2 mt47h64m16hr-3 (the same as on the EVM board), and 27MHz as ref freq for decoder and davinci. Then we've made few changes about ref freq & "How to: TVP5150 with DM365EVM + DVSDK4.02" (posted to this forum by senchuss). One thing I have to mention: ddr2 works only on freqs under 150Mhz (SDTIMR & SDTIMR2 were setup accoding to ddr2 datasheet for 277 MHz, 150Mhz and many others; SDCR.18 bit is also set). On higher freqs bootloading process may reset the board or stalls. On my opinion, the cause of the freq problem is in omitting any termination resistors between davinci and ddr2 (but we've tried to observe length&distance tracing routes rules). Am i right? Is drr2@150Mhz enought for 30/25fps PAL capturing and mpeg4 encoding? 

But even after a successful bootstrapping process our encoder program stalls in Capture_get() function (stalls at very first call). printk() added into isr of vpfe_capture.c file indicates no interrupts (those prink() had never call). Oscilloscope says that YOUT and PCLK signals from the decoder are present. (YOUT of tvp5151 are connected to YIN of dm368, but the YCINSWP bit in CCDCFG is set).

Can anybody show us a direction to solving our capture and ddr2 problems?

Can davinci capture to the ddr2@150Mhz?