I actually found it was my mistake (I was using the wrong pinout). Thanks! Matias
On Mon, Jan 11, 2021, at 04:46, raiden00pl wrote: > Does your I2C device use I2C_M_NOSTART or I2C_M_NOSTOP flags for > communication ? They are not supported by the current NRF52 I2C > implementation. > > niedz., 10 sty 2021 o 05:42 Matias N. <mat...@imap.cc> napisał(a): > > > I was about to enable error support but I noticed it is disabled in-code. > > From the look of it there's not that > > much else to do but to issue a STOP. > > > > Regarding the error I'm receiving, I'm seeing a NACK for every possible > > address, so I either have the wrong set of > > pins for the device or there something else going on. > > > > Best, > > Matias > > > > On Sun, Jan 10, 2021, at 00:36, Brennan Ashton wrote: > > > If I recall the error handling logic is largely missing for the I2C in > > > interrupt mode. I added some more to improve the situation for polled > > mode. > > > Have you tried that? > > > > > > --Brennan > > > > > > On Sat, Jan 9, 2021, 7:34 PM Matias N. <mat...@imap.cc> wrote: > > > > > > > Hi, > > > > > > > > I'm having a hard time getting I2C working on nRF52840, the I2C read > > > > operation seems to hang (never reaches ISR). Depending on which set of > > pins > > > > (connected to different I2C device) it either hangs on TXSTARTED or I > > see > > > > the ERROR event set to 0x1. Since this is on a closed device I cannot > > > > verify signals so I'm not sure if I'm making a mistake or the I2C code > > is > > > > faulty. Anyone currently using I2C on this chip with code from master? > > > > > > > > Best, > > > > Matias > > > > > >
