https://community.nxp.com/t5/Kinetis-Software-Development-Kit/SDK-2-0-I2C-driver-is-not-properly-detecting-stop-events-when/m-p/533197#M5537 <HTML><HEAD></HEAD><BODY><P><BR />I am using the SDK 2.0 I2C driver with FreeRTOS on a KL16. I am setting up as an I2C slave. I am finding that the driver is not properly detecting stop events when the master is reading data from the slave. Instead the driver continues to send data to the D register and eventually returns an NAK event.</P><P style="min-height: 8pt; padding: 0px;">&nbsp;</P><P>Using an I2C sniffer I can see that the bus did, in fact, send a stop and moves on to communicating to the next device on the bus. For now my solution has been to remove the ifdef I2C_HAS_STOP_DETECT and force the kI2C_SlaveCompletionEvent when I know the entire packet has been read by the master. But I would rather it did not work this way.</P><P style="min-height: 8pt; padding: 0px;">&nbsp;</P><P>The code is nearly identical to the freeRTOS I2C example.</P></BODY></HTML> Fri, 22 Jul 2016 17:43:04 GMT davidfindlay 2016-07-22T17:43:04Z https://community.nxp.com/t5/Kinetis-Software-Development-Kit/SDK-2-0-I2C-driver-is-not-properly-detecting-stop-events-when/m-p/533197#M5537 <HTML><HEAD></HEAD><BODY><P><BR />I am using the SDK 2.0 I2C driver with FreeRTOS on a KL16. I am setting up as an I2C slave. I am finding that the driver is not properly detecting stop events when the master is reading data from the slave. Instead the driver continues to send data to the D register and eventually returns an NAK event.</P><P style="min-height: 8pt; padding: 0px;">&nbsp;</P><P>Using an I2C sniffer I can see that the bus did, in fact, send a stop and moves on to communicating to the next device on the bus. For now my solution has been to remove the ifdef I2C_HAS_STOP_DETECT and force the kI2C_SlaveCompletionEvent when I know the entire packet has been read by the master. But I would rather it did not work this way.</P><P style="min-height: 8pt; padding: 0px;">&nbsp;</P><P>The code is nearly identical to the freeRTOS I2C example.</P></BODY></HTML> Fri, 22 Jul 2016 17:43:04 GMT https://community.nxp.com/t5/Kinetis-Software-Development-Kit/SDK-2-0-I2C-driver-is-not-properly-detecting-stop-events-when/m-p/533197#M5537 davidfindlay 2016-07-22T17:43:04Z https://community.nxp.com/t5/Kinetis-Software-Development-Kit/SDK-2-0-I2C-driver-is-not-properly-detecting-stop-events-when/m-p/533198#M5538 <HTML><HEAD></HEAD><BODY><P>Hi David,</P><P></P><P>I am sorry, but I don't think you have to remove the ifdef I2C_HAS_STOP_DETECT and force the kI2C_SlaveCompletionEvent, because the i2c slave interrupt handler sets this event when STOP flag is set, please kindly refer to the following for details.</P><P><span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"><img src="https://community.nxp.com/t5/image/serverpage/image-id/37343i18069A977C825108/image-size/large?v=v2&amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /></span></P><P>and kI2C_StopDetectFlag is checked in I2C_SlaveGetStatusFlags().</P><P></P><P>Hope that helps,</P><P>Best regards,</P><P>Kan</P></BODY></HTML> Tue, 26 Jul 2016 03:51:21 GMT https://community.nxp.com/t5/Kinetis-Software-Development-Kit/SDK-2-0-I2C-driver-is-not-properly-detecting-stop-events-when/m-p/533198#M5538 Kan_Li 2016-07-26T03:51:21Z