• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 924 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AES hardware accelerator OMAP 3430

levon poghosyan
Prodigy 20 points
Other Parts Discussed in Thread: OMAP3530

Hi,

 

According to TI's OMAP 3430 public documentation there are support of hardware cryptographic acceleretion, and especially for AES.

So I would like to know how to encypt/decrypt using AES hardware acceleration. I need a simple example/code snippet.

 

Regards,

Levon

  • 0
    TI__Mastermind 41665 points

    The OMAP3430 is not a widely available/supported device, it is marketed toward high volume wireless phone customers, as per the disclaimer on the OMAP3430 site:

    Availability Disclaimer said:

    Availability Disclaimer

    This product is intended for high-volume wireless OEMs and ODMs and is not available through distributors. If your company meets this description, please contact your TI sales office. For OMAP products now available for all customers and applications, please click here.

    As to support for AES, this is something you would have to work with your local TI contact even for a OMAP3530 implementation and further details as mentioned in this prior thread.

  • 0 in reply to Bernie Thompson TI
    Prodigy 20 points

    Actually I'm interested in usage of AES hardwaer in Nokia N900 Maemo which has OMAP 3430 in it. 

    Are there any software APIs, I've looked for it in TrustZone but couldn't find anything.

    I will appreciate if code snippet or example were shown, how to use it in linux.

    Generally openssl uses hardware engine to encode/decode with AES HW algorithm.

    1. CPU: openssl speed -evp aes-128-cbc -elapsed

    2. HW Engine: openssl speed -evp aes-128-cbc -engine "SOME ENGINE" -elapsed

    In this case the differences of execution time for encryption/decryption should be visible for CPU and HW accelerator.

    Basically all available engines failed to run with above "2. HW Engine" command or gave the same result as "1. CPU" command.

    Maybe by default openssl uses Hardware accelerator ?

    PS. Contacting to TI is not convenient for me so please help to figure out the problem.

  • 0 in reply to levon poghosyan
    TI__Mastermind 41665 points

    I am under the impression that anything for OMAP3430 requires NDA, and anything requiring AES hardware acceleration in general requires NDA as of today, and as I do not really work much with NDA requiring devices/peripherals there is not much else I can do to help, I really don't know much about the AES accelerator and even less about how it is leveraged in an OMAP34xx with Maemo. This community is currently really only focused on publicly supported devices and software from TI, so I am afraid it may not be the best place to ask such a question, which is what I was trying to get at with my prior post. If you cannot ask your local TI sales contact (or they are unable to help you) you may want to ask in other more OMAP34xx or Maemo based communities to see if anyone else has used AES hardware acceleration under your particular conditions. Of course if anyone else in the community has thoughts on this I hope they will post in this thread to help you out, I just wanted to try to point you in the right general direction.