X-CUBE-TOUCHGFX 4.16.0 is out

[Romain DIELEMAN]

Hi Everyone, the TouchGFX team wishes you a happy new year.

If you haven't noticed by now, X-CUBE-TOUCHGFX 4.16.0 is out, available from CubeMX 6.0+ and from st.com as a zip (Also installable through CubeMX).

Here is the documentation for 4.16.0: https://support.touchgfx.com/

Main features:

1. Built in support for a Gauge widget
2. New screen transition called "Block Transition"
3. New invalidation algorithm for improved performances

You can see all the bug fixing and improvements in the changelog.

/Romain

[Jazman]

Is anyone having issues after updating to v4.16.1 from v4.15?

So, hoping it would solve some of the issues with dynamic bitmaps, I was trying to update to the latest version from 4.15.

All dynamic bitmap references have been removed from the code because of the issues I was having. Went into CubeIDE v1.6.0 and made sure the MPU version was up to date. Installed TouchGFX 4.16.1 and switched the .ioc file over to that version. Generated code. Installed the 4.16.1 version of the Designer, updated my touchgfx design file and generated code. Built the code. Corrected the typo in one of the header files that was generated (Area misspelled). Compiled and everything is good. Sent to target and a hard fault is generated before the first screen displays. I'm not sure how to figure out what generated the fault.

Rolled my code back to the commit before doing the update and with 4.15 everything still builds and runs fine.

Thoughts?

Keith

[Romain DIELEMAN]

Hi,

I'll try to replicate that. Could you give more details on your setup ? Are you working on a custom board or a ST dev kit ? If from a dev kit, have you started your project from an application template ? What version of CubeMX are you using (6.2 ?) ? Which headers files had mistakes ?

Thanks in advance,

/Romain

[ADębs.1]

Jak napisałem jeszcze raz, zainstalowałem STM32CubeIDE i TouchGFX najnowsze wersje. Nie ma żadnych błędów.

[Romain DIELEMAN]

Hi,

Could you write in English please ?

/Romain

[ADębs.1]

As I wrote again, I installed STM32CubeIDE and TouchGFX the latest versions. There are no bugs.:smiling_face_with_smiling_eyes:

[Romain DIELEMAN]

Good to hear that ^^

/Romain

[Jazman]

Re: Header file - Romain, I am really sorry now that I didn't make a note of it when I fixed it. Honestly, I'm completely surprised now that it didn't re-appear. But, as I've learned how files are generated (and not generated) by the various ToughGFX bits, I've grown concerned about how fragile the ecosystem can be.

I've long since moved on from a dev kit and am developing a real product. And because of that, things need to work as they are critical to a business. So, it's a custom board.

More details: I am using an entirely ST toolchain at this point so that should make things easier. The MPU is an STM32F746ZGT (note: debugging is a real pain with this part due to the interrupt/breakpoint bug in this generation of ARM core). STM32CubeIDE v1.6.0. I'm not running a stand-alone CubeMX except what's built into the IDE and I'm not sure how to find that version as part of that. It's the STM32Cube MCU package v1.16.1.

I'd be happy to zip my entire directory up and send it if that might help. I just need to know how to get that to you.

The behavior/error is indicative of a memory fault but I haven't researched how to work back from the fault dump... probably need to do that.

Keith

[KevinA]

Got an eMail "new TouchGFX", I checked my repository and found 4.16.1 so I installed it and tried it. Much better than the last time I tried it but I did find another show stopper: 296 X 128 4 bit grayscale display yet the color pallet is for a color display, I could not find a means to make it grayscale. The other minor issue was screen background, I think that is a learning curve so I'll RTM first but for my quick test I created a 296x128 white backgound png file and tried to use it, 296x128.png is not a valid file name.... Next was the save issue, you have to save any changes to get the preview button to show, why not let me click Preview and you save the files saving me a click? (lazy yes). I ordered the X-NUCLEO-GFX01M1 but the issue is power, I'm amazed that other than the STM32L0538-DISCO STM has not pushed more eDisplays as the means to achieve long battery life, whats the point of STM32L with a display that needs a car battery?.

[Romain DIELEMAN]

Hi,

Thank you very much for the feedbacks. Out of curiosity what was the previous version you tried ?

What do you mean by the color pallet set for a color display ? Do you mean that when you use a widget in Designer that requires a color (like a simple box widget) you still have the possibility to select different colors even though you should not be able to ? Makes total sense :thumbs_up: (if this is what you meant )

Could you give more detail on the screen background elements that confused you at first (by the way what does RTM mean :grinning_face_with_sweat: ?) Concerning the image name error the issue is that the name of an image cannot start by a number, i296x128 is fine for example (design choice). I am also confused by the Preview button, what preview button ?

For the issue power, I forwarded it to the marketing team I know but I doubt we can do something.

/Romain

[Romain DIELEMAN]

OK so I talked with some other people from the team, we agree that for the grayscale issue it would be a nice thing to change. For the moment you are still able to run the simulator and see that only the right values are used (so even if you set a box to red it will be in greyscale instead).

For the image naming we checked and the framework actually supports naming that do not start with a letter, so this means we can fix that bug easily for the next release :thumbs_up: Concerning the Preview I believe you are talking about the "Run Simulator" button, right ? The error you faced is actually linked to the image naming error. Usually when you get a red warning in TouchGFX Designer, the simulator button is greyed out. When you fix it it is then usable again. However with the image naming issue it is not the case and you need to save the project like you said. Ctrl s is faster than a click but you are completely right, and this can be fixed.

Thanks again for the feedbacks.

/Romain