right.. so an interrupt handler that deals with USART ERR condix and buffer handling (about 4 lines of C) will be just fine.


On 7/09/2016 8:05 AM, Bruce Perens wrote:
Glenn, he wants to be a CAT target or host.

On Tue, Sep 6, 2016 at 2:51 PM, glen english <g...@cortexrf.com.au> wrote:
and furthermore to my previous USART post

Eric, you are going to have to implement a USASRT interrupt handler anyway.
why ?
Because you need to handle an error condition as it happens. This is for any peripheral, DMA or not.

So, using the usart, just have a single IRQ handler  that does everything, and enable all IRQ flags
so it is a catch all.


Now, if you want fast SPI, so 42 Mbps (what I do on all four ports)
I use DMA for transfer , but I still have a interrupt but have the IRQ flags only for errors- IE normal TXE or RXNE dont generate interrupts (they trigger a DMA xfer) in that case but ERR does.

The peripherals are quite complex compared to the AVR days. And poorly behaved.

Read the errata for the chip part number you have
With 20 page errata, there will be something affecting what you are doing....


glen


------------------------------------------------------------------------------
_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to