You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/lib/INTRO.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
###uVisor
1
+
## uVisor
2
2
3
3
The uVisor is a self-contained software hypervisor that creates independent secure domains on ARM Cortex®-M3 and Cortex®-M4 microcontrollers. It increases resilience against malware and protects secrets from leaking even among different modules of the same application. You can find a [high-level overview here](http://www.slideshare.net/FoolsDelight/practical-realtime-operating-system-security-for-the-masses) ([Download PDF](https://github.com/ARMmbed/uvisor/raw/docs/uVisorSecurity-TechCon2016.pdf)).
4
4
@@ -12,7 +12,7 @@ When the uVisor is enabled, all NVIC APIs are rerouted to the corresponding uVis
12
12
13
13
Although this behavior is different from that of the original NVIC, it is backward compatible. Legacy code (such as a device HAL) still works after uVisor is enabled.
14
14
15
-
####Usage
15
+
### Usage
16
16
17
17
1. Include uVisor library in your application.
18
18
1. Specify capabilities in mandatory access control list.
@@ -22,20 +22,20 @@ Although this behavior is different from that of the original NVIC, it is backwa
22
22
23
23
For detailed usage guides and best practices, look [here](https://github.com/ARMmbed/uvisor/blob/master/docs/README.md)
This is a simple example to show how to write a uVisor-secured threaded application with IRQ support. One LED blinks periodically from the public box main thread. A secure box exclusively owns the second LED, which toggles you press the user button.
0 commit comments