It seems that System would be locked or doesn't work properly when Mutex cannot get due to PlatformMutex_Lock doesn't have return value

[KeitaKashima]

Hi, I wonder the system would be locked or not work properly if PlatformMutex_Lock API cannot get Mutex or happened the timeout of Mutex.

FreeRTOS-Cellular-Interface/source/cellular_common_api.c

Line 211 in ccbd0fc

PlatformMutex_Lock( &pContext->PktRespMutex );

    PlatformMutex_Lock( &pContext->PktRespMutex );    // It gets the Mutex however, the API doesn't have return value. So, the code cannot check timeout.
    pContext->cbEvents.networkRegistrationCallback = networkRegistrationCallback;
    pContext->cbEvents.pNetworkRegistrationCallbackContext = pCallbackContext;
    PlatformMutex_Unlock( &pContext->PktRespMutex );

Does it nerver happnened?

[shubnil]

HI @KeitaKashima ,
Thanks for bringing this up. We have not observed this.
Do you have a use case where you are seeing this behavior

[KeitaKashima]

Hi @shubnil ,

Thank you for your reply.
I have never seen the lock of the system here. I just checked the implementation of the Semaphore portion.

[chinglee-iot]

Hi @KeitaKashima,
The PktRespMutex is used to protect the cellular context which can be accessed by the pktio thread and the application thread. The code with the mutex held should not block indefinitely, and no timeout is expected with the mutex lock operation. You can reference the example implementation in this file.