How are LPCOpen releases named?

lpcware-support — Wed, 30 Mar 2016 23:51:57 GMT

LPCOpen releases are named from the release version, supported platform(s) in the release, and supported toolchain(s) in the release.

Version of release
- Example: 2_01 indicates release v2.01
- Example:2_03a indicates release v2.03a
Support toolchain(s) for the release
- 'lpcxpresso' indicates the LPCXpresso toolchain
- 'keil' indicates the Keil Uvision (MDK) toolchain
- 'iar' indicates the IAR Embedded Workbench toolchain
Board or platforms for the release
- Example: lpcxpresso_812 indicates the LPCXpresso LPC812 board
- Example: hitex_eva_4350 indicates the Hitex LPC4350 evaluzation board

The LPCOpen release file name always startyed with 'lpcopen' and concatenates the version, supported toolchain(s), and supported platform(s) into the name in that order.

The full name is indicated like this:

lpcopen_<version>_(toolchains>_<platforms>

Example for a v2.01 release reelased for both Keil and IAR toolchains for the LPCXPresso LPC812 board.

lpcopen_2_01_keil_iar_lpcxpresso_812.zip

It is common for the Keil and IAR toolchains to be released in a single package.

Example for a v2.10a release reelased for the LPCXpresso toolchain for the LPCXPresso LPC11U37 board.

lpcopen_2_10a_lpcxpresso_lpcxpresso_812.zip

LPC FAQsのトピックHow are LPCOpen releases named?

How are LPCOpen releases named?