Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is it worth to use CC310 HW Crypto for LESC?

I have an application with LESC. When I compile it for the 52840 I get the following RAM/Flash sizes with Oberon vs CC310:

CC310 Oberon
Flash 119820 101208
RAM 31984 29712

Despite being HW Crypto CC310 needs more flash and more RAM than Oberon, how does that make sense? And I don't see any other benefit such as faster LESC connection initiation. So does it make sense to use CC310 for LESC at all?

Parents
  • Hi Bruno

    The CC310 is just a hardware accelerator, and while it accelerates many of the heavier cryptographic operations it still leaves a lot to be handled in software. 

    Secondly, the Oberon library is extremely well optimized and is designed by developers that know how to squeeze the absolute maximum out of the ARM Cortex architecture, which is why they have been able to achieve lower memory consumption without the hardware accelerator available. 

    There should still be some advantage to the CC310 backend in terms of execution time (and as such energy consumption), but if it is enough to cause a noticeable difference in LESC pairing time is doubtful. 

    Considering how seldom pairing is performed in a normal application I would recommend using the Oberon library in this case. 

    Best regards
    Torbjørn

Reply
  • Hi Bruno

    The CC310 is just a hardware accelerator, and while it accelerates many of the heavier cryptographic operations it still leaves a lot to be handled in software. 

    Secondly, the Oberon library is extremely well optimized and is designed by developers that know how to squeeze the absolute maximum out of the ARM Cortex architecture, which is why they have been able to achieve lower memory consumption without the hardware accelerator available. 

    There should still be some advantage to the CC310 backend in terms of execution time (and as such energy consumption), but if it is enough to cause a noticeable difference in LESC pairing time is doubtful. 

    Considering how seldom pairing is performed in a normal application I would recommend using the Oberon library in this case. 

    Best regards
    Torbjørn

Children
No Data
Related