cancel
Showing results for 
Search instead for 
Did you mean: 

TouchGFX documentation feedback

Romain DIELEMAN
ST Employee

We wish to always improve our documentation. The best reviews and critics always come from the people that read it, so we would like to use this post to collect your thoughts and feedbacks.

Please share what you like, dislike, what you think is missing, etc ...

/The TouchGFX team

47 REPLIES 47

@jchernus-fikst wrote:

> "I was able to write a custom build script (using STM32CubeIDE headless build) and also a custom script for flashing (using STM32CubeProgrammer) and they both get called when clicking the program button in TouchGFX."

Would you be willing to share some documentation you found helpful, sample code, or anything that can help someone like me who's trying to accomplish the same?


Sure. For building I use headless build. The only modification I made was disabling indexing (slows down build).
https://community.st.com/t5/stm32cubeide-mcus/headless-build-bat-bug-headless-build-freezes-for-20-seconds/td-p/665855
For flashing I'm using STM32CubeProgrammer CLI.
https://community.st.com/t5/stm32cubeprogrammer-mcus/stm32-programmer-cli-doesn-t-return-errorlevel-in-case-of-some/td-p/91198

 

Kudo posts if you have the same problem and kudo replies if the solution works.
Click "Accept as Solution" if a reply solved your problem. If no solution was posted please answer with your own.

Never mind this reply, I was wrong and resolved my problem - documentation is fine!

MPamenter
Associate II

The documentation is excellent so far!  I found a little spelling mistake in the board bring up section.

https://support.touchgfx.com/4.25/docs/development/board-bring-up/how-to/02-cpu-running#touchgfx-internal-dcache-state-machine

"majority" is written as "mijority"

Southbranch
Senior II

Hi,

The documentation has become pretty good.

However, on my wishlist would be a section describing on how to use TouchGFX's built in APIs to track FPS and CPU usage in percentage in the same way as many board's demos have in their GUIs. Would be very helpful during prototyping.

Thanks

abbas78
Associate II

Overall, the TouchGFX documentation is quite well-structured and informative. But i got few suggestions 

 

1.  Include more practical examples

2.  Include a visual roadmap or workflow diagram

3.  Include Getting Started Checklist

ARM_and
Associate III

a small suggestion:

Step 8 of board bring up, https://support.touchgfx.com/docs/development/board-bring-up/how-to/08-hardware-acceleration#write-to-framebuffer-memory is less prescriptive than the initial steps where the location of where to insert the code e.g. /* USER CODE BEGIN X */ where given. It leaves a bit of room for confusion.

 

 

 

RobNewbury
Associate III

I notice that documentation for TouchGFX 4.25, section 'Video Decoding' has been thinned down. It no longer contains detailed information on the following sub-topics, other sub-topics are also missing.
* Software Decoding
* RTOS Support

Without this information, the software video decoder can't be properly setup for software decoding.
Has this information been moved elsewhere in the documentation? I don't see a link to it on the Video Decoding page.  

RobNewbury_2-1754947331325.png

 

RobNewbury_1-1754947229650.png

 

 

Apologies, now I look closer I now see that I mistook the Video Decoding Section for the TouchGFX Generator with the Video Decoding section in 'Scenarios' which does contain all the necessary information.