Add RX64/RX71 SHA hardware support

[Tathorack]

Description

Adding support for SHA1, SHA224, and SHA256 hardware acceleration on Renesas RX64 and RX71 microcontrollers. This follows the a similar pattern as the Renesas TSIP support.

Testing

Tested with WolfSSL 5.6.0 running on a RX64M, verified through debugging that hardware acceleration functions were being called for SHA256 hashes, verified that operation continued as expected after enabling hardware acceleration, verified that several different known values calculated the correct SHA256 hash.

Speed comparison for hashing 64KB of data on a RX64M

Hash Speed	SHA1	SHA256
Hardware	4ms	4ms
Software	11ms	89ms

Checklist

• [ ] added tests
• [ ] updated/added doxygen
• [ ] updated appropriate READMEs
• [ ] Updated manual and documentation

[wolfSSL-Bot]

Can one of the admins verify this patch?

[embhorn]

Hi @TakayukiMatsuo

Please give this a cursory review.

[dgarske]

OK to test. No contributor agreement on file yet.

[Tathorack]

Thank you very much for the work. Please take a look at my comments.

Thanks for the comments, it might be a while before I will have time to make updates

[Tathorack]

@miyazakh I've made some updates addressing the comments. What would be the next step here?

[miyazakh]

Hi @Tathorack I add other three comments about copyright. I am assigning @cconlon as a senior engineer review. He will review by himself or assign another senior engineer for final review.

Also, there are three PRB test failures that should be fixed.

[miyazakh]

Hello @cconlon Assigning this to you as final review. I have left open three comments about copyright. Could you give comments for those too?

[Tathorack]

Hi @Tathorack I add other three comments about copyright. I am assigning @cconlon as a senior engineer review. He will review by himself or assign another senior engineer for final review.

Also, there are three PRB test failures that should be fixed.

How do I get access to Jenkins to see what the test failures are? I created an account but it says "jhanserh is missing the Overall/Read permission". Otherwise is there a way I can run the tests locally?

[dgarske]

Retest this please. Last run was too long ago, so need to rerun to see

[Tathorack]

Seems like I still cannot access the Jenkins builds

[dgarske]

Seems like I still cannot access the Jenkins builds

The failures are because you have not rebased this PR to latest master and some of the commit messages have failed. There is no real failures I can see. Please rebase, squash and force push the PR.

@cconlon or @kaleb-himes will need to look into if we can give you Jenkins permissions?

[Tathorack]

Rebased and looks like all the checks have passed now

[embhorn]

Signed contributor agreement received. Starting tests.

[Tathorack]

@embhorn @cconlon What are the next steps for getting this merged in?

[embhorn]

Hi @Tathorack

The contributor agreement and the verbiage have been accepted. I've restarted the tests.

Thanks, @embhorn

[Tathorack]

@dgarske Do I need to rebase this again to fix the test failures?

[kaleb-himes]

retest this please.

[embhorn]

@cconlon @TakayukiMatsuo

Please resume the review on this PR.

[kaleb-himes]

@dgarske Do I need to rebase this again to fix the test failures?

Jumping in here sorry. Yes @Tathorack please go ahead and rebase so your changes are on top of commit history, the way our automated build system attempts to checkout the changes in some cases is still having issues replaying the changes on top of master.

[kaleb-himes]

Update: Rebase resolved the checkout issues, thank you! I hit retry on the one failing test (some background stuff caused it to timeout prematurely, not a true failure)

[Tathorack]

@embhorn what's the next steps for this PR?

[embhorn]

@cconlon

Reviewers have approved. Please merge when you are ready.

[Tathorack]

@dgarske I've addressed your comments and rebased on master

[dgarske]

Retest this please

[dgarske]

Hi @Tathorack , making sure you saw my comments for a few minor cleanups. I'd like to get this merged. Thanks, David Garske, wolfSSL

[Tathorack]

@dgarske I did see them, working on them now and some final testing. I should have some changes up by the end of the day. I noticed some of the tests failed, anything I need to do there to address them or should the be fixed with a rebase?

[dgarske]

Wonderful. Things looks good. The tests for pipeline is a new one we are working on to speed things up. The multi-test is the "C++-style comments". The other had a network failure and when you push will resolve.