TWI communication between two nrf52 device

RE: TWI communication between two nrf52 device

Anisa — Mon, 08 Jul 2019 18:33:33 GMT

SCL and SDL pins were interchanged in my HW. Changing pin numbers worked!

RE: TWI communication between two nrf52 device

awneil — Fri, 05 Jul 2019 09:42:41 GMT

Jolly Good.

For the benefit of others who may find this with similar questions, please describe what was the issue (or issues) and how you solved it/them.

And verify the answer:

RE: TWI communication between two nrf52 device

Anisa — Fri, 05 Jul 2019 06:59:28 GMT

I got it working. Thanks awneil.

RE: TWI communication between two nrf52 device

awneil — Thu, 04 Jul 2019 08:31:46 GMT

[quote userid="81289" url="~/f/nordic-q-a/49316/twi-communication-between-two-nrf52-device/196393"]I verified that both nRF52 work as master and can detect another MCU on the I2C bus.[/quote]

detecting a Slave is just the start!

You have a long way to go from there before you have a fully-functional, usable Master implementation!

Again:

[quote userid="6462" url="~/f/nordic-q-a/49316/twi-communication-between-two-nrf52-device/196292"]Make sure you thoroughly test & debug your Master to cope with common problems such as no ACK, unexpected NAK, no pullups, etc[/quote][quote userid="6462" url="~/f/nordic-q-a/49316/twi-communication-between-two-nrf52-device/196292"]Make sure you carefully instrument your Master to report problems such as no ACK, unexpected NAK, no pullups, etc[/quote]

Also instrument it to confirm when things are successful!

RE: TWI communication between two nrf52 device

Anisa — Thu, 04 Jul 2019 06:55:44 GMT

Thank you awneil for your quick reply.

I verified that both nRF52 work as master and can detect another MCU on the I2C bus.

They both could not communicate with each other as master and slave.

I will connect logic analyser and check further.

RE: TWI communication between two nrf52 device

awneil — Wed, 03 Jul 2019 13:26:35 GMT

I2C always needs pullups - it is an inherent part of the way the bus works!

https://www.nxp.com/docs/en/user-guide/UM10204.pdf

I would strongly suggest that you don't try to do both Slave and Master at the same time! Because then you have no idea whether the problem is in your Slave, or in your Master, or in both!

Since being that Master is by far the commonest use case for a Microcontroller, I suggest that you start with that; get it talking to some standard I2C peripheral.

Make sure you thoroughly test & debug your Master to cope with common problems such as no ACK, unexpected NAK, no pullups, etc

Make sure you carefully instrument your Master to report problems such as no ACK, unexpected NAK, no pullups, etc.

You will need an oscilloscope and/or analyser so that you can see what is happening on the I2C lines.

Study the SDK examples.

how to properly post source code: