原创 IAR 的Evaluation版本和Kickstart版本区别

IAR 的Evaluation版本和Kickstart版本有何区别呢？

Luminary下有的链接是Kickstart版的，有的是Evaluation的。

The following product packages are available:


Standard edition
The standard edition has all features implemented.

Limited edition
The limited edition is a version of IAR Embedded Workbench with the follwing limitations:
The C-SPY debugger is not available,
MISRA C is not available.

Baseline edition
The baseline edition is a low-priced version of IAR Embedded Workbench with the follwing limitations:
The compiler supports a maximum of 256 Kbytes of generated code,
MISRA C is not available,
The linker will link a maximum of 256 Kbytes originating from C/C++ and assembler source code.

Kickstart edition
The kickStart edition is a special starter-kit/evaluation version of IAR Embedded Workbench with limitations both in code size and in the service and support that is provided. Limitations:
The code limit of the compiler is typically set to 32 Kbytes, this is true for all supported ARM cores including Cortex-M3,
MISRA C is not available,
The runtime library source code is not available,
The linker will link the number of bytes up to the preset code size limit for the compiler, originating from C/C++ and assembler source code,
The object files generated by the compiler are in an encrypted form and will only be readable by the IAR ILINK linker. The linker will also read AEABI compliant ELF/DWARF code for linking of legacy and third party code.
Compiler assembly list output is disabled.
If you have a kickstart license issued before the release of 4.41A your code limit will be 8 Kbytes for Cortex-M3. Remove your kickstart license in the license manager and request a new license on www.iar.com to upgrade to 32 Kbytes.

Evaluation edition
The Evaluation edition is a time-limited evaluation version that you can use for 30 days. Limitations:
Expires 30 days after generation of the evaluation key,
MISRA C is not available,
The runtime library source code is not available.
The object files generated by the compiler are in an encrypted form and will only be readable by the IAR ILINK linker. The linker will also read AEABI compliant ELF/DWARF code for linking of legacy and third party code.
Compiler assembly list output is disabled.