2025-11-28 5:07 AM
Hello Everyone,
Since the STM32CubeMX .ioc file does not exist for the DAC_GenerateWaveform_TriggerHW example code (as usual), does anyone have suggestions/recommendations on the best way to recreate it?
Seems like I need to make iterative guesses in STM32CubeMX and then see if the numbers start matching up in the original DAC_GenerateWaveform_TriggerHW example code?
Thanks!
C:\ST\STM32Cube_FW_H7_V1.12.1\Projects\NUCLEO-H7A3ZI-Q\Examples_LL\DAC\DAC_GenerateWaveform_TriggerHW\Src\main.c
Solved! Go to Solution.
2025-11-28 6:11 AM
Hello @JFlowers ,
The following article Getting started with DAC will help you on how to set up the DAC as wave generator in STM32CubeMX and creating a simple application to test the DAC.
2025-11-28 5:15 AM - edited 2025-11-28 5:16 AM
@JFlowers wrote:Since the STM32CubeMX .ioc file does not exist for the DAC_GenerateWaveform_TriggerHW example code (as usual),
not sure what you mean by "as usual" ?
Some ST examples do have .ioc files (ie, they were created using CubeMX); some weren't - see previous discussions, eg here.
The clue to which is which seems to be here.
@JFlowers wrote:does anyone have suggestions/recommendations on the best way to recreate it?
These projects just weren't created using CubeMX at all - you can't re-create something which wasn't ever there.
2025-11-28 6:11 AM
Hello @JFlowers ,
The following article Getting started with DAC will help you on how to set up the DAC as wave generator in STM32CubeMX and creating a simple application to test the DAC.
2025-12-17 6:51 PM
@JFlowers wrote:Since the STM32CubeMX .ioc file does not exist for the DAC_GenerateWaveform_TriggerHW example code (as usual),
> not sure what you mean by "as usual" ?
C:\ST\STM32Cube_FW_H7_V1.12.0>dir
Volume in drive C has no label.
Volume Serial Number is 6614-55BB
Directory of C:\ST\STM32Cube_FW_H7_V1.12.0
11/27/2025 07:01 AM <DIR> .
11/27/2025 07:11 PM <DIR> ..
11/27/2025 06:59 AM <DIR> Documentation
12/05/2024 10:45 AM <DIR> Drivers
11/27/2025 07:00 AM <DIR> Middlewares
12/05/2024 10:36 AM 252 package.xml
12/05/2024 10:35 AM 18,821 Package_license.html
12/05/2024 10:35 AM 15,287 Package_license.md
12/05/2024 10:45 AM <DIR> Projects
12/05/2024 10:36 AM 367,652 Release_Notes.html
11/27/2025 07:01 AM <DIR> Utilities
11/27/2025 07:02 AM <DIR> _htmresc
4 File(s) 402,012 bytes
8 Dir(s) 2,361,461,895,168 bytes free
C:\ST\STM32Cube_FW_H7_V1.12.0>dir *.ioc /s/b
File Not Found <-------------------------------------------------- "as usual"
C:\ST\STM32Cube_FW_H7_V1.12.0>
2025-12-18 2:26 AM
Again, some examples do have .ioc files; some don't - so neither having nor not having an .ioc file is "usual".
There are plenty of examples which do have .ioc files, and plenty which don't.
2025-12-18 2:41 AM - edited 2025-12-18 2:49 AM
"Since the STM32CubeMX .ioc file does not exist for the DAC_GenerateWaveform_TriggerHW example code (as usual)"
Please bear in mind that at time where STM32CubeH7 was released, providing ioc file with the examples was not the policy.
That policy started after with newest products and Cube-HALs of older MCU families (F1, F2, F3, F4, F7 etc ..) don't contain ioc files in their examples.
2025-12-18 3:00 AM
I can understand this. Thanks. I cannot/will not believe that "plenty" is equal to zero.