• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 204 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.

CC2642R: ECDSA_verify issue

oliver zhang
Prodigy 10 points

Part Number: CC2642R

Hi, I was using aesKeyAgreement example code for testing the ECDSA_verify operation. By default blocking mode, this function call took about 230ms ticks to finish, which is not acceptable for our ECU product (max 50ms response time). However, when I changed the mode to callback, the system crashed and didn't invoke my callback function. Is there any configuration needs to be added? My modified example code is attached, with macro TEST_USE_CALLBACK to switch between blocking/callback mode. I'm using TI SDK 4.4 example "C:\ti\simplelink_cc13x2_26x2_sdk_4_40_00_44\examples\rtos\CC26X2R1_LAUNCHXL\drivers\aesKeyAgreement" and run it on launchpad.

  • 0
    TI__Guru**** 223557 points

    Hi oliver,

    Please reference ECDSA.h of the TI Drivers Runtime APIs to get a better understanding of callback functionality.  You could also further debug the CC2642R device in your IDE to determine the reason behind the system crash.  The modified code did not attach properly so you may want to try again.  How did you benchmark the ECDSA_verify execution time?  Note that callback mode will return the function immediately while the ECDSA operation goes on in the background.  It will not perform the actual verification operation any faster than blocking mode.

    Regards,
    Ryan