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.

Can the TMS320C6678 security accelerator be used to verify the integrity of data received on interfaces other than the SGMII interface?

Other Parts Discussed in Thread: TMS320C6678, SYSBIOS

Can the TMS320C6678 security accelerator be used to verify the integrity of data received on interfaces other than the SGMII interface?

For example, lets assume an I2C device connected to the TMS320C6678 - I2C interface appends an MD5 hash value to a message it sources to the TMS320C6678 DSP.

Can data accepted by the TMS320C6678 on the I2C interface (with a hash value embedded in the received data) be sourced to the Security Accelerator, then have the Authentication Engine compute a hash value for the data.(minus the embedded hash value) that the CorePac can use to compare to the hash embedded in the message?

Can data sourced to the Security Accelerator - Authentication Engine be consumed by the Authentication Engine without getting sourced to the SGMII interface? I don't want to unintentionally retransmit my message, only verify its data integrity.

Thank you for your time.

  • James,

    One of the SA is compliant with the following standard: RFC 1321 The Message Digest(MD5) Algorithm.
    SA functions on the packet level with the packet and the associated security context.
    Its coupled with network coprocessor, and receives the packet descriptor containing the security context in the buffer descriptor, and the data to be encrypted/decrypted in the linked buffer descriptor.
    All accelerators except for the SA LLD are packaged with both the Linux and SYSBIOS versions of the MCSDK for Keystone I device.