Device Packs
A device pack is a file from the chip vendor that describes a family of microcontrollers. It gives Mission Control 3 the memory map of each part and the routine that programs its flash. The MCU Programmer lists no target until a pack is opened.
What a Device Pack Is
Section titled “What a Device Pack Is”CMSIS-Pack is an open format for distributing device support for Arm-based microcontrollers. The pack that describes the chips themselves is the device family pack (DFP). The chip vendor, or Arm (Keil) for some families, publishes one DFP per MCU family: Keil.STM32H5xx_DFP covers the whole STM32H5 series.
A pack is a single zip archive with the .pack extension. Microchip packs use .atpack. Keil MDK, pyOCD and CMSIS-Toolbox use the same packs. A pack already downloaded by one of them can be opened in Mission Control 3.
What a Pack Contains
Section titled “What a Pack Contains”| Item | What it is |
|---|---|
.pdsc file | The pack description: every part in the family, with its core, its memory regions and the files that apply to it |
.FLM flash algorithms | Small routines that run from the target’s RAM to erase and program its flash |
.svd files | The peripheral registers of each part |
| Other files | Device headers, startup code and documentation |
Mission Control 3 takes the list of parts, the memory map and the flash algorithm from the pack.
Why Mission Control 3 Needs One
Section titled “Why Mission Control 3 Needs One”Flashing is different for every MCU: where the flash is, how it is divided into sectors, and which routine erases and programs it. That data belongs to the chip vendor and is published in the DFP.
Mission Control 3 has no built-in parts, so every target comes from an opened pack. The MCU Debugger’s Flash & debug uses the same pack: pick the part there under Attach… → Target.
Binho does not ship vendor packs. Each pack is distributed under its vendor’s license, so download it from the vendor or from Arm.
Which Pack to Choose
Section titled “Which Pack to Choose”Choose the device family pack of the MCU’s family. Its name ends in _DFP, for example Keil.STM32H5xx_DFP for an STM32H503.
A board pack (the name often ends in _BSP) or a software pack gets the message … describes no MCU.
One DFP covers every part in its family. After the pack is open, pick the exact part in the target list.
Get and Open a Pack
Section titled “Get and Open a Pack”Download the DFP, then click Open pack… in the MCU Programmer and pick the part. Open pack… is in the desktop app only. Install a Device Pack has the download sources, the folder each tool keeps its packs in, and the steps.
MCUs Without a CMSIS Pack
Section titled “MCUs Without a CMSIS Pack”Mission Control 3 lists a part only from a CMSIS pack. For an MCU that has none, see the pyOCD route named in Install a Device Pack.
Parts Mission Control 3 Does Not Support
Section titled “Parts Mission Control 3 Does Not Support”Mission Control 3 marks the parts it does not support and gives the reason. A part whose pack declares vendor connect steps that the Atira doesn’t run is flashed only after a confirmation. The table in Install a Device Pack lists each message and what to do.
Need help? Contact [email protected].

