Sander Huijsen

Thank you, Miro.

This is a very old post, but upgrading my project to qpcpp v7.3.3 exposed this (almost exact) problem 10 years later (Cortex-M4 project). I thought I'd point this out in case anyone else runs into the same issue. And I apologize if anyone already raised this (I did search for it but couldn't find anything related). I hit the qep_msm:310 assertion, meaning I had hit the nesting limit as well. I have to clarify, I hit the second assert on line 233, because, unfortunately, there are two asserts that...

This is a very old post, but upgrading my project to qpcpp v7.3.3 exposed this (almost exact) problem 10 years later (Cortex-M4 project). I thought I'd point this out in case anyone else runs into the same issue. And I apologize if anyone already raised this (I did search for it but couldn't find anything related). I hit the qep_msm:310 assertion, meaning I had hit the nesting limit as well. I have to clarify, I hit the second assert on line 233, because, unfortunately, there are two asserts that...

Hi Miro. Thanks for your comprehensive response. I'm using an STM32L452, which is a Cortex M4. Also, I never use QActive::stop() anywhere. I only ever start AOs and the only way they are stopped is from a power cycle/reset. In fact, the macro QACTIVE_CAN_STOP is undefined, so the code isn't even included. Thanks for the pointers. Looks like the problem may be even more obscure than I thought. Many thanks, Sander

Hi! I ran into a rather obscure issue. I don't think I've seen this happen before. In the function publishFromISR, the following ASSERT triggered: // no need to lock the scheduler in the ISR context do { // loop over all subscribers // the prio of the AO must be registered with the framework uxSavedInterruptStatus = portSET_INTERRUPT_MASK_FROM_ISR(); Q_ASSERT_INCRIT(510, registry_[p] != nullptr); // <<<<<----- portCLEAR_INTERRUPT_MASK_FROM_ISR(uxSavedInterruptStatus); (qf_port.cpp version 7.3.1)...

Thanks Miro, that makes indeed total sense to me.

Hi, I know that the implementation for the QTicker AO is provided in qf_actq.cpp. This file, however, should not be used for the FreeRTOS port, which is explicitly mentioned in the "Ports" section of the documentation. I was wondering (consequently) why an implementation of QTicker for FreeRTOS is not provided? Am I missing something? Kind regards, Sander Huijsen

Sorry, better title would be "Q_REQUIRE_INCRIT in gc triggers".