nRF52832 NRF_ERROR_BUSY from nrf_drv_twi_tx()

[serzh]

i used aplication twi_sensor form nRF5_SDK_12.3.0_d7731ad and i use s132.i conected mpu9060 every time get error on my terminl NRF_ERROR_BUSY.There is exemle of codemain.c and scren from terminal d324ssa42d3434234.png what i do wrong?

new main main.c and new terminal d38dkvjxcfk0965234.png i get msg sucses but i have not value from register. i have same resalt without mpu

this is variant main.c as you sad.i get msg sucses but i have not value from register. i have same resalt without mpu

[Jørgen Holmefjord]

Hi,

When the TWI driver is operating in non-blocking mode, you need to wait for the first transfer to finish before you start another one. In the original twi_sensor example, the flag m_xfer_done is used to assure this, but you are not implementing this in your code.

In the function mpu_6050_init, you make a call to mpu_6050_I2C_register_write, which again calls nrf_drv_twi_tx. Righ after that you call mpu_6050_I2C_register_read, which calls both nrf_drv_twi_tx and nrf_drv_twi_rx. Both these function calls will return NRF_ERROR_BUSY if a transfer is allready in progress.

You need to use the flag, or init the TWI driver in blocking mode, by not specifying a handler.

Best regards,

Jørgen

[Jørgen Holmefjord]

You are still calling nrf_drv_twi_rx right after calling nrf_drv_twi_tx and in mpu_6050_I2C_register_read, without waiting for the first transfer to finish. You need to put while(!m_xfer_done) before m_xfer_done = false. I would recommend that you use the flag in main as well, in place of the delays.

[serzh]

i put while(!m_xfer_done) before m_xfer_done = false but. ihve same resalt

ret_code_t mpu_6050_I2C_register_read( uint8_t reg_addr, uint8_t * p_rx_data, uint32_t bytes) { ret_code_t ret_code;

ret_code = nrf_drv_twi_tx(&m_twi_mpu_6050,MPU_6050_I2C_ADDR, &reg_addr, 1, false);

if(ret_code != NRF_SUCCESS)
{
    return ret_code;
}
while(!m_xfer_done);
m_xfer_done = false;
ret_code = nrf_drv_twi_rx(&m_twi_mpu_6050, MPU_6050_I2C_ADDR, p_rx_data, bytes);
return ret_code;

}

[Jørgen Holmefjord]

You should put these two lines before every call to nrf_drv_twi_tx\nrf_drv_twi_rx:

while(!m_xfer_done);
m_xfer_done = false;

Also, make sure that your sensor will actually send the correct read response when you are sending the stop condition after nrf_drv_twi_tx (see last parameter no_stop in the documentation).

[serzh]

i stuk in while(!m_xfer_done); when i usde while(!m_xfer_done); m_xfer_done = false; befor nrf_drv_twi_tx