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.

[FAQ] TDA4VM: How to address the assertion Issue from EthFw, due to race condition between multiple client requests for EnetMcm Module Server Task.

Part Number: TDA4VM

How to address the assertion Issue from EthFw, due to race condition between multiple client requests for EnetMcm Module Server Task.

  • Assertion Issue in EthFw is due to race conditions between multiple Mailbox post requests for EnetMcm server task, when two or more client tasks were posting Mailbox with MCM commands for EnetMcm server task and then pending on the response.

    As MCM Module had only one response queue, the response was pulled in by the wrong client task followed by Assertion.

    This condition is not easily reproducible, it happens only when server task is processing one client task and simultaneously another client task posted on the server Mailbox.

    The patch attached below will address this issue, have a queue of response mailbox per client in order to handle MCM commands for EnetMcm server task, so that each client have its own response mailbox for its requested MCM command.

    TI SDK Version 9.0 already addressed this issue so, SDK version 9.0 and above has this fix by default in SDK.

    For SDK versions below 9.0, need to refer the patch below and integrate the changes into the SDK required.

    Patch for SDK 8.6 (ti-processor-sdk-rtos-j721e-evm-08_06_00_12)
    7065.0001-mcm-Fix-race-condition-in-MCM-request-response-handl_SDK_8_6.patch

    Patch for SDK 8.2 (ti-processor-sdk-rtos-j721e-evm-08_02_00_05)
    0001-mcm-Fix-race-condition-in-MCM-request-response-handl_SDK_8_2.patch