In my configuration, the tick source for touchGFX is the LTDC vsync interrupt. This was the recommended configuration in STM32CubeMX. However, that means that ThreadX is doing its own thing while model::tick (e.g., TouchGFX) is also running. The ThreadX timer priority is 0, whereas the LTDC priority is 10. Are there potential pitfalls to having a message queue or mutex to share a common resource between the two?
The documentation here seems to indicate that what I have described above is the prescribed method. I just want to make sure there are no issues with the two threads being unaware of ech other. https://support.touchgfx.com/4.18/docs/development/ui-development/touchgfx-engine-features/backend-communication
Side question: what user code might go into frontendapplication.cpp?
