This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
I've been trying to integrate the rlRfGetTemperatureReport function with the MRR lab, as shown in this Thread . However, when testing the lab on-field with a larger number of target objects, the Lab often crashes. If I increase the interframe processing time, these crashes are less frequent, although they still occur. I was curious about the timing requirements to call this API. Upon further investigation, I found that the rlRfGetTemperatureReport function uses the rlDriverExecuteGetApi function to execute the API, which in turn calls rlDriverCmdInvoke. This API tries to lock the globalMutex before writing into the outMsg. If the globalMutex is not available, it waits until it becomes available. My question is, does this waiting state also block the whole application?
Hi,
Let us look into this and get back to you this week.
Thank you,
Jin