Skip to content

GitLab

To receive notifications about scheduled maintenance, please subscribe to the mailing-list gitlab-operations@sympa.ethz.ch. You can subscribe to the mailing-list at https://sympa.ethz.ch

Commit 933ae0ab authored by ReinhardKeil's avatar ReinhardKeil
Browse files

Clean-up of General section

parent 4a4e39ce
Hide whitespace changes
Inline Side-by-side
CMSIS/DoxyGen/General/general.dxy
View file @ 933ae0ab
......@@ -1138,7 +1138,7 @@ HTML_EXTRA_STYLESHEET = ../Doxygen_Templates/cmsis.css
HTML_EXTRA_FILES = ../Doxygen_Templates/tabs.css \
../Doxygen_Templates/tab_topnav.png \
"../../../LICENSE" \
"../../../LICENSE.txt" \
../Doxygen_Templates/printComponentTabs.js
# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
......
CMSIS/DoxyGen/General/src/images/CMSISv4_small.png
View file @ 933ae0ab
File suppressed by a .gitattributes entry or the file's encoding is unsupported.
CMSIS/DoxyGen/General/src/introduction.txt
View file @ 933ae0ab
......@@ -14,25 +14,28 @@ and middleware components. The CMSIS is intended to enable the combination of so
from multiple middleware vendors.
CMSIS Version 5 supports also the <a class="el" href="http://www.arm.com/products/processors/instruction-set-architectures/armv8-m-architecture.php" target="_blank">ARMv8-M architecture</a>
including <a class="el" href="http://www.arm.com/products/processors/technologies/trustzone/index.php" target="_blank">TrustZone&reg; for ARMv8-M</a> hardware security extensions.
including <a class="el" href="http://www.arm.com/products/processors/technologies/trustzone/index.php" target="_blank">TrustZone&reg; for ARMv8-M</a> hardware security extensions and the
<a class="el" href="http://www.arm.com/products/processors/cortex-m/cortex-m23-processor.php" target="_blank">Cortex-M23</a> and <a class="el" href="http://www.arm.com/products/processors/cortex-m/cortex-m33-processor.php" target="_blank">Cortex-M33</a> processors.
\anchor CM_Components
The CMSIS components are:
- <a href="../../Core/html/index.html"><b>CMSIS-CORE</b></a>: API for the Cortex-M processor core and peripherals. It provides a standardized interface for Cortex-M0, Cortex-M3, Cortex-M4, Cortex-M7, SC000, and SC300.
Also included are SIMD intrinsic functions for Cortex-M4 and Cortex-M7 SIMD instructions.
- <a href="../../Core/html/index.html"><b>CMSIS-CORE</b></a>: API for the Cortex-M processor core and peripherals.
It provides a standardized interface for Cortex-M0, Cortex-M0+, Cortex-M3, Cortex-M4, Cortex-M7, Cortex-M23, Cortex-M33, SC000, and SC300.
Also included are SIMD intrinsic functions for Cortex-M4, Cortex-M7, and Cortex-M33 SIMD instructions.
- <a href="../../Driver/html/index.html"><b>CMSIS-Driver</b></a>: defines generic peripheral driver interfaces for middleware making it reusable across supported devices. The API is RTOS independent
and connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces.
- <a href="../../DSP/html/index.html"><b>CMSIS-DSP</b></a>: DSP Library Collection with over 60 Functions for various data types: fixed-point (fractional q7, q15, q31) and single precision floating-point (32-bit).
The library is available for all Cortex-M cores. The Cortex-M4 and Cortex-M7 implementations are optimized for the SIMD instruction set.
The library is available for all Cortex-M cores. Implementations that are optimized for the SIMD instruction set are available for Cortex-M4, Cortex-M7, and Cortex-M33.
- <a href="../../RTOS/html/index.html"><b>CMSIS-RTOS v1</b></a>: Common API for Real-Time Operating Systems along with reference implementation based on RTX.
It provides a standardized programming interface that is portable to many RTOS and enables software components that can work across multiple RTOS systems.
- <a href="../../RTOS2/html/index.html"><b>CMSIS-RTOS v2</b></a>: extends CMSIS-RTOS v1 with support for ARMv8-M architecture, dynamic object creation,
provisions for multi-core systems, and binary compatible interface across ABI compliant compilers.
- <a href="../../Pack/html/index.html"><b>CMSIS-Pack</b></a>: describes with an XML-based package description (PDSC) file the user and device relevant parts of a file collection (called a software pack) that includes source, header and library files, documentation,
Flash programming algorithms, source code templates, and example projects. Development tools and web infrastructures use the PDSC file to extract device parameters,
software components, and evaluation board configurations.
......@@ -121,7 +124,7 @@ with C language standards, specifically warnings that may be generated by the va
\section License Licence
The CMSIS is provided free of charge by ARM under Apache 2.0 license.
View the <a href="LICENSE">Apache 2.0 License</a>.
View the <a href="LICENSE.txt">Apache 2.0 License</a>.
\section CM_Pack_Content ARM::CMSIS Pack
......@@ -130,29 +133,27 @@ The <b>ARM::CMSIS</b> Pack contains the following:
File/Directory |Content
:-----------------|:---------------------------------------------------------------------------------
\b ARM.CMSIS.pdsc |Package description file
\b ARM.CMSIS.pdsc |Package description file in CMSIS-Pack format.
\b LICENSE.txt |CMSIS License Agreement (Apache 2.0)
\b CMSIS |\ref CM_Components "CMSIS components" (see below)
\b Device |ARM reference implementations of Cortex-M devices
\b Device |CMSIS reference implementations of ARM Cortex-M processor based devices
CMSIS Directory
---------------
The directory <b>CMSIS</b> contains the "CMSIS End User License Agreement" as PDF and RTF, a README text file, the
index.html file for this documentation, and the following sub-directories:
Directory |Content
:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------
\b Documentation |This documentation
\b Core |User code templates for Core related files, referenced in ARM.CMSIS.PDSC
\b DAP |<a href="../../DAP/html/index.html"><b>CMSIS-DAP</b></a> Debug Access Port source code and reference implementations
\b Driver |Header files for the <a href="../../Driver/html/index.html"><b>CMSIS-Driver</b></a> peripheral interface API
\b DSP_Lib |<a href="../../DSP/html/index.html"><b>CMSIS-DSP</b></a> software library source code
\b Include |Include files for <a href="../../Core/html/index.html"><b>CMSIS-CORE</b></a> and <a href="../../DSP/html/index.html"><b>CMSIS-DSP</b></a>
\b Lib |<a href="../../DSP/html/index.html"><b>CMSIS-DSP</b></a> generated libraries for ARMCC and GCC
\b Pack |<a href="../../Pack/html/pack_Example.html"><b>CMSIS-Pack</b></a> example
\b RTOS |<a href="../../RTOS/html/index.html"><b>CMSIS-RTOS API Version 1</b></a> along with RTX reference implementation
\b RTOS |<a href="../../RTOS/html/index.html"><b>CMSIS-RTOS Version 1</b></a> along with RTX reference implementation
\b RTOS2 |<a href="../../RTOS/html/index.html"><b>CMSIS-RTOS Version 2</b></a> along with RTX reference implementation
\b SVD |<a href="../../SVD/html/index.html"><b>CMSIS-SVD</b></a> example
\b UserCodeTemplates\\ARM |ITM_Retarget.c, CMSIS <a href="../../Core/html/group__ITM__Debug__gr.html"><b>retarget output</b></a> to ITM Channel 0 template file
\b Utilities |PACK.xsd (<a href="../../Pack/html/pack_Example.html"><b>CMSIS-Pack</b></a> schema file), PackChk.exe (checking tool for software packs), \n CMSIS-SVD.xsd (<a href="../../SVD/html/index.html"><b>CMSIS-SVD</b></a> schema file), SVDConv.exe (conversion tool for SVD files)
<hr>
......@@ -186,8 +187,8 @@ In addition, each CMSIS component has its own release history:
<td>5.0.0</td>
<td>
Added <a href="http://www.arm.com/products/processors/instruction-set-architectures/armv8-m-architecture.php" target="_blank"><b>ARMv8-M architecture</b></a> support.
- CMSIS-CORE 5.0.0
- CMSIS-RTOS 2.0.0
- CMSIS-CORE 5.0.0 adding support for ARMv8-M and Cortex-M23, Cortex-M33 processors
- CMSIS-RTOS 2.0.0 new API with RTX 5.0.0 reference implementation
- CMSIS-PACK 1.4.4 introducing CPDSC project description
</td>
</tr>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment