Arm Community
Arm Community
  • Site
  • User
  • Site
  • Search
  • User
Open Source Software and Platforms
Open Source Software and Platforms
Wiki MPS2+ SSE-200 Devices Secure/Non-secure Example
  • Help
  • Jump...
  • Cancel
  • About this wiki
  • Supported platforms
  • Obtaining support
  • +Arm Reference Platforms deliverables
  • +A-class platforms
  • +M-class platforms
  • +R-class platforms
  • -FPGA prototyping boards
    • -MPS2(+) FPGA prototyping board
      • MPS2(+) M-class prototyping system
      • Keil Board Support Packs for MPS2(+)
      • -Keil pack for SSE-200 IoT System for MPS2+
        • -SSE-200 for MPS2+ Software Examples
          • MPS2+ SSE-200 TF-M Examples User Guide
          • MPS2+ SSE-200 Devices Example
          • MPS2+ SSE-200 Devices Secure/Non-secure Example
          • MPS2+ SSE-200 Secure/Non-secure Blinky Example
      • Running uCLinux on the Arm MPS2(+) platform
      • MPS2(+) Mbed OS automated testing
      • FPGA Prescale register address incorrect in MPS2(+) software header file
      • MPS2+ Firmware update for reboot.txt method
    • +MPS3 FPGA Prototyping System
  • +Open source software

You are currently reviewing an older revision of this page.

  • History View current version

MPS2+ SSE-200 Devices Secure/Non-secure Example

PLEASE NOTE: These examples do not build when Keil Arm MPS2 SSE-200 BSP v2.0.0 or later is installed.

This example shows the same functionality described in the MPS2 device example. However, the implementation is different. The implementation is divided into secure and non-secure code.

The secure code performs the following functionality:

  • Sets secure and non-secure system configuration.
  • Gets and provides button states.
  • Gets and provides touchscreen information.
  • Sleep function.
  • Switchs on/off user LEDs based on user button states.

The non-secure code performs the following functionality:

  • Requests to the secure code:
    • Button states.
    • If the touchscreen is pressed in the central area.
    • Sleep for X amount of ms.
  • Switches on/off the SCC LEDs.

To compile the example correctly it is necessary to first compile the secure code, and then the non-secure code.
Compiling the secure code generates the veneers object file required by the non-secure code to compile correctly.

See the ReadMe file provided with the example for further information.