Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/robotdad/gpio_iotoggle_trustzone_nucleo_u5

GPIO_IOToggle_TrustZone_Nucleo_U5
https://github.com/robotdad/gpio_iotoggle_trustzone_nucleo_u5

Last synced: 11 months ago
JSON representation

GPIO_IOToggle_TrustZone_Nucleo_U5

Awesome Lists containing this project

README 

          
## GPIO_IOToggle_TrustZone Example Description



How to use HAL GPIO to toggle secure and unsecure IOs when TrustZone security is activated (Option bit TZEN=1).



The purpose of this example is to declare a secure IO with HAL GPIO and to toggle it

every second on Secure SysTick timer interrupt basis. All other IOs are released to

non-secure application and a non-secure IO is initialized by the non-secure application

to toggle every two seconds on Non-secure Systick timer interrupt basis.



The secure IO is PC.07 which corresponds to LED1 and the non-secure toggling IO is PB.07 for LED2.



The secure **LED1 toggles** every second and remains on in case of error in secure code.

The non-secure **LED2 toggles** twice faster and remains on in case of error in non-secure code.



This project is composed of two sub-projects:



- One for the secure application part (xxxxx_S)

- One for the non-secure application part (xxxxx_NS).



Please remember that on system with security enabled:



- the system always boots in secure and the secure application is responsible for

launching the non-secure application.

- the SystemInit() function in secure application sets up the SAU/IDAU, FPU and

secure/non-secure interrupts allocations defined in partition_stm32u575xx.h file.



This project shows how to switch from secure application to non-secure application

thanks to the system isolation performed to split the internal Flash and internal SRAM memories

into two halves:



 - The first half for the secure application and

 - The second half for the non-secure application.



User Option Bytes configuration:

Please note the internal Flash is fully secure by default in TZEN=1 and User Option Bytes

SECWM1_PSTRT/SECWM1_PEND and SECWM2_PSTRT/SECWM2_PEND should be set according to the application

configuration. Here the proper User Option Bytes setup in line with the project linker/scatter

file is as follows:



    - TZEN=1

    - SECWM1_PSTRT=0x0  SECWM1_PEND=0x7F  meaning all 128 pages of Bank1 set as secure

    - SECWM2_PSTRT=0x7F SECWM2_PEND=0x0   meaning all 128 pages of Bank2 set as non_secure



Any attempt by the non-secure application to access unauthorized code, memory or

peripheral generates a fault as demonstrated in non secure application by uncommenting some

code instructions in main.c.



This project is targeted to run on STM32U5 device on boards from STMicroelectronics.



This example configures the maximum system clock frequency at 160Mhz.



#### Notes



 1. Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds)

    based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from

    a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower)

    than the peripheral interrupt. Otherwise the caller ISR process will be blocked.

    To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function.



 2. The application need to ensure that the SysTick time base is always set to 1 millisecond

    to have correct HAL operation.



 3. The following sequence is needed to disable TrustZone:

 

      - **Boot from user Flash memory**: 

         a.	Make sure that secure and non-secure applications are well loaded and executed (jump done on non-secure application).

         b.	If not yet done, set RDP to level 1 through STM32CubeProgrammer. Then only Hotplug connection is possible during non-secure application execution.

         c.	Use a power supply different from ST-LINK in order to be able to connect to the target.

         d.	Uncheck the TZEN box and set RDP to level 0 (option byte value 0xAA), then click on Apply.



     - **Boot from RSS**:

         a.	Make sure to apply a high level on BOOT0 pin (make sure that nSWBOOT0 Option Byte is checked).

         b.	If not yet done, set RDP to level 1 through STM32CubeProgrammer. Then only Hotplug connection is possible during non-secure application execution.

         c.	Use a power supply different from ST-LINK in order to be able to connect to the target.

         d.	Uncheck the TZEN box and set RDP to level 0 (option byte value 0xAA), then click on Apply.

		 

	Please refer to AN5347 for more details.	 



