CubeMX 4.25 & 4.26 GRAPHICS configuration MULTIBUF bug

If we create a graphics window for GRAPHICS configuration with GUIBuilder for file GUI_App.c

CreateWindow();



The CubeMX is creates function in file STemwin_wrapper.c



void GRAPHICS_Init(void)
{
/* Initialize the GUI */
GUI_Init();

//WM_MULTIBUF_Enable(1);
/* Enable the multi-buffering functionality */

/* Activate the use of memory device feature */
/* USER CODE BEGIN WM_SetCreateFlags */
//WM_SetCreateFlags(WM_CF_MEMDEV);
/* USER CODE END WM_SetCreateFlags */
}



If you delete comments

WM_MULTIBUF_Enable(1);
/* Enable the multi-buffering functionality */

/* Activate the use of memory device feature */
/* USER CODE BEGIN WM_SetCreateFlags */
WM_SetCreateFlags(WM_CF_MEMDEV);



after this, the graphical interface stops running !!!

(Attention!  After deleting comments and compiling, turn off and turn on the power)

The problem is solved by adding a line



WM_MULTIBUF_Enable(1);
/* Enable the multi-buffering functionality */

/* Activate the use of memory device feature */
/* USER CODE BEGIN WM_SetCreateFlags */
HAL_LTDC_ProgramLineEvent(&hltdc, 0); //!!!!!!!!!!!!!!!!!!!!!!!
WM_SetCreateFlags(WM_CF_MEMDEV);
/* USER CODE END WM_SetCreateFlags */



And everything works fine!



P.S.

If FREERTOS is used, it is necessary to eliminate one more bug


in file  ..........STemWin\Target\STemwin_wrapper.c   comment

line (85):

//extern volatile GUI_TIMER_TIME OS_TimeMS;

line (876) :

//   OS_TimeMS++;

Add CMSIS-RTOS RTX & CubeMX adapt generated files

This section explains how to add the CMSIS-RTOS RTX real-time operating system.

Setup in STM32CubeMX

In STM32CubeMX ensure that the System Tick Interrupt is set to the lowest priority (which is the highest number).

Configuration tab

• Under System open NVIC Configuration.
• Click on System tick timer and set Preemption Priority to 15 (highest possible value).
• Click OK to close the NVIC Configuration dialog.

Setup in MDK

In MDK, the steps to add the CMSIS-RTOS RTX real-time operating system to a project that is configured with STM32CubeMX are:

Step 1: Add CMSIS-RTOS RTX

• Open the Manage Run-Time Environment window and add CMSIS:RTOS (API):Keil RTX.

Step 2: Configure CMSIS-RTOS RTX parameters

• Open the configuration file RTX_Conf_CM.c from the project window, component group CMSIS.
• Optionally you may change to the Configuration Wizard tab.
• Change the following settings:
  • Main Thread stack size [bytes] 1024
  • RTOS Kernel Timer input clock frequency [Hz] set to core clock frequency
• Save the file.

Step 3: Add code for CMSIS-RTOS RTX in 'main.c'

• Open the source file main.c from the project window, source group STM32CubeMX:Common Sources and add code lines in the sections USER CODE BEGIN / USER CODE END as shown below:

:

/* USER CODE BEGIN Includes */

#include "cmsis_os.h" // ARM::CMSIS:RTOS:Keil RTX

/* USER CODE END Includes */

:

/* USER CODE BEGIN 0 */

extern uint32_t os_time;

uint32_t HAL_GetTick(void) { // Add HAL_GetTick function for STM32Cube HAL

return os_time;

}

/* USER CODE END 0 */

:

int main(void)

{

:

/* USER CODE BEGIN 1 */

osKernelInitialize (); // Initialize RTOS Kernel for setup

/* USER CODE END 1 */

:

/* USER CODE BEGIN 2 */

osKernelStart (); // Begin thread switching

/* USER CODE END 2 */

:

Step 4: Remove SysTick_Handler in stm32f7xx_it.c

• STM32CubeMX generates a SysTick_Handler that is in-compatible with CMSIS-RTOS RTX. Remove the code for the SysTick_Handler in the source file stm32f7xx_it.c as shown below.

#if 0

void SysTick_Handler(void)

{

/* USER CODE BEGIN SysTick_IRQn 0 */

/* USER CODE END SysTick_IRQn 0 */

HAL_IncTick();

HAL_SYSTICK_IRQHandler();

/* USER CODE BEGIN SysTick_IRQn 1 */

/* USER CODE END SysTick_IRQn 1 */

}

#endif

Step 5: Build Project in MDK

• Use Project - Build Target to generate the application code.

The source file generated by STM32CubeMX can be accessed in the MDK project window, source group STM32CubeMX:Common Sources. These file require the following modifications.

Changes to 'stm32fxxx_it.c'

CMSIS-Driver and CMSIS-RTOS RTX implement their own interrupt handlers.

• For using CMSIS-RTOS RTX remove the code of the SysTick_Handler.
• For using CMSIS-Driver remove the code of the related Interruption Handler.

Note

STM32CubeMX re-generates this file and it is required to remove the interrupt handlers after using Generate Code.

Changes to 'main.c'

• CMSIS-Driver initialize peripherals using dedicated functions that are called by middleware. Initialization code in 'main.c' for the related peripherals is therefore not required and may be removed.
• CMSIS-RTOS RTX requires initialization code. Refer to Add CMSIS-RTOS RTX for detailed information.

Implementation Keil RTOS-RTX in CubeMX project

Create CubeMX project with STM32F429 Discovery

In NVIC set prioryti of System tick timer and Generate Code in MDK v5

Project STM32F429 Keil +CubeMX

После запуска Keil 5.18 появляется меню выбора типа используемого процессора:

После выбора процессора происходит сразу переход в Manage Run-Time Enviroiment:

и в папке, где был создан проект появляются файлы (в папке Debug находится файл Target_1_STM32F429ZITx.dbgconf):

Если, не производя никаких действий с окном, нажать ОК, то в папке проекта будет создана следующая структура каталогов: