https://devzone.nordicsemi.com/f/nordic-q-a/56268/nrf52-bmi160-on-i2cHi, I have a peculiar problem problem with BMI160 and nrf52. BMI160 is connected to nrf52 via pins 12 and 13. I am using peripheral/twi_sensor example. After configuring it via I2c I am able to read the chip ID of 0x1d , but the chip does not go toen-USTelligent Community 13Fri, 10 Jan 2020 03:20:41 GMThttps://devzone.nordicsemi.com/thread/228453?ContentTypeID=1Fri, 10 Jan 2020 03:20:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7e4dedea-0ca3-48fd-acd4-fc06c083fd9eparvathi<p>Jorgen, Thank&nbsp; you for your reply.&nbsp;</p> <p>I could resolve this issue. There was a bug in the code &quot;<span> </span>rslt = nrf_drv_twi_tx(&amp;m_twi, dev_id, reg_data, len + 1, false);&quot; It should be &quot;data&quot; here and not &quot;reg_data&quot;. Thankyou for your help</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/227978?ContentTypeID=1Tue, 07 Jan 2020 17:01:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:38f0a61a-882f-4d23-9728-36b6cebea7f0J&#248;rgen Holmefjord<p>Hi,</p> <p>Can you post the definitions of&nbsp;bmi160_set_power_mode() and&nbsp;bmi160_get_regs()?</p> <p>Can you provide a logic trace of the TWI-bus communication between the nRF and the sensor?</p> <p>I see that in Acc_i2c_Read(), you set the no_stop parameter to false, have you checked that this is correct according to the communication protocol of the sensor, described in the datasheet? Typically, this kind of sensors does not expect a stop between writing the control byte and reading the response, rather a repeated start condition.</p> <p>Best regards,<br />Jørgen</p><div style="clear:both;"></div>