Updating timer compare offsets
This commit is contained in:
parent
598a48b178
commit
7a2f950667
@ -246,7 +246,7 @@ macro_rules! adc_input {
|
||||
// Generate DMA events when an output compare of the timer hits the specified
|
||||
// value.
|
||||
trigger_channel.listen_dma();
|
||||
trigger_channel.to_output_compare(2);
|
||||
trigger_channel.to_output_compare(2 + $index);
|
||||
|
||||
// The trigger stream constantly writes to the SPI CR1 using a static word
|
||||
// (which is a static value to enable the SPI transfer). Thus, neither the
|
||||
|
@ -14,7 +14,7 @@
|
||||
///! 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 2 batches after the ADC batch that generated it.
|
||||
///! output batch is always exactly 3 batches 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
|
||||
@ -134,7 +134,7 @@ macro_rules! dac_output {
|
||||
// Generate DMA events when an output compare of the timer hitting zero (timer roll over)
|
||||
// occurs.
|
||||
trigger_channel.listen_dma();
|
||||
trigger_channel.to_output_compare(0);
|
||||
trigger_channel.to_output_compare(4 + $index);
|
||||
|
||||
// The stream constantly writes to the TX FIFO to write new update codes.
|
||||
let trigger_config = DmaConfig::default()
|
||||
|
Loading…
Reference in New Issue
Block a user