<?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のトピックUrgent: Issues with camera frame buffer</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Urgent-Issues-with-camera-frame-buffer/m-p/624719#M94820</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From past two weeks, facing issues with my user-define data type supported camera and iMX.&lt;BR /&gt;I've configured the iMX MIPI driver for IPU GENERIC to process the raw data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the MIPI exercisor setup which will send user defined data format image (here, I'm not using my MIPI camera) to iMX MIPI data path.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is my test scenario:&lt;BR /&gt;I've configured the MIPI exercisor to send 1440069 bytes of user defined data format image&amp;nbsp; (because my actual camera will send the data 1440069bytes)&lt;BR /&gt;My user application doesn't know about the width and height but size alone, so I will define the height and width based on the size requested by our user v4l2 application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Say for ex:&lt;BR /&gt;Requested size and Camera user defined data size is 1440069bytes&lt;BR /&gt;I will take square root for the given size and make it to 8bit divisible (stride limitation) and assign that value to width and height values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS : The problem here is that, I can't use 1200*1200(1440000bytes), if I use that, I lose some of the data (69bytes), so I will configure to next 8bit divisible width and height i.e 1208x1808 resolution.&lt;BR /&gt;I will get 1459264bytes data then I will remove the 19295bytes of data (1459264 - 1440069 = 19295)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mxc_v4l2_capture.c&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;width_height = int_sqrt(size)&lt;BR /&gt;//Code for make it to be 8bit divisible&lt;BR /&gt;size = f-&amp;gt;fmt-&amp;gt;pix.sizeimage; //Setting user defined data size to size&lt;BR /&gt;f-&amp;gt;fmt-&amp;gt;pix.width = width_height; //Setting width&lt;BR /&gt;f-&amp;gt;fmt-&amp;gt;pix.height = width_height; //Setting height&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1208*1208 = 1459264bytes (1440069bytes)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After this changes, iMX was able to capture the frames (1459264bytes) but it has data of second frame buffer (i.e mixed of 1st and 2nd frame) due to 1208*1208 configurations.&lt;BR /&gt;Do we have any settings to set zero after 1440069bytes (i.e actual data) ?&lt;BR /&gt;Or how we can address the problem ?&lt;BR /&gt;Or any different approach, any insights on this issue ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your support.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Titus S.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Dec 2016 10:13:02 GMT</pubDate>
    <dc:creator>titusstalin</dc:creator>
    <dc:date>2016-12-19T10:13:02Z</dc:date>
    <item>
      <title>Urgent: Issues with camera frame buffer</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Urgent-Issues-with-camera-frame-buffer/m-p/624719#M94820</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From past two weeks, facing issues with my user-define data type supported camera and iMX.&lt;BR /&gt;I've configured the iMX MIPI driver for IPU GENERIC to process the raw data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the MIPI exercisor setup which will send user defined data format image (here, I'm not using my MIPI camera) to iMX MIPI data path.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is my test scenario:&lt;BR /&gt;I've configured the MIPI exercisor to send 1440069 bytes of user defined data format image&amp;nbsp; (because my actual camera will send the data 1440069bytes)&lt;BR /&gt;My user application doesn't know about the width and height but size alone, so I will define the height and width based on the size requested by our user v4l2 application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Say for ex:&lt;BR /&gt;Requested size and Camera user defined data size is 1440069bytes&lt;BR /&gt;I will take square root for the given size and make it to 8bit divisible (stride limitation) and assign that value to width and height values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS : The problem here is that, I can't use 1200*1200(1440000bytes), if I use that, I lose some of the data (69bytes), so I will configure to next 8bit divisible width and height i.e 1208x1808 resolution.&lt;BR /&gt;I will get 1459264bytes data then I will remove the 19295bytes of data (1459264 - 1440069 = 19295)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mxc_v4l2_capture.c&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;width_height = int_sqrt(size)&lt;BR /&gt;//Code for make it to be 8bit divisible&lt;BR /&gt;size = f-&amp;gt;fmt-&amp;gt;pix.sizeimage; //Setting user defined data size to size&lt;BR /&gt;f-&amp;gt;fmt-&amp;gt;pix.width = width_height; //Setting width&lt;BR /&gt;f-&amp;gt;fmt-&amp;gt;pix.height = width_height; //Setting height&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1208*1208 = 1459264bytes (1440069bytes)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After this changes, iMX was able to capture the frames (1459264bytes) but it has data of second frame buffer (i.e mixed of 1st and 2nd frame) due to 1208*1208 configurations.&lt;BR /&gt;Do we have any settings to set zero after 1440069bytes (i.e actual data) ?&lt;BR /&gt;Or how we can address the problem ?&lt;BR /&gt;Or any different approach, any insights on this issue ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your support.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Titus S.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Dec 2016 10:13:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Urgent-Issues-with-camera-frame-buffer/m-p/624719#M94820</guid>
      <dc:creator>titusstalin</dc:creator>
      <dc:date>2016-12-19T10:13:02Z</dc:date>
    </item>
  </channel>
</rss>

