TWI Transaction Manager and TWIM

[Ros]

Hi,

What is TWI transaction manager? Is this a hardware or just software library? Does it work with TWIM (with easy DMA)?

I have a suggestion that when making an example application it may better to write as a tutorial, or with step by step instructions. For example, the example "twi_master_using_nrf_twi_mngr" is not easy to change to another application as I can't easily find the steps to configure the library/hardware.

[Einar Thorsrud]

Hi,

What is TWI transaction manager? Is this a hardware or just software library? Does it work with TWIM (with easy DMA)?

The TWI transaction manager itself is a library, but it is built on top of the TWI driver. The driver can be configured to be used both with the TWI peripheral (without DMA) and the TWIM peripheral (with DMA), in the exact same way as if you use the driver directly.

I have a suggestion that when making an example application it may better to write as a tutorial, or with step by step instructions. For example, the example "twi_master_using_nrf_twi_mngr" is not easy to change to another application as I can't easily find the steps to configure the library/hardware.

I see your point, and it has been reported before that there should be better documentation. However, I recomend you refer to the TWI transaction manager documentation, which shows how you can include it in any application. You still need to copy-paste and adjust sdk_config.h configuration defines, add required files and include folder, etc, so I agree that it is not on the same level as a tutorial (far from it, in fact).

[Ros]

Hi,

As others posted the documentation link is not accessible to the public, instead  the following link may useful

https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/lib_nrf_twi_mngr.html?cp=7_1_3_54

Is it a good idea to provide a link from API documentation (or from the examples) to the above? Because I was stuck at API documentation and examples, the above link came to my attention very late.

I think the TWI manager is not useful for my case, as there is a delay (100us) is required between the first transaction and the second; nrfx_twim driver is used instead.