2019-11-04 02:55 PM
This is a warning listed under the "Problems" tab in STM32CubeIDE (1.1.0). I am seeing some strange behavior and am wondering if this is the cause.
The strange behavior I am seeing is that often when I change something in the TouchGFX Designer and click "Generate Code" then do a Run > Debug in STM32CubeIDE, the change does not take effect. What runs on the target is some previous build (without the changes).
Sometimes if I disconnect the target and reconnect it, the latest code is correctly running on the target.
Solved! Go to Solution.
2019-11-05 01:41 PM
Evening exchange for you. Still afternoon here. ;)
I do see it there in the Compiler Settings:
2019-11-05 01:44 PM
Deleting it from there did, in fact, remove the warning as you said it would.
2019-11-05 01:50 PM
Great! Oh, Sometimes i forget that the world doesn't revolve around the TouchGFX office in Denmark :p
2019-11-05 02:18 PM
Martin,
I was able to recreate this.
I am currently trying to figure out the BPP on this project and was setting the Pixel Parameters for the LTDC (in CubeMX perspective).
Changing that apparently caused it to reference GRAPHICS and reintroduced the warning again. I can easily delete it from the compiler settings, but I wanted to let you know how I recreated it.
Regardless, when I selected ARGB8888 , the TouchGFX Frame Buffer Color Format and Color Frame Buffer Depth settings didn't like it (red in screen capture below):
Maybe I am not correctly setting this up? Is this the place to do this so that I correctly use ARGB8888 for dynamic bmps?
I plan on eventually using the index (L8) but am using this type for now.
2019-11-05 03:02 PM
Concerning the GRAPHICS being added to the .cproject file, I see that the following two lines are added to the .mxproject file when I make the above changes in CubeMX:
Maybe that will help.
2019-11-06 12:00 AM
Doesn't look wrong to me. I'm just wondering why this wasn't caught during testing, so maybe there's an edge case here, although this configuration seems straight forward. We gave lots of feedback to the CubeMX/IDE teams during the making of version 5.4 and 1.1.0. Maybe we missed something when the project is generated from within CubeIDE instead of CubeMX standalone.
/Martin
2023-08-30 06:18 AM
2024-03-01 06:47 AM
Hi,
I have a similar situation for the "RTOS2" folder
The entry with the RTOS folder can be found in the .cproject file. CubeMx is responsible for this.
Simply adding the missing folder from the file manager solves the problem.
Additionally, this folder can be deleted from the file project tree in STM32CubeIDE, which will remove the folder from the file system and from the .cproject file to...
--
Arkadiusz M.