I2C problems in SDK v2.6.0 on nRF5340DK

RE: I2C problems in SDK v2.6.0 on nRF5340DK

Vidar Berg — Mon, 08 Apr 2024 06:01:15 GMT

Thanks for the update and your feedback. It looks like we need add a note for those building for the _ns target. I will report this internally.

RE: I2C problems in SDK v2.6.0 on nRF5340DK

vladimir.k — Mon, 08 Apr 2024 05:55:45 GMT

Thanks! Yes, now it's working. It would be good to add this information to the nRF Connect SDK Fundamentals course (https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-6-serial-com-i2c/topic/exercise-1-6-2/) because it would obviously be repeated among other students (or fix it in the future releases).

RE: I2C problems in SDK v2.6.0 on nRF5340DK

Vidar Berg — Fri, 05 Apr 2024 13:44:42 GMT

Hello,

I was able to reproduce this issue. It seems the problem occurs because logging is now enabled by default in TFM with UART1, which shares a peripheral ID with TWIM1 (see Peripherals with shared ID). This means that TWIM1 will be configured as a secure peripheral. A secure fault is triggered when the main app tries to initialize TWIM1.

Please add the following symbols to your prj.conf to disable TFM logging and see if it fixes the problem:

CONFIG_TFM_SECURE_UART=n

CONFIG_TFM_LOG_LEVEL_SILENCE=y

Best regards,

Vidar

Edit: I found this from the SDK v2.6.0 release notes:

So, I think this explains why the issue started arising after v2.6.0.

EDIT2: The course includes this note now: