Skip to main content
GMula.1
Associate
February 26, 2023
Question

Swipe Container stuck between two screen (stm32f750)

  • February 26, 2023
  • 3 replies
  • 2174 views

Hello ,

when i swap slowly from one screen to anotheir, i get stuck beetween two screen on my board (STM32F7508-DK)

0693W00000aHfr4QAC.jpg 

I have attached a full the project.

This topic has been closed for replies.

3 replies

GMula.1
GMula.1Author
Associate
February 26, 2023

i have also note some strange things in the generated code :

1) MX_TouchGFX_Init() is called before MX_TouchGFX_PreOSInit and before osKernelInitialize().

 MX_TouchGFX_Init();
 /* Call PreOsInit function */
 MX_TouchGFX_PreOSInit();
 /* USER CODE BEGIN 2 */
 
 /* USER CODE END 2 */
 
 /* Init scheduler */
 osKernelInitialize();

MX_TouchGFX_Init() call :

void OSWrappers::initialize()
{
 // Create a queue of length 1
 frame_buffer_sem = osSemaphoreNew(1, 1, NULL); // Binary semaphore
 assert((frame_buffer_sem != NULL) && "Creation of framebuffer semaphore failed");
 
 // Create a queue of length 1
 vsync_queue = osMessageQueueNew(1, 4, NULL);
 assert((vsync_queue != NULL) && "Creation of vsync message queue failed");
}

It means we are calling os_*** api before kernel initalise.

Note that it doesn't seem to cause any issue (i was thinking that osKernelInitialize() should be call prio any otheir os_*** call) as osSemaphoreNew and osMessageQueueNew doesn't return null.

2) frame_buffer_sem and vsync_queue doesn't have name, and i don't know why, there are not displayed in freertos debug view in STM32CUBEIDE. If i modify the code and give them a name, they are displayed.

3) The issue is problably related with frame_buffer_sem, touchgfx task blocked by this semaphore when screen freeze.

Osman SOYKURT
ST Technical Moderator
February 27, 2023

Hello GMula.1,

I've tried your project and I could reproduce the issue. Thank you for reporting it, we will investigate on this bug and I'll get back to you when I'll have more info.

/Osman

ST Software Developer | TouchGFX
ST Employee
August 3, 2023

Hello @GMula.1 ,

Sorry for the late update but this issue is now resolved in TouchGFX 4.22

Mohammad MORADIST Software Developer | TouchGFX