Keil Option选项Target页面说明

1. Target页面 

           

•      Xtal (MHz) : specifies the XTAL frequency of your device to be used for configuring the debugger and Flash programmer. Note that XTAL reflects the main oscillator externally connected to the device.
•     Operating System(操作系统):  allows to select the RTX Kernel which adds the correct RTX library and enables kernel aware debugging. Not required for Keil RTX5.

• System Viewer File： specifies the System View Description (SVD) file for debugging peripheral registers with the System Viewer. Using software packs, this is already pre-filled.

• Use Custom File, when checked allows to select a custom System Viewer Description (SVD) file. For details refer to Adding System Viewer Windows

 

     Software Model (only for Armv8-M devices) lets you select the software model of the project:

Options	Description
Non-Secure Mode (default)	Code generated runs in non-secure context. Usually, a secure library is required for calling secure functions.
Secure Mode	Code generated runs in secure context. Accesses from the outside have to go through the secure gateway (SG) function.
TrustZone disabled	Code generated does not use any security settings. Programmer's model is similar to Armv7-M.

    Use MicroLIB to change the C run-time library set for smallest code application code. MicroLIB is not fully ANSI compatible but sufficient for most small embedded applications，具体详见

                http://t.zoukankan.com/longbiao831-p-7155380.html

Floating Point Hardware (only for devices integrated FPU) tells the compiler whether floating point operations should be handled via emulating floating point operations, or whether the floating point hardware instructions of the process should be used instead (which will make the execution faster). If the hardware offers only single precision floating point operations, then only double precision operation need emulation. If the hardware supports double precision, then the double precision instructions can be generated and executed by the processor giving you the performance benefit for double precision computation. Refer to Floating-point support for details.

The options listed in the tables below depend on the device in use and are shown for devices with an implemented FPU.

• Floating Point Hardware options for Cortex-M7 and Cortex-M55 with single precision FPU:

  Options	Description
  Not Used	Code generated does not use any VFP instructions.
  Use Single Precision (default)	Code generated uses VFP single precision instructions.

• Floating Point Hardware options for Cortex-M7 and Cortex-M55 with double precision FPU:

  Options	Description
  Not Used	Code generated does not use any VFP instructions.
  Use Single Precision	Code generated uses VFP single precision instructions.
  Use Double Precision (default)	Code generated uses VFP double precision instructions.

• Floating Point Hardware options for Cortex-M4 with FPU:

  Options	Description
  Not Used	Code generated does not use any VFP instructions.
  Use Single Precision (default)	Code generated uses VFP single precision instructions.

• Floating Point Hardware options for Arm9 with FPU:

  Options	Description
  Not Used	Code generated does not use any VFP instructions (Compiler switch: none, Assembler switch: none)
  Library calls	Compiler generates library calls that use VFP instructions (generates typically the smallest code and should be used when Thumb mode is selected) (Compiler switch: --fpu=softvfp+vfpv2, Assembler switch: --fpu=vfpv2)
  In-line (strict ANSI) (default)	Compiler mostly uses the VFP unit with in-line code (generates fast code that conforms to the ANSI standard). (Compiler switch: --fpu=vfpu2, Assembler switch: --fpu=vfpv2)
  In-line (fast)	Compiler uses for all VFP instructions in-line code (error checking does not always conform to the ANSI standard). (Compiler switch: --fpu=vfpv2 --fpmode=fast, Assembler switch: --fpu=vfpv2)