µVision User's GuideAbout µVision User Interface Creating Applications Creating Projects Setup the Project Use Software Components Add Source Files to Project Create File Groups Set Tool Options Configure Startup Code Build the Project Build Log File µVision Build Output Messages Software Components Pack Installer Importing Custom Software Packs Using Local Repositories Packs Dialog Examples Dialog Managing Run-Time Environment Select Software Packs Update Software Component Files Components in Project Options for Component Project Targets and File Groups File, Group, and Component Attribute Icons Configuration Dialogs Project Information and Layers Multi-Projects Create a Multi-Project Manage a Multi-Project Batch Setup for Single and Multi-Projects Tips and Tricks Start External Tools Redirect Output for Object and Listing Files Customize or Add Devices Create a Library File File and Group Specific Options Different Compiler and Assembler Settings Set Folders and File Extensions Version and Serial Number Information Including Library Modules Use a Custom Translator Manage Arm Compiler Versions Setup Default Arm Compiler Version GNU C Compiler Support Manage Component Viewer Description Files Use MDK Version 4 Projects Debugging Debug Commands Debug Functions Simulation Flash Programming Dialogs Utilities Command Line Example Programs Appendix
Importing Custom Software Packs
Software packs can be created by Arm, third-parties, customers or you might want to build your own. Software pack files are ZIP files that have the preferred extension *.pack (*.zip is also supported). Pack Installer checks if the file is a valid pack.
There are two ways to import software packs:
Apart from importing, you can directly use an existing folder structure that is interpreted as a pack. Refer to Using Local Repositories for more information.
Import a software pack
The menu File - Import... adds software packs to the MDK installation. Software packs get stored in the folder \Pack\vendor_name\pack_name\version.
The picture shows an example of the imported software pack CustomPack delivered by the vendor CustomVendor. The pack has two versions. Only the latest version is installed and can be used in projects.
Import a folder
The menu File - Import from Folder... adds one or more extracted packs from the specified folder to the installation. All software packs found below the root folder get stored in the respective folder \Pack\vendor_name\pack_name\version.
Using a custom software component
The example software pack adds a software component called CustomPHY to the sub-class Ethernet PHY (API) of the class CMSIS Driver. The software component can be added to a project using the Run-Time-Environment window by ticking the check-box Sel:
Also note the item "Custom" in the list of available Ethernet PHY drivers. It comes with the CMSIS pack and can be used to create a new PHY driver directly in the application using the CMSIS Driver template files. Section Add Source Files to Project explains how to add user code templates.
In our example CustomPack provides Ethernet PHY implementation and so selecting the CustomPHY component adds the file CustomPHY.c to the software component class CMSIS Driver in the Project window.
Right-click the file name and select Options for Component Class 'CMSIS Driver'.
Click on CustomPHY to set options. The software pack from which the software component originated is shown on the Properties tab.
of your data.