We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
The attached project is configured without TrustZone (this should be anyway default, but the cproject.yml specifies this explicit).
The CMSIS.pdsc defines:
<component Cclass="CMSIS" Cgroup="CORE" Cversion="6.1.0" condition="ARMv6_7_8-M Device" > <description>CMSIS-CORE for Cortex-M, SC000, SC300, Star-MC1, ARMv8-M, ARMv8.1-M</description> <files> <file category="header" name="CMSIS/Core/Include/tz_context.h" condition="TrustZone"/>
To Reproduce
Use this project and run cbuild setup CubeMX.zip
Expected behavior
tz_context.h should not be included in *.cbuild.yml
tz_context.h
components: - component: ARM::CMSIS:CORE@6.1.0 files: - file: ${CMSIS_PACK_ROOT}/ARM/CMSIS/6.1.0/CMSIS/Core/Include/tz_context.h # this is wrong category: header version: 6.1.0
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered:
The condition in the pdsc file checks for Dtz but not Dsecure
Dtz
Dsecure
<condition id="TrustZone"> <description>TrustZone</description> <require Dtz="TZ"/> </condition>
Dtz is set by the device description The trustzone node sets the Software Model Selection Dsecure
Sorry, something went wrong.
No branches or pull requests
Describe the bug
The attached project is configured without TrustZone (this should be anyway default, but the cproject.yml specifies this explicit).
The CMSIS.pdsc defines:
To Reproduce
Use this project and run cbuild setup
CubeMX.zip
Expected behavior
tz_context.h
should not be included in *.cbuild.ymlEnvironment (please complete the following information):
The text was updated successfully, but these errors were encountered: