cancel
Showing results for 
Search instead for 
Did you mean: 

What is typical development flow for TouchGFX?

BParh.1
Senior III

So I developing prototype using STM32F769 Discovery Kit. At first I develop the UI using TouchGFX and so far so good.

But I realize the generated codes from TouchGFX does not really generate driver code for other component e.g. Virtual Component Port. So I search around STM site and found CubeMX tool which seems the right tool for me generate this low level code. So when the code generated by CubeMX, I use Keil IDE vs 5.34. But when I build the code I end up with errors/warning:

"Rebuild started: Project: STM32F769I_DISCO

*** Using Compiler 'V5.06 update 7 (build 960)', folder: 'C:\Keil_v5\ARM\ARMCC\Bin'

*** Warning: You are compiling one or more files of source type C++ and have selected 'use MicroLIB'. MicroLIB does not support C++!

....................

linking...

STM32F769I_DISCO\STM32F769I_DISCO.axf: error: L6050U: The code size of this image (88518 bytes) exceeds the maximum allowed for this version of the linker.

Finished: 0 information, 0 warning, 0 error and 1 fatal error messages.

"STM32F769I_DISCO\STM32F769I_DISCO.axf" - 1 Error(s), 1 Warning(s).

Target not created.

...........

"

And at this pointl, when I use TouchGFX to run simulator, it is ok, But when I run on target, the following error occurred:

"  Core/Src/main.c:24:10: fatal error: usb_device.h: No such file or directory

     #include "usb_device.h"

         ^~~~~~~~~~~~~~"

So it seems to me TouchGFX and Keil IDE cannot be used hand in hand?

So my question is, what is typical flow to develop using TouchGFX? So after we design the GUI, but then we need to configure other HW setting e.g. Virtual Com port, where should I go form here?

10 REPLIES 10
BParh.1
Senior III

Thanks @Vahid Ajallooeian​  and @Romain DIELEMAN​ , I decided to use STMCubeIDE for now, I just want to get this prototyping going as soon as possible without too much troubled with license issue :).

So it seems to me either way it should work, I can develop GUI first using TouchGFX Designer. When it is done, I can use the generated .ioc file using STM32CubeMX to configure further my hardware. Or just the other way around. It's just depending on what toolchains we choose, there might be some caveats need to figure out on the way.