TWI does not work on custom board with BMD-330 (nRF52810 chipset) even though it works fine on development kits

RE: TWI does not work on custom board with BMD-330 (nRF52810 chipset) even though it works fine on development kits

Ahmad Shakir — Thu, 28 May 2020 13:52:46 GMT

Thank you so much for clarifying this :D

RE: TWI does not work on custom board with BMD-330 (nRF52810 chipset) even though it works fine on development kits

Simonr — Tue, 26 May 2020 07:23:34 GMT

This is because of the debugger on the DK, it likely allows the TWI to "override" the UART logging when you use the same pins for the two, while your custom board seems to prioritize the UART logging instead. You should be able to see that UART logging won't work while the TWI is configured to this pin on your DK.

Best regards,

Simon

RE: TWI does not work on custom board with BMD-330 (nRF52810 chipset) even though it works fine on development kits

Ahmad Shakir — Mon, 25 May 2020 12:28:24 GMT

Hi Simonr,

It turns out you were absolutely right about the pin number 6 being used by UART logging. There is one thing that is still unclear to me. Why does the same code works fine on the development board since the same pin works without any issue on it?

RE: TWI does not work on custom board with BMD-330 (nRF52810 chipset) even though it works fine on development kits

Simonr — Fri, 22 May 2020 09:13:39 GMT

Hi Ahmad

I think you're seeing this busy error because the pins you're using for TWI are already in use by the logger module. By default, pins 5-8 are used by the UART, and I'm guessing you are using the UART for logging in your example. Please try either disabling the logger module or changing the pins for UART or TWI.

Best regards,

Simon