K64F: Add call to uvisor_init() in the startup code

This is backwards-compatible with unsupported targets.

If an application is compiled using the K64F target without uVisor
(UVISOR_PRESENT not set or set to 0) then uvisor_init() will just be an
empty function that immediately returns.
pull/1753/head
Alessandro Angelino 2016-06-09 11:53:59 +01:00 committed by Milosch Meriac
parent 6aeafab6b3
commit a076f9a415
1 changed files with 9 additions and 0 deletions

View File

@ -332,6 +332,15 @@ Reset_Handler:
ldr r0,=SystemInit
blx r0
#endif
/* The call to uvisor_init() happens independently of uVisor being enabled or
* not, so it is conditionally compiled only based on FEATURE_UVISOR. */
#ifdef FEATURE_UVISOR
/* Call uvisor_init() */
ldr r0, =uvisor_init
blx r0
#endif /* FEATURE_UVISOR */
/* Loop to copy data from read only memory to RAM. The ranges
* of copy from/to are specified by following symbols evaluated in
* linker script.