Hi.
Yes but be sure to:
1) review the first post here and note the details for your target kit:
https://community.st.com/s/question/0D50X0000A7VYsC/guides-for-using-touchgfx-410-with-cubemx-50-known-limitations
2) select the v2.0 template from the TouchGFX toolchain
Summary (as of this writing):
1) You will launch the TouchGFX toolchain FIRST
2) Select your target kit but be sure to use the drop down menu to select V2.0 Template on the kit screen. This step is very important.
3) Proceed to draw up your Picasso GUI graphics.
4) Compile -> test with the simulator. All good? If not, post back and/or revise the GUI.
5) After the above is done, proceed to review the Generate Code (lower right corner). Go up one level of the file folder and then double-click the generated .IOC file -> will launch the STMCube toolchain.
6) Do your thing here and save the project. From experience, IAR is recommended till ST reports otherwise due to varying raised error codes.
Generate code. Most likely this step will BREAK the code. This is known to ST and is being refined for future releases.
To fix the broken (wizard generated) code, follow this webpage (for your kit):
https://touchgfx.zendesk.com/hc/en-us/articles/360019884752-Configuring-STM32F746G-DISCO
- this webpage chats about using IAR compiler (only) to fix the code hence our reservation to recommend the IAR compiler - you may be able to also get this to work with the free SW4STM32 compiler but no direct experience with this combination of tools and kit. Post back if you do have a working recipe using your kit and/or alternate compilers.
Anytime you work with STMCube and select Generate Code, the above webpage must be reviewed to fix the wizard code.
It is a pain (for now) but may still be worth the exercise as even simple generated code can consume weeks of quality time to learn from scratch.
Hope this helps.
