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.

CC2745P10-Q1: Regarding HSM processing, the relationship between callbacks and STATUS_RESOURCE_UNAVAILABLE

Part Number: CC2745P10-Q1

Tool/software:

Which behavior, as shown in Table 1 or Table 2_1, is correct? Or could both be incorrect?
On the CC2745, if TASK B is using the HSM for encryption and TASK A sends an encryption request:
・In the case of Table 1, TASK A receives STATUS_RESOURCE_UNAVAILABLE. Once TASK B completes, TASK A is automatically processed, and the encryption result is returned.
・Alternatively, as shown in Table 2_1, TASK A receives STATUS_RESOURCE_UNAVAILABLE and must resend the encryption request to the HSM.

If Table 2_1 is correct:
・Would TASK A need to send repeated encryption requests to the HSM, as shown in Table 2_2?
・Or would the HSM provide a “HSM completion response,” as shown in Table 2_3, to notify that it is ready for a new request?

  • Hi,

    Due to the holidays there will be some delays in getting an answer to this question. Once the team is back, I will provide an update.

    Thank you for your patience.

    Best,

    Nima Behmanesh

  • Hi,

    Thank you for your patience over the holidays.


    If Table 2_1 is correct:
    ・Would TASK A need to send repeated encryption requests to the HSM, as shown in Table 2_2?

    This is correct. Task A would need to send repeated encryption requests to the HSM. Unfortunately, there is no way to ping the HSM to know if it's already executing something. So Task A would need to send repeated requests until success occurs.

    Best,

    Nima Behmanesh

  • Dear Nima Behmanesh,
    Thank you very much.
    Your explanation was clear and thorough.
    It seems that it follows the behavior outlined in Table 2_2.
    I look forward to your continued support.
    Sincerely,
    ????