2024-10-14 05:39 AM
I am facing some problems with TouchGFX 4.24.1.
After creating a project from Demos -> Board Specific Demo and selecting the STM32F746G-DISCO, and selecting the project: STM32F746G-DISCO Control LED from GUI. I got two problems:
- Problem 1: Frozen Screen and incorrect display of toggle button and light icon
Program and Run Target "F6", After flashing it
Memory Programming ...
Opening and parsing file: target.hex
File : target.hex
Size : 507.87 KB
Address : 0x08000000
Erasing memory corresponding to segment 0:
Erasing internal memory sector 0
Erasing memory corresponding to segment 1:
Erasing internal memory sectors [0 4]
Erasing memory corresponding to segment 2:
Erasing external memory sectors [0 5]
Download in Progress:
±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±± 0%
ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ 62%ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ 97%ÛÛ 100%
File download complete
Time elapsed during download operation: 00:00:07.805
Hard reset is performed
Done
Done
The light toggle button is not showing correctly and not interacting from the touchscreen.
- Problem 2: incorrect display of toggle button and light icon
After opening the project with STM32CubeIDE 1.16.0, compiling and running the project. It interacts but the LED icon and the toggle button are still displaying incorrectly.
(I have faced the some problem also with 1.16.1, but since TouchGFX suggests software tools CubeMX 6.12.0 and FW 1.17.2)
- Problem 3: Program and Run Target "F6", with TouchGFX fails sometimes
Compiling TouchGFX/target/TouchGFXGPIO.cpp
0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error 487
AllocationBase 0x0, BaseAddress 0x60EA0000, RegionSize 0x1F0000, State 0x10000
C:\TouchGFX\4.24.1\env\MinGW\msys\1.0\bin\mkdir.exe: *** Couldn't reserve space for cygwin's heap, Win32 error 0
gcc/Makefile:328: recipe for target 'TouchGFX/build/STM32F746-DISCO/TouchGFX/target/TouchGFXGPIO.o' failed
make[2]: *** [TouchGFX/build/STM32F746-DISCO/TouchGFX/target/TouchGFXGPIO.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [generate_assets] Error 2
gcc/Makefile:294: recipe for target 'generate_assets' failed
make: *** [all] Error 2
../gcc/Makefile:49: recipe for target 'all' failed
Failed
Failed
Can anyone help me to get TouchGFX running properly?
Thanks
Tools used:
- STM32CubeIDE 1.16.1 and STM32CubeMX 6.12.1
- STM32CubeIDE 1.16.0 and STM32CubeMX 6.12.0
with both TouchGFX 4.24.1 Designer and TouchGFX 4.24.0 Designer
2024-10-15 01:06 AM
@GaetanGodart wrote:Also, What do you mean by
I tried generating other demos or examples from the TouchGFX by specifying the Board, generating the code, running to target and they don't work!!
What is not working? Can you flash? Do they freeze? Do they work but looks werid?
Regards,
On MB1191-F746NGH6-C03, using TouchGFX to generate the code of a Demo project and running it from TouchGFX. It might flash the Board after few attempts, but it will show incorrect displaying of the toggle button and the light as attached in the picture above, and when I touch the button it does not change the color of the light bulb.
If I build and run the program using STM32CubeIDE instead, I get incorrect displaying of the toggle button and the light but. And when I touch the button it changes the color of the light bulb although it is still displayed in a pink box
2024-10-15 03:36 AM - edited 2024-10-15 03:36 AM
I saw that on the MB1191 F746NGH6-C01 there is an External Flash MT25QL128ABA1EW9-0SIT,
while on the MB1191-F746NGH6-C03 there is a W25Q128JVEIQ Quad SPI Flash Memory. Could it be related to the issue?
2024-10-15 04:07 AM
@GaetanGodart Im going to post this in sequence so we can keep the photos grouped by test.
i compared both the c03 first and the b04 second.
Test 1: was background image from washer machine example in external memory.
c03
b04
test 2: internal memory only background image
C03
b04
test 3: external Memory with two images
c03
b04
test 4: ext Memory , 2 Images, Button no text
c03
b04
test 5: int Memory, 2 img, button no text
c03
b04
based on this, I suspect that @janid_a migjt be on to something.
if bits are missing because it’s a quad being used like a single interface, it might explain the color differences.
2024-10-15 06:38 PM
@GaetanGodart
Going back and merely adding a text area to a graphic now causes a hard fault in the touchgfx::TextArea::getTextWidth().
The colors and visual presentation improved by moving the code into internal memory, however I'm still seeing hard faults anytime I try to add a simple text label.
I don't believe that adding a mere label shouldn't cause a hard fault to occur. I'm new to TouchGFX and at this point I'm not sure it's ready for prime time. I haven't been able to successfully to add a label without it causing a Hard Fault. Not being able to use a fundamental widget like that is debilitating to any graphics project. The examples are much more involved in this. There must be something I'm missing, a step I failed to do. At this point I'm still trying to see the line of code where the actual failure is happening so that maybe I can inspect it. Other than that, I'm not sure what to try next.
2024-10-22 02:38 AM
2024-11-15 01:46 AM
2024-11-15 02:10 AM
Hi @GaetanGodart. Can tell me what was the main issue?
Thanks.
2024-11-15 04:19 AM
There was a new board revision with a different memory.
Regards,