Mcuxsdkpacksgsug Cleaned

MCUXSDKPACKSGSUG
Getting Started with MCUXpresso SDK CMSIS Packs

Rev. 1 — 08 August 2020 User's Guide
Contents
1 Introduction 1 Introduction......................................1
2 MCUXpresso SDK CMSIS packs
The MCUXpresso Software Development Kit (SDK) is a comprehensive
introduction......................................1
software enablement package designed to simplify and accelerate application
® ® 3 Installing MCUXpresso SDK CMSIS
development with NXP’s MCUs based on Arm Cortex -M cores. The pack.................................................2
MCUXpresso SDK includes production-grade software with integrated RTOS 4 Opening a demo application........... 6
(optional), integrated stacks and middleware, reference software, and more. 5 Creating a new application............ 12
For more information about the MCUXpresso SDK, see MCUXpresso 6 Converting a project created with Keil
CMSIS packs to NXP MCUXpresso
SDK homepage.
SDK CMSIS packs........................ 27
The MCUXpresso SDK is distributed in two ways:
• SDK packages downloaded from MCUXpresso SDK builder homepage
• CMSIS packs downloaded from the MCUXpresso packs repository
NOTE
The CMSIS pack repository is only accessible in the Pack Installer (MDK µVision or Pack Manager (IAR
Workbench) tools.
This document describes how to download the MCUXpresso SDK CMSIS packs, how to open the demo application, and how to
create a new project using the packs.
2 MCUXpresso SDK CMSIS packs introduction

It is recommended to check the latest news, descriptions of problems and their solutions, user experiences with MCUX SDK
CMSIS packs on the NXP community, in the MCUXpresso software and tools community space.
2.1 CMSIS pack standard

The CMSIS pack is a delivery mechanism for software components, devices, and evaluation boards support. The CMSIS pack
standard is defined by Arm and supported by various IDE vendors including the Keil uVision and IAR Embedded Workbench for
Arm IDEs.
The CMSIS standard recognizes three main types of CMSIS packs:
• Pack with software components (Software Pack, SWP)
• Pack with device support (Device Family Pack, DFP)
• Pack with board support (Board Support Pack, BSP)
The software components (CMSIS components) are a collection of source modules, header and configuration files, and libraries.
They can be used in all three types of CMSIS packs. Each CMSIS component has a unique identification that serves also for
components organization in the IDE CMSIS component managers: CMSIS component vendor, bundle, class, group, subgroup,
variant, and version.
NXP Semiconductors
Installing MCUXpresso SDK CMSIS pack
The content of the CMSIS packs including CMSIS components is described by the XML-based package description (PDSC) file.
The PDSC file is designed for software development environments and describes the user- and device-relevant context for the
files supplied within a pack.
For more information about the CMSIS pack standard, see CMSIS Pack Documentation homepage.
2.2 CMSIS packs with MCUXpresso SDK overview

The MCUXpresso SDK is delivered in the Device Family Packs and the Board Support Packs.
2.2.1 MCUXpresso SDK DFPs
A DFP provides minimal device support. Installing a DFP provides enough resources to create, compile, and debug MCUXpresso
SDK projects.
The MCUXpresso SDK DFP contains:
• Device header files and system initialization modules
• Startup files
• Linker files
• SVD files
• Flash drivers (for some development tools)
• SDK drivers and utilities
• SDK project templates
The content of the DFP is organized into these CMSIS components:
• Startup, contains a minimal set of sources needed to create and compile MCUXpresso SDK projects
• SDK drivers
• SDK utilities
• SDK CMSIS drivers
• RTE Device SDK project template, contains the RTE_Device.h file required by CMSIS drivers
• Board SDK project template, contains board, clock configuration, peripherals, and pin mux SDK configuration files with
general implementation
2.2.2 MCUXpresso SDK BSPs
The BSP provides support for NXP evaluation boards and example projects for the boards.
The MCUXpresso SDK BSP contains:
• Example projects and demo applications
• SDK project templates containing the board, clock configuration, peripherals, and pin mux SDK configuration files
implemented for a specific board
3 Installing MCUXpresso SDK CMSIS pack

®
This section describes the installation of the MCUXpresso SDK CMSIS packs in the Keil MDK/μVision and IAR Embedded
Workbench for Arm IDEs. The MK64F12 DFP is used as an example. However, the following steps can be used to install any
MCUXpresso SDK CMSIS packs.
Getting Started with MCUXpresso SDK CMSIS Packs, Rev. 1, 08 August 2020
User's Guide 2 / 40
NXP Semiconductors
NOTE
The MCUXpresso SDK CMSIS packs use the Arm CMSIS pack. Make sure that the Arm CMSIS pack is installed in
your development environment. In the Keil MDK/μVision IDE, this pack is installed by default. To install it in the IAR
Embedded Workbench for Arm IDE, go to Project > CMSIS-Packs > Pack Installer. In the CMSIS Pack Manager
window, go to Arm > CMSIS and install the Arm CMSIS pack. See the MCUXpresso SDK CMSIS Packs Release
Notes for the version of the Arm CMSIS pack to use.
®
3.1 Installing MCUXpresso SDK CMSIS pack using Keil MDK/μVision IDE
1. Open the Pack Installer. Go to Project > Manage > Pack Installer or use the toolbar:
Figure 1. Running Pack Installer from Keil MDK/μVision IDE toolbar
2. In the Pack Installer, on the left pane, you can switch between the Devices and Boards views. In the Devices view,
select NXP > MK64F12 or type MK64F12 into the Search field on the top.
3. On the right pane, you can switch between the Packs and Examples views. In the Packs view, the CMSIS packs related
to a device or a board are selected on the left pane. Find NXP MK64F12_DFP and click the Install button next to it.
Figure 2. Pack installation in Keil MDK/μVision IDE Pack Installer
4. Before the pack installation, accept the license agreement. After you accept the license terms, the pack is installed.
User's Guide 3 / 40
NXP Semiconductors
Figure 3. License agreement dialog
5. Close Pack Installer.
3.2 Install MCUXpresso SDK CMSIS pack using IAR Embedded Workbench for Arm IDE
3.2.1 IAR Embedded Workbench 8.2.x
1. Add Keil CMSIS pack repository to Remote Pack Repositories. Go to Tools > Options and in the CMSIS Pack options
add http://www.keil.com/pack to Remote Pack Repositories. Click OK.
User's Guide 4 / 40
NXP Semiconductors
Figure 4. Remote Pack Repositories in IAR Embedded Workbench for ARM tool options
2. Open the Pack Installer. Go to Project > CMSIS-Packs > Pack Installer or use the toolbar:
Figure 5. Running Pack Installer from IAR Embedded Workbench for Arm IDE toolbar
3. In the Pack view, select NXP > MK64F12_DFP.

4. Expand MK64F12_DFP to see the available versions of this pack. Right-click the required version and click on Install in
the pop-up menu.
User's Guide 5 / 40
NXP Semiconductors
Opening a demo application
Figure 6. Pack installation in IAR Embedded Workbench for Arm IDE Pack Installer
3.2.2 IAR Embedded Workbench 8.3.x and later versions

1. Open the CMSIS Manager via Project > CMSIS-Pack manager. Click on 'Check for updates' button and after that you
should be able to see:
2. In the "Device Specific" packs, find NXP.MK6412_DFP, click “Install” and the most recent version of the pack will be
installed. If unable to find the NXP pack, check the note below.
3. Close the CMSIS Manager.
NOTE
If you cannot find NXP CMSIS packs on a list of available packs in the CMSIS Pack Manager, add the Keil CMSIS
pack repository to Remote Pack Repositories. In CMSIS Manager go to Window > Preferences and select CMSIS
Packs in the left pane. Here you can add www.keil.com/pack to Remote Pack Repositories. Click the ‘Apply and
Close’ button. After that the NXP CMSIS-packs should appear in the list.
4 Opening a demo application

This section describes how to open a demo application from the MCUXpresso SDK BSP in the Keil MDK/μVision and IAR
Embedded Workbench for Arm IDEs. The Hello World demo from the FRDM-K64F BSP is used to demonstrate the process. The
same steps can be used to open all example projects in the MCUXpresso SDK BSPs.
User's Guide 6 / 40
NXP Semiconductors
4.1 Opening an example application using Keil MDK/μVision IDE

1. Go to Project > Manage > Pack Installer and install the NXP MK64F12_DFP and NXP FRDM-K64F_BSP packs. Make
sure that the Arm CMSIS pack is also installed.
2. In the Pack Installer, on the left pane, select the Boards view and select the FRDM-K64F board. Use the Search field at
the top of the window to filter the board. To make sure that a correct BSP is selected, hover the mouse cursor over the
board name. The NXP.FRDM-K64F_BSP pack should be shown as the parent pack.
Figure 7. Board selection in Keil MDK/μVision Pack Installer
3. On the right pane, select the Examples view and select an example application. Click the Copy button next to it.
Figure 8. Example selection from a pack in Keil MDK/μVision IDE Pack Installer
4. Choose the directory to copy the demo application into. If you want to keep the directory structure from the pack, tick the
Use Pack Folder Structure checkbox. Tick the Launch μVision checkbox to automatically open the copied project. Click
the OK button.
User's Guide 7 / 40
NXP Semiconductors
Figure 9. Copying example from pack in Keil MDK/μVision IDE
5. A new instance of the μVision IDE with the selected example application is opened. Now build and run the example
application.
Figure 10. Example project from pack in Keil MDK/μVision IDE
4.2 Opening an example application using IAR Embedded Workbench for Arm
1. Go to Project > CMSIS-Packs > Pack Installer and install the NXP MK64F12_DFP and FRDM-K64F_BSP packs. Make
sure that the Arm CMSIS pack is also installed.
2. Go to Project > Create New Project…, select the CMSIS Pack example and click the OK button.
User's Guide 8 / 40
NXP Semiconductors
Figure 11. Creating a new project from example in pack in IAR Embedded Workbench for Arm IDE
3. Go to NXP > MK64F12 > MK64FN1M0xxx12 and select one of the package variants. You can also use the Search field
above the device selector. Click the Next button.
User's Guide 9 / 40
NXP Semiconductors
Figure 12. Creating a new project from example in pack in IAR Embedded Workbench for Arm IDE
4. Select the hello_world example from demo_apps/hello_world. Click the Finish button.
Figure 13. Selecting an example from pack in IAR Embedded Workbench for Arm IDE
User's Guide 10 / 40
NXP Semiconductors
5. Choose the directory to copy the demo application into and click the OK button.
6. The Hello World demo application is opened. Now you can build and run the demo.
Figure 14. Example project from pack in IAR Embedded Workbench for Arm IDE
4.2.2 IAR Embedded Workbench 8.3.x and later versions

1. Go to the CMSIS Manager via Project > CMSIS-Pack manager and install NXP MK64F12_DFP and FRDMK64F_BSP
packs. Make sure that ARM CMSIS pack is also installed.
NXP Semiconductors
Creating a new application
2. In CMSIS-Pack manager, go to "Examples" and look for an example project:
3. Now click the "Copy" button to open the example project in your workspace.
4. A sub-window in the CMSIS-Pack manager will be opened, allowing you to configure your example project further:
5 Creating a new application

This section describes how to create a new project using the MCUXpresso SDK CMSIS packs in the Keil MDK/μVision and
IAR Embedded Workbench for Arm IDEs. A new project for the MK64F1M0VLL12 device from the MK64F12_DFP pack is
used to demonstrate the process. However, the same steps can be used to create new project for all devices supported in the
MCUXpresso SDK DFPs.
NXP Semiconductors
NOTE
Depending on the IDE version used, configuring the newly created project may be difficult. To easily configure a
project, start with an existing demo application and modify it according to your needs.
5.1 Creating a new application using Keil MDK/μVision IDE

1. Go to Project > Manage > Pack Installer and install NXP MK64F12_DFP. Make sure that the Arm CMSIS pack is also
installed.
2. Go to Project > New μVision Project… and select the folder for the new project.
3. Go to NXP > MK64F12 and select a device package variant, for example MK64F1M0VLL12. You can also use the
Search field to find devices.
Figure 15. Device selection in Keil MDK/μVision IDE
4. Open Manager Run-Time Environment in Project > Manage > Run-Time Environment. Here you can add and remove
components in the project.
a. To create a basic MCUXpresso SDK project, enable the Device > Startup component. This component contains
a basic set of files for a new project. Resolve the unresolved dependencies, if reported. To resolve the
dependencies, select a required component manually or click the Resolve button to auto-resolve.
NXP Semiconductors
Figure 16. Creating a basic MCUXpresso SDK project in Keil MDK/μVision IDE
b. To create a new project with a minimal set of MCUXpresso SDK components, enable the Board Support > SDK
Project Template > project_template component. This component contains the board configuration files used by
the MCUXpresso SDK and requires additional MCUXpresso SDK components to create a simple Hello World
application.
After the project_template component is enabled, the number of missing components is reported. To add
the missing MCUXpresso SDK components required to build a simple MCUXpresso SDK project, click the
Resolve button.
NXP Semiconductors
Figure 17. Creating an MCUXpresso SDK project in Keil MDK/μVision IDE
c. If you also install FRDM-K64F_BSP, you can select a project template with the board configuration files
preconfigured for that specific board by switching the variant of the project template component.
Figure 18. Selecting a board-specific MCUXpresso SDK project template in Keil MDK/μVision IDE
NXP Semiconductors
5. Click OK to close the Run-Time Environment Manager.

6. Add the main function. Right-click Source Group 1 and select Add New Item to Group. Select C File (.c) and add
“main” to Name. Click Add. A new main.c file is added to the project where you can add the main() function of your
application.
Figure 19. Adding a new file in Keil MDK/μVision IDE
NXP Semiconductors
Figure 20. Creating main.c file in Keil MDK/μVision IDE
7. To correctly build the MCUXpresso SDK project, use the scatter file included in the MCUXpresso SDK pack. To make
sure that the scatter file is not generated by the Keil MDK/μVision IDE and a file from the pack is used instead, go
to Project > Options for Target > Linker and make sure that the Use Memory Layout from Target Dialog option is not
enabled.
NXP Semiconductors
Figure 21. Disabling a generated scatter file in Keil MDK/μVision IDE
8. Build and debug your application.
5.2 Creating a new application using IAR Embedded Workbench for Arm IDE
1. Go to Project > CMSIS-Packs > Pack Installer and install NXP MK64F12_DFP. Make sure that the Arm CMSIS pack is
also installed.
2. Go to Project > Create New Project…, select Empty CMSIS Pack project, and click the OK button.
NXP Semiconductors
Figure 22. Creating a new project in IAR Embedded Workbench for Arm IDE
3. Select NXP > MK64F12 > MK64FN1M0xxx12 > MK64F1M0VLL12. You can also use the Search field above the device
selector. Click the Next button.
NXP Semiconductors
Figure 23. Device selection in IAR Embedded Workbench for Arm IDE
4. Open Project CMSIS Component Manager in Project > CMSIS-Pack > Project Components. Here you can add and
remove the components in the project.
a. To create a basic MCUXpresso SDK project, enable the Device > Startup component. This component contains
a basic set of files for a new project. To use it, enable also the CMSIS > CORE component, which is highlighted
in a yellow color as a dependency for Device > Startup. Enable the CMSIS > CORE component manually or click
the Resolve button to resolve the dependency automatically.
NXP Semiconductors
Figure 24. Creating a basic MCUXpresso SDK project in IAR Embedded Workbench for Arm IDE
b. To create a new project with a minimal set of MCUXpresso SDK components, enable the Board Support > SDK
Project Template > project_template component. This component contains the board configuration files used by
the MCUXpresso SDK and requires additional MCUXpresso SDK components to create a simple Hello World
application.
After the project_template component is enabled, the number of missing components is reported. Click the
Resolve button to add the missing MCUXpresso SDK components required to build a simple MCUXpresso
SDK project.
NXP Semiconductors
Figure 25. Creating an MCUXpresso SDK project in IAR Embedded Workbench for Arm IDE
c. If you also install FRDM-K64F_BSP, you can select the project template with the board configuration files
preconfigured for that specific board by switching the variant of the project template component.
NXP Semiconductors
Figure 26. Selecting a board-specific MCUXpresso SDK project template in IAR Embedded Workbench
for Arm IDE
5. Click the OK button to close the Project CMSIS Component Manager.

6. Add the main function. Go to File > New File and create a new main.c file where you add the main() function of your
application. Add the created file to the project using Project > Add Files….
7. Build and debug your application.
NOTE
To debug projects using the CMSIS DAP debugger, the default flash loader .board file used by the IAR
Embedded Workbench IDE must be overridden. In the project options, go to Debugger > Download, enable
Override default .board file, and select the .board file from {IAR Embedded Workbench installation
directory}\arm\config\flashloader\NXP\. In Debugger > CMSIS DAP > Reset, set the reset source
to Software.
NXP Semiconductors
Figure 27. Overriding default flash loader in IAR Embedded Workbench for Arm IDE
NXP Semiconductors
Figure 28. Setting CMSIS DAP software reset in IAR Embedded Workbench for Arm IDE
5.2.2 IAR Embedded Workbench 8.3.x or later versions

1. Go to Project > CMSIS Manager and install NXP MK64F12_DFP. Make sure that Arm CMSIS pack is also installed.
2. Go to Project > Create New Project…, select Empty CMSIS Pack project and click the OK button.
3. Select NXP > MK64F12 > MK64FN1M0xxx12 > MK64F1M0VLL12 . You can also use the Search field above the
device selector.
4. Click the Next button.
5. Once confirmed, you are automatically asked to select the components that you want to use in your project in the
CMSIS manager:
a. To create basic MCUXpresso SDK project, enable Device > Startup component. This component contains basic set
of files for a new project. To use it, you also have to enable CMSIS > CORE component, which is highlighted in yellow
color as dependency for the Device > Startup . Enable the CMSIS > CORE component manually or click the Resolve
button to resolve the dependency automatically.
NXP Semiconductors
Figure 29. Resolving dependencies
b. To create a new project with minimal set of MCUXpresso SDK components, enable Board Support > SDK
Project Template > project_template component. This component contains board configuration files used by
MCUXpresso SDK and requires additional MCUXpresso SDK components that are a must for creating a simple Hello
World application.
Figure 30. Add missing MCUXpresso SDK components
c. If you also install FRDM-K64F_BSP, you can select project template with board configuration files preconfigured for
that specific board by switching variant of the project template component.
Figure 31. Switching variant of the project template component
NXP Semiconductors
Converting a project created with Keil CMSIS packs to NXP MCUXpresso SDK CMSIS packs
6. Close the CMSIS-pack manager.

7. Add the main function. Go to File > New File and create a new main.c file where you can add main() function of your
application. Add the created file to the project using Project > Add Files….
8. You can build and debug your application now.
6 Converting a project created with Keil CMSIS packs to NXP MCUXpresso

SDK CMSIS packs
This section describes how to convert an existing project built on the CMSIS packs for NXP devices created by Keil. The process
is described using the conversion of a project created for the MK64F1M0xxx12 device from the Keil pack to a project using the
MK64FN1M0VLL12 device from the MCUXpresso SDK pack in the Keil MDK/μVision and IAR Embedded Workbench for Arm
IDEs. The same steps can be used to convert projects for all devices supported in the MCUXpresso SDK DFPs.
NOTE
It is recommended to create a backup copy of the project before the conversion.
NOTE
Using the Keil MDK/μVision IDE, after switching the project to a device from a different CMSIS pack, the debugger
selected in the project debug settings is not preserved. The debugger is automatically set to ULINK and must be
restored manually.
6.1 Convert a project created with Keil CMSIS packs to NXP MCUXpresso SDK CMSIS packs
using Keil MDK/μVision IDE
1. Go to Project > CMSIS-Packs > Pack Installer and install MK64F12_DFP.
2. Go to Project > Options for Target > Device.
3. NXP > K60 Series > MK64FN1M0xxx12 is selected in the device selector. Change it to NXP > MK64F12 >
MK64FN1M0VLL12.
CMSIS packs produced by the Keil IDE use the Keil. prefix in the pack name visible in Software Pack > Pack and
www.keil.com/pack in Software Pack > URL.
NXP Semiconductors
Figure 32. Device from Keil pack in Keil MDK/μVision IDE
MCUXpresso SDK CMSIS packs produced by NXP use the NXP. prefix in the pack name visible in Software Pack > Pack
and mcuxpresso.nxp.com/cmsis_pack/repo in Software Pack > URL.
NXP Semiconductors
Figure 33. Device from MCUXpresso SDK pack in Keil MDK/μVision IDE
4. In Options for Target, switch from the Device to the Debug tab. Restore the debugger used in the project.
NXP Semiconductors
Figure 34. Debugger settings in Keil MDK/μVision IDE
5. Click the OK button to close Options for Target.

6. Open Run-Time Environment manager. The Device > Startup component is switched to a component from the NXP
MK64F12 DFP. If the component is not switched automatically, switch it manually. Distinguish the components by
hovering the mouse cursor over the component name. The parent pack is shown in the hint.
NXP Semiconductors
Figure 35. Component from Keil pack in Keil MDK/μVision IDE
Figure 36. Component from MCUXpresso SDK pack in Keil MDK/μVision IDE
NXP Semiconductors
7. In the Project window, the Startup component files from the NXP MCUXpresso pack replaced the files from the Keil
pack. Note that the files from the Keil pack are still available in the {project}\RTE\Device\MK64FN1M0xxx12\ directory.
Figure 37. Startup component from Keil pack in Keil MDK/μVision IDE
Figure 38. Startup component from KMCUXpresso SDK pack in Keil MDK/μVision IDE
NXP Semiconductors
8. Add more MCUXpresso SDK components using the Run-Time Environment manager. To make sure that the
MCUXpresso SDK components work properly. It is recommended to use the scatter file included in the MCUXpresso
SDK Device Family Pack. To make sure that the scatter file is not generated by the Keil MDK/μVision IDE and the file
from the pack is used instead, go to Project > Options for Target > Linker and make sure that the Use Memory Layout
from Target Dialog option is not enabled.
Figure 39. Disabling generated scatter file in Keil MDK/μVision IDE
6.2 Convert project created with Keil CMSIS packs to NXP MCUXpresso SDK CMSIS packs
using IAR Embedded Workbench for Arm 8.2.x
1. Go to Project > Options > General Options. On Target tab. Select CMSIS-Pack processor variant and click on button
next to it to open device selector.
NXP Semiconductors
Figure 40. Changing device in IAR Embedded Workbench for Arm
2. You can see NXP > K60 Series > MK64FN1M0xxx12 selected in the device selector. Change the selection to NXP >
MK64F12 > MK64FN1M0xxx12 > MK64FN1M0VLL12. Click the OK button to close device selector.
NXP Semiconductors
Figure 41. Device selection in IAR Embedded Workbench for Arm
MCUXpresso SDK CMSIS packs produced by Keil use the Keil. prefix in pack name visible in the device selector.
NXP Semiconductors
Figure 42. Device from Keil pack in IAR Embedded Workbench for Arm
MCUXpresso SDK CMSIS packs produced by NXP use the NXP. prefix in pack name visible in the device selector.
NXP Semiconductors
Figure 43. Device from MCUXpresso SDK pack in IAR Embedded Workbench for Arm
3. Go to Project > CMSIS-Pack > Project Components and unfold the Device class. Find Startup component, click on
the Vendor column and switch the startup component from Keil to NXP. Click the OK button to close Project CMSIS
Component Manager.
NXP Semiconductors
Figure 44. Switching startup component in IAR Embedded Workbench for Arm
4. In the Workspace window you can see that Startup component files from NXP MCUXpresso pack replaced the files
from Keil pack. Note that the files from Keil pack are still available in the {project}\RTE\Kinetis_K60_DFP\Keil\
directory.
NXP Semiconductors
Figure 45. Startup component from Keil pack in IAR Embedded Workbench for Arm
Figure 46. Startup component from MCUXpresso SDK pack in IAR Embedded Workbench for Arm
5. You can add more MCUXpresso SDK components using Project CMSIS Component Manager.
How To Reach Us Information in this document is provided solely to enable system and software implementers
to use NXP products. There are no express or implied copyright licenses granted hereunder
Home Page:
to design or fabricate any integrated circuits based on the information in this document. NXP
nxp.com reserves the right to make changes without further notice to any products herein.
Web Support: NXP makes no warranty, representation, or guarantee regarding the suitability of its products
nxp.com/support for any particular purpose, nor does NXP assume any liability arising out of the application
or use of any product or circuit, and specifically disclaims any and all liability, including
without limitation consequential or incidental damages. “Typical” parameters that may be
provided in NXP data sheets and/or specifications can and do vary in different applications,
and actual performance may vary over time. All operating parameters, including “typicals,”
must be validated for each customer application by customer's technical experts. NXP does
not convey any license under its patent rights nor the rights of others. NXP sells products
pursuant to standard terms and conditions of sale, which can be found at the following address:
nxp.com/SalesTermsandConditions.
While NXP has implemented advanced security features, all products may be subject to
unidentified vulnerabilities. Customers are responsible for the design and operation of their
applications and products to reduce the effect of these vulnerabilities on customer’s applications
and products, and NXP accepts no liability for any vulnerability that is discovered. Customers
should implement appropriate design and operating safeguards to minimize the risks associated
with their applications and products.
NXP, the NXP logo, NXP SECURE CONNECTIONS FOR A SMARTER WORLD, COOLFLUX,
EMBRACE, GREENCHIP, HITAG, ICODE, JCOP, LIFE VIBES, MIFARE, MIFARE CLASSIC,
MIFARE DESFire, MIFARE PLUS, MIFARE FLEX, MANTIS, MIFARE ULTRALIGHT,
MIFARE4MOBILE, MIGLO, NTAG, ROADLINK, SMARTLX, SMARTMX, STARPLUG, TOPFET,
TRENCHMOS, UCODE, Freescale, the Freescale logo, AltiVec, CodeWarrior, ColdFire,
ColdFire+, the Energy Efficient Solutions logo, Kinetis, Layerscape, MagniV, mobileGT, PEG,
PowerQUICC, Processor Expert, QorIQ, QorIQ Qonverge, SafeAssure, the SafeAssure logo,
StarCore, Symphony, VortiQa, Vybrid, Airfast, BeeKit, BeeStack, CoreNet, Flexis, MXC, Platform
in a Package, QUICC Engine, Tower, TurboLink, EdgeScale, EdgeLock, eIQ, and Immersive3D
are trademarks of NXP B.V. All other product or service names are the property of their
respective owners. AMBA, Arm, Arm7, Arm7TDMI, Arm9, Arm11, Artisan, big.LITTLE, Cordio,
CoreLink, CoreSight, Cortex, DesignStart, DynamIQ, Jazelle, Keil, Mali, Mbed, Mbed Enabled,
NEON, POP, RealView, SecurCore, Socrates, Thumb, TrustZone, ULINK, ULINK2, ULINK-ME,
ULINK-PLUS, ULINKpro, µVision, Versatile are trademarks or registered trademarks of Arm
Limited (or its subsidiaries) in the US and/or elsewhere. The related technology may be protected
by any or all of patents, copyrights, designs and trade secrets. All rights reserved. Oracle
and Java are registered trademarks of Oracle and/or its affiliates. The Power Architecture and
Power.org word marks and the Power and Power.org logos and related marks are trademarks
and service marks licensed by Power.org.
© NXP B.V. 2017-2020. All rights reserved.

For more information, please visit: http://www.nxp.com
For sales office addresses, please send an email to: salesaddresses@nxp.com
Date of release: 08 August 2020

Document identifier: MCUXSDKPACKSGSUG

Mcuxsdkpacksgsug Cleaned

Uploaded by

Copyright:

Available Formats

You might also like

Mcuxsdkpacksgsug Cleaned

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mcuxsdkpacksgsug Cleaned

Uploaded by

Copyright:

Available Formats

MCUXSDKPACKSGSUG

Getting Started with MCUXpresso SDK CMSIS Packs

2 MCUXpresso SDK CMSIS packs introduction

2.1 CMSIS pack standard

2.2 CMSIS packs with MCUXpresso SDK overview

2.2.1 MCUXpresso SDK DFPs

2.2.2 MCUXpresso SDK BSPs

3 Installing MCUXpresso SDK CMSIS pack

Figure 1. Running Pack Installer from Keil MDK/μVision IDE toolbar

Figure 2. Pack installation in Keil MDK/μVision IDE Pack Installer

Figure 3. License agreement dialog

5. Close Pack Installer.

3.2.1 IAR Embedded Workbench 8.2.x

3. In the Pack view, select NXP > MK64F12_DFP.

3.2.2 IAR Embedded Workbench 8.3.x and later versions

4 Opening a demo application

4.1 Opening an example application using Keil MDK/μVision IDE

Figure 7. Board selection in Keil MDK/μVision Pack Installer

Figure 9. Copying example from pack in Keil MDK/μVision IDE

Figure 10. Example project from pack in Keil MDK/μVision IDE

4.2.1 IAR Embedded Workbench 8.2.x

4.2.2 IAR Embedded Workbench 8.3.x and later versions

2. In CMSIS-Pack manager, go to "Examples" and look for an example project:

5 Creating a new application

5.1 Creating a new application using Keil MDK/μVision IDE

Figure 15. Device selection in Keil MDK/μVision IDE

Figure 17. Creating an MCUXpresso SDK project in Keil MDK/μVision IDE

5. Click OK to close the Run-Time Environment Manager.

Figure 19. Adding a new file in Keil MDK/μVision IDE

Figure 20. Creating main.c file in Keil MDK/μVision IDE

Figure 21. Disabling a generated scatter file in Keil MDK/μVision IDE

8. Build and debug your application.

5.2.1 IAR Embedded Workbench 8.2.x

5. Click the OK button to close the Project CMSIS Component Manager.

5.2.2 IAR Embedded Workbench 8.3.x or later versions

Figure 29. Resolving dependencies

Figure 30. Add missing MCUXpresso SDK components

Figure 31. Switching variant of the project template component

6. Close the CMSIS-pack manager.

6 Converting a project created with Keil CMSIS packs to NXP MCUXpresso

Figure 32. Device from Keil pack in Keil MDK/μVision IDE

Figure 34. Debugger settings in Keil MDK/μVision IDE

5. Click the OK button to close Options for Target.

Figure 35. Component from Keil pack in Keil MDK/μVision IDE

Figure 39. Disabling generated scatter file in Keil MDK/μVision IDE

Figure 40. Changing device in IAR Embedded Workbench for Arm

Figure 41. Device selection in IAR Embedded Workbench for Arm

© NXP B.V. 2017-2020. All rights reserved.

Date of release: 08 August 2020

You might also like