<?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>topic RT1170 'MIPI CSI RGB CM7' example change I2C bus &amp;amp; check configuration in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1170-MIPI-CSI-RGB-CM7-example-change-I2C-bus-amp-check/m-p/1590134#M23507</link>
    <description>&lt;P&gt;We are using the MIMXRT1176CVM8A with evkmimxrt1170 sdk version 2.12.1 and the 'csi_mipi_rgb_cm7' example project. The chip is on a custom board where I2C5 goes to the CSI header instead of I2C6.&lt;/P&gt;&lt;P&gt;During the busy loop, the "CAMERA_RECEIVER_GetFullBuffer" call returns the enum "kStatus_CSI_NoFullBuffer" every time. I suspected this is due to the I2C6 bus still being used, leading to the camera not configuring, so I updated the pin configuration.&lt;/P&gt;&lt;P&gt;Once I have updated the pin config and "pin_mux.*" files, then replaced relevant #defines in board.h etc; Is there a way to sanity check the initialisation of the camera and CSI drivers? The camera is a PCAM 5C, utilising the OV5640 sensor.&lt;/P&gt;</description>
    <pubDate>Tue, 31 Jan 2023 01:00:09 GMT</pubDate>
    <dc:creator>wtsmc</dc:creator>
    <dc:date>2023-01-31T01:00:09Z</dc:date>
    <item>
      <title>RT1170 'MIPI CSI RGB CM7' example change I2C bus &amp; check configuration</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1170-MIPI-CSI-RGB-CM7-example-change-I2C-bus-amp-check/m-p/1590134#M23507</link>
      <description>&lt;P&gt;We are using the MIMXRT1176CVM8A with evkmimxrt1170 sdk version 2.12.1 and the 'csi_mipi_rgb_cm7' example project. The chip is on a custom board where I2C5 goes to the CSI header instead of I2C6.&lt;/P&gt;&lt;P&gt;During the busy loop, the "CAMERA_RECEIVER_GetFullBuffer" call returns the enum "kStatus_CSI_NoFullBuffer" every time. I suspected this is due to the I2C6 bus still being used, leading to the camera not configuring, so I updated the pin configuration.&lt;/P&gt;&lt;P&gt;Once I have updated the pin config and "pin_mux.*" files, then replaced relevant #defines in board.h etc; Is there a way to sanity check the initialisation of the camera and CSI drivers? The camera is a PCAM 5C, utilising the OV5640 sensor.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2023 01:00:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1170-MIPI-CSI-RGB-CM7-example-change-I2C-bus-amp-check/m-p/1590134#M23507</guid>
      <dc:creator>wtsmc</dc:creator>
      <dc:date>2023-01-31T01:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: RT1170 'MIPI CSI RGB CM7' example change I2C bus &amp; check configuration</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1170-MIPI-CSI-RGB-CM7-example-change-I2C-bus-amp-check/m-p/1592250#M23556</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/211306"&gt;@wtsmc&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;The easy way is to use an oscilloscope to check I2C signal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jing&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 10:28:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1170-MIPI-CSI-RGB-CM7-example-change-I2C-bus-amp-check/m-p/1592250#M23556</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2023-02-02T10:28:10Z</dc:date>
    </item>
  </channel>
</rss>

