Supper Weird I2C faliture

[Meh]

Hey Devzone community

I have a super weird I2C problem.

While configuring, everything is fine - however, when I'm trying to use the I2C API read_register and write_register functions, I'm getting the 0X0BAE0001 error (Internal error), which corresponds to a connection error - even though it just confirmed the connection microseconds before. 

I tried it in multiple DKs, and also colleagues of mine are suffering from the same problem.

Any suggestion?

I've used this method to configure the I2C device, and the program is compiled perfectly.

I'm using 832dk and 840dk  with NCS v1.9.1.

[Michal]

Hello,

Have you checked the connection with a logic analyzer or an oscilloscope?

0x0BAE0001 error means "TWI error: Address not acknowledged.", which is when your I2C peripheral returns a NACK, because of a wrong I2C address.

There was also an earlier case with that error, where it was a hardware issue.

Best regards,

Michal

[Meh]

Well.

I tried scanning for different sensors, and the target DEVKIT for that specific sensor appears defective.