-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the CC310 IAR libraries #9122
Conversation
Can this be captured in the readme for these libs (version of the code used, toolchain version). Same would be good to have inthe commit msg as well |
In this case, I will update this PR with the ARM and GCC_ARM libraries as well, to be synced |
@RonEld, thank you for your changes. |
I am currently working on updating the other toolchain libraries for specific version information, and updating the readme file, as requested earlier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes are only binaries, there is nothing to review.
Waiting on #9131 for a fix to Travis CI. |
06ca95f
to
d89c7a0
Compare
I have amended the commit message with version information, and uploaded the libraries for ARM and GCC_ARM with the specific version information. |
* The CC 310 libraries were built from version `arm_sw-cc310-1.1.0.1285` | ||
* The `IAR` libraries were built using `IAR ANSI C/C++ Compiler V7.80.1.11864/W32 for ARM` with `--cpu Cortex-M4f`. | ||
* The `ARM` libraries were built using `ARM Compiler 5.06 update 4 (build 422)` with `--cpu cortex-m4`. | ||
* The `GCC_ARM` libraries were built using `arm-none-eabi-gcc 7.3.1 20180622 (release)` with `-mcpu=cortex-m4`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested with GCC ARM 6 as that one is supported, this would rather be recompiled
Update the cryptocell 310 IAR libraries, since the previous ones were not built correct. The libraries were built from the Cryptocell 310 release version 1.1.0.1285, using IAR version 7.80.1.11864.
Update the cryptocell 310 ARM libraries with known version. The libraries were built from the Cryptocell 310 release version 1.1.0.1285, using `ARM Compiler 5.06 update 4 (build 422)`.
Update the cryptocell 310 GCC_ARM libraries with known version. The libraries were built from the Cryptocell 310 release version 1.1.0.1285, using arm-none-eabi-gcc 6.3.1 20170620 (release) (release).
Update the Cryptocell 310 readme file with the binary library version information.
d89c7a0
to
2446470
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One remaining question: increase binary sizes (in case of IAR 240 percent reported by Github - is that correct) ?
You can check by viewing files in the PR, Github reports the size differences
Since the previous IAR libraries were actually broken. I assume this is correct. I haven't built them, and they were built with wchar defined as short ( Probably for IAR 8 ). This could explain why it was broken, and why the size was smaller. |
|
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
@AnotherButler for later review, she is currently OoO. Reviewed by a maintainer should be sufficient for this change |
Description
After testing the Mbed TLS On Target Tests with IAR, on NRF52840 platform, it was discovered that the Cryptocell library is not initiated correct. This fix replaces the libraries received by Mail, with libraries built from the official Cryptocell 310 release, version 1.1.0.1285, using IAR version 7.80.1.11864 and the
NRF52840
platform registers base address.Tested with GreenTea Mbed TLS On Target Tests.
Pull request type