RE: I²C communication between a nrf5240 and a MCP3221

Karl Ylvisaker — Mon, 13 Sep 2021 13:00:19 GMT

Hello,

In addition to Prasad's comment I would like to ask: are you checking the error codes returned by I2C_register_read?
The error codes returned by SDK functions should always be checked, for example by passing them to an APP_ERROR_CHECK.
Are you getting any non-NRF_SUCCESS errors from either call to nrf_drv_twi_tx or nrf_drv_twi_rx? If so, which one?

You should also try to run the TWI Scanner example from the SDK to verify that your hardware connections is correct. The example will scan through all devices on the TWI bus and report any found devices in the log. If all your hardware connections are correct and the TWI Slave is operating as intended it will be found here.

Please also make sure that you have DEBUG defined in your preprocessor defines, like shown in the included image.

This will make a detailed error message be output by your logger in the case that a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK.

For future reference, please use the Insert -> Code option when sharing code here on DevZone.

Best regards,
Karl

RE: I²C communication between a nrf5240 and a MCP3221

Prasad — Sun, 12 Sep 2021 20:59:49 GMT

From the MCP3121 datasheet, "The eighth bit of the slave address determines if the master device wants to read conversion data or write to the MCP3021. When set to a 1, a read operation is selected. When set to a 0, a write operation is selected. There are no writable registers on the MCP3021, therefore, this bit must be set to a 1 to initiate a conversion."

[quote userid="108107" url="~/f/nordic-q-a/79554/i2c-communication-between-a-nrf5240-and-a-mcp3221"]ret_code = nrf_drv_twi_rx(p_twi_master,slave_addr, pdata, bytes);[/quote]

should be sufficient.