NRF9160DK i2c device no response

RE: NRF9160DK i2c device no response

Kenneth — Thu, 13 Feb 2025 16:36:41 GMT

Fin tuning it a bit:

Start, h80 [ h40 | WR ], h00, h00, Stop

msg[0].buf = 0x00 0x00;
msg[0].len = 2;
msg[0].flags = I2C_MSG_WRITE | I2C_MSG_STOP;

i2c_transfer_dt(spec, msg, 1);

Start, h80 [ h40 | WR ], h00,
Restart, h81 [ h40 | RD ], h39, h9F NACK, Stop

msg[0].buf = 0x00;
msg[0].len = 1;
msg[0].flags = I2C_MSG_WRITE;

msg[1].buf = 0x39 0x9F;
msg[1].len = 2;
msg[1].flags = I2C_MSG_RESTART | I2C_MSG_READ | I2C_MSG_STOP;

i2c_transfer_dt(spec, msg, 2);

Something along of those lines.

Kenneth

RE: NRF9160DK i2c device no response

Kenneth — Thu, 13 Feb 2025 16:33:59 GMT

I can understand, but take a look at how i2c_transfer_dt() is used in my "example", and search also for drivers in zephyr that use i2c_transfer_dt(), I think you should be able to replicate the same with nRF9160 using the suggestion I provided as guide.

Kenneth

RE: NRF9160DK i2c device no response

drc_ch2 — Thu, 13 Feb 2025 14:47:11 GMT

Kenneth

Thank you for your response. What I am trying to show with the log information is the difference in the I2C capture from when i am trying to read data from the INA219 with the Digilent device as the I2C master versus the NRF9160Dk as the I2C master. What i was trying to show is that there is a difference (with same hw connections) between them and the digilent as the master works (i get data), and the nrf9160 as master (it doesn't work i2C return value of -5).

From what i am seeing with the Digitlent master there is an additional transaction "Start, h80 [ h40 | WR ], h00," between the initial start and restart. The NRF9160 capture does not have intermediary transaction.

RE: NRF9160DK i2c device no response

Kenneth — Thu, 13 Feb 2025 13:32:23 GMT

Hi,

I don't exactly understand the log information, but on a high level I would expect something along the lines of:

Start, h80 [ h40 | WR ], h00, h00, Stop

msg[0].buf = 40/80 00 00;
msg[0].len = 2/3 bytes?;
msg[0].flags = I2C_MSG_WRITE | I2C_MSG_STOP;

i2c_transfer_dt(spec, msg, 1);

Start, h80 [ h40 | WR ], h00,
Restart, h81 [ h40 | RD ], h39, h9F NACK, Stop

msg[0].buf = 40/80 00;
msg[0].len = 1/2 bytes?;
msg[0].flags = I2C_MSG_WRITE;

msg[1].buf = 81/40?;
msg[1].len = 2/3bytes?;
msg[1].flags = I2C_MSG_RESTART | I2C_MSG_READ | I2C_MSG_STOP;

i2c_transfer_dt(spec, msg, 2);

Something along of those lines.

Kenneth