TWI - Easy DMA

RE: TWI - Easy DMA

wpaul — Tue, 11 Dec 2018 17:28:56 GMT

I don't know offhand if nrf_fstorage_t has a pointer to the TWI register window. The nrfxxx.h header files for each chip define special types for the register overlay structures and they also have macros to define the base addresses. You should be able to do something like:

printf ("enable register: %x\n", NRF_TWI0->ENABLE);

printf ("enable register: %x\n", NRF_TWIM0->ENABLE);

The NRF_TWI0 handle is for using the TWI instance in programmed I/O mode. NRF_TWIM0 should be used when the instance is in EasyDMA mode. Some of the registers are the same, e.g. ENABLE, so you'll get the same result regardless of which you choose, but many others are different, so for actual operation you need to use the right handle depending on the mode.

But yes, if you get back 6, that means the TWI instance is set for EasyDMA master mode.

As for measuring performance, be aware that the two major advantages to using EasyDMA are: 1) You can transmit a block of data at a once instead having to read/write a byte at a time, and 2) while the DMA engine is busy moving the data, the CPU can go off and do other things (i.e. parallelization). TWI/I2C isn't a very high speed interface, so it's possible that you can actually get reasonably good data transfer speed in either mode. So unless you measure very carefully you might not notice much difference. With programmed I/O you may see a little worse performance due to pauses between transmissions of individual bytes (this may be mitigated somewhat if the interface is designed with a FIFO). But using EasyDMA drastically reduces CPU usage.

RE: TWI - Easy DMA

Roei — Tue, 11 Dec 2018 11:30:24 GMT

Hi wpaul,

Did you mean to read ENABLE register through nrf_fstorage_t?

I did it, and I saw the value 6. Does it mean that I'm using Easy DMA for sure?

Thanks!

RE: TWI - Easy DMA

Nguyen Hoan Hoang — Mon, 10 Dec 2018 21:34:27 GMT

Try to hookup a logic analyser and compare signal from both modes to see if there are any differences in the timing.

RE: TWI - Easy DMA

wpaul — Mon, 10 Dec 2018 18:09:37 GMT

In the nRF52 design, you have a set number of instances of various peripherals (SPI. TWI, UART, etc...) Each instance has a memory-mapped block of registers. Note however that there are a couple of possible overlaps:

- Different types of peripheral blocks can share the same instance -- for example, the register block at 0x40003000 can be configured to be either SPI or TWI.

- The same instance can be used for the same kind of peripheral but in either EasyDMA mode or programmed I/O mode.

How do you choose which mode is in use? It depends on the value written to the ENABLE register, which is typically at offset 0x500 within a given instance's register block.

For example, look at the Product Specification document for the nRF52840. Section "4.2.4 Instantiation" gives you an overview of all the peripheral blocks. You'll notice that register block at 0x40003000 can be configured for up to 6 different modes: SPI, SPIS, SPIM, TWI, TWIS and TWIM.

You can only have at most two instances of TWI configured at the same time: one at 0x40003000 and another at 0x40004000. The value written to the enable register, i.e. 0x40003500 and 0x40004500, tells you what mode it's set for.

How do you know the mode value? You have to look at the peripheral description for TWI, TWIS and TWIM. For example, section 6.29 describes TWI (the programmed I/O mode). You'll notice that section 6.29.8.5 documents two values for the ENABLE register: 0 to disable TWI, and 5 to enable TWI.

Now look at section 6.31, which is for TWIM (the EasyDMA master mode). Section 6.31.7.6 documents two values for the ENABLE register as well: 0 to disable TWIM and 6 to enable TWIM.

Note the difference: 5 is for TWI mode (programmed I/O) and 6 is for TWIM (EasyDMA). For TWIS mode, the value is 9. These values also show up in the nrf52xxx.h header files included in the SDK.

The meaning of many of the other registers in the block depends on which value you write. Remember: the same block is used for both modes, but the layout of the register table is different. (In TWI mode for example, the EasyDMA source address register doesn't exist.)

So if you want confirm if a given TWI instance is being used in programmed I/O mode or EasyDMA mode, add some code to read the value from the ENABLE register (0x40003500 for TWI0 and 0x40004500 for TWI1) and print it on the console (or else examine it using the debugger). If it says 5 then you're using programmed I/O mode, and if it says 6 then you're using EasyDMA mode. If it says 0, the instance is disabled. When you set the EASY_DMA flag in the example code, this controls which mechanism the example code uses to program the TWI instance, and you can detect that by checking what value is programmed into the ENABLE register.

RE: TWI - Easy DMA

Martin Lesund — Mon, 10 Dec 2018 15:12:25 GMT

Hi Roei,

Could you please upload your project so I could test it out on my side?

we can make this case private if you do not want to share the code on the public view.

//cheers

RE: TWI - Easy DMA

Roei — Mon, 26 Nov 2018 07:04:56 GMT

Hi Martin,

I don't use any callback handlers.

I think our first step should be indicating easy DMA activation. Maybe I didn't do the right steps. I can't see any difference after using easy DMA, so it's strange.

RE: TWI - Easy DMA

Martin Lesund — Thu, 22 Nov 2018 13:31:52 GMT

Hi Roei,

That's not that too big of packets, could you test with 255 to see if you get any higher throughput.

(btw. the nrf52840 supports 16 bit MAXCNT register, so you could send 65535 bytes in one transfer)

Anyway, the TWI has to send an address for each new transfer, including start/stop/repeated start bits which takes throughput.

Most likely it takes a few µs each time you have to update the buffer, etc. You should also make sure that you do not do anything special in the callback handler that could slow things down. (Like logging etc.)

RE: TWI - Easy DMA

Roei — Wed, 21 Nov 2018 15:55:04 GMT

The configured frequency is 400k. I'm sending packets of 35 bytes.

RE: TWI - Easy DMA

Martin Lesund — Wed, 21 Nov 2018 13:14:42 GMT

Hi Roei,

What frequency have you configured the TWI bus to run at?

If you are able to transfer 24 bytes every 1 ms, this corresponds to 192 kbit/s. The maximum supported frequency of the TWI peripheral is 400 kbit/s.

With the handshaking on the bus and other overhead in the peripheral, this throughput might not be that far from the limit.

How large packets do you send in each transfer?

RE: TWI - Easy DMA

Roei — Mon, 12 Nov 2018 15:06:05 GMT

Hi Martin,

I'm measuring the max running time of a task which sends buffers through twi interface. It takes too long (2-3 milliseconds). I got the same results after using easy DMA. I'm not sure I did the right things.

Thanks

RE: TWI - Easy DMA

Martin Lesund — Mon, 12 Nov 2018 14:58:52 GMT

Hi Roei,

How are you measuring performance?

Also please check out this thread.

RE: TWI - Easy DMA

Roei — Mon, 12 Nov 2018 11:28:45 GMT

Hi Martin,

Thank you! I tried to work by the example, but I didn't see any performance changes. Do I have a way to see if Easy DMA is now activated?

Thanks!

RE: TWI - Easy DMA

Martin Lesund — Mon, 17 Sep 2018 06:34:48 GMT

Hi Roei,

If you look at the TWI sensor example you can see that the:

// <q> TWI0_USE_EASY_DMA  - Use EasyDMA (if present)
 

#ifndef TWI0_USE_EASY_DMA
#define TWI0_USE_EASY_DMA 1
#endif

is set. Please use that example as reference on how you can use eDMA with TWI.

RE: TWI - Easy DMA

Roei — Wed, 12 Sep 2018 12:20:31 GMT

Hi Martin, thanks for the response!

I went through your links, and I still have the same questions:
I'm using SDK15.00, with nrfx_twim interface. Do I need to do anything else besides changing EASY_DMA flag to 1, in order to use easy DMA?

Thanks!

RE: TWI - Easy DMA

Martin Lesund — Tue, 21 Aug 2018 06:22:25 GMT

Hi Roei,

I would like you to take a look at the TWI master documentation and then go through this thread and the links posted on how to use TWI eDMA.