ARM-software
/
CMSIS_5
cermin dari https://github-proxy.rt-thread.io/ARM-software/CMSIS_5.git


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227
							<!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>/package/apis element</title>
<title>CMSIS-Pack: /package/apis element</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
   &#160;<span id="projectnumber">Version 1.6.3</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&#160;Page</span></a></li>
      <li class="current"><a href="pages.html"><span>Usage&#160;and&#160;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('pdsc_apis_pg.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">&#160;</span>All</a><a class="SelectItem" href="javascript:void(0)" onclick="searchBox.OnSelectItem(1)"><span class="SelectionMark">&#160;</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">/package/apis element </div>  </div>
</div><!--header-->
<div class="contents">
<div class="textblock"><p>Application Programming Interfaces (apis) are C/C++ interface specifications that allow software to be divided into largely independent modules. Such modules can then be developed, tested, and maintained independently, and reused by different projects. One example is the use of device drivers. If device drivers are developed for different devices implementing the same API, the application software itself can be written independent from the device it is build for.</p>
<p>The <b>apis</b> allow to distribute the Application Programming Interface Specifications decoupled from actual implementation. One example is the CMSIS-RTOS API, which is specified as part of CMSIS, however, the actual RTOS implementation is provided by different vendors.</p>
<p>An API consists of a name, a brief description as well as one or more header files, and a document containing a detailed specification of the API.</p>
<p>The API typically defines one or more header files and optionally an include directory. It should have also related documentation that describes the API.</p>
<p><b>Example:</b> </p>
<div class="fragment"><div class="line">&lt;api Cclass=<span class="stringliteral">&quot;ACloud IF&quot;</span> Cgroup=<span class="stringliteral">&quot;TRNG&quot;</span> Capiversion=<span class="stringliteral">&quot;1.2.0&quot;</span>&gt; </div>
<div class="line">  &lt;files&gt; </div>
<div class="line">    &lt;file category=<span class="stringliteral">&quot;header&quot;</span> name=<span class="stringliteral">&quot;include/trng.h&quot;</span>/&gt; </div>
<div class="line">    &lt;file category=<span class="stringliteral">&quot;include&quot;</span> name=<span class="stringliteral">&quot;include/somestuff&quot;</span>/&gt; </div>
<div class="line">    &lt;file category=<span class="stringliteral">&quot;doc&quot;</span> name=<span class="stringliteral">&quot;html/trng.html&quot;</span>/&gt; </div>
<div class="line">  &lt;/files&gt; </div>
<div class="line">&lt;/api&gt; </div>
</div><!-- fragment --><p>The API can be used either in the same software pack or other software packs. Having the API definition in one central software pack provides the benefit that implementations are consistent.</p>
<p>The include file and directory are <b>included in the application project</b> when a <b>component</b> is selected that specifics the same <b>Cclass</b> and <b>Cgroup</b>. The selection of a software component adds therefore both to a project: the files specified by the <a class="el" href="pdsc_components_pg.html#element_component">component element</a> and the files specified by the <a class="el" href="pdsc_apis_pg.html#element_api">api element</a>. Therefore, the component that is based on the API should not contain the header file that defines the API.</p>
<p><b>Example:</b> this component adds also the api header file above</p>
<div class="fragment"><div class="line">&lt;component Cclass=<span class="stringliteral">&quot;ACloud IF&quot;</span> Cgroup=<span class="stringliteral">&quot;TRNG&quot;</span> Csub=<span class="stringliteral">&quot;Emulation&quot;</span> Capiversion=<span class="stringliteral">&quot;1.1.0&quot;</span>&gt; </div>
<div class="line">  &lt;description&gt;Software simulation of random number generator&lt;/description&gt; </div>
<div class="line">  &lt;files&gt; </div>
<div class="line">    &lt;file category=<span class="stringliteral">&quot;sourceC&quot;</span> name=<span class="stringliteral">&quot;source/trng_emulation.c&quot;</span>/&gt; </div>
<div class="line">  &lt;/files&gt; </div>
<div class="line">&lt;/component&gt; </div>
</div><!-- fragment --><p> Optionally, it is possible to request a minimum API version using the <b>Capiversion</b> attribute.</p>
<p>It is also possible to expose a combination of API definitions. An example for that is the CMSIS-Driver for Ethernet that is defined as:</p>
<ul>
<li><b>Ethernet MAC</b> interface</li>
<li><b>Ethernet PHY</b> interface</li>
<li><b>Ethernet</b> interface that defines both MAC and PHY (this defines two API header files)</li>
</ul>
<p>&#160;</p>
<hr/>
<h1><a class="anchor" id="element_apis"></a>
/package/apis</h1>
<p>This element is a grouping element for all application programming interfaces included in the <a class="el" href="cp_SWComponents.html">Software Pack</a>. The element itself is optional. Only one such section can exist in a package.</p>
<p><b>Example:</b> </p>
<div class="fragment"><div class="line">&lt;package&gt;</div>
<div class="line">  &lt;apis&gt;</div>
<div class="line">    ...</div>
<div class="line">  &lt;/apis&gt;</div>
<div class="line">&lt;/package&gt;  </div>
</div><!-- fragment --><p>&#160;</p>
<table  class="cmtable" summary="Element: APIs">
<tr>
<th>Parents  </th><th>Element Chain </th><th>&#160; </th><th>&#160;  </th></tr>
<tr>
<td><a class="el" href="pdsc_package_pg.html">package</a> </td><td><a class="el" href="pdsc_package_pg.html">/package</a> </td><td>&#160; </td><td>&#160;  </td></tr>
<tr>
<th>Child&#160;Elements </th><th>Description </th><th>Type </th><th>Occurrence  </th></tr>
<tr>
<td><a class="el" href="pdsc_apis_pg.html#element_api">api</a> </td><td>Named specification of an API containing a brief description, C/C++ header files and documentation </td><td>ApiType </td><td>1..*  </td></tr>
</table>
<p>&#160;</p>
<hr/>
<h1><a class="anchor" id="element_api"></a>
/package/apis/api</h1>
<p>Application Programming Interfaces (apis) are C/C++ interface specifications that allow components to inter-work by either implementing or using a set of functions, data types, and definitions. This element is mandatory and can exist multiple times.</p>
<p><b>Example:</b> </p>
<div class="fragment"><div class="line">&lt;apis&gt;</div>
<div class="line">  &lt;api Cclass=<span class="stringliteral">&quot;Device&quot;</span> Cgroup=<span class="stringliteral">&quot;Driver UART&quot;</span> exclusive=<span class="stringliteral">&quot;0&quot;</span>&gt;</div>
<div class="line">    &lt;description&gt;UART Driver API <span class="keywordflow">for</span> the Cortex-M processor based devices&lt;/description&gt;</div>
<div class="line">    &lt;files&gt;</div>
<div class="line">      &lt;file category=<span class="stringliteral">&quot;doc&quot;</span> name=<span class="stringliteral">&quot;Driver/Doc/UART/html/index.html&quot;</span>/&gt;</div>
<div class="line">      &lt;file category=<span class="stringliteral">&quot;header&quot;</span> name=<span class="stringliteral">&quot;Driver/Include/Driver_UART.h&quot;</span>/&gt;</div>
<div class="line">    &lt;/files&gt;</div>
<div class="line">  &lt;/api&gt;</div>
<div class="line">  &lt;api Cclass=<span class="stringliteral">&quot;Device&quot;</span> Cgroup=<span class="stringliteral">&quot;Driver SPI&quot;</span> exclusive=<span class="stringliteral">&quot;0&quot;</span>&gt;</div>
<div class="line">    &lt;description&gt;SPI Driver API <span class="keywordflow">for</span> the Cortex-M processor based devices&lt;/description&gt;</div>
<div class="line">    &lt;files&gt;</div>
<div class="line">      &lt;file category=<span class="stringliteral">&quot;doc&quot;</span> name=<span class="stringliteral">&quot;Driver/Doc/SPI/html/index.html&quot;</span>/&gt;</div>
<div class="line">      &lt;file category=<span class="stringliteral">&quot;header&quot;</span> name=<span class="stringliteral">&quot;Driver/Include/Driver_SPI.h&quot;</span>/&gt;</div>
<div class="line">    &lt;/files&gt;</div>
<div class="line">  &lt;/api&gt;</div>
<div class="line">  ...</div>
<div class="line">&lt;/apis&gt;</div>
</div><!-- fragment --><p>&#160;</p>
<table  class="cmtable" summary="Element: api">
<tr>
<th>Parent&#160;Element </th><th colspan="3">Element Chain  </th></tr>
<tr>
<td><a class="el" href="pdsc_apis_pg.html#element_apis">apis</a> </td><td colspan="3"><a class="el" href="pdsc_apis_pg.html#element_apis">/package/apis</a>  </td></tr>
<tr>
<th>Attributes </th><th>Description </th><th>Type </th><th>Use  </th></tr>
<tr>
<td>Cclass </td><td>Defines the component class to which this component belongs. This is a mandatory part of the component ID. Predefined values can be used as listed in the table <a class="el" href="element_taxonomy.html#CclassType">Component Classes</a>. </td><td>CclassType </td><td>required  </td></tr>
<tr>
<td>Cgroup </td><td>Defines the component group to which this component belongs. This is a mandatory part of the component ID. Predefined values can be used as listed in the table <a class="el" href="element_taxonomy.html#CgroupType">Component Groups</a>. </td><td>CgroupType </td><td>required  </td></tr>
<tr>
<td>exclusive </td><td>Makes the selection of a component implementing the API exclusive. If set to <span class="XML-Token">0</span>, then multiple components implementing the API can be selected. Default is <span class="XML-Token">1</span>. </td><td>xs:boolean </td><td>optional  </td></tr>
<tr>
<td>condition </td><td>Enter the identifier (attribute <em><b>id</b></em>) of a <a class="el" href="pdsc_conditions_pg.html#element_condition">condition</a>. The element is used if the condition resolves to <span class="XML-Token">true</span>. If the condition resolves to <span class="XML-Token">false</span>, then the element will be ignored. For example, an API might be specific for a certain toolchain or processor instruction set. </td><td>xs:string </td><td>optional  </td></tr>
<tr>
<td>Capiversion </td><td>Version of this component. Is a mandatory part of the component ID. The version format is described in <a class="el" href="pdsc_package_pg.html#VersionType">Version Type</a>.  </td><td>VersionType </td><td>optional  </td></tr>
<tr>
<th>Child&#160;Elements </th><th>Description </th><th>Type </th><th>Occurrence  </th></tr>
<tr>
<td>description </td><td>Brief summary about the purpose and scope of an API. </td><td>xs:string </td><td>0..1  </td></tr>
<tr>
<td><a class="el" href="pdsc_components_pg.html#element_files">files</a> </td><td>Grouping element for all file descriptions that are part of this component.. </td><td>group </td><td>0..1  </td></tr>
</table>
<p>&#160;</p>
</div></div><!-- contents -->
</div><!-- doc-content -->
<!-- start footer part -->
<div id="nav-path" class="navpath"><!-- id is needed for treeview function! -->
  <ul>
    <li class="navelem"><a class="el" href="packFormat.html">Pack Description (*.pdsc) Format</a></li>
    <li class="footer">Generated on Thu Apr 9 2020 15:49:54 for CMSIS-Pack Version 1.6.3 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>