-
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
Disable MBEDTLS_CONFIG_HW_SUPPORT on STM targets. #8142
Conversation
targets/targets.json
Outdated
@@ -2373,6 +2373,7 @@ | |||
"MBED_CONNECT_ODIN": { | |||
"inherits": ["MODULE_UBLOX_ODIN_W2"], | |||
"release_versions": ["5"], | |||
"macros_add": ["MBEDTLS_CONFIG_HW_SUPPORT"], |
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.
Should it not be removed, I believe?
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.
Is should be disabled for the all three as CONNECT_ODIN and MTB boards are using same WIFI binary driver.
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.
Yep, but if you ADD the CONFIG_HW_SUPPORT, then you are again activating it - i.e. reversing the 1st change done to the common target fíle. In my humble opinion these macros_add
changes should not be done, we should ONLY do the common target removal.
fd28d78
to
ae906df
Compare
As in the referenced issue, disabling it for other platforms comes in a separate PR ? |
@moranpeker Please review this one, what shall happen to other platforms? |
We can proceed with this one, but as I understood also other platforms are affected and should be updated (I haven't yet seen PR neither an action that will take care of it). |
Ah, OK - it can't be done for this target alone, it should be done to all STM targets (I assume the driver is shared amongst all STM targets). |
@Patater should |
@ARMmbed/team-st-mcd Thoughts on #8142 (comment) ? |
Yes, hardware acceleration should be removed from all targets that fail testing. At the time this PR was made, only |
/morph build |
Build : FAILUREBuild number : 3160 |
@adustm |
then is there any other target which support CRYPTO HW ACCELERATION working? |
Hello, Only the SHA256 hw acceleration is causing the problem. This PR is doing more than simply removing SHA256 as it removes every HW acceleration...
(+the same for other devices) |
Could you please share how did you reproduce it?
I agree with you on that. |
It is not plug and play... You have to know that NUCLEO_F439ZI = NUCLEO_F429ZI + hw crypto functionality. Both platforms are 100 % compatible.
Then a task to find every NUCLEO_F429ZI in any json file, any cpp file, any heady file to make sure the NUCLEO_F439ZI has the same declarations and settings than the NUCLEO_F429ZI
mbed-cloud-client-example/mbed-cloud-client modified files
mbed-cloud-client-example/mbed-os modified files
mbed-cloud-client-example/mbed-os Untracked files
I have copied the bootloader file from the NUCLEO_F429ZI, because I don't know how to create one. This means that this binary file is compiled with sw crypto if any mbedtls functions inside.
|
@moranpeker @Patater Please review the proposal |
Hello, Kind regards |
e1d0cc1
to
333f087
Compare
Hi, |
/morph build |
Build : SUCCESSBuild number : 3244 Triggering tests/morph test |
License issue, restarting /morph mbed2-build |
/morph export-build |
Exporter Build : FAILUREBuild number : 2829 |
IAR license issue, restarting /morph export-build |
Exporter Build : SUCCESSBuild number : 2835 |
Test : SUCCESSBuild number : 3053 |
Description
Disable MBEDTLS_CONFIG_HW_SUPPORT on all STM targets.
Fix issue: #6545
Pull request type