It seems there is no example shows how to deal with it. kStatus_I2C_Busy is caused by I2Cx->S.BUSY register bit. When busy, it is set by hardware, which means a start condition is detected on bus. It is cleared when a stop condition is detected on bus. Please use a oscilloscope to check the waveform. I guess a previous communication sequence was not ended correctly.