How to handle NACK in I2C (TWI) communication.

RE: How to handle NACK in I2C (TWI) communication.

Simon — Tue, 19 Mar 2019 08:56:51 GMT

I think this is the right approach, and it seems like the reason for the NACK signal is due to the sensor being busy at the moment. However, I found a nice blog post here that explains how to handle I2C NACK signals.

Best regards,

Simon

RE: How to handle NACK in I2C (TWI) communication.

powerup — Wed, 13 Mar 2019 01:31:23 GMT

Hi,

I haven't found the exact cause of getting a NACK yet.
Thus, the code was modified as follows to enable it to function even when it received NACK.

void IQS263_reg_read(uint8_t reg, uint8_t* rx, uint8_t len){
    ret_code_t err_code;

    uint8_t myTX[1] = {reg};
    m_xfer_done = false;
    do{
      while(nrf_gpio_pin_read(RDY) == 1);
      err_code = nrf_drv_twi_tx(&CDC_twi_master, CDC_ADDRESS, myTX, 1, true);
      APP_ERROR_CHECK(err_code);
      nrf_delay_us(500);
    }while (m_xfer_done == false);
    //while (m_xfer_done == false);

    err_code = nrf_drv_twi_rx(&CDC_twi_master, CDC_ADDRESS, rx, len);
    APP_ERROR_CHECK(err_code);
    nrf_delay_ms(1);
}

We used "do,while" instead of "while" to send the data again when we received "nack".
Is there any problem with this?
Or is there another way?

(It would be best not to receive the NACK, but we haven't found the exact cause. T^T)

Best regards,

RE: How to handle NACK in I2C (TWI) communication.

Simon — Mon, 11 Mar 2019 13:52:03 GMT

Receiving a NACK indicates that something is wrong, and according to this document it may be due one of the following conditions:

"The receiver is unable to receive or transmit because it is performing some real-time function and is not ready to start communication with the master."
"During the transfer, the receiver gets data or commands that it does not understand."
"During the transfer, the receiver cannot receive any more data bytes."

You should check with your sensor, if any of the following conditions may happen.

Best regards,

Simon