nRF9160 SES TWIS (i2c slave) implementation

[Smart.Enrg]

Hi,

I understand there's no high level TWIS (i2c slave) driver for nRF9160 (i.e. in Zephyr); 
as such, I need to use TWIS driver that's part of nrfx, or even lower (HAL) level driver.

Question I have - is there nrfx sample that shows how this could be done, using SES?

Please advise. Thanks.

[Sigurd]

Hi,

Question I have - is there nrfx sample that shows how this could be done, using SES?

I have not seen any samples for this, but anangl explains some of the steps you need to follow in order to get it to work here:

https://github.com/zephyrproject-rtos/zephyr/issues/21445

[Smart.Enrg]

Thanks Sigurd,
I did glance through the link you shared but at the end pabigot warns "the existing API cannot be supported for NRF, so I'm going to close this". I think they are referring to approach in shared link (existing nrf API) being Not supported in Zephyr(?)
pabigot further mentions replacement implementation - https://github.com/zephyrproject-rtos/zephyr/issues/27675 looking through that link, it states right up top - "It is also unsuitable for DMA-based solutions" such as Nordic TWIS, right?
Therefore my question - is the approach in https://github.com/zephyrproject-rtos/zephyr/issues/21445 (over a year old) is it still valid approach with ncs v1.3.1 on nRF9160-DK?
Thanks,
SE

[Sigurd]

Smart.Enrg said:

I think they are referring to approach in shared link (existing nrf API) being Not supported in Zephyr(?)

 As I understand it, pabigot refers to anangl's comment "It is not feasible to use nRF TWIS peripherals via the I2C slave API that is currently available in Zephyr. ".

Smart.Enrg said:

is it still valid approach with ncs v1.3.1 on nRF9160-DK?

Yes, I believe so, it should be fully possible to use the nrfx driver directly instead, with the approach anangl explains.