Assigning TouchGFX to the M7 Runtime context in CubeMX - Dual Core STM32H747
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-11-27 9:33 PM
Hi,
Why CubeMX forces the TouchGFX generator to the M4 context? I can't uncheck the M4 and assign it to M7 context from within CubeMX. I was wondering if I did something wrong or if this was known issue when generating project with TouchGFX using CubeMX?
Zaher
- Labels:
-
STM32CubeMX
-
STM32H7 Series
-
TouchGFX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-11-27 9:37 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-11-28 5:27 PM
** Update **
It seems TouchGFX Designer has witnessed a whole lot of improvements since last time I used it. The code generated from TouchGFX has the project template I was looking for. It has included all of the following items:
- All BSP files needed for the board
- Multi-core support (dual core booting)
- Projects for Keil, CubeIDE, and IAR
- CubeMX .ioc file (yep, I can easily modify project structure from CubeMX
- TouchGFX is already assigned to the appropriate context
This is marvelous. Such a harmony and cohesion among the tools used to generate the code is what I call a great investment and a step forward from STMicroelectronics.
