X-CUBE-TOUCHGFX 4.26.1 is out!

[Osman SOYKURT]

TouchGFX 4.26.1 is now out.

Please follow this link to download it.

This version is a patch release and includes bugfixes of issues seen on TouchGFX Designer 4.26.1 version, as well as adding support of the new STM32H5F5 and Chrom-ART 2.

Please visit our dedicated website for STM32H5 graphics to know more about high performance graphics on our most powerful Cortex-M33 MCU.

Release details:

• Release date: March 2nd, 2026
• New TouchGFX Designer Features
  • Allow selecting a CMakeLists.txt file as the project file without requiring a STM32CubeMX .ioc file.
    
    
• Bugfixes in TouchGFX Designer
  
  • Fix caching issue when changing text configurations and re-generating code.
  • Fix outdated timestamp on files when importing a GUI.
  • Fix faulty code generation when a Shape widget has two identical end points.
  • Fix faulty code generation when a Shape widget uses an "interaction ended" callback.

• New TouchGFX Generator Features
  • Support for STM32H5F5/E5 and STM32H5F4/E4 series with the new Chrom-Art 2 hardware accelerator.

• Bugfixes in TouchGFX Generator
  • Fixed an issue where YCbCr video buffer sizes were generated incorrectly for some framebuffer width values.
  • Fixed an issue where the task memory pool used by ThreadX was not aligned correctly.
    
    
• New TouchGFX Core Features
  • Added Chrom-Art 2 support.
    
    
• Bugfixes in TouchGFX Core
  • Fixed an issue where the noise function for 16-bit linear gradient painters compiled to incorrect instructions on some platforms.
  • Fixed an issue in font code generation where compressed fonts could not compile when building with MSVS.
  • Fixed an incorrect build configuration for IAR9 Libcpp (C/C++17 runtime) libraries.
  • Inserted missing namespace touchgfx in Atomic.hpp.
    
    

Enjoy this new version :)

[MillerWeldsJack]

Let's say I wanted to change the .ioc dependency to a CMakeLists.txt file on a current project. Is that possible? My recent projects don't even use .ioc files for ease of maintenance and to remove the need for another tool. 

[Osman SOYKURT]

Hello @MillerWeldsJack ,

If the project does not include an ioc file, updating the project to a newer version of TouchGFX is more difficult. You can copy updated code from another project that uses the latest version of TouchGFX; however, this process is not trivial.

[MillerWeldsJack]

Fair enough. We will continue developing as-is, then. I'd urge the team to continue to decouple from the CubeMX tool. While I understand the benefits for quick hardware setup and prototyping, it becomes an obstacle with version control and reuse across projects. This update is definitely a step in the right direction, from our team's perspective. 

Thanks for the speedy reply.

[Duc]

Hi @Osman SOYKURT ,

Do your team have any plans for TouchGFX to support automatic updates or allow updating directly from an existing version, instead of requiring users to download and install a new version each time an update is released?

[Osman SOYKURT]

Hello Duc,

Thank you for your idea. Yes, this is under consideration, but since our program is very linked to other ST programs like STM32CubeMX or STM32CubeProgrammer, we are trying to find a way to install the "full" package instead of just TouchGFX.
I'll let you know if we come to a conclusion on this.

[PeterVang]

Hello MillerWeldsJack

I just want to clarify that that you should be able to migrate your project simply by opening your .touchgfx file in TouchGFX Designer 4.26.1 and clicking "Yes" to the migration process. After this, you should able to update your project reference to be the CMakeLists.txt file.

Be aware that your might need to adapt your TouchGFXHAL/target files to be compatible with the new version of TouchGFX libraries. This adaption is normally done by the X-CUBE-TOUCHGFX in STM32CubeMX.

Best regards

Peter