<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックRe: NTSC field order flipped with e-CAMNT_MX53x</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276399#M30859</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I haven't written a patch for the macros, instead I used an unsigned value that yielded the desired signed value.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Jul 2014 02:05:33 GMT</pubDate>
    <dc:creator>fcs</dc:creator>
    <dc:date>2014-07-07T02:05:33Z</dc:date>
    <item>
      <title>NTSC field order flipped with e-CAMNT_MX53x</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276394#M30854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are capturing NTSC video using an e-consystems e-CAMNT_MX53x (using tvp5147m1_tvin.ko) plugged into an i.MX53 Quick Start Board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We run the e-consystems demo program selecting option 2 for NTSC and option 5 to combine the odd and even fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The field order is flipped, &lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;&lt;SPAN lang="EN" style="font-family: Arial; font-size: 10pt;"&gt;I think it is related to analog PAL being "upper field first" and NTSC being "lower field first". It is as if the capture board never switches to NTSC field order.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have tried two different NTSC video sources, one of which was a camcorder.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However there is no field order problem with PAL signals.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We believe there is something missing from the e-consystems drivers that tells the capture board to interpret the fields correctly. We have looked in the i.MX53 Reference Manual but haven't found what hardware interface controls this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Apr 2013 06:31:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276394#M30854</guid>
      <dc:creator>fcs</dc:creator>
      <dc:date>2013-04-19T06:31:45Z</dc:date>
    </item>
    <item>
      <title>Re: NTSC field order flipped with e-CAMNT_MX53x</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276395#M30855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt;I am looking into the control registers for the TVP5147M1. I have tried setting &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt;tvp5147m1_write_reg(REG_SYNC_CONTROL, 0x10);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt;to change the polarity of the FID (Field ID?)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt;and&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt;tvp5147m1_write_reg(REG_FID_CONTROL, 0x01 );&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt;where I’ve defined&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt;#define REG_FID_CONTROL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (0x57)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;&lt;A href="http://pdf1.alldatasheet.com/datasheet-pdf/view/227323/TI/TVP5147M1.html" title="http://pdf1.alldatasheet.com/datasheet-pdf/view/227323/TI/TVP5147M1.html"&gt;http://pdf1.alldatasheet.com/datasheet-pdf/view/227323/TI/TVP5147M1.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt;I have tried each of the above together and alone (with the other defaulted) and nothing has changed the field order problem with NTSC. I note that it looks OK when the image is slowly rolling before synchronisation, but not when it has ceased rolling.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM style="font-family: Arial;"&gt;2.11.26 Sync Control Register&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 8pt;"&gt;Subaddress 32h&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 8pt;"&gt;Default 00h&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-size: 8pt; font-family: Arial;"&gt;7 6 5 4 3 2 1 0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 8pt;"&gt;Reserved Polarity FID Polarity VS Polarity HS VS/VBLK HS/CS&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;Polarity FID: determines polarity of FID terminal&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;0 = First field high, second field low (default)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;1 = First field low, second field high&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM style="font-size: 10pt; font-family: Arial;"&gt;2.11.48 Field ID Control Register&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;Subaddress 57h&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;Default 00h&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-size: 10pt; font-family: Arial;"&gt;7 6 5 4 3 2 1 0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;656 version FID control&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;656 Version&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;0 = ITU-R BT.656-4 (default)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;1 = ITU-R BT.656-3&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;FID control&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;0 = 0→1 adapts to field 1, 1→0 adapts to field 1+ field 2 (default)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 10pt;"&gt;1 = 0→1 adapts to field 2, 1→0 adapts to field 1+ field 2 (for TVP5147M1 EVM)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; color: navy; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Apr 2013 02:41:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276395#M30855</guid>
      <dc:creator>fcs</dc:creator>
      <dc:date>2013-04-22T02:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: NTSC field order flipped with e-CAMNT_MX53x</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276396#M30856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;TI replied to my query on their site very promptly&lt;/P&gt;&lt;P&gt;&lt;A href="http://e2e.ti.com/support/data_converters/videoconverters/f/376/p/260421/911152.aspx"&gt;http://e2e.ti.com/support/data_converters/videoconverters/f/376/p/260421/911152.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Seems the problem needs to be fixed using a negative Interlace Offset.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Apr 2013 00:37:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276396#M30856</guid>
      <dc:creator>fcs</dc:creator>
      <dc:date>2013-04-24T00:37:40Z</dc:date>
    </item>
    <item>
      <title>Re: NTSC field order flipped with e-CAMNT_MX53x</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276397#M30857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The NTSC field flip problem is solved.&lt;/P&gt;&lt;P&gt;I have found a bug in ipu_param_mem.h, the macro ipu_ch_param_mod_field can't handle negative signed values properly, as required to set a negative interlace offset (ILO). Same would probably apply to macro ipu_ch_param_set_field&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Apr 2013 05:07:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276397#M30857</guid>
      <dc:creator>fcs</dc:creator>
      <dc:date>2013-04-24T05:07:28Z</dc:date>
    </item>
    <item>
      <title>Re: NTSC field order flipped with e-CAMNT_MX53x</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276398#M30858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would you be able to post a patch for ipu_param_mem.h that fixes those macros? Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Oct 2013 14:07:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276398#M30858</guid>
      <dc:creator>donfreiling</dc:creator>
      <dc:date>2013-10-02T14:07:32Z</dc:date>
    </item>
    <item>
      <title>Re: NTSC field order flipped with e-CAMNT_MX53x</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276399#M30859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I haven't written a patch for the macros, instead I used an unsigned value that yielded the desired signed value.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2014 02:05:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276399#M30859</guid>
      <dc:creator>fcs</dc:creator>
      <dc:date>2014-07-07T02:05:33Z</dc:date>
    </item>
    <item>
      <title>Re: NTSC field order flipped with e-CAMNT_MX53x</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276400#M30860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have solved the problem setting NTSC active_top field to 4 in mxc_v4l2_capture.c&lt;/P&gt;&lt;P&gt;with a value of 3 as recommended around the community (instead of the default value 13), the captured frames stop rolling but the fields are flipped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;{&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt; /*! NTSC */&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .v4l2_id = V4L2_STD_NTSC,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .name = "NTSC",&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .raw_width = 720,&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt; /* SENS_FRM_WIDTH */&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .raw_height = 525,&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt; /* SENS_FRM_HEIGHT */&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .active_width = 720,&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt; /* ACT_FRM_WIDTH */&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .active_height = 480,&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt; /* ACT_FRM_HEIGHT */&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .active_top = 4,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .active_left = 0,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; },&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Oct 2014 16:13:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NTSC-field-order-flipped-with-e-CAMNT-MX53x/m-p/276400#M30860</guid>
      <dc:creator>augusto</dc:creator>
      <dc:date>2014-10-22T16:13:32Z</dc:date>
    </item>
  </channel>
</rss>

