2024-08-21 07:43 AM - edited 2024-08-21 08:25 AM
Hi there,
I have a STM32F746G Discovery board on which I have developed an application. The application was running fine, there was some strange behaviour, probably some minor bugs, but it looked good.
When I bought a new identical board and flashed the application, the display literally showed some random noise, like this:
I flashed the examples from TouchGFX to see if it made a difference, but I got the same result. My old board is DK32F746G$U2, which works fine, but the new one is DK32F746G$CU4, which renders everything wrong.
I found a STM post on this link: STM32F746G_Discovery touch screen buttons stop wor... - STMicroelectronics Community, that says there may be different display built-in:
1. CU1 uses - HT043C
2. CU2 uses - GJX043A6 -40D Y
I have no clue what the display is used for CU4 as I could not find any information about it.
How do I solve this?
Thanks for the help!!!
Solved! Go to Solution.
2024-09-06 08:10 AM
Hello @Mohammad MORADI ESFAHANIASL,
You have hit the nail on the head. Now it works!
The problem why the draw function threw an error was probably that it could not get the fonts, texts and the image from the external memory, and with no data it cannot update the framebuffer. Maybe it would be cool to print out some text so the user could see the problem.
What was missing was the quad spi driver, which was not the latest, and the W25Q128J QSPI memory header with all the register definitions.
If someone else has the same problem, this is what you need to do:
Thanks for the help!!!!
2024-10-01 02:38 AM
Hello @Jackiii1989
Sorry for the late response, I was not in the office.
I'm really glad that you managed to fix the issue :D
Best regards,
2024-11-21 03:53 AM
2024-11-21 04:16 AM
Hi,
Please elaborate the 3rd Step of defining the symbol.
Thanks and warm regards,
Bansi Attara.
2024-11-21 05:16 AM
2024-11-24 02:06 AM - edited 2024-11-25 12:49 AM
@BA2 wrote:
Thank you so much for your assistance; it's working now.
I would greatly appreciate your help in resolving my new issue...
New question moved to new Thread