OFFICIAL RELEASE: X-CUBE-TOUCHGFX v4.13.0

[Martin KJELDSEN]

Goodmorning everyone!

With the release of CubeMX 5.5.0 we've removed TouchGFX from the Middleware section of CubeMX and are now offering TouchGFX configuration through an X-CUBE.

The X-CUBE pack contains the following:

1. TouchGFX Designer .msi, as per usual
2. TouchGFX Generator - A tool through "additional software" for creating your TouchGFX HAL based on CubeMX settings.

CubeMX is a tool for configuring your MCU.

CubeMX is not a tool for completely configuring peripherals like touch controllers and external memories.

TouchGFX Generator (new since 4,13) is a CubeMX extension that can generate all or parts of your TouchGFX HAL Layer based partially on settings taken from your MCU configuration in CubeMX.

TouchGFX Generator (new since 4,13) is not a tool that provides complete configurations for touch controllers, external memories, etc. It only generates the TouchGFX HAL - Rendering strategies, acceleration strategies, etc.

TouchGFX Designer is a tool that can supply you with application templates for existing stm32 display kits. We are working on getting all of them updated to use the new Generator.

Please read the following guides for instructions on how to install the new TouchGFX X-CUBE and how to use the TouchGFX Generator to develop your TouchGFX HAL:

• https://touchgfx.zendesk.com/hc/en-us/articles/360011039799-Installing-TouchGFX
• https://touchgfx.zendesk.com/hc/en-us/articles/360010921760-TouchGFX-HAL-Development

From now on it is the X-CUBE that receives a version bump, bumping the version of both tools contained within.

A few application templates already support the new TouchGFX Generator (and thus CubeMX 5.5.0), with lots more to come. One of our main priorities is to get the rest of the application templates ported to use the TouchGFX Generator,

• STM32H7BI-DK v.3.0.0 (uploaded)
• STM32F746-DISCO v.3.0.0 (uploaded)
• STM32F769I-DISCO v.3.0.0 (uploaded)
• STM32H750B-DK v3.0.0 (uploaded)
• STM32F750-DK v3.0.0 (in progress)
• STM32L4R9-DISCO v3.0.0 (in progress)
• STM32L4P5-DISCO v3.0.0 (in progress)
• STM32H743-EVAL v3.0.0 (In progress)

Generally, any application template that supports the Generator/CubeMX 5.5.0 will be major version 3.

 

Let me know here if you have any questions or face any issues! We're eager to see how this works for everyone.

Now that we are officially live with X-CUBE-TOUCHGFX we'll continue working on improving documentation, offering support and updating the current application templates you can find through the designer.

Aside from that i'll do my best to catch up on this community, something i've had to neglect a bit because of the new Generator.

Best regards,

TouchGFX Generator Team

[ADusi]

Okay, thanks ;)

[Martin KJELDSEN]

Hi,

First glance It looks like you haven't pressed "Generate code" from the touchgfx designer. I need to know more about which process you went through to get these errors.

[Kasun Dinesh]

Hi,

I use the .ioc file in STM32F746-DISCO v.3.0.0 project, import it to CUBE IDE and used the option to create a project form ioc file. But even i compiled and run in in stm32f746 board, nothing happens. Any reason for this, or whats the fix. My end goal is to make it compatible with a display of 800x480.

[Karl Yamashita]

So i tried another approach to getting a working project going. Before when generating code in TouchGFX it only did it for EWARM. But now i see it generates for STM32CubeIDE and Keil. So i used your V3 template for the STM32F746G-DISC0 kit but still no success in getting a gui to show on the LCD. All i get now is a white screen. In the attached video you can see the QUADSPI section has no code, so no resources are being generated when compiled.

[Martin KJELDSEN]

Just to give everyone an update on Eyals issue here which we solved offline.

CubeMX in 32-bit mode (and/or a 32-bit java version) will cause CubeMX project generation to silently fail (aside from some project generation errors in the log) for CubeIDE projects.

So, make sure you have 64-bit versions all around (CubeMX and Java) and you should be fine.

/Martin

[Martin KJELDSEN]

I'll check it out tomorrow.

[Martin KJELDSEN]

Can you elaborate on "nothing happens" ? :)

[zul-a]

@Martin KJELDSEN​  Yes you are right as always :).... I generated a new project and after configuring Touchgfx within CubeMx I opened the Touchgfx Designer and made sure I click "Generate Code" after configuring my GUI. Everything compiles fine now. Just another quick one.

Do I have to add "BSP" myself into the project distributed via "en.x-cube-touchgfx" if I wish to use them or is there a way of adding/configuring them via CubeMx workflow?

Kind Regards

[Martin KJELDSEN]

Generally, yes. E.g. SDRAM CAS Latency and QSPI Memory mapped mode is not something CubeMX can help you with. For CubeMX' part, this is done in user code sections called somewhere in your main method (main.cpp)

/Martin

[Martin KJELDSEN]

The V3 template may not be available yet for your board - we're working harrrrrrrd to get everything done asap :)

Black screen/white screen - Is your framebuffer memory set up right? CubeMX can't help you configure timings of your external ram. Did you do any debugging? What's the application doing? Can you break in setupScreen() of one of your views?

/Martin