Guides for using TouchGFX 4.10 with CubeMX 5.0 & Known limitations.

I was able to (eventually) get a STM32CubeMX started project fully working in Atollic TrueSTUDIO for an STM32F746G-DISCO board.

If you are targeting Atollic TrueSTUDIO, below are some useful notes based on what I found:

Web guides of note:

A)     Overall guide – except missing specific Atollic True Studio usage. FOLLOW the STM32CubeMX start path of the tree… https://touchgfx.zendesk.com/hc/en-us/articles/360020001492-Getting-Started-with-CubeMX-and-TouchGFX

B)     Missing C++ Symbols: https://community.st.com/s/question/0D50X00009bMlNPSA0/convert-cubemx-project-in-atollic-to-c-pane-to-input-symbols-for-c-missing NOTE: I found a better way, - see below ADDING C++ section.

C)     TouchGFX – as close to a help file as we get… https://touchgfx.zendesk.com/hc/en-us/categories/200529271-Getting-Started

Steps:

1)     Configure your board in SMT32ubeMX, then follow the instructions for adding TouchGFX Middleware under GRAPHICS found on web guide A) – size your display for the real display, not their example. This will start your TouchGXF Designer project as well. For that part, any rough layout is fine – finish the visual/functional design later.

2)     Under the “Project Manager�? tab, “Project�? block, set your project name, pick TrueSTUDIO Toolchain/IDE, select a heap & stack size. I picked to copy all used libraries in the “Code Generator�? block – but it didn’t get them all.

3)     Generate code in STM32CubeMX – follow the instruction order in web guide A) which creates a TouchGFX project as well.

4)     Save your SMT32CubeMX and TouchGFX projects for further use.

Copy the files indicated by web guide A) into the project folders. 

5)     Start Atollic TrueSTUDIO – note that your Workspace location cannot contain your actual project files!! (This messed me up for a while). In your workspace (I suggest one workspace per project!!), import the project you created with STM32CubeMX. It won’t compile – there’s a lot of work to do yet…

6)     Change the project in TrueSTUDIO to a C/C++ project (it’s a pure C project as generated!!). To do so, in TrueSTUDIO select ‘File’ under the main menu. Hover over ‘New’ and on the pop up list, select ‘Convert to a C/C++ Project (Adds C++ Nature)’.

Add the needed include paths to the new C++ compiler settings:  Menu ‘Project’ -> ‘Properties’ ->’C/C++ General’->’Paths and Symbols’. 1)     If you look at the GNU C++ Language, you will see that it is EMPTY. Use the ‘Export Settings’ to generate an XML file – edit that XML file in Notepad++. Duplicate the section <language name="C Source File"> and name the new one <language name="C++ Source File">. Save the edited version. In TrueSTUDIO, use the ‘Import Settings’ – now the GNU C++ language has the same paths as is needed.

7)     Under the ‘Libraries’ tab, if missing, add ‘touchgfx-float-abi-hard’ and ‘touchgfx’ (Note: the file names are libtouchgfx-float-abi-hard.a and libtouchgfx.a but GNU adds the ‘lib’ and the ‘.a’)

8)     Under ‘Library Paths’ add Middleware/ST/TouchGFX/touchgfx/lib/core/cortex_m7/gcc (provided your processor is an m7).

9)     Under the ‘C/C++ Build’->’Settings’->’Tool Settings’->’C++ Compiler’->’Optimization’, check the box beside ‘Disable RTTI’

10)     Close project properties. In the ‘Project Explorer’, go through the folders and for all ‘template’ files and other IDE types, use a right click menu ‘Resource Configuration’->’Exclude from Build’ (select all configurations) to keep them from being compiled. The same for the whole folders ‘build’ and ‘simulator’ under folder ‘TouchGFX’.

11)     This is probably not the proper way to do this step, but it works: Edit file ‘startup_stm32f746xx.s’ (where 746 becomes your exact processor type). Replace the line about ½ way down the file ‘.thumb_set SysTick_Handler,Default_Handler’ with ‘.thumb_set SysTick_Handler,osSystickHandler’. This sets up the proper SysTick interrupt handler – but the expected method is to use a define in an include file – which is hard to follow in a debugger!!

12)     The project may compile  and debug now. Maybe. Use TouchGFX to design your screens, and TrueSTUDIO to work out the underpinings. Follow web guide C) for linking actions to software.

​bbenntett,

Could you please list the versions you used for TouchGFX, TrueStudio and CubeMX?

I am using the latest versions and struggling to setup a starter project as well. 

Thank You

I am using Windows 10, and no issues with the extremely long command for linking -

arm-atollic-eabi-g++ -o TouchGFXCube.elf Core\Src\freertos.o Core\Src\main.o Core\Src\stm32f7xx_hal_msp.o Core\Src\stm32f7xx_hal_timebase_tim.o Core\Src\stm32f7xx_it.o Core\Src

[...]

\STM32F746GDISCOTests3\CubeGenTouchGFX\TouchGFXCube\Middlewares\ST\TouchGFX\touchgfx\lib\core\cortex_m7\gcc -L../Middlewares/ST/TouchGFX/touchgfx/lib/core/cortex_m7/gcc -Wl,-cref,-u,Reset_Handler -Wl,-Map=TouchGFXCube.map -Wl,--gc-sections -Wl,--defsym=malloc_getpagesize_P=0x1000 -Wl,--start-group -lc -lm -lstdc++ -lsupc++ -Wl,--end-group

(ironically too long to post:* )

This eclipse plug-in might help: https://mcuoneclipse.com/2015/03/29/solving-the-8192-character-command-line-limit-on-windows/

@Soren Myllerup MIKKELSEN​ , this information really needs to be a sticky page that can be quickly found. Wasted days in trying to work with a STM32769I-DISCOVERY kit only to realize, this past weekend with thanks to @Martin KJELDSEN​ , that v2.0.0 template is much more refined than template v1.1.0 for this target.

We did find the same Draupner landing page but there is NO mention of the v2.0.0 template use - can that webpage be updated? So the proper "temp fix" would have been to start with this thread and then go to the Draupner page once the IOC project is broken.

Even template v2.0.0 appears to break once CubeMX imports the generated IOC project file and GENERATE CODE is selected inside of CubeMX. Your article on Draupner website is for the most parts, accurate but with assorted typos. After CubeMX breaks the working IOC file, the corrections must be manually applied (as noted on the Draupner landing page).

For future readers, there should be a must read FAQ / sticky page that offers this webpage since this information was available back in December. This info should be quickly available for developers.

The search engine on the ST website is a mess.

It appears only one is missing - libtouchgfx.a (which might not be needed?).

Is it actually in the folder??

I tested the build WITHOUT libtouchgfx.a - and it works fine, just REMOVE that library from "Libraries".

(You can also remove the first entry - the second is how STM32CubeMX generates the settings)

@BBenn​ , the missing files are used by the simulator. Learned this from @Martin KJELDSEN​.

or building through the designer the mingw32 library must be present: Middlewares\ST\TouchGFX\touchgfx\lib\win\mingw32\libtouchgfx.a

The SDL libs are inside: Middlewares\ST\TouchGFX\touchgfx\lib\sdl2\win32

We just cut & pasted the above from another working project and this fixed our simulator.

@BBenn​ , if I remove this library the compiler returns the same error. But I think is necessary because below you can see that the compiler call some functions in this library "touchgfx::HAL::tick()" for example.

Here is my situation:

Thanks.

All of those are library functions.

I am thinking perhaps your issue is the "Multiple definitions of MX_GPIO_Init" - there should only be ONE in main.cpp. I wonder if you have a second file included in the build with this function defined?

@BBenn​ , I have the MX_GPIO_Init function implemented in the gpio.c (generated by cube) and the call in the main.cpp, nothing else. Everything was generated by CubeMX.

About the second file I already searched for this function and appears only in gpio.c, gpio.h and main.cpp files.

Thansk for reply.

Could anyone share the project with Atollic + TouchGFX + CubeMX compiling?

At the forum I found the project only for SW4STM32...

Thanks.