Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I think that I'm seeing this issue as well. In my case, I saw that when porting from 3.3.1 to 3.5.2.
As a workaround, I used the higher frequency timer callback to invoke the lower frequency timer callback every such and such invocations.
Note that I suspect that it might be related to placing a stack pointer object (message) on the thread queue while the thread is already performing a task. Since I don't have the ThreadX code, I cannot verify that hypothesis.