Skip to content
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

Failed to build ARM_MUSCA_B1 with this example #44

Open
jamesbeyond opened this issue Aug 17, 2020 · 15 comments
Open

Failed to build ARM_MUSCA_B1 with this example #44

jamesbeyond opened this issue Aug 17, 2020 · 15 comments

Comments

@jamesbeyond
Copy link
Contributor

jamesbeyond commented Aug 17, 2020

What target(s) are you using?
ARM_MUSCA_B1

What toolchain(s) are you using?
GCC_ARM and ARMC6

What version of Mbed OS are you using (tag or sha)?
Master or mbed-os-6.4.0

to reproduce:
mbed test -t ARM -m ARM_MUSCA_B1

Failed to build ARM_MUSCA_B1 with this example

[Fatal Error] main.cpp@21,10: psa_initial_attestation_api.h: No such file or directory
[ERROR] ./main.cpp:21:10: fatal error: psa_initial_attestation_api.h: No such file or directory
   21 | #include "psa_initial_attestation_api.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ciarmcom
Copy link
Member

@jamesbeyond 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.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
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 mirroredto our internal defect tracking system or investigated until this has been fully resolved.

@ciarmcom
Copy link
Member

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

11 similar comments
@ciarmcom
Copy link
Member

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

@ciarmcom
Copy link
Member

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

@ciarmcom
Copy link
Member

ciarmcom commented Nov 4, 2020

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

@ciarmcom
Copy link
Member

ciarmcom commented Nov 9, 2020

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

@ciarmcom
Copy link
Member

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

@ciarmcom
Copy link
Member

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

@ciarmcom
Copy link
Member

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

@ciarmcom
Copy link
Member

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

@ciarmcom
Copy link
Member

ciarmcom commented Dec 5, 2020

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

@ciarmcom
Copy link
Member

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

@ciarmcom
Copy link
Member

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

@ciarmcom
Copy link
Member

@jamesbeyond This issue has an incomplete or old issue template.For future reference please use an up to date clone of the repository before raising issues. Many thanks.

@ciarmcom
Copy link
Member

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-3107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants