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

[JHarding]

Thank you @HP​ , that video made it clear as day for me, and im sure its going to help others.

[zul-a]

@Martin KJELDSEN​ fixed the CubeIDE code generation issue by updating Cube Mx to V 5.5.0. Somehow missed the update earlier.

Any updates on the debug issue of Stm32f746 Disco board? I am assuming it would be fixed in the next release now?

[Martin KJELDSEN]

@zul-a​, i'm still awaiting feedback from CubeIDE team on that, sorry. Will update asap.

[Karl Yamashita]

I've created a YouTube video on how to setup TouchGFX 4.13.0, STM32CubeIDE using a STM32F746G-DISC0 board. I'd like to point out that HP (Community Member) helped me to get a previous project up and running. Thank you!

But I thought I'd show another alternative to setting up a project.

https://www.youtube.com/watch?v=12KXreXaLp0

[scottSD]

Great video @Community member​.

However, when I go through your steps, (I even used the toggle button), the button is distorted on my target.

That is, until I switched the Debugger to the External Loader like you did.

I didn't know about that step.

Thanks!

[HP]

Nice with another view on the implementation @Community member​ I learned a few bits as well although I'm not a fan of all that copy/pasting :D

I would like to point out that with your approach you effectively lock yourself to the exact hardware spec. of the 746 board. maybe not a bad thing for getting up and running but in the long run it could cause problems.

It would be nice to automate this process though. if one generated the template project first then those files wouldn't need changing. Then the files could be automatically copied into the project and added to the project structure and so on..

[Karl Yamashita]

Actually if you think about it, this approach is not locked to the 746 board at all. Going this way you're only using the necessary peripherals to get the LCD and touch controller working. All the other peripherals like uart, spi, timers, Ethernet, USB, etc.. are not enabled. You can then enable the unused pins like Ethernet to be GPIO's or ADC and so on, for a custom board.

[ADusi]

Does anyone tried this touchGFX version with SPI ?

I want to use partial frame Buffer and I use ManyBlockAllocator. When program call flushFrameBuffer function I can see that buffer have in state[0] = ALLOCATED but memory[0] is all empty.

When I try call const uint8_t* pixels = frameBufferAllocator -> getBlockForTransfer(r); I get empty array and blockRect[0] is 160x3 so it's wird because I have 160x80.

Where the image is copied to this buffer ??

[Martin KJELDSEN]

I updated the list of V3.0 Application templates. H750-DK done and uploaded, L4R9- and L4P5-Disco incoming.

/Martin

[Karl Yamashita]

I don't see the STM32H747I-DISCO listed in the OP. Will that board be supported at all?