Versions Compared

Old Version 35

changes.mady.by.user Larry Li

Saved on

compared with

New Version Current

changes.mady.by.user Larry Li

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Image Added

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

If FreeRTOS is selected and there is access to NSC functions from a Thread in the Non-secure project, it is necessary to enable Allocate secure context for this thread in the configurator for that Thread.

Image Addedddd

1.3.6 USB debug interface setup

...

<Verify that FSP-RA4E1 has the same>

When developing with e2 studio e2studio and using Renesas evaluation kits for Trust Zone MCUs, the MCU is automatically transitioned from the CM state to the SSD state when the first secure program is downloaded to the MCU if the above required connection is provided.

...

  1. RA Flexible Software Package Users Manual
  2. Security Design with ARM Trust Zone using Cortex M33
  3. Renesas Device Life Cycle Management Key Injection
  4. Renesas Device Life Cycle Management for Cortex M33
  5. RA4E1 device data sheet
  6. Segger J-Link RTT
  7. J-Link Telnet Interface
  8. J-Link SDK

...