Migrating Projects to CMSIS v6
Introduction
Supported toolchains
Required CMSIS-Packs
Device mapping
Project format conversion
Troubleshooting
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Advanced
Reading time:  10 min
Last updated:  13 Aug 2026
Skill level:
  Advanced
Reading time:
  10 min
Last updated:
  13 Aug 2026
Author:Christopher Seidl, Arm
Arm IP:Cortex-M
Tags: Libraries Baremetal RTOS CMSIS CMSIS-Toolbox
Author:
  • Christopher Seidl, Arm
Arm IP:
Cortex-M
Tags:
Libraries Baremetal RTOS CMSIS CMSIS-Toolbox

Who is this for?

This is an advanced topic for embedded developers who want to migrate their projects to CMSIS v6.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Identify the supported toolchains.
  • Install the required CMSIS-Packs.
  • Select the software components needed to migrate your projects to CMSIS v6.

Prerequisites

Before starting, you will need the following:

  • A CMSIS v5 based project.
  • A basic understanding of the CMSIS-Pack system.

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll migrate an existing CMSIS v5 project to CMSIS v6 by aligning its toolchain, packs, and device selection. First, you’ll replace deprecated packs, map generic devices to Cortex_DFP equivalents, and convert Keil MDK uvprojx projects to Open-CMSIS-Pack csolution format. Then, you’ll diagnose missing devices, unresolved RTE components, and linker warnings during migration.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I confirm my toolchain is supported?
Check your versions against the supported list: Arm Compiler for Embedded v6 and later, Arm GNU Toolchain v12 and later, LLVM v16 and later, or IAR Embedded Workbench for Arm v9.30 and later. Use the Arm Compiler for Embedded Migration and Compatibility Guide to move from v5 to v6.
Which CMSIS-Packs do I need when migrating from CMSIS v5?
Install ARM.CMSIS.6.0.0.pack, ARM.Cortex_DFP.1.0.0.pack, and ARM.CMSIS-RTX.5.8.0.pack. These packs replace the ARM.CMSIS.5.x.x pack during migration to CMSIS v6.
I used the Keil.ARM_Compiler pack — what should I install now?
Install ARM.CMSIS-View.1.1.0.pack and ARM.CMSIS_Compiler.2.0. These packs contain the content that moved from the deprecated Keil.ARM_Compiler pack.
How do I resolve a missing device after migration?
Change the device selection from the CMSIS v5 generic device to the corresponding device in the Cortex_DFP pack. Use the included device mapping table to select the matching ARMCMx variant and features.
Where can I find instructions for converting a `uvprojx` project?
For instructions, see the Convert uvprojx-based projects to csolution Learning Path. It covers importing, converting, and building uvprojx projects in Keil Studio for VS Code and on the command line.
Next