Receiving NACK from the slave device after sending the slave address

RE: Receiving NACK from the slave device after sending the slave address

awneil — Fri, 03 May 2019 12:38:35 GMT

So have you resolved this now?

If so, please describe the solution for the benefit of future readers who may come along with similar questions.

And verify the answer:

RE: Receiving NACK from the slave device after sending the slave address

Nirupama — Fri, 03 May 2019 12:28:44 GMT

That is the hardware issue, thanks for the response.

RE: Receiving NACK from the slave device after sending the slave address

Nirupama — Fri, 03 May 2019 08:05:25 GMT

Sure, I will check with that, Thank you. Yes that is the site. I also checked Power-on procedure.

RE: Receiving NACK from the slave device after sending the slave address

awneil — Fri, 03 May 2019 07:56:52 GMT

Again, if the TWI scanner is not detecting it, and other devices on the same bus at the same time are detected, then it has to be something to do with the particular Slave.

So this is nothing to do with Nordic - you are going to have to seek help from the Slave manufacturer.

Review the datasheet, and all available supporting documentation from the manufacturer - make sure you have everything correct in your design

EDIT

Is this the part you're talking about:

https://www.mouser.co.uk/new/kionix/kionix-kx124-1051/

Have you checked out the 'Resources' there?

Have you visited the manufacturer's own site to check for further resources?

In particular, have you got the Evaluation Board:

https://www.mouser.co.uk/new/kionix/kionix-kx124-1051-evb0b0-eval-board/

Even if you don't have it, check out the 'Resources' that go with it ...

RE: Receiving NACK from the slave device after sending the slave address

Nirupama — Fri, 03 May 2019 06:11:06 GMT

I tried adding some delay for startup to complete. It didn't work out. And it is not even detected by TWI scanner. I have connected other sensors and they are getting detected. Why not this?

RE: Receiving NACK from the slave device after sending the slave address

awneil — Thu, 02 May 2019 12:44:35 GMT

If you need clarification of 3rd-party documentation, then you need to contact the 3rd-party for that - it has nothing to do with Nordic!

It sounds perfectly clear to me - what bit don't you understand?

Presumably, the documentation tells you how long "the startup" can be expected to last?

So just wait a bit longer than that before trying to communicate with it!

RE: Receiving NACK from the slave device after sending the slave address

Nirupama — Thu, 02 May 2019 12:25:15 GMT

I haven't tested with any other master, Clock is also fine. But in the datasheet, they mentioned like
Note : if the accelerometer is accessed through I2C protocol before the startup is finished a NACK signal is sent.

This i didn't understand. Do you have any idea?

RE: Receiving NACK from the slave device after sending the slave address

awneil — Thu, 02 May 2019 11:38:11 GMT

[quote userid="74060" url="~/f/nordic-q-a/46853/receiving-nack-from-the-slave-device-after-sending-the-slave-address/184842"]Even with TWI Scanner app, i was not able to detect the tag[/quote]

Then there's something fundamentally wrong!

Have you looked at the I2C lines with a scope or analyser ?

[quote userid="74060" url="~/f/nordic-q-a/46853/receiving-nack-from-the-slave-device-after-sending-the-slave-address/184842"]Under what conditions slave sends NACK even though address is correct? [/quote]

You would have to check the device's documentation for that.

Have you had this slave working with any other Master?

RE: Receiving NACK from the slave device after sending the slave address

Nirupama — Thu, 02 May 2019 11:08:53 GMT

Yes, I checked many times. Even with TWI Scanner app, i was not able to detect the tag. Under what conditions slave sends NACK even though address is correct? The slave address is 0x1E. This address is the correct one.

RE: Receiving NACK from the slave device after sending the slave address

awneil — Thu, 02 May 2019 09:55:15 GMT

Are you sure that the slave is actively sending a NACK?

Remember that a NACK will be seen if there is no slave connected at all ...

Also, a NAK will be seen if the Slave simply ignores the address - which would be the case if you have the wrong address ...

Have you looked at the I2C lines with a scope or analyser ?

Have you tried the TWI Scanner ?