537 lines
50 KiB
HTML
537 lines
50 KiB
HTML
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|||
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|||
|
|
<head>
|
|||
|
|
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
|
|||
|
|
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
|
|||
|
|
<title>Pack with Device Support</title>
|
|||
|
|
<title>CMSIS-Pack: Pack with Device Support</title>
|
|||
|
|
<link href="tabs.css" rel="stylesheet" type="text/css"/>
|
|||
|
|
<link href="cmsis.css" rel="stylesheet" type="text/css" />
|
|||
|
|
<script type="text/javascript" src="jquery.js"></script>
|
|||
|
|
<script type="text/javascript" src="dynsections.js"></script>
|
|||
|
|
<script type="text/javascript" src="printComponentTabs.js"></script>
|
|||
|
|
<link href="navtree.css" rel="stylesheet" type="text/css"/>
|
|||
|
|
<script type="text/javascript" src="resize.js"></script>
|
|||
|
|
<script type="text/javascript" src="navtree.js"></script>
|
|||
|
|
<script type="text/javascript">
|
|||
|
|
$(document).ready(initResizable);
|
|||
|
|
$(window).load(resizeHeight);
|
|||
|
|
</script>
|
|||
|
|
<link href="search/search.css" rel="stylesheet" type="text/css"/>
|
|||
|
|
<script type="text/javascript" src="search/search.js"></script>
|
|||
|
|
<script type="text/javascript">
|
|||
|
|
$(document).ready(function() { searchBox.OnSelectItem(0); });
|
|||
|
|
</script>
|
|||
|
|
</head>
|
|||
|
|
<body>
|
|||
|
|
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
|
|||
|
|
<div id="titlearea">
|
|||
|
|
<table cellspacing="0" cellpadding="0">
|
|||
|
|
<tbody>
|
|||
|
|
<tr style="height: 46px;">
|
|||
|
|
<td id="projectlogo"><img alt="Logo" src="CMSIS_Logo_Final.png"/></td>
|
|||
|
|
<td style="padding-left: 0.5em;">
|
|||
|
|
<div id="projectname">CMSIS-Pack
|
|||
|
|
 <span id="projectnumber">Version 1.4.9</span>
|
|||
|
|
</div>
|
|||
|
|
<div id="projectbrief">Delivery Mechanism for Software Packs</div>
|
|||
|
|
</td>
|
|||
|
|
</tr>
|
|||
|
|
</tbody>
|
|||
|
|
</table>
|
|||
|
|
</div>
|
|||
|
|
<!-- end header part -->
|
|||
|
|
<div id="CMSISnav" class="tabs1">
|
|||
|
|
<ul class="tablist">
|
|||
|
|
<script type="text/javascript">
|
|||
|
|
<!--
|
|||
|
|
writeComponentTabs.call(this);
|
|||
|
|
//-->
|
|||
|
|
</script>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
<!-- Generated by Doxygen 1.8.6 -->
|
|||
|
|
<script type="text/javascript">
|
|||
|
|
var searchBox = new SearchBox("searchBox", "search",false,'Search');
|
|||
|
|
</script>
|
|||
|
|
<div id="navrow1" class="tabs">
|
|||
|
|
<ul class="tablist">
|
|||
|
|
<li><a href="index.html"><span>Main Page</span></a></li>
|
|||
|
|
<li class="current"><a href="pages.html"><span>Usage and Description</span></a></li>
|
|||
|
|
<li>
|
|||
|
|
<div id="MSearchBox" class="MSearchBoxInactive">
|
|||
|
|
<span class="left">
|
|||
|
|
<img id="MSearchSelect" src="search/mag_sel.png"
|
|||
|
|
onmouseover="return searchBox.OnSearchSelectShow()"
|
|||
|
|
onmouseout="return searchBox.OnSearchSelectHide()"
|
|||
|
|
alt=""/>
|
|||
|
|
<input type="text" id="MSearchField" value="Search" accesskey="S"
|
|||
|
|
onfocus="searchBox.OnSearchFieldFocus(true)"
|
|||
|
|
onblur="searchBox.OnSearchFieldFocus(false)"
|
|||
|
|
onkeyup="searchBox.OnSearchFieldChange(event)"/>
|
|||
|
|
</span><span class="right">
|
|||
|
|
<a id="MSearchClose" href="javascript:searchBox.CloseResultsWindow()"><img id="MSearchCloseImg" border="0" src="search/close.png" alt=""/></a>
|
|||
|
|
</span>
|
|||
|
|
</div>
|
|||
|
|
</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
</div><!-- top -->
|
|||
|
|
<div id="side-nav" class="ui-resizable side-nav-resizable">
|
|||
|
|
<div id="nav-tree">
|
|||
|
|
<div id="nav-tree-contents">
|
|||
|
|
<div id="nav-sync" class="sync"></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div id="splitbar" style="-moz-user-select:none;"
|
|||
|
|
class="ui-resizable-handle">
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<script type="text/javascript">
|
|||
|
|
$(document).ready(function(){initNavTree('createPack_DFP.html','');});
|
|||
|
|
</script>
|
|||
|
|
<div id="doc-content">
|
|||
|
|
<!-- window showing the filter options -->
|
|||
|
|
<div id="MSearchSelectWindow"
|
|||
|
|
onmouseover="return searchBox.OnSearchSelectShow()"
|
|||
|
|
onmouseout="return searchBox.OnSearchSelectHide()"
|
|||
|
|
onkeydown="return searchBox.OnSearchSelectKey(event)">
|
|||
|
|
<a class="SelectItem" href="javascript:void(0)" onclick="searchBox.OnSelectItem(0)"><span class="SelectionMark"> </span>All</a><a class="SelectItem" href="javascript:void(0)" onclick="searchBox.OnSelectItem(1)"><span class="SelectionMark"> </span>Pages</a></div>
|
|||
|
|
|
|||
|
|
<!-- iframe showing the search results (closed by default) -->
|
|||
|
|
<div id="MSearchResultsWindow">
|
|||
|
|
<iframe src="javascript:void(0)" frameborder="0"
|
|||
|
|
name="MSearchResults" id="MSearchResults">
|
|||
|
|
</iframe>
|
|||
|
|
</div>
|
|||
|
|
|
|||
|
|
<div class="header">
|
|||
|
|
<div class="headertitle">
|
|||
|
|
<div class="title">Pack with Device Support </div> </div>
|
|||
|
|
</div><!--header-->
|
|||
|
|
<div class="contents">
|
|||
|
|
<div class="textblock"><p>A <a class="el" href="cp_SWComponents.html">Software Pack</a> that contains a <a class="el" href="pdsc_devices_pg.html"><devices></a> element is called Device Family Pack (DFP). A DFP may contain additional <b>Software Components</b> or <b>Example Projects</b> or any combination of those. The typical content of a DFP is:</p>
|
|||
|
|
<ul>
|
|||
|
|
<li><a class="el" href="createPack_DFP.html#cp_DeviceProperties">Device Properties</a> explaining the capabilities of a device or a device family in more detail.</li>
|
|||
|
|
<li><a class="el" href="cp_SWComponents.html#cp_Components">Software Components</a> that configure the device and basic device drivers, in particular:<ul>
|
|||
|
|
<li>CMSIS-compliant <a class="el" href="createPack_DFP.html#cp_System_Startp">System and Startup Files</a> required to setup the C run-time library, device clock, and memory interface.</li>
|
|||
|
|
<li>Peripheral Driver Interfaces that provide software routines for physical device peripherals used by middleware stacks. Drivers may adhere to the <a href="http://www.keil.com/cmsis/driver" class="el" target="_blank">CMSIS-Driver</a> standard.</li>
|
|||
|
|
</ul>
|
|||
|
|
</li>
|
|||
|
|
<li>One or more <a class="el" href="createPack_DFP.html#cp_SVD">System View Description Files</a> describing the programmer's view of the device's peripherals.</li>
|
|||
|
|
<li><a class="el" href="createPack_DFP.html#cp_FlashProgrammingAlgorithm">Flash Programming Algorithms</a> for erasing and downloading code into on-chip Flash.</li>
|
|||
|
|
<li><a class="el" href="createPack_DFP.html#cp_debugdescription">Debug Descriptions</a> enable tool-agnostic debug and trace configurations.</li>
|
|||
|
|
<li><a class="el" href="cp_SWComponents.html#cp_Examples">Example Projects</a> that show the usage of the device and its peripherals.</li>
|
|||
|
|
<li><a class="el" href="cp_SWComponents.html#cp_CodeTemplates">User Code Templates</a> that can be used as a starting point for application development.</li>
|
|||
|
|
</ul>
|
|||
|
|
<p>This section explains how to create a DFP. Initially, the PDSC file in the DFP only describes devices. This DFP is then extended to contain also SVD files, Flash algorithms, and device related software components such as system and HAL files. Example projects and code templates may be added as described in the section <a class="el" href="cp_SWComponents.html">Pack with Software Components</a>.</p>
|
|||
|
|
<h2>DFP Use Cases </h2>
|
|||
|
|
<p>A <a class="el" href="pdsc_devices_pg.html">Device Family Pack (DFP)</a> may be provided by a Silicon Vendor and is used to extend development tools with support for new devices. In general, the DFP enables Silicon Vendors to distribute tool independent device support for their device families.<br/>
|
|||
|
|
DFPs can also be used to provide information for the display on <b>web sites</b>. One example is the new device database on <a href="http://www.keil.com/dd2/" class="el" target="_blank">www.keil.com/dd2/</a>:</p>
|
|||
|
|
<p><a class="anchor" id="DevWebSite"></a></p>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="DeviceDatabase2.png" alt="DeviceDatabase2.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
Device information on a web site extracted from a DFP</div></div>
|
|||
|
|
<h2>Steps to Create a DFP </h2>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="DFPFlow.png" alt="DFPFlow.png"/>
|
|||
|
|
</div>
|
|||
|
|
<h1><a class="anchor" id="cp_BasicDFP"></a>
|
|||
|
|
Basic Device Family Pack</h1>
|
|||
|
|
<p>In the following sections, a DFP will be created for a fictional device family called <b>MVCM3</b> from the device vendor <b>MyVendor</b>. The device family consists of four member that are separated into two sub-families. The specification of the MVCM3 family is as follows:</p>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="MVCM3SpecTable.png" alt="MVCM3SpecTable.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
MVCM3 Device Family Specification</div></div>
|
|||
|
|
<p> <b>Preparations</b></p>
|
|||
|
|
<ol type="1">
|
|||
|
|
<li>Create a working directory on you PC, for example <b>C:\temp\working_dfp</b>.</li>
|
|||
|
|
<li>Go to the directory <b>\CMSIS\Pack\Tutorials</b> available in the <b>ARM::CMSIS</b> Pack installation. Please consult your development tool's documentation for more information on the Pack installation directory structure. In a standard µVision installation, you will find it below <b>C:\Keil_v5\ARM\Pack\ARM\CMSIS\<em>version</em></b>.</li>
|
|||
|
|
<li>Open the file <b>Pack_with_Device_Support.zip</b>.</li>
|
|||
|
|
<li>Copy the <em>content</em> of the ZIP file's <b>01_Basic_Pack</b> directory into your working directory.</li>
|
|||
|
|
<li>Make sure that files/directories are not write protected (remove read-only flag).</li>
|
|||
|
|
<li>Copy from the directory <b>\CMSIS\Utilities</b> available in the <b>ARM::CMSIS</b> Pack installation the following files into your working directory:<ul>
|
|||
|
|
<li>packChk.exe</li>
|
|||
|
|
<li>PACK.xsd</li>
|
|||
|
|
<li>SVDConv.exe</li>
|
|||
|
|
</ul>
|
|||
|
|
</li>
|
|||
|
|
<li>Open the <b>MyVendor.MVCM3.pdsc</b> file in an editor.</li>
|
|||
|
|
</ol>
|
|||
|
|
<p><b>Code Example</b> </p>
|
|||
|
|
<ol>
|
|||
|
|
<li>
|
|||
|
|
Add a <a class="el" href="pdsc_family_pg.html#element_device"><devices></a> section in the PDSC file with the following: <div class="fragment"><div class="line"><devices></div>
|
|||
|
|
<div class="line"> <family Dfamily=<span class="stringliteral">"MVCM3 Series"</span> Dvendor=<span class="stringliteral">"Generic:5"</span>></div>
|
|||
|
|
<div class="line"> <processor Dcore=<span class="stringliteral">"Cortex-M3"</span> DcoreVersion=<span class="stringliteral">"r2p1"</span> Dfpu=<span class="stringliteral">"0"</span> Dmpu=<span class="stringliteral">"0"</span> Dendian=<span class="stringliteral">"Little-endian"</span>/></div>
|
|||
|
|
<div class="line"> <description></div>
|
|||
|
|
<div class="line"> The MVCM3 device family contains an ARM Cortex-M3 processor, running up to 100 MHz with a versatile set of on-chip peripherals.</div>
|
|||
|
|
<div class="line"> </description></div>
|
|||
|
|
<div class="line"> <!-- ************************ Sub-family <span class="stringliteral">'MVCM3100'</span> **************************** --></div>
|
|||
|
|
<div class="line"> <subFamily DsubFamily=<span class="stringliteral">"MVCM3100"</span>></div>
|
|||
|
|
<div class="line"> <processor Dclock=<span class="stringliteral">"50000000"</span>/></div>
|
|||
|
|
<div class="line"> <!-- ************************* Device <span class="stringliteral">'MVCM3110'</span> ***************************** --></div>
|
|||
|
|
<div class="line"> <device Dname=<span class="stringliteral">"MVCM3110"</span>></div>
|
|||
|
|
<div class="line"> <memory name=<span class="stringliteral">"IROM1"</span> access=<span class="stringliteral">"rx"</span> start=<span class="stringliteral">"0x00000000"</span> size=<span class="stringliteral">"0x4000"</span> startup=<span class="stringliteral">"1"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"> <memory name=<span class="stringliteral">"IRAM1"</span> access=<span class="stringliteral">"rw"</span> start=<span class="stringliteral">"0x20000000"</span> size=<span class="stringliteral">"0x0800"</span> init =<span class="stringliteral">"0"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"> </device></div>
|
|||
|
|
<div class="line"> <!-- ************************* Device <span class="stringliteral">'MVCM3120'</span> ***************************** --></div>
|
|||
|
|
<div class="line"> <device Dname=<span class="stringliteral">"MVCM3120"</span>></div>
|
|||
|
|
<div class="line"> <memory name=<span class="stringliteral">"IROM1"</span> access=<span class="stringliteral">"rx"</span> start=<span class="stringliteral">"0x00000000"</span> size=<span class="stringliteral">"0x8000"</span> startup=<span class="stringliteral">"1"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"> <memory name=<span class="stringliteral">"IRAM1"</span> access=<span class="stringliteral">"rx"</span> start=<span class="stringliteral">"0x20000000"</span> size=<span class="stringliteral">"0x1000"</span> init =<span class="stringliteral">"0"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"> </device></div>
|
|||
|
|
<div class="line"> </subFamily></div>
|
|||
|
|
<div class="line"> <!-- ************************ Sub Family <span class="stringliteral">'MVCM3200'</span> **************************** --></div>
|
|||
|
|
<div class="line"> <subFamily DsubFamily=<span class="stringliteral">"MVCM3200"</span>></div>
|
|||
|
|
<div class="line"> <processor Dclock=<span class="stringliteral">"100000000"</span>/></div>
|
|||
|
|
<div class="line"> <!-- ************************* Device <span class="stringliteral">'MVCM3250'</span> ***************************** --></div>
|
|||
|
|
<div class="line"> <device Dname=<span class="stringliteral">"MVCM3250"</span>></div>
|
|||
|
|
<div class="line"> <memory name=<span class="stringliteral">"IROM1"</span> access=<span class="stringliteral">"rx"</span> start=<span class="stringliteral">"0x00000000"</span> size=<span class="stringliteral">"0x4000"</span> startup=<span class="stringliteral">"1"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"> <memory name=<span class="stringliteral">"IRAM1"</span> access=<span class="stringliteral">"rw"</span> start=<span class="stringliteral">"0x20000000"</span> size=<span class="stringliteral">"0x0800"</span> init =<span class="stringliteral">"0"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"> </device></div>
|
|||
|
|
<div class="line"> <!-- ************************* Device <span class="stringliteral">'MVCM3260'</span> ***************************** --></div>
|
|||
|
|
<div class="line"> <device Dname=<span class="stringliteral">"MVCM3260"</span>></div>
|
|||
|
|
<div class="line"> <memory name=<span class="stringliteral">"IROM1"</span> access=<span class="stringliteral">"rx"</span> start=<span class="stringliteral">"0x00000000"</span> size=<span class="stringliteral">"0x8000"</span> startup=<span class="stringliteral">"1"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"> <memory name=<span class="stringliteral">"IRAM1"</span> access=<span class="stringliteral">"rw"</span> start=<span class="stringliteral">"0x20000000"</span> size=<span class="stringliteral">"0x1000"</span> init =<span class="stringliteral">"0"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"> </device></div>
|
|||
|
|
<div class="line"> </subFamily></div>
|
|||
|
|
<div class="line"> </family></div>
|
|||
|
|
<div class="line"></devices></div>
|
|||
|
|
</div><!-- fragment --> <dl class="section note"><dt>Note</dt><dd><ul>
|
|||
|
|
<li><code>Dvendor</code> IDs are not freely selectable. The current set of IDs can be found in the PACK.xsd file (available in the <b>ARM::CMSIS</b> Pack in the <b>CMSIS\Pack\Utilities</b> directory).</li>
|
|||
|
|
<li>All code examples in this and the following sections can be found in the <code>snippets.xml</code> file in the <b>01_Basic_Pack</b> directory.</li>
|
|||
|
|
</ul>
|
|||
|
|
</dd></dl>
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
<p class="startli">Save the PDSC file and generate the Pack file using the <b>gen_pack.bat</b> script. See <a class="el" href="cp_SWComponents.html#cp_GeneratePack">Generate a Pack</a> for further details. Afterwards, install the Pack in your development tool.</p>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="BasicDFPDisplay.png" alt="BasicDFPDisplay.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
Display of microcontroller devices in development tools</div></div>
|
|||
|
|
</li>
|
|||
|
|
</ol>
|
|||
|
|
<dl class="section note"><dt>Note</dt><dd>packChk.exe will display <b>M350</b> informations: <pre class="fragment">*** INFO M350:
|
|||
|
|
No 'Startup' found for [Generic:5] 'MVCM3110' ()
|
|||
|
|
</pre> We will address this problem in the next section.</dd></dl>
|
|||
|
|
<h1><a class="anchor" id="cp_System_Startp"></a>
|
|||
|
|
System and Startup Files</h1>
|
|||
|
|
<p><a href="http://www.keil.com/cmsis/core" class="el" target="_blank">CMSIS-CORE</a> defines the following files to be used by an embedded application:</p>
|
|||
|
|
<ul>
|
|||
|
|
<li><code>startup_<device>.s</code> with reset handler and exception vectors. It is executed after reset and calls <code>SystemInit</code> and may contain stack and heap configurations for the user application.</li>
|
|||
|
|
<li><code>system_<device>.c</code> and <code>system_<device>.h</code> with general system configuration information (i.e. for clock and BUS setup).</li>
|
|||
|
|
<li><code><device.h></code> gives access to processor core and all peripherals. This file should be generated out of the <a class="el" href="createPack_DFP.html#cp_SVD">SVD</a> file using <a href="../../SVD/html/svd_SVDConv_pg.html"><b>SVDConv.exe</b></a> to ensure consistency between the header file and what is being displayed by the debugger.</li>
|
|||
|
|
</ul>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="SystemStartupFiles.png" alt="SystemStartupFiles.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
System and startup files in relation to user code</div></div>
|
|||
|
|
<dl class="section note"><dt>Note</dt><dd><a href="http://www.keil.com/pack/doc/CMSIS/Core/html/_templates_pg.html" class="el" target="_blank">CMSIS-CORE</a> explains the structure of the system and startup files and how to create them.</dd></dl>
|
|||
|
|
<p>Copy the <em>content</em> of the <b>02_System_and_Startup</b> directory of the <b>Pack_with_Device_Support.zip</b> file to the <b>Files</b> directory in your working environment: </p>
|
|||
|
|
<ol>
|
|||
|
|
<li>
|
|||
|
|
Add a <code><conditions></code> section in your PDSC with the following (the <a class="el" href="cp_SWComponents.html#cp_Conditions">conditions</a> section provides more information on this step): <div class="fragment"><div class="line"><condition <span class="keywordtype">id</span>=<span class="stringliteral">"MVCM3 CMSIS-CORE"</span>></div>
|
|||
|
|
<div class="line"> <!-- conditions selecting Devices --></div>
|
|||
|
|
<div class="line"> <description>MyVendor MVCM3 Series devices and CMSIS-CORE</description></div>
|
|||
|
|
<div class="line"> <require Cclass=<span class="stringliteral">"CMSIS"</span> Cgroup=<span class="stringliteral">"CORE"</span>/></div>
|
|||
|
|
<div class="line"> <require Dvendor=<span class="stringliteral">"Generic:5"</span> Dname=<span class="stringliteral">"MVCM3*"</span>/></div>
|
|||
|
|
<div class="line"></condition></div>
|
|||
|
|
<div class="line"><condition <span class="keywordtype">id</span>=<span class="stringliteral">"Startup ARM"</span>></div>
|
|||
|
|
<div class="line"> <description>Startup assembler file <span class="keywordflow">for</span> ARMCC</description></div>
|
|||
|
|
<div class="line"> <require Tcompiler=<span class="stringliteral">"ARMCC"</span>/></div>
|
|||
|
|
<div class="line"></condition></div>
|
|||
|
|
<div class="line"><condition <span class="keywordtype">id</span>=<span class="stringliteral">"Startup GCC"</span>></div>
|
|||
|
|
<div class="line"> <description>Startup assembler file <span class="keywordflow">for</span> GCC</description></div>
|
|||
|
|
<div class="line"> <require Tcompiler=<span class="stringliteral">"GCC"</span>/></div>
|
|||
|
|
<div class="line"></condition></div>
|
|||
|
|
<div class="line"><condition <span class="keywordtype">id</span>=<span class="stringliteral">"Startup IAR"</span>></div>
|
|||
|
|
<div class="line"> <description>Startup assembler file <span class="keywordflow">for</span> IAR</description></div>
|
|||
|
|
<div class="line"> <require Tcompiler=<span class="stringliteral">"IAR"</span>/></div>
|
|||
|
|
<div class="line"></condition></div>
|
|||
|
|
</div><!-- fragment --> <dl class="section note"><dt>Note</dt><dd>The assembler based <code>startup_<device>.s</code> file is tool dependent. Therefore, separate conditions for the various tool vendors are required. </dd></dl>
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
Add a <code><components></code> section in your PDSC with the following (the <a class="el" href="cp_SWComponents.html#cp_Components">components</a> section provides more information on this step): <div class="fragment"><div class="line"><component Cclass=<span class="stringliteral">"Device"</span> Cgroup=<span class="stringliteral">"Startup"</span> Cversion=<span class="stringliteral">"1.0.0"</span> condition=<span class="stringliteral">"MVCM3 CMSIS-CORE"</span>></div>
|
|||
|
|
<div class="line"> <description>System Startup <span class="keywordflow">for</span> MyVendor MVCM3 Series</description></div>
|
|||
|
|
<div class="line"> <files></div>
|
|||
|
|
<div class="line"> <!-- include folder --></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"include"</span> name=<span class="stringliteral">"Device/Include/"</span>/></div>
|
|||
|
|
<div class="line"></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"source"</span> name=<span class="stringliteral">"Device/Source/ARM/startup_MVCM3xxx.s"</span> attr=<span class="stringliteral">"config"</span> condition=<span class="stringliteral">"Startup ARM"</span> version=<span class="stringliteral">"1.0.0"</span>/></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"source"</span> name=<span class="stringliteral">"Device/Source/GCC/startup_MVCM3xxx.S"</span> attr=<span class="stringliteral">"config"</span> condition=<span class="stringliteral">"Startup GCC"</span> version=<span class="stringliteral">"1.0.0"</span>/></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"source"</span> name=<span class="stringliteral">"Device/Source/IAR/startup_MVCM3xxx.s"</span> attr=<span class="stringliteral">"config"</span> condition=<span class="stringliteral">"Startup IAR"</span> version=<span class="stringliteral">"1.0.0"</span>/></div>
|
|||
|
|
<div class="line"></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"source"</span> name=<span class="stringliteral">"Device/Source/system_MVCM3xxx.c"</span> attr=<span class="stringliteral">"config"</span> version=<span class="stringliteral">"1.0.0"</span>/></div>
|
|||
|
|
<div class="line"> </files></div>
|
|||
|
|
<div class="line"></component></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
Add a new version number: <div class="fragment"><div class="line"><release version=<span class="stringliteral">"1.0.1"</span>></div>
|
|||
|
|
<div class="line"> Startup files included</div>
|
|||
|
|
<div class="line"></release></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
<p class="startli">Finally, save the PDSC file and regenerate the Pack file using the <a class="el" href="cp_SWComponents.html#cp_GeneratePack">gen_pack.bat</a> script. Afterwards, install the Pack in your development tool and create a new project. Select the software components <b>::CMSIS:CORE</b> and <b>::Device:Startup</b> for the project:</p>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="StartupSystemFilesAdded.png" alt="StartupSystemFilesAdded.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
Startup and system files added to a project</div></div>
|
|||
|
|
</li>
|
|||
|
|
</ol>
|
|||
|
|
<dl class="section note"><dt>Note</dt><dd>packChk.exe will display <b>M350</b> informations: <pre class="fragment">*** INFO M353: .\Files\MyVendor.MVCM3.pdsc (Line 98)
|
|||
|
|
No 'Device Headerfile' File found for Component 'Startup' (MyVendor::Device.Startup:1.0.0) for '[Generic:5] MVCM3110' (ARMCC)
|
|||
|
|
</pre> We will address this problem in the next section.</dd></dl>
|
|||
|
|
<h1><a class="anchor" id="cp_SVD"></a>
|
|||
|
|
System View Description File</h1>
|
|||
|
|
<p><a href="http://www.keil.com/cmsis/svd" class="el" target="_blank">CMSIS-SVD</a> formalizes the description of the programmer's view for the system contained in ARM Cortex-M processor-based microcontrollers, in particular the memory mapped registers of the peripherals. The level of detail contained in system view descriptions is comparable to what is found in device reference manuals published by silicon vendors. The information ranges from a high level functional description of a peripheral all the way down to the definition and purpose of an individual bit field in a memory mapped register. CMSIS-SVD files are developed and maintained by the silicon vendors. The XML based SVD file is the input for <a href="../../SVD/html/svd_SVDConv_pg.html"><b>SVDConv.exe</b></a> that generates the tool dependent debug view and the device header file.</p>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="SVDFlow.png" alt="SVDFlow.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
SVD file conversion flow</div></div>
|
|||
|
|
<p> Copy the <em>content</em> of the <b>03_SVD_File</b> directory of the <b>Pack_with_Device_Support.zip</b> file to the <b>Files</b> directory in your working environment: </p>
|
|||
|
|
<ol>
|
|||
|
|
<li>
|
|||
|
|
Open the file MVCM3xxx.svd in the <b>Files\SVD</b> directory in an editor and change the following: <div class="fragment"><div class="line"><device schemaVersion=<span class="stringliteral">"1.1"</span> xmlns:xs=<span class="stringliteral">"http://www.w3.org/2001/XMLSchema-instance"</span> xs:noNamespaceSchemaLocation=<span class="stringliteral">"CMSIS-SVD.xsd"</span> ></div>
|
|||
|
|
<div class="line"> <vendor>MyVendor</vendor> <!-- device vendor name --></div>
|
|||
|
|
<div class="line"> <vendorID>Generic</vendorID> <!-- device vendor <span class="keywordtype">short</span> name --></div>
|
|||
|
|
<div class="line"> <name>MVCM3xxx</name> <!-- name of part--></div>
|
|||
|
|
<div class="line"> <series>MVCM3xxx</series> <!-- device series the device belongs to --></div>
|
|||
|
|
<div class="line"> <version>1.2</version> <!-- version of <span class="keyword">this</span> description, adding CMSIS-SVD 1.1 tags --></div>
|
|||
|
|
<div class="line"> <description>ARM 32-bit Cortex-M3 Microcontroller based device, CPU clock up to 100 MHz.</description></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
Open a command window in your working directory and enter: <pre class="fragment">C:\temp\working_dfp>SVDConv.exe Files\SVD\MVCM3xxx.svd --generate=header –-fields=macro
|
|||
|
|
</pre> </li>
|
|||
|
|
<li>
|
|||
|
|
You should see some output of SVDConv similar to this: <pre class="fragment">CMSIS-SVD SVD Consistency Checker / Header File Generator V2.86g
|
|||
|
|
Copyright (C) 2010 - 2014 ARM Ltd and ARM Germany GmbH. All rights reserved.
|
|||
|
|
Options: "Files\SVD\MVCM3xxx.svd" --generate=header --fields=macro
|
|||
|
|
Reading file: "Files\SVD\MVCM3xxx.svd"
|
|||
|
|
|
|||
|
|
Decoding using XML SVD Schema V1.1
|
|||
|
|
|
|||
|
|
Found 0 Errors and 0 Warnings
|
|||
|
|
|
|||
|
|
Return Code: 0 (OK)
|
|||
|
|
</pre> Move the generated header file <b>MVCM3xxx.h</b> to the <b>Device\Include</b> directory. </li>
|
|||
|
|
<li>
|
|||
|
|
Add the following two lines at the family level in the PDSC file: <div class="fragment"><div class="line"><compile header=<span class="stringliteral">"Device/Include/MVCM3xxx.h"</span>/></div>
|
|||
|
|
<div class="line"><debug svd=<span class="stringliteral">"SVD/MVCM3xxx.svd"</span>/></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
Add a new version number: <div class="fragment"><div class="line"><release version=<span class="stringliteral">"1.0.2"</span>></div>
|
|||
|
|
<div class="line"> SVD and header file included</div>
|
|||
|
|
<div class="line"></release></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
<p class="startli">Finally, save the PDSC file and regenerate the Pack file using the <a class="el" href="cp_SWComponents.html#cp_GeneratePack">gen_pack.bat</a> script. Afterwards, install the Pack in your development tool and create a new project. Depending on your development environment, you will be able to see the SVD file included in your project:</p>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="SVDIncluded.png" alt="SVDIncluded.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
Project with SVD file</div></div>
|
|||
|
|
<dl class="section note"><dt>Note</dt><dd>For more information on CMSIS-SVD, please visit <a href="http://www.keil.com/cmsis/svd" class="el" target="_blank">www.keil.com/cmsis/svd</a> </dd></dl>
|
|||
|
|
</li>
|
|||
|
|
</ol>
|
|||
|
|
<h1><a class="anchor" id="cp_FlashProgrammingAlgorithm"></a>
|
|||
|
|
Flash Programming Algorithms</h1>
|
|||
|
|
<p><a class="el" href="flashAlgorithm.html">Flash Programming Algorithms</a> are used to erase or download applications to Flash devices. A DFP usually contains predefined Flash algorithms for programming its supported devices. The page <a class="el" href="algorithmFunc.html">Algorithm Functions</a> explains the mechanisms in more detail.</p>
|
|||
|
|
<p>For the MVCM3 device family, two flash algorithms have to be created. MVCM3110/250 have 16 kB of Flash, whereas MVCM3120/260 have 32 kB of Flash memory.</p>
|
|||
|
|
<p>Copy the <em>content</em> of the <b>04_Flash_Programming</b> directory of the <b>Pack_with_Device_Support.zip</b> file to the <b>working</b> directory: </p>
|
|||
|
|
<ol>
|
|||
|
|
<li>
|
|||
|
|
Rename the project file <b>NewDevice.uvproj</b> (in the <b>_Template_Flash</b> directory) to represent the new Flash ROM device name, for example MVCM3XXX_16.uvproj. </li>
|
|||
|
|
<li>
|
|||
|
|
<p class="startli">Open the project with uVision. The selected target (Cortex-M) is fine for the device.</p>
|
|||
|
|
<dl class="section note"><dt>Note</dt><dd>Creating a Flash programming algorithm with <a href="http://www.keil.com/arm/selector.asp" class="el" target="_blank">MDK-Lite</a> is not supported. </dd></dl>
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
<p class="startli">Open the dialog <b>Project - Options for Target - Output</b> and change the content of the field <b>Name of Executable</b> to represent the device, here MCVM3XXX_16.</p>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="FPATargetOptions.png" alt="FPATargetOptions.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
Options for Target 'Cortex-M'</div></div>
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
In the real world, you would now start to adapt the programming algorithms in the file <b>FlashPrg.c</b>. For now, only change the device parameters (Device Name, Device Size, and Sector Size) in the <b>FlashDev.c</b> file: <div class="fragment"><div class="line"><span class="keyword">struct </span>FlashDevice const FlashDevice = {</div>
|
|||
|
|
<div class="line"> FLASH_DRV_VERS, <span class="comment">// Driver Version, do not modify!</span></div>
|
|||
|
|
<div class="line"> <span class="stringliteral">"MVCM3110/250 Flash"</span>, <span class="comment">// Device Name </span></div>
|
|||
|
|
<div class="line"> ONCHIP, <span class="comment">// Device Type</span></div>
|
|||
|
|
<div class="line"> 0x00000000, <span class="comment">// Device Start Address</span></div>
|
|||
|
|
<div class="line"> 0x00004000, <span class="comment">// Device Size in Bytes (16kB)</span></div>
|
|||
|
|
<div class="line"> 1024, <span class="comment">// Programming Page Size</span></div>
|
|||
|
|
<div class="line"> 0, <span class="comment">// Reserved, must be 0</span></div>
|
|||
|
|
<div class="line"> 0xFF, <span class="comment">// Initial Content of Erased Memory</span></div>
|
|||
|
|
<div class="line"> 100, <span class="comment">// Program Page Timeout 100 mSec</span></div>
|
|||
|
|
<div class="line"> 3000, <span class="comment">// Erase Sector Timeout 3000 mSec</span></div>
|
|||
|
|
<div class="line"></div>
|
|||
|
|
<div class="line"><span class="comment">// Specify Size and Address of Sectors</span></div>
|
|||
|
|
<div class="line"> 0x002000, 0x000000, <span class="comment">// Sector Size 8kB (2 Sectors)</span></div>
|
|||
|
|
<div class="line"> SECTOR_END</div>
|
|||
|
|
<div class="line">};</div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
Use <b>Project - Build Target</b> to generate the new Flash programming algorithm. The algorithm will be created in the parent directory of the <b>_Template_Flash</b> directory. </li>
|
|||
|
|
<li>
|
|||
|
|
Copy the output file <b>..\MVCM3XXX_16.FLM</b> to a new subdirectory called <b>Files\Flash</b>. Add these lines to the MVCM3110/250 device sections: <div class="fragment"><div class="line">algorithm name=<span class="stringliteral">"Flash/MVCM3XXX_16.FLM"</span> start=<span class="stringliteral">"0x00000000"</span> size=<span class="stringliteral">"0x4000"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
Create a <b>MVCM3XXX_32.flm</b> for the MVCM3120/260 devices. </li>
|
|||
|
|
<li>
|
|||
|
|
Add these lines to the MVCM3120/260 device sections: <div class="fragment"><div class="line">algorithm name=<span class="stringliteral">"Flash/MVCM3XXX_32.FLM"</span> start=<span class="stringliteral">"0x00000000"</span> size=<span class="stringliteral">"0x8000"</span> <span class="keywordflow">default</span>=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
Add a new version number: <div class="fragment"><div class="line"><release version=<span class="stringliteral">"1.0.3"</span>></div>
|
|||
|
|
<div class="line"> Flash Programming Algorithms added</div>
|
|||
|
|
<div class="line"></release></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
<p class="startli">Finally, save the PDSC file and regenerate the Pack file using the <a class="el" href="cp_SWComponents.html#cp_GeneratePack">gen_pack.bat</a> script. Afterwards, install the Pack in your development tool. Depending on your development environment, you will be able to see the Flash Programming Algorithms included in your project (either for a new project or by adding it manually to an existing project):</p>
|
|||
|
|
<div class="image">
|
|||
|
|
<img src="FPADisplay.png" alt="FPADisplay.png"/>
|
|||
|
|
<div class="caption">
|
|||
|
|
Display of Flash Programming Algorithm</div></div>
|
|||
|
|
<dl class="section note"><dt>Note</dt><dd>The page <a class="el" href="flashAlgorithm.html">Flash Programming Algorithms</a> gives more information on the subject. </dd></dl>
|
|||
|
|
</li>
|
|||
|
|
</ol>
|
|||
|
|
<h1><a class="anchor" id="cp_debugdescription"></a>
|
|||
|
|
Debug Descriptions</h1>
|
|||
|
|
<h1><a class="anchor" id="cp_DeviceProperties"></a>
|
|||
|
|
Device Properties</h1>
|
|||
|
|
<p>To limit redundancy, devices can be organized in two hierarchy groups:</p>
|
|||
|
|
<ul>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_family">family</a>: the attributes of a device family which includes also the processor.</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_subFamily">subFamily</a>: attributes of an optional sub-family; this adds or modifies features of a family.</li>
|
|||
|
|
</ul>
|
|||
|
|
<p>Parameters of each single device are defined in:</p>
|
|||
|
|
<ul>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_device">device</a>: attributes of a specific silicon device</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_variant">variant</a>: attributes of a device variant (for example, with different package or temperature range) or an OEM device or board that integrates the device.</li>
|
|||
|
|
</ul>
|
|||
|
|
<p>A device is described by the following properties:</p>
|
|||
|
|
<ul>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_description">description</a>: textual device description</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_feature">feature</a>: categorized list of device peripherals and features. This list is used on <a class="el" href="createPack_DFP.html#DevWebSite">web sites</a> for the display of device features.</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_book">book</a>: documentation about the device and its processor(s)</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_processor">processor</a>: processor and processor features embedded in the device</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_compile">compile</a>: device specific general settings for the build tools</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_debugconfig">debugconfig</a>: default settings for a debug connection</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_debugport">debugport</a>: debug port description of the device for the debugger to configure a debug connection.</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_debug">debug</a>: device specific information for the debugger to configure a debug connection including System View Description files.</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_trace">trace</a>: device specific information for the debugger to configure trace.</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_memory">memory</a>: memory layout of the device for internal and external RAM and ROM regions</li>
|
|||
|
|
<li><a class="el" href="pdsc_family_pg.html#element_algorithm">algorithm</a>: device specific Flash programming algorithms</li>
|
|||
|
|
</ul>
|
|||
|
|
<p>A device inherits all specifications from both the family and sub-family levels. Some properties are required to be unique. For example, the name of the SVD file attribute of the <b><debug></b> property. Therefore, the SVD file specified on the family level can be redefined by the attribute on the sub-family or device level. Other information like the <description> and <feature> entries are adding up, starting with the information from the family and sub-family level and finalizing with the information on the device level.</p>
|
|||
|
|
<p>The following shows how to specify the device properties for the MVCM3110 device (refer to the specification shown in <a class="el" href="createPack_DFP.html#cp_BasicDFP">Basic Device Family Pack</a>). The other members of the family are specified accordingly.</p>
|
|||
|
|
<p>Copy the <em>content</em> of the <b>05_Device_Properties</b> directory of the <b>Pack_with_Device_Support.zip</b> file to the <b>Files</b> directory of your working environment: </p>
|
|||
|
|
<ol>
|
|||
|
|
<li>
|
|||
|
|
The <b>MVCM3 Series</b> family properties <a class="el" href="pdsc_family_pg.html#element_processor">processor</a>, <a class="el" href="pdsc_family_pg.html#element_compile">compile</a>, <a class="el" href="pdsc_family_pg.html#element_description">description</a>, and <a class="el" href="pdsc_family_pg.html#element_debug">debug</a> are already specified. There are additional common properties that can be specified on the family level: <a class="el" href="pdsc_family_pg.html#element_book">book</a> and <a class="el" href="pdsc_family_pg.html#element_feature">feature</a>. Add the following lines to the PDSC file in the <b><family></b> section: <div class="fragment"><div class="line"><book name=<span class="stringliteral">"Docs/dui0552a_cortex_m3_dgug.pdf"</span> title=<span class="stringliteral">"Cortex-M3 Generic User Guide"</span>/></div>
|
|||
|
|
<div class="line"><book name=<span class="stringliteral">"Docs/MVCM3XXX_Datasheet.pdf"</span> title=<span class="stringliteral">"MVCM3 Series Datasheet"</span>/></div>
|
|||
|
|
<div class="line"><book name=<span class="stringliteral">"Docs/MVCM3XXX_Product_Brief.pdf"</span> title=<span class="stringliteral">"MVCM3 Product Brief"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"ExtInt"</span> n=<span class="stringliteral">"16"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"Temp"</span> n=<span class="stringliteral">"-40"</span> m=<span class="stringliteral">"105"</span> name=<span class="stringliteral">"Extended Temperature Range"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"VCC"</span> n=<span class="stringliteral">"2.5"</span> m=<span class="stringliteral">"3.6"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"RTC"</span> n=<span class="stringliteral">"32768"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"WDT"</span> n=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
The <b>MVCM31xx</b> sub-family has some features that are common for the two member devices. Please add the following code to the MVCM31100 <b><subFamily></b> section: <div class="fragment"><div class="line"><feature type=<span class="stringliteral">"IOs"</span> n=<span class="stringliteral">"26"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"I2C"</span> n=<span class="stringliteral">"1"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"UART"</span> n=<span class="stringliteral">"4"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"Timer"</span> n=<span class="stringliteral">"6"</span> m=<span class="stringliteral">"32"</span>/></div>
|
|||
|
|
<div class="line"><feature type=<span class="stringliteral">"QFP"</span> n=<span class="stringliteral">"32"</span>/></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
The <b>MVCM3110</b> device has some features that are unique to that device. Please add the following code to the MVCM3110 <b><device></b> section: <div class="fragment"><div class="line"><feature type=<span class="stringliteral">"PWM"</span> n=<span class="stringliteral">"2"</span> m=<span class="stringliteral">"16"</span>/></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
</ol>
|
|||
|
|
<h2><a class="anchor" id="cp_DeviceSWComp"></a>
|
|||
|
|
Device Specific Software Components</h2>
|
|||
|
|
<p>Finally, <a class="el" href="cp_SWComponents.html#cp_Components">software components</a> and <a class="el" href="cp_SWComponents.html#cp_Examples">example projects</a> need to be added to the DFP. </p>
|
|||
|
|
<ol>
|
|||
|
|
<li>
|
|||
|
|
Add the following lines to the PDSC file in the <b><components></b> section: <div class="fragment"><div class="line"><component Cclass=<span class="stringliteral">"Device"</span> Cgroup=<span class="stringliteral">"HAL"</span> Csub=<span class="stringliteral">"GPIO"</span> Cversion=<span class="stringliteral">"1.0.0"</span> condition=<span class="stringliteral">"MVCM3 CMSIS-CORE"</span>></div>
|
|||
|
|
<div class="line"> <description>GPIO HAL <span class="keywordflow">for</span> MyVendor MVCM3 Series</description></div>
|
|||
|
|
<div class="line"> <files></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"header"</span> name=<span class="stringliteral">"Device/Include/GPIO.h"</span>/></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"source"</span> name=<span class="stringliteral">"Device/Source/GPIO.c"</span>/></div>
|
|||
|
|
<div class="line"> </files></div>
|
|||
|
|
<div class="line"></component></div>
|
|||
|
|
<div class="line"></div>
|
|||
|
|
<div class="line"><component Cclass=<span class="stringliteral">"Device"</span> Cgroup=<span class="stringliteral">"HAL"</span> Csub=<span class="stringliteral">"ADC"</span> Cversion=<span class="stringliteral">"1.0.0"</span> condition=<span class="stringliteral">"MVCM3 CMSIS-CORE"</span>></div>
|
|||
|
|
<div class="line"> <description>ADC HAL <span class="keywordflow">for</span> MyVendor MVCM3 Series</description></div>
|
|||
|
|
<div class="line"> <files></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"header"</span> name=<span class="stringliteral">"Device/Include/ADC.h"</span>/></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"source"</span> name=<span class="stringliteral">"Device/Source/ADC.c"</span>/></div>
|
|||
|
|
<div class="line"> </files></div>
|
|||
|
|
<div class="line"></component></div>
|
|||
|
|
<div class="line"></div>
|
|||
|
|
<div class="line"><component Cclass=<span class="stringliteral">"CMSIS Driver"</span> Cgroup=<span class="stringliteral">"I2C"</span> Cversion=<span class="stringliteral">"1.0.0"</span> condition=<span class="stringliteral">"MVCM3 CMSIS-CORE"</span> maxInstances=<span class="stringliteral">"3"</span>></div>
|
|||
|
|
<div class="line"> <description>I2C Driver <span class="keywordflow">for</span> MVCM3 Series</description></div>
|
|||
|
|
<div class="line"> <RTE_Components_h></div>
|
|||
|
|
<div class="line"><span class="preprocessor"> #define RTE_Drivers_I2C0 </span><span class="comment">/* Driver I2C0 */</span><span class="preprocessor"></span></div>
|
|||
|
|
<div class="line"><span class="preprocessor"></span><span class="preprocessor"> #define RTE_Drivers_I2C1 </span><span class="comment">/* Driver I2C1 */</span><span class="preprocessor"></span></div>
|
|||
|
|
<div class="line"><span class="preprocessor"></span><span class="preprocessor"> #define RTE_Drivers_I2C2 </span><span class="comment">/* Driver I2C2 */</span><span class="preprocessor"></span></div>
|
|||
|
|
<div class="line"><span class="preprocessor"></span> </RTE_Components_h></div>
|
|||
|
|
<div class="line"> <files></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"source"</span> name=<span class="stringliteral">"Drivers/I2C/I2C_MVCM3.c"</span>/></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"header"</span> name=<span class="stringliteral">"Drivers/I2C/I2C_MVCM3.h"</span>/></div>
|
|||
|
|
<div class="line"> </files></div>
|
|||
|
|
<div class="line"></component></div>
|
|||
|
|
<div class="line"></div>
|
|||
|
|
<div class="line"><component Cclass=<span class="stringliteral">"CMSIS Driver"</span> Cgroup=<span class="stringliteral">"UART"</span> Cversion=<span class="stringliteral">"1.0.0"</span> condition=<span class="stringliteral">"MVCM3 CMSIS-CORE"</span> maxInstances=<span class="stringliteral">"5"</span>></div>
|
|||
|
|
<div class="line"> <description>UART Driver <span class="keywordflow">for</span> MVCM3 Series</description></div>
|
|||
|
|
<div class="line"> <RTE_Components_h></div>
|
|||
|
|
<div class="line"><span class="preprocessor"> #define RTE_Drivers_UART0 </span><span class="comment">/* Driver UART0 */</span><span class="preprocessor"></span></div>
|
|||
|
|
<div class="line"><span class="preprocessor"></span><span class="preprocessor"> #define RTE_Drivers_UART1 </span><span class="comment">/* Driver UART1 */</span><span class="preprocessor"></span></div>
|
|||
|
|
<div class="line"><span class="preprocessor"></span><span class="preprocessor"> #define RTE_Drivers_UART2 </span><span class="comment">/* Driver UART2 */</span><span class="preprocessor"></span></div>
|
|||
|
|
<div class="line"><span class="preprocessor"></span><span class="preprocessor"> #define RTE_Drivers_UART3 </span><span class="comment">/* Driver UART3 */</span><span class="preprocessor"></span></div>
|
|||
|
|
<div class="line"><span class="preprocessor"></span><span class="preprocessor"> #define RTE_Drivers_UART4 </span><span class="comment">/* Driver UART4 */</span><span class="preprocessor"></span></div>
|
|||
|
|
<div class="line"><span class="preprocessor"></span> </RTE_Components_h></div>
|
|||
|
|
<div class="line"> <files></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"source"</span> name=<span class="stringliteral">"Drivers/UART/UART_MVCM3.c"</span>/></div>
|
|||
|
|
<div class="line"> <file category=<span class="stringliteral">"header"</span> name=<span class="stringliteral">"Drivers/UART/UART_MVCM3.h"</span>/></div>
|
|||
|
|
<div class="line"> </files></div>
|
|||
|
|
<div class="line"></component></div>
|
|||
|
|
</div><!-- fragment --> <dl class="section note"><dt>Note</dt><dd>The first two software components are added to <b>Device::HAL</b> because they are specific to the device family and are not using a published API. The drivers for I2C and UART are adhering to the <a href="http://www.keil.com/cmsis/driver" class="el" target="_blank">CMSIS-Driver</a> specification. Thus, they are added to the Cclass <b>CMSIS Driver</b>. </dd></dl>
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
An example project has also been created. Add an <b><examples></b> section with the following: <div class="fragment"><div class="line"><examples></div>
|
|||
|
|
<div class="line"> <example name=<span class="stringliteral">"Dummy"</span> doc=<span class="stringliteral">"Abstract.txt"</span> folder=<span class="stringliteral">"Examples/dummy"</span>></div>
|
|||
|
|
<div class="line"> <description>Dummy project</description></div>
|
|||
|
|
<div class="line"> <board name=<span class="stringliteral">"MVCM3 Starter Kit"</span> vendor=<span class="stringliteral">"MyVendor"</span>/></div>
|
|||
|
|
<div class="line"> <project></div>
|
|||
|
|
<div class="line"> <environment name=<span class="stringliteral">"uv"</span> load=<span class="stringliteral">"dummy.uvprojx"</span>/></div>
|
|||
|
|
<div class="line"> </project></div>
|
|||
|
|
<div class="line"> <attributes></div>
|
|||
|
|
<div class="line"> <category>Getting Started</category></div>
|
|||
|
|
<div class="line"> </attributes></div>
|
|||
|
|
<div class="line"> </example></div>
|
|||
|
|
<div class="line"></examples></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
Add a new version number: <div class="fragment"><div class="line"><release version=<span class="stringliteral">"1.0.4"</span>></div>
|
|||
|
|
<div class="line"> DFP finalized</div>
|
|||
|
|
<div class="line"></release></div>
|
|||
|
|
</div><!-- fragment --> </li>
|
|||
|
|
<li>
|
|||
|
|
Finally, save the PDSC file and regenerate the Pack file using the <a class="el" href="cp_SWComponents.html#cp_GeneratePack">gen_pack.bat</a> script. Afterwards, install the Pack in your development tool. </li>
|
|||
|
|
</ol>
|
|||
|
|
</div></div><!-- contents -->
|
|||
|
|
</div><!-- doc-content -->
|
|||
|
|
<!-- start footer part -->
|
|||
|
|
<div id="nav-path" class="navpath"><!-- id is needed for treeview function! -->
|
|||
|
|
<ul>
|
|||
|
|
<li class="footer">Generated on Wed Feb 8 2017 10:21:01 for CMSIS-Pack by ARM Ltd. All rights reserved.
|
|||
|
|
<!--
|
|||
|
|
<a href="http://www.doxygen.org/index.html">
|
|||
|
|
<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.8.6
|
|||
|
|
-->
|
|||
|
|
</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|