Romain,
As I've been digging into this more, I've been able to debug the issue and find a specific line of code that when break-pointed on and continuing after a button or power on reset, I can get the touchscreen to still work. Again, I have the following setup: TouchGFX 4.21.4 and STM32CubeMX V6.8.1. I'm not sure if it has to do with TouchGFX and/or CubeMX code generation, but I've tried some of the different items in here (uwtick-stops-updating-stuck-in-hal-initialize) that seem similar to my problem, but haven't gotten any of them to work.
I.e. this is what I've found in debugging:
1. The first run (debug mode) after starting works without a breakpoint. When reset without a breakpoint the screen stops responding to touch events. If I breakpoint at 'MX_TouchGFX_Init(); found in main.c then run, the screen works again. This is fully repeatable.
/* Initialize all configured peripherals */
MX_GPIO_Init();
MX_CRC_Init();
MX_DMA2D_Init();
MX_FMC_Init();
MX_I2C3_Init();
MX_LTDC_Init();
MX_QUADSPI_Init();
MX_USART6_UART_Init();
MX_TouchGFX_Init();
/* Call PreOsInit function */
MX_TouchGFX_PreOSInit();
/* USER CODE BEGIN 2 */
Driving into this, I go through the following lines fine:
void MX_TouchGFX_Init(void)
{
// Calling forward to touchgfx_init in C++ domain
touchgfx_components_init();
touchgfx_init();
}
/**********Into --> touchgfx_init()*******************/
void touchgfx_init()
{
Bitmap::registerBitmapDatabase(BitmapDatabase::getInstance(), BitmapDatabase::getInstanceSize());
TypedText::registerTexts(&texts);
Texts::setLanguage(0);
FontManager::setFontProvider(&fontProvider);
FrontendHeap& heap = FrontendHeap::getInstance();
/*
* we need to obtain the reference above to initialize the frontend heap.
*/
(void)heap;
/*
* Initialize TouchGFX
*/
hal.initialize();
}
/**********Into --> hal.initialize();*******************/
void TouchGFXHAL::initialize()
{
// Calling parent implementation of initialize().
//
// To overwrite the generated implementation, omit call to parent function
// and implemented needed functionality here.
// Please note, HAL::initialize() must be called to initialize the framework.
TouchGFXGeneratedHAL::initialize();
setFrameBufferStartAddresses((void*)0xC0000000, (void*)0xC003FC00, (void*)0xC007F800); //enable the animation storage to allow slide animations
lockDMAToFrontPorch(false);
instrumentation.init();
setMCUInstrumentation(&instrumentation);
enableMCULoadCalculation(true);
}
At TouchGFXGeneratedHAL::initialize(); --> HAL::initialize(); is where I get the specific failure. Now this function goes to a 'virtual void initialize();' and I can't seem to be able to find how/what this initialize is doing.
void TouchGFXGeneratedHAL::initialize()
{
HAL::initialize();
registerEventListener(*(Application::getInstance()));
setFrameBufferStartAddresses((void*)0xC0000000, (void*)0xC003FC00, (void*)0);
}
Someone said that using CubeMX v6.5.0 for code generation fixes it, but I haven't been able to revert back from CubeMX v6.8.1 to v6.5.0, it gives me an error that the .ioc was generated for a later version and cannot be opened.
Can you or anyone at ST please provide some guidance on how to fix this issue?
Thanks!
