NR52832 I2C problem

RE: NR52832 I2C problem

catelain — Tue, 07 Nov 2017 08:38:18 GMT

Thanks its working better. Regards Guillaume

RE: NR52832 I2C problem

MartinBL — Tue, 31 Oct 2017 23:17:35 GMT

In your main.c file you configure the TWI in non-blocking mode. You need to wait for the first tx to complete and for the event handler to be called before you start the rx. In your code there is a flag called m_xfer_done, that is set to true in the twi_handler. You can use this flag by setting it to false before you start each TWI transfer and then wait for it to be set to true again before you start the next transfer.

It is also always good practice to check the return codes in your code with APP_ERROR_CHECK(err_code);

RE: NR52832 I2C problem

Jason Hendrix — Tue, 31 Oct 2017 16:52:20 GMT

Hi, I don't know about your first question, but I recently developed something that sounds like your second question. Here's my code to do a write/restart/read. regNum is a uint8_t.:

// Address and sub-address IMU; no I2C stop 
ret_code_t err_code = nrf_drv_twi_tx(&SensorTWI, SENSOR_IMU_ADDR, &regNum, 1, true);

// Read nBytes from the specified offset.  This is a "repeated start" from 
// the transaction started by twi_tx */
err_code = nrf_drv_twi_rx(&SensorTWI, SENSOR_IMU_ADDR, buf, nBytes);

Hope that helps.