Page History

...

When e2studio/FSP is used, the S project and NS project reside in the same workspace and are linked to one another.  e2studio can generate NSC veneer.

Access to NSC drivers from a Non-secure project is possible through the Guard APIs. The FSP automatically generates guard functions for all the top-of-stack/driver APIs configured in the Secure project as Non-secure Callable.  Example below:

Image Added

1.3.5 Creating user-defined NSC functions

One can create a customized NSC API in the Secure project to expose only the top-level control of your algorithms and store the IP in the Secure Arm® Trust Zone® region. Precautions mentioned previously should be exercised during the creation of the user-defined NSC API.

The steps to create a customized NSC API are:

1. Create the Non-secure Callable custom function by declaring the function with BSP_CMSE_NONSECURE_ENTRY.
2. Create a header file that includes all the customized NSC function prototypes, for example, my_nsc_api.h.
3. Include the path to the NSC header using the Build Variable as shown in below figure.
4. Compile the Secure project to create the Secure Bundle. The NSC header will be automatically extracted for use in the Non-secure project.

Image Added

1.3.5 S code calling NS code

...