search

ARMmbed / mbed-os-example-mbed-crypto

Mbed Crypto example for Mbed OS 5
Apache License 2.0
5 stars 19 forks source link

Doesn't seem to work for NUCLEO_F767ZI #91

Open jameshoweee opened 3 years ago

jameshoweee commented 3 years ago

Description of defect

I get issues running mbed compile -m NUCLEO_F767ZI -t GCC_ARM

The error is to do with not being able to find files e.g. #include "psa/crypto.h". The directory the main.cpp file is in doesn't have a psa/ folder.

Is PSA required or why it cant find it?

Target(s) affected by this defect ?

NUCLEO_F767ZI and other Nucleos.

Toolchain(s) (name and version) displaying this defect ?

I'm using GNU ARM GGC 10.2.1, which may be an issue as it says <10.0.0, but this doesn't cause any issues for the example target K64F.

What version of Mbed-os are you using (tag or sha) ?

mbed-os-6.10.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

Not relevant

How is this defect reproduced ?

Compile this example with the defined target and you should hit the error.

ciarmcom commented 3 years ago

@jameshoweee thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words. How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered. Please update the issue header with the missing information, the issue will not be mirrored to our internal defect tracking system or investigated until this has been fully resolved.

jameshoweee commented 3 years ago

I get issues running mbed compile -m NUCLEO_F767ZI -t GCC_ARM

The error is to do with not being able to find files e.g. #include "psa/crypto.h". The directory the main.cpp file is in doesn't have a psa/ folder.

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

0xc0170 commented 3 years ago

PSA is a feature to be enabled. Quick checking at NUCLEO_F767ZI, they do not enable PSA feature. K64F for instance does. Have you verified PSA feature is enabled and being included in the build?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

@jameshoweee it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

ciarmcom commented 3 years ago

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-4277