STM32CubeIDE with TouchGFX Display show multi color error?

[GMano.1]

Hai..,

I am using STM32F746IGT MCU ( Waveshare Development Board ) and 7Inch Display

(1024x600)

Software are using " STM32CubeIDE 1.6.0 " and " TouchGFX 4.16.0 ".

I am Just create screen_1 (one color Box and one button) in TouchGFX

Configure in STM32CubeMX :

1. FMC --> SDRAM 1--> SDCKE1+SDNE1 Starting Address 0xD0000000 (SDRAM : ISSI IC42S16400J-7TL)
2. QUADSPI --> Bank1 with Quad SPI Lines (MICRON : MT25QL128ABA1ESE-0SIT)
3. DMA2D
4. LTDC --> RGB888 (24bits)
5. CRC
6. FREERTOS --> CMSIS_V2 --> Stack Size(Words) 512 or 4096 also.
7. TouchGFX 4.16.0

I am facing problems :

1. If i use SYS --> Timebase Source : TIM6,

While Debugging " SystemClock_Config() " then go to " TIM6_IRQHandler ".

2 Without using Timebase Source

While Debugging " osKernelStart() " then go to " HardFault_Handler ".

After upload ( Debugging) What's my display shows image mentioned bellow for your reference .

And in STM32Cube IDE main.cpp file show hide, that screen short also attached below

Please give me a idea for rectify my problem, I need to developed my own GUI using TouchGFX .

Thanks & Regards

M.Govind

[MM..1]

At 1 you need use timebase and TIM6 is OK

At 2 main.cpp is only for PC Simulator and in CUBE is excluded OK

At 3 after generate MX code you need next steps for ready your project to use TochGFX: add process, dimense heap , write display drivers and setup display before start RTOS usw.

[GMano.1]

Thanks for your replay....,

Yes.... I do all this kind of things but it not workout.

what is dimense heap ( you mean " TOTAL_HEAP_SIZE ")..? Where i find display driver?

This display is suitable or not on this project? (24 pin RGB)

almost i try every things for interface.... and i am very tried.

Please give your any idea for this problem.

Thanks & Regards

M.Govind

[MM..1]

As first you comment out start RTOS and in main test your framebuffer and LTDC config.

For example in main while wait press button and fill framebuff with an colour, then next usw.

And when you use custom display you cant find display driver, but you need WRITE one.

When you connect RGB display then your connector need all signals and too init over for example SPI ...