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.

dm6467 - Raw VPIF Control Signals



Hello,

we are using the DaVinci's VPIF to accept large amounts of incoming data.  Some of this data will be imagery, some will be meta data, such as frame number, etc.  We have thought of several different schemes of doing this, and have a few questions to clarify which scheme has the best chance of working.

Ideally, we would like to send one large packet of data at a time, without line delimitation.  With this in mind:

  1. Page 23 of SPRUER9D (November, 2009), states that the maximum screen size that is supported in frame format is 2048 x 1536.  
    1. Does this mean that we may send an arbitrary frame size as long as it is within 31,45,728 (2048*1536) pixels (i.e. would a 4x786,432 frame be valid)? 
    2. Or does it mean that we may send an arbitrary frame size as long as each dimension is within its respective boundary (i.e. 1024x768)?
    3. Is there another format to send data via raw VPIF other than the frame format?
  2. If we must use line delimitation, we would like to send the meta data as an independent "line".
    1. Must all the lines the be same length, or can our meta data line be different from the image line lengths?  i.e. could we send a frame with the first line (meta data) being 4 bytes long while the following image lines all be 1024 bytes long?
    2. If the previous is true, how would we calculate the minimum 3-line vertical line blanking on the raw_v_valid control line (SPRUE9D, page 24), since our lines are different lengths?

Thank you very much for your help!

  • Answered below.

    r_robotics said:

    Hello,

    we are using the DaVinci's VPIF to accept large amounts of incoming data.  Some of this data will be imagery, some will be meta data, such as frame number, etc.  We have thought of several different schemes of doing this, and have a few questions to clarify which scheme has the best chance of working.

    Ideally, we would like to send one large packet of data at a time, without line delimitation.  With this in mind:

    1. Page 23 of SPRUER9D (November, 2009), states that the maximum screen size that is supported in frame format is 2048 x 1536.  
      1. Does this mean that we may send an arbitrary frame size as long as it is within 31,45,728 (2048*1536) pixels (i.e. would a 4x786,432 frame be valid)? answer: NO
      2. Or does it mean that we may send an arbitrary frame size as long as each dimension is within its respective boundary (i.e. 1024x768)? answer: NO
      3. Is there another format to send data via raw VPIF other than the frame format? answer: NO
    2. If we must use line delimitation, we would like to send the meta data as an independent "line".
      1. Must all the lines the be same length, or can our meta data line be different from the image line lengths?  i.e. could we send a frame with the first line (meta data) being 4 bytes long while the following image lines all be 1024 bytes long? answer: NO
      2. If the previous is true, how would we calculate the minimum 3-line vertical line blanking on the raw_v_valid control line (SPRUE9D, page 24), since our lines are different lengths?

    Thank you very much for your help!

     

  • Nagabhushana,

    Thank you for your help, however, please explain how 'a' and 'b' of question 1 can both be false.  What resolutions are supported ?

     

    Thanks

  • For question 1b., if the size is arbitrary but still a constant over all the frames, it is OK to capture. Of you are using RAW mode, you need to configure the timings accordingly, and if you use embedded sync mode, you need to make sure that all of your data (meta or not) is with 16-235.

    Here I hope arbitrary does not mean a different size for every frame.

     

    -Manju

     

  • r_robotics,

    I thought that you are mentioning about 'non-constant frame size(arbitrary)'  in questions 1a. and 1b.  As Manju mentioned above, if it is constant, it should be OK. 2 threads(links below) are active which are relating VPIF raw capture. Please refer them,  you might find them useful, experts have clarified lot of queries.

    http://e2e.ti.com/support/embedded/f/354/p/95683/337197.aspx#337197

    http://e2e.ti.com/support/embedded/f/354/t/92939.aspx