kai
/
pounder_test
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Adding documentation about double-buffered mode to DACs

This commit is contained in:
Ryan Summers 2020-12-17 14:32:53 +01:00
parent fb1ea765ce
commit ee8f4d849f
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/dac.rs
View File

@ -13,6 +13,16 @@
///! configuring a DMA stream for a number of successive DAC codes, hardware can regularly update ///! configuring a DMA stream for a number of successive DAC codes, hardware can regularly update
///! the DAC without requiring the CPU. ///! the DAC without requiring the CPU.
///! ///!
///! In order to ensure alignment between the ADC sample batches and DAC output code batches, a DAC
///! output batch is always exactly 1 batch after the ADC batch that generated it.
///!
///! The DMA transfer for the DAC output codes utilizes a double-buffer mode to avoid losing any
///! transfer events generated by the timer (for example, when 2 update cycles occur before the DMA
///! transfer completion is handled). In this mode, there should always be a valid buffer in the
///! "next-transfer" double-buffer location for the DMA transfer. Once a transfer completes,
///! software then has exactly one batch duration to properly configure the next buffer before it
///! begins transfer.
///!
///! ## Multiple Samples to Single DAC Codes ///! ## Multiple Samples to Single DAC Codes
///! ///!
///! For some applications, it may be desirable to generate a single DAC code from multiple ADC ///! For some applications, it may be desirable to generate a single DAC code from multiple ADC