Quantum Leaps

Hi Christopher, The file qf_actq.c should NOT be included in the FreeRTOS or any other traditional RTOS ports. (That file is only used in the built-in kernels: QV, QK, and QXK). Please check the documentation of the qf_actq.c file and the none of the provided examples for FreeRTOS include that file in the build. For example, please take a look at: qpc\examples\freertos\arm-cm\dpp_nucleo-u545re\gnu\Makefile. So, the solution is to just remove the file qf_actq.c from your build for QP 8.1.4. --MMS

Hi Christopher, The file qf_actq.c should NOT be included in the FreeRTOS builds. (That file is only used in the built-in kernels: QV, QK, and QXK). Please check that none of the provided examples for FreeRTOS include that file in the build. For example, please take a look at: qpc\examples\freertos\arm-cm\dpp_nucleo-u545re\gnu\Makefile. So, the solution is to just remove the file qf_actq.c from your build for QP 8.1.4. --MMS

The AOs process events from their queue in the order the events were posted. The event queue of each AO can hold muliple events, and you decide how many events when you start the AO. --MMS

The AOs process events from their queue in the order the events were posted. The event queue of each AO can hold muliple events, and you decide how many events at the time you start the AO. --MMS

Hi Denis, I probably don't appreciate some hidden complexity here, but isn't this a textbook example for a state machine? I have attached a state machine for your AO1 that would do what you describe. This assumes that your AO2 produces events ACTIVATE and DEACTIVATE for AO1. --MMS

Hi Harry, You can use classes as data members inside the QP events (subclasses of QP::QEvt). This is no problem as long as these classes don't have pointers or references. This is because if they had such pointers or references, the referenced data would be outside framework's control and would most likely not be managed correctly. The restrictions on the QEvt subclasses are listed explicitly in the QP/C++ Manual: Attention Event parameters must be included in the event instance directly (as opposed...

Hi Harry, You can use classes as data members inside the QP events (subclasses of QP::QEvt). This is no problem as long as these classes don't have pointers or references. This is because if they had such pointers or references, the referenced data would be outside framework's control and would most likely not be managed correctly. The restrictions on the QEvt subclasses are listed explicitly in the QP/C++ Manual: Attention Event parameters must be included in the event instance directly (as opposed...

Hi Harry, You can use classes as data members inside the QP events (subclasses of QP::QEvt). This is no problem as long as these classes don't have pointers or references. This is because if they had such pointers or references, the referenced data would be outside framework's control and would most likely not be managed correctly. The restrictions on the QEvt subclasses are listed explicitly in the QP/C++ Manual: Attention Event parameters must be included in the event instance directly (as opposed...