### Keywords



System, GPIO, GTZC, Output, Alternate function, Push-pull, TrustZone



### Directory contents



  - Secure/Src/main.c                            Secure Main program

  - Secure/Src/secure_nsc.c                      Secure Non-secure callable functions

  - Secure/Src/stm32u5xx_hal_msp.c               Secure HAL MSP module

  - Secure/Src/stm32u5xx_it.c                    Secure Interrupt handlers

  - Secure/Src/system_stm32u5xx_s.c              Secure STM32U5xx system clock configuration file

  - Secure/Inc/main.h                            Secure Main program header file

  - Secure/Inc/partition_stm32u575xx.h           STM32U5 Device System Configuration file

  - Secure/Inc/stm32u5xx_hal_conf.h              Secure HAL Configuration file

  - Secure/Inc/stm32u5xx_it.h                    Secure Interrupt handlers header file

  - Secure_nsclib/secure_nsc.h                   Secure Non-Secure Callable (NSC) module header file

  - NonSecure/Src/main.c                         Non-secure Main program

  - NonSecure/Src/stm32u5xx_hal_msp.c            Non-secure HAL MSP module

  - NonSecure/Src/stm32u5xx_it.c                 Non-secure Interrupt handlers

  - NonSecure/Src/system_stm32u5xx_ns.c          Non-secure STM32U5xx system clock configuration file

  - NonSecure/Inc/main.h                         Non-secure Main program header file

  - NonSecure/Inc/stm32u5xx_hal_conf.h           Non-secure HAL Configuration file

  - NonSecure/Inc/stm32u5xx_it.h                 Non-secure Interrupt handlers header file



### Hardware and Software environment



  - This example runs on STM32U575xx devices with security enabled (TZEN=1).



  - This example has been tested with STMicroelectronics NUCLEO-U575ZI-Q (MB1549)

    board and can be easily tailored to any other supported device

    and development board.



  - User Option Bytes requirement (with STM32CubeProgrammer tool)



        - TZEN = 1                            System with TrustZone-M enabled

        - SECWM1_PSTRT=0x0  SECWM1_PEND=0x7F  All 128 pages of internal Flash Bank1 set as secure

        - SECWM2_PSTRT=0x7F  SECWM2_PEND=0x0  No page of internal Flash Bank2 set as secure, hence Bank2 non-secure



### How to use it ?



In order to make the program work, you must do the following :



IAR



 - Open your toolchain

 - Open Multi-projects workspace file Project.eww

 - Set the "xxxxx_S" as active application (Set as Active)

 - Rebuild xxxxx_S project

 - Rebuild xxxxx_NS project

 - Load the secure and non-secures images into target memory (Ctrl + D)

 - Run the example



MDK-ARM



 - Open your toolchain

 - Open Multi-projects workspace file Project.uvmpw

 - Select the xxxxx_S project as Active Project (Set as Active Project)

 - Build xxxxx_S project

 - Select the xxxxx_NS project as Active Project (Set as Active Project)

 - Build xxxxx_NS project

 - Load the non-secure binary (F8)

   (this shall download the \MDK-ARM\xxxxx_ns\Exe\Project_ns.axf to flash memory)

 - Select the xxxxx_S project as Active Project (Set as Active Project)

 - Load the secure binary (F8)

   (this shall download the \MDK-ARM\xxxxx_s\Exe\Project_s.axf to flash memory)

 - Run the example



STM32CubeIDE



 - Open STM32CubeIDE

 - File > Import. Point to the STM32CubeIDE folder of the example project. Click Finish.

 - Select and build the xxxxx_NS project, this will automatically trigger build of xxxxx_S project

 - Select the xxxxx_S project and select “Debug configuration”

   - Double click on “STM32 Cortex-M C/C++ Application”

   - Select  “Startup” >  “Add” >

 - Select the xxxxx_NS project

 - Build configuration : Select Release/Debug

   - Click Debug to debug the example