STM32CubeIDE and TouchGFX 4.10.0: Resolving compilation issues

Martin KJELDSEN · ‎2019-05-21

Hi everyone,

I've removed the previous, textual guide. Instead, here's a video guide on how to get CubeIDE and TouchGFX working on an STM32F746G-DISCO board. I accidentally exported the video in 720p but have created a 1080p version. Leaving both links here because the 720p version may have useful comments and resolutions:

1080p: https://youtu.be/VOs2LYO7wSA

720p: https://youtu.be/xZ0pPhQCQUY

And here's the project i created and modified:

https://community.st.com/s/question/0D50X0000At0N95SQE/cubeide-100-touchgfx-4100-working-project-inside-stm32f746gdisco

(NOTE: This project does not have the modifications from our STM32F746G-DISCO/CubeMX article).

Best regards,

Martin

Martin KJELDSEN · ‎2019-08-23

Also, what is the application doing when you're debugging? Might give us a clue as to why the screen is black. Is the application even running? Are you in a hardfault during init maybe?

/Martin

HP · ‎2019-08-25

A user over at youtube asked why the boot-up time was about 10 seconds.

I've found that disabling the MX_ETH_Init call in the start-up can reduce the delay to what we 'usually' see when starting up TouchGFX on a board.

I thought it would be nice to know that if you don't need ethernet connection you can disable this (the 746-Disco board have this on by default) - and save some time

Martin KJELDSEN · ‎2019-08-25

Yeah, there's something in the Ethernet stack that takes an abnormal amount of time to start. I'm not sure when and if that'll be fixed, but if you start from the board selector with default IP configuration then Ethernet will probably be enabled, yea.

I've asked the guy in charge of Youtube to ask users on the channel to ask questions on this forum instead, so it's generally not something i monitor.

Thanks for the heads up.

/Martin

HP · ‎2019-08-26

I posted a few answers in there and linked to this article as well 🙂

Martin KJELDSEN · ‎2019-08-26

Thanks for the help! :p

HP · ‎2019-09-10

I've taken the liberty to do my own videoguide covering the subject of creating a working project in CubeIDE with TouchGFX integrated.

I'm basically doing the same things you do in the video but I try to cut a few corners and talk a bit about some other caveats that exists at the moment. If anyone is interested it's available here:

https://www.youtube.com/watch?v=43qQhrXc3n4

scottSD · ‎2019-09-10

Awesome job, HP!

I appreciate it and can actually make out what you're doing on the video 😉

I hadn't commented out MX_ETH_Init(), so thanks for a heads up on that.

The only thing I would add is that a person might want to change the STM32CubeMX > Connectivity > QUADSPI settings to increase the size to what is available on the board. I ended up running out of space and needed to do that. And of course, as you stated, you only have one chance to generate the IOC file because it really messes things up if you do generate it again.

Here are the settings I used:

(From the link: https://touchgfx.zendesk.com/hc/en-us/articles/360019884752-Configuring-STM32F746G-DISCO)

Michael B · ‎2019-09-10

Awesome, you beat me to it. I may be adding a tool shortly to patch projects as I find it really annoying not only that ST has not gotten around to fixing this, but every time I use CubeMX I have to configure my ignore's and includes.

HP · ‎2019-09-11

Thanks! and thanks for watching through the video and finding even more details I should clarify.

I had the exact problem with the QSPI not working due to the fact that I didn't change the 'default settings'

In another thread (https://community.st.com/s/question/0D50X0000BI1CvjSQF/external-vs-internal-flash-memory-for-touchgfx-assets) I have found those exact settings - so instead of configuring the QSPI during the init of the project I will make another video detailing what to do to get the external flash to work.

I will mention:

Sdding an external loader as per Charles suggestions (yet another thread referred in the one above)
Setting the right QSPI details - the ones you show in your screenshot above
Adding the QSPI driver so it will also work outside the debug environment
Showing the build analyzer to show the memory distribution

II hope that a few of those videos will help others as well

HP · ‎2019-09-11

i've had a similar idea! a sort of 'fix-my-project' tool since it should be possible to automate that process. I would love to give it a try if you make one 🙂

On the other hand I think that a number of people are biting their time to see how many fixes are provided with the next releases.