Andy Aoe

Thank you so much for your help guys! This "pig" was definitely the issue.

Hi Miro, here is a video explaining what I'm seeing. It seems like a bug in QP but I'm sure it's something on my end. https://www.loom.com/share/1244ec59d39a470d8429b3bdae9f3aff

I've used QP on several projects now so what I'm seeing right now has puzzled and questioning life in general. I have 2 questions. 1. Is there any technical issue in arming a timer, waiting for the event, and then arming the timer again? 2. In the implementation below, I get to the line Printf("How did I get here?!?!?\r\n"); I disarm the timer in Network_websocketConnecting so I don't understand why it's doing this. You help would be much appreciated! static QState Network_websocketConnecting(Network_t...

Hi Miro and Support Team, I ported the DPP example to the DA16600 which runs FreeRTOS. I'm not calling QP function in interrupts so I'm wondering if you know what I'm getting the following assert? I don't know if this is useful information but if I comment out the initialization of the philos the assert does not occur. Do you know what we should check? void ATTRIBUTE_RAM_FUNC vPortEnterCritical( void ) { portDISABLE_INTERRUPTS(); uxCriticalNesting++; /* This is not the interrupt safe version of the...

I've tried me->super.super.state but it doesn't seem to be correct. I've seen some old post that says it is not possible, is this still true?

Hmmm, I'm getting the same assert again but now probably for a different reason. Is there a way to know how many messages are active in the pool?

Nevermind...I found the issue. For test purposes, I had commented out the QF_PUBLISH so I was allocating Events that never got sent. I hope this helps someone out there! ModemEvt* modem_evt = Q_NEW(ModemEvt, SEND_MODEM_DATA_SIG); modem_evt->txBuffer = l_lynxaPacketBuffer; modem_evt->txSize = tx_length; //QF_PUBLISH(&modem_evt->super, me);

Hi, able to consistently reproduce this issue where a a Q_NEW fails but I don't know which of the messages are backing up. Is there a way I can view what is currently queued in the event pool? Is there a better way to get at the root cause? I am using QV and none of my states are blocking