Mikhail Nagoga

Your QS output doesn't show that. From what I can tell, your state machine seems to enter the state w4_hsync_1b_h, which does not do any event deferring. The super state of the w4_hsync_1b state is busy and it's up to this state to defer SYNC_PACKET_1B_SIG event. (I removed other substates of busy for simplicity). With glbfilter(GRPUA, GRPSM) we have the following qspy output: Trg-RST QP-Ver=722,Build=230301_154222 Obj-Dict 0x00005648ABED1DA0->QS_RX Obj-Dict 0x00005648ABEBF320->l_clock_tick Usr-Dict...

Hi, I am trying to test with qutest an active object SyncTx. This object accepts an event SYNC_PACKET_1B_SIG which contains some useful data and sends it via uart interface. While it sending a packet, each incoming request is deferred to the queue busy_Q. In the python script I send (post) the event SYNC_PACKET_1B_SIG and consume all the qspy output until "@timestamp Trg-Done QS_RX_EVENT". The question: how can I test the event deferring? I tried to send another SYNC_PACKET_1B_SIG when the state...

Update After some searching I found that the following macro defined in the qv.h: #define QACTIVE_EQUEUE_SIGNAL_(me_) \ QPSet_insert(&QV_readySet_, (uint_fast8_t)(me_)->prio) This macro is redefined in the port to arm-cm (qpc_6_5_1/ports/arm-cm/qutest/qf_port.h) but not to pic32 as following: #define QACTIVE_EQUEUE_SIGNAL_(me_) \ QPSet_insert(&QS_rxPriv_.readySet, (uint_fast8_t)(me_)->prio) I copied the missing section to the qf_port.h of pic32 port and my AO started to get messages. However now...

Hello, I am evaluating the QP/C 6.5.1 and QTools 6.6.0 on a PIC32 based platform and trying to get work the QUTest, but observing some strange behaviour. The event USER_STANDBY_SIG is posted to the AO l_arbitre. After the message AO-POST I expected to find the AO-Get, but there is no such. Where could be the problem? It's looking like the posted message remains in the AO queue (29 of 30 slots free) but the AO never gets it. Who is supposed to check the AO queue and extract the messages in the test...

Hello, I am evaluating the QP/C 6.5.1 and QTools 6.6.0 on a PIC32 based platform and trying to get work the QUTest, but observing some strange behaviour. The event USER_STANDBY_SIG is posted to the AO l_arbitre. After the message AO-POST I expected to find the AO-Get, but there is no such. Where could be the problem? It's looking like the posted message remains in the AO queue (29 of 30 slots free) but the AO never gets it. Who is supposed to check the AO queue and extract the messages in the test...

Hello, I am evaluating the QP/C 6.5.1 and QTools 6.6.0 on a PIC32 based platform and trying to get work the QUTest, but observing some strange behaviour. The event USER_STANDBY_SIG is posted to the AO l_arbitre. After the message AO-POST I expected to find the AO-Get, but there is no such. Where could be the problem? It's looking like the posted message remains in the AO queue (29 of 30 slots free) but the AO never gets it. Who is supposed to check the AO queue and extract the messages in the test...

Hello, I am evaluating the QP/C 6.5.1 and QTools 6.6.0 on a PIC32 based platform and trying to get work the QUTest, but observing some strange behaviour. The event USER_STANDBY_SIG is posted to the AO l_arbitre. After the message AO-POST I expected to find the AO-Get, but there is no such. Where could be the problem? It's looking like the posted message remains in the AO queue (29 of 30 slots free) but the AO never gets it. Who is supposed to check the AO queue and extract the messages in the test...