<?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 Re: MMA8653FC read data error in Sensors</title>
    <link>https://community.nxp.com/t5/Sensors/MMA8653FC-read-data-error/m-p/242159#M322</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Roy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;The MMA8653FC signals an interrupt by driving the INTx output either low or high depending on the setting of the IPOL bit in the CTRL_REG3 register. A selected interrupt pin on your MCU needs to be configured in accordance with this setting (falling edge or rising edge). To deassert the interrupt on the MMA8653FC, it is necessary to read the appropriate status register for the embedded functions or X, Y, Z data output registers (0x01 - 0x06) for the DRDY and FIFO. I do not recommend to perform these I2C reads and any operations with the data in ISRs, I would leave it up to non-interrupt code. It is a good practice to keep ISRs as short as possible.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;I hope it helps.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;Tomas&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Dec 2013 14:20:35 GMT</pubDate>
    <dc:creator>TomasVaverka</dc:creator>
    <dc:date>2013-12-04T14:20:35Z</dc:date>
    <item>
      <title>MMA8653FC read data error</title>
      <link>https://community.nxp.com/t5/Sensors/MMA8653FC-read-data-error/m-p/242158#M321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,all&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I set the ODR to 50HZ, and use INT1 ping to trigger a data read. Since my CPU can only set to use rising/falling edge interrupt. so I need to read data several time before INT1 pin go high. Everything go whell when I only read back data and return the interrupt quickly. But if I Insert a data calculate function in the interrupt service function the chip would&amp;nbsp; be&amp;nbsp; not ACK for I2C data read after server Interrupt. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Is there something wrong?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Roy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Feb 2026 21:25:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/MMA8653FC-read-data-error/m-p/242158#M321</guid>
      <dc:creator>roysit</dc:creator>
      <dc:date>2026-02-03T21:25:47Z</dc:date>
    </item>
    <item>
      <title>Re: MMA8653FC read data error</title>
      <link>https://community.nxp.com/t5/Sensors/MMA8653FC-read-data-error/m-p/242159#M322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Roy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;The MMA8653FC signals an interrupt by driving the INTx output either low or high depending on the setting of the IPOL bit in the CTRL_REG3 register. A selected interrupt pin on your MCU needs to be configured in accordance with this setting (falling edge or rising edge). To deassert the interrupt on the MMA8653FC, it is necessary to read the appropriate status register for the embedded functions or X, Y, Z data output registers (0x01 - 0x06) for the DRDY and FIFO. I do not recommend to perform these I2C reads and any operations with the data in ISRs, I would leave it up to non-interrupt code. It is a good practice to keep ISRs as short as possible.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;I hope it helps.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;Tomas&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2013 14:20:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/MMA8653FC-read-data-error/m-p/242159#M322</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2013-12-04T14:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: MMA8653FC read data error</title>
      <link>https://community.nxp.com/t5/Sensors/MMA8653FC-read-data-error/m-p/242160#M323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tomas,&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Thanks for your advice. May be I put data operation in the ISR is the problem. I would try to take it out.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Many Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Roy&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Dec 2013 01:52:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/MMA8653FC-read-data-error/m-p/242160#M323</guid>
      <dc:creator>roysit</dc:creator>
      <dc:date>2013-12-05T01:52:17Z</dc:date>
    </item>
  </channel>
</rss>

