/**
@page DAC_SignalsGeneration DAC Signals generation example
@verbatim
******************************************************************************
* @file DAC/DAC_SignalsGeneration/readme.txt
* @author MCD Application Team
* @brief Description of the DAC Signals generation example.
******************************************************************************
* @attention
*
* Copyright (c) 2016 STMicroelectronics.
* All rights reserved.
*
* This software is licensed under terms that can be found in the LICENSE file
* in the root directory of this software component.
* If no LICENSE file comes with this software, it is provided AS-IS.
*
******************************************************************************
@endverbatim
@par Example Description
How to use the DAC peripheral to generate several signals using the DMA
controller.
For each press on User push-button, a signal has been selected and can be monitored on
the DAC channel one:
- Triangle waveform (Channel 1).
- Escalator waveform (Channel 1) using DMA transfer.
STM32746G-DISCOVERY board's LED can be used to monitor the process status:
- LED1 is slowly blinking (1 sec. period) and example is stopped (using infinite loop)
when there is an error during process.
@note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds)
based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from
a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower)
than the peripheral interrupt. Otherwise the caller ISR process will be blocked.
To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function.
@note The application need to ensure that the SysTick time base is always set to 1 millisecond
to have correct HAL operation.
@par Keywords
Analog, DAC, Signals generation, DMA, Triangle, Escalator, Waveform, Amplitude
@Note<74>If the user code size exceeds the DTCM-RAM size or starts from internal cacheable memories (SRAM1 and SRAM2),that is shared between several processors,
<20><><A0><A0><A0>then it is highly recommended to enable the CPU cache and maintain its coherence at application level.
<0A><><A0><A0><A0><A0>The address and the size of cacheable buffers (shared between CPU and other masters) must be properly updated to be aligned to cache line size (32 bytes).
@Note It is recommended to enable the cache and maintain its coherence, but depending on the use case
<0A><><A0><A0><A0> It is also possible to configure the MPU as "Write through", to guarantee the write access coherence.
<0A><><A0><A0><A0><A0>In that case, the MPU must be configured as Cacheable/Bufferable/Not Shareable.
<0A><><A0><A0><A0><A0>Even though the user must manage the cache coherence for read accesses.
<0A><><A0><A0><A0><A0>Please refer to the AN4838 <20>Managing memory protection unit (MPU) in STM32 MCUs<55>
<0A><><A0><A0><A0><A0>Please refer to the AN4839 <20>Level 1 cache on STM32F7 Series<65>
@par Directory contents
- DAC/DAC_SignalsGeneration/Inc/stm32f7xx_hal_conf.h HAL configuration file
- DAC/DAC_SignalsGeneration/Inc/stm32f7xx_it.h DAC interrupt handlers header file
- DAC/DAC_SignalsGeneration/Inc/main.h Header for main.c module
- DAC/DAC_SignalsGeneration/Src/stm32f7xx_it.c DAC interrupt handlers
- DAC/DAC_SignalsGeneration/Src/main.c Main program
- DAC/DAC_SignalsGeneration/Src/stm32f7xx_hal_msp.c HAL MSP file
- DAC/DAC_SignalsGeneration/Src/system_stm32f7xx.c STM32F7xx system source file
@par Hardware and Software environment
- This example runs on STM32F756xx/STM32F746xx devices.
- This example has been tested with STM32746G-DISCOVERY board and can be
easily tailored to any other supported device and development board.
- STM32746G-DISCOVERY Set-up :
- Visualize PA4 (DAC Channel1) (pin 17 on P1 connector) signal with an oscilloscope.
- Use User push-button connected to PI.11.
@par How to use it ?
In order to make the program work, you must do the following :
- Open your preferred toolchain
- Rebuild all files and load your image into target memory
- Run the example
*/
767d083e20