STM32H7B3I - First Experience with CubeIDE

There must be a config file somewhere in TouchGFX to allow for setting the path to STM32CubeProgrammer and such.

One option would be to set it in the gcc/Makefile for the project:

stm32cubeProgrammer := STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin\\STM32_Programmer_CLI.exe
stm32cubeLoader := STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin\\ExternalLoader\\MX25L512G_STM32F769I-DISCO.stldr

ifneq ("$(shell find "$(PROGRAMFILES)\\$(stm32cubeProgrammer)" 2> nul )","")
# STM32CubeProgrammer is placed in Program Files (x86)
st_stm32cube_programmer := "$(PROGRAMFILES)\\$(stm32cubeProgrammer)"
st_stm32cube_external_loader := "$(PROGRAMFILES)\\$(stm32cubeLoader)"
else
# STM32CubeProgrammer is placed in Program Files
st_stm32cube_programmer := "$(PROGRAMW6432)\\$(stm32cubeProgrammer)"
st_stm32cube_external_loader := "$(PROGRAMW6432)\\$(stm32cubeLoader)"
endi

TouchGFX 4.14.0 just recently came out so perhaps there are some issues with it.  I did not seem to have these issues with 4.13.0 though.

Nice work getting past this though.

The installation page for TouchGFX does have messages concerning the location of the STM32CubeProgrammer. This still should be something that can be set tough.

https://support.touchgfx.com/docs/introduction/installation/

There must be a config file somewhere in TouchGFX to allow for setting the path to STM32CubeProgrammer and such.

One option would be to set it in the gcc/Makefile for the project:

stm32cubeProgrammer := STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin\\STM32_Programmer_CLI.exe
stm32cubeLoader := STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin\\ExternalLoader\\MX25L512G_STM32F769I-DISCO.stldr

ifneq ("$(shell find "$(PROGRAMFILES)\\$(stm32cubeProgrammer)" 2> nul )","")
# STM32CubeProgrammer is placed in Program Files (x86)
st_stm32cube_programmer := "$(PROGRAMFILES)\\$(stm32cubeProgrammer)"
st_stm32cube_external_loader := "$(PROGRAMFILES)\\$(stm32cubeLoader)"
else
# STM32CubeProgrammer is placed in Program Files
st_stm32cube_programmer := "$(PROGRAMW6432)\\$(stm32cubeProgrammer)"
st_stm32cube_external_loader := "$(PROGRAMW6432)\\$(stm32cubeLoader)"
endi

TouchGFX 4.14.0 just recently came out so perhaps there are some issues with it.  I did not seem to have these issues with 4.13.0 though.

Nice work getting past this though.

The installation page for TouchGFX does have messages concerning the location of the STM32CubeProgrammer. This still should be something that can be set tough.

https://support.touchgfx.com/docs/introduction/installation/

I haven't been able to get something on a screen with a fresh project started from CubeIDE yet.

RTOS runs, but my screen isn't shown - investigating.

What I did get to work, is have the CubeIDE load the TouchGFX example that you can import, and TGFX-generated examples,

by changing Debug settings, and selecting external loader MX25LM51245G_STM32H7B3I_DISCO, 0x90000000, NOR_FLASH, MX25LM51245G_STM32H7B3I-DISCO.stldr.

Using the default STM32 Cortex debug settings (that work with a CubeIDE generated project) fails during load.

But using the external script works.

Action photo below: debugger breaking on clicking the light control ON in the bathroom.

I still want to fiddle out how to get a CubeIDE generated project working with TGX-Designer. Because I want to use the configurator to manage other hardware.

That's not working with TGX-Designer and the imported project.

I think it's a silly thing, but yet to find out ...

I found what's wrong, by stepping through a CubeIDE generated project and a TouchGFX generated project.

The following virtual function is not available in the CubeIDE generated TouchGFX/target/TouchGFXHAL.*pp files - and it's the one that enables the screen:

in .hpp:

public:
...
virtual void taskEntry();

in .cpp:

/* USER CODE BEGIN TouchGFXHAL.cpp */

#include <touchgfx/hal/OSWrappers.hpp>

...

void TouchGFXHAL::taskEntry()
{
    enableLCDControllerInterrupt();
    enableInterrupts();

    OSWrappers::waitForVSync();
    backPorchExited();

    // Turning on display after first frame is rendered
    HAL_GPIO_WritePin(GPIOK, GPIO_PIN_7, GPIO_PIN_RESET);
    /* Assert display enable LCD_DISP_CTRL pin */
    HAL_GPIO_WritePin(GPIOA, GPIO_PIN_2, GPIO_PIN_SET);
    /* Assert back light LCD_BL_CTRL pin */
    HAL_GPIO_WritePin(GPIOA, GPIO_PIN_1, GPIO_PIN_SET);

    for (;;)
    {
        OSWrappers::waitForVSync();
        backPorchExited();
    }
}

tadaaa:

... no touch screen though ...

Jan Cumps

Nice!

Out of curiosity, when you are creating a new project in CubeIDE, are you creating it as a STM32 Project or just a plain C/C++ Project?

Also, with TouchGFX, You should be able to create a project from TouchGFX for the board you are designing for, Generate Code from the Interface, and then click "Browse Code" at the bottom right of the screen to get to the generated code.  This takes you to the TouchGFX folder, but if you go up one, there should be a STM32CubeIDE folder with a .cproject file that you can just click on to open the project in CubeIDE.  That seemed to work for me with other boards, although I have not done this with the STM32H7B3i.

One issue I did run into with CubeIDE was that after upgrading to 1.3.0 it would no longer create projects using STM32 Project.  I had intially installed CubeIDE in a non default location under a 'H:' drive, so I ended up removing it and then reinstalling CubeIDE and just let it install it in the default location.  This seemed to solve the issue.  It's a bit quirky like that.

I got the touch screen working too now.

This is a little complex. I'll write a separate blog about it.

For the interested and fellow road testers, I attached a project zip to the main article above.

It works with TouchGFX Designer, CubeIDE,the MX Configurator.and the debugger.