Patrick Moerwald

Hi, if i have NUM_MY_AO of similar AOs and each should have a message Queue of size "myQueueSize" elements, do i initialize the queue with: static QEvt const * myAOQSto[NUM_MY_AO][myQueueSize] or static QEvt const * myAOQSto[myQueueSize][NUM_MY_AO] ? Thanks!

Ok. Clear now. Thanks

Hi, quick update, i got the signal dispatching working now. However this was just the first step for me. What i really want to achieve is to dispatch events with payload from the tcl script. I tried doing it like this: dispatch MY_SIG eventParam_1 eventParam2 I dont think it works though, its also hard to debug for me since my GDB only runs through the source coce once the test is already done. I wish i could see it in real time. Any chance the QUTest tutorial for HSMs and Active Objects will be...

I am writing a test scrip to test an active object. I wan tto be able to dispatch a signal from the code but i am struggling to do so. Right now i have to do it this way, but i think there is a better solution: test "LED_REQUEST_BUS_EVENT_MANAGER_1->RS485Arbiter (dispatch)" command 4 1 expect "%timestamp Disp===> Obj=l_RS485_arbiter,Sig=LED_REQUEST_BUS_SIG,State=RS485Arbiter_bus_free" And in my test harness: /*! callback function to execute user commands */ void QS_onCommand(uint8_t cmdId, uint32_t...

Hi, i always see this function in tests, but what is it good for? /! Host callback function to "massage" the event, if necessary / void QS_onTestEvt(QEvt *e) { (void)e; } Regards, Patrick

Wrong description in QUTest tutorial

Specifically, test fixture means the C or C++ code that calls (exercises) the CUT and runs either in the embedded target, or (exclusive-OR) on the host computer. If the test fixture is running on the host, the embedded target is not used at all and there is obviously no communication with the embedded target. Ok got it, thanks. This was the point i wasnt sure about. So if its better to test my code in the host i will do so. I guess this implies i have to mock all the function calls in my code that...

Hi, what i dont understand is how the test fixture - if running on the host computer - is communicating with the firmware running on the embedded target. I know it is over QS protocol but in the fixture i find the QS_onCommand function which calls certain fuction of the CUT. So doesnt this have to be part of my QS component of the compiled STM32 firmware? How can it invoke functions in the embedded target otherwise if i dont download that part of code to my embedded target? Or do you mean that the...