TWI interface locks up when MCLK on I2S is activated

RE: TWI interface locks up when MCLK on I2S is activated

Jørgen Holmefjord — Tue, 10 Jan 2023 16:26:01 GMT

Hi,

I'm not sure how the I2S could affect that, but there is some improvements in the TWIM driver in NRFX v1.8.2, related to bus lockup when a slave misbehaves:

Fixed an issue in the TWI driver that would make the driver stuck when a premature STOP condition was generated by a slave device. The driver now handles this situation properly and signals that a bus error occurred."

Could you try to upgrade your SDK version (or NRFX version), to see if this fix helps with your problem? NRFX v1.8.6 was included in nRF5 SDK v17.0.2.

Best regards,
Jørgen

RE: TWI interface locks up when MCLK on I2S is activated

John Blackburn — Tue, 10 Jan 2023 15:44:45 GMT

We are using SDK 15.2

The I2C is on P0.14 and P0.15

The I2S is on P0.20, P0.21, P0.22 and P0.23. I'm only using the data out since we aren't using the CODEC to sample, only generate.

I'm also using a UART for communications with another processor and a SPI for flash. Everything else is just I/O

I've scoped the TWI lines along with the MCLK and I'm not seeing any noise that would explain the problem. My 16MHz MCLK is clean and my 100KHz I2C shows no sign of crosstalk or interference. I also turned on the bus translator and it is able to decode the bus without any problem

I'll see if I can get a code snippet from my software guy.

RE: TWI interface locks up when MCLK on I2S is activated

Jørgen Holmefjord — Tue, 10 Jan 2023 09:18:18 GMT

Hi,

Like you said, the I2S and TWI peripherals are not related or have shared resources (apart from GPIOs), so there should not be any issues using both the the same time.

Can you post more details about your setup?

Which SDK are you using?
Which GPIOs are you using for the two peripherals?
Can you post your code for initializing/configuring the peripherals?
Do you have other modules enabled in the application? E.g. UART/logger, BSP (buttons/LEDs), etc?
Have you checked the TWI bus with a logic analyzer, to see if there are any noise/interference that can explain why this issue occurs?

Best regards,
Jørgen