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.

DM648 CAPEN timing on 16 bit raw capture

Does anyone know if video capture only happens when CAPEN is high or whether a rising edge on CAPEN causes a block of pixels to be acquired? This is for 16-bit raw capture on a DM648.

Our application is entirely bespoke and the image is passed over from an FPGA on the video port interface at a fairly slow rate (around 1 fps). We want to increase image throughput at our processing stage by braking up the image block into sub frames. At the moment we use CAPEN to span an entire frame which gets passed into our processing buffer. We want to break the CAPEN into about 1/8th of a frame and think this may be possible using single rising edge pulses to trigger a block of pixels to be acquired. We already use data contained within the initial line to indicate frame start information so synchronisation wouldn't be a problem. The system is real time so we don't want to interrupt the pixel capture in this transfer.

Are there any video capture timing diagrams available for the DM648 that show the raw capture mode?

I have been reading the SPRUEM1B Video Port Users Guide but this only seems to show timing diagrams for the display modes. I also note that section 3.7 indicates that "...the data is sampled by the interface only when the CAPEN signal is active", however we suspect that this is not true all of the time.

 Thanks

Paul Kushner

 

 

  • Hi Paul,

    Some comments:

    - Timing diagram are available in the DM648 datasheet. Typically CAPENA is using the VPxCTL0 signal (see section 1.4 of SPRUEM1B) and VPxCTL0 timings for cpature are shown at page 122 of the datasheet - SPRS372H.

    - The below is written in section 3.7 of SPRUEM1B:
    "The CAPEN signal must go inactive for a minimum of two VPCLK cycles after the pixel count has expired. Keeping the CAPEN signal active after the pixel count
    expires may cause a loss of pixels; therefore, it is not recommended to permanently enable the CAPEN signal during raw data capture mode."

    This means that the CAPEN signal has a relation with the value of the the pixel counter that is programmed in the video port.

    Best regards,

    Anthony

  • Thanks for the reply.

    The timing diagrams show the setup / hold requirements. I would like a diagram showing the constraints of these signals to each other (VP[N]CTLx etc) for the different video capture modes at a functional level. Does such a thing exist please?

    What happens if CAPEN goes inactive before the pixel count has expired? Or is the statement (in section 3.7 of SPRUEM1B) clarifying that this may not be done?

    Regards

    Paul

  • Paul,

    - Unfortunately there are no such timings available. The timings reflect the way each device is tested on the production chain. The VP timings shown in the DM648 datasheet are the one that are production tested. Other timings (like between CTL signals) are not tested.

    - Every valid pixel need to be taken into accoung by the pixel counter. CAPEN need to be active for the given pixel to be acquired therefore it need to be active for the acquisition windows that is set up via the counter.
    Then there is the additionnal requirement of CAPEN being inactive for 2 pixel clocks mentionned in my previous post.

    Hope it helps.

    Anthony