Acasă Explorează Ajutor
Autentificare
ARM-software
/
CMSIS_5
oglindă de https://github-proxy.rt-thread.io/ARM-software/CMSIS_5.git
2
0
Bifurcare 0
Fisiere Probleme 0 Wiki
Răsfoiți Sursa

fixed broken links;

bruneu01 9 ani în urmă
părinte
5d6d6a6658
comite
ecdc7ee51f
11 a modificat fișierele cu 50 adăugiri și 58 ștergeri
Vizualizare divizată Arată Statisticile Diff
  1. 1 1
      CMSIS/DoxyGen/Core/src/Ref_Peripheral.txt
  2. 4 2
      CMSIS/DoxyGen/Core/src/UsingTrustZone.txt
  3. 1 10
      CMSIS/DoxyGen/DAP/src/dap.txt
  4. 0 1
      CMSIS/DoxyGen/Doxygen_Templates/cmsis_header.html
  5. 2 2
      CMSIS/DoxyGen/Driver/src/Driver_CAN.c
  6. 28 28
      CMSIS/DoxyGen/General/src/introduction.txt
  7. 9 9
      CMSIS/DoxyGen/Pack/src/flash_algorithms.txt
  8. 1 1
      CMSIS/DoxyGen/Pack/src/pack_check.txt
  9. 2 2
      CMSIS/DoxyGen/Pack/src/pack_dfp.txt
  10. 1 1
      CMSIS/DoxyGen/RTOS2/src/cmsis_os.txt
  11. 1 1
      CMSIS/DoxyGen/RTOS2/src/cmsis_os2.txt

+ 1 - 1
CMSIS/DoxyGen/Core/src/Ref_Peripheral.txt
Vizualizați fișierul 

@@ -9,7 +9,7 @@ Most of the rules also apply to the core peripherals.  The \ref device_h_pg cont
 
 the core specific header files.
 
 
 Most of the definitions can be generated using the <a href="../../SVD/html/index.html"><b>CMSIS-SVD</b></a> System View Description for Peripherals.
 
-Refer to <a href="../../SVD/html/svd__s_v_d_conv_pg.html"><b>SVDConv.exe</b></a> for more information.
 
+Refer to <a href="../../SVD/html/svd_SVDConv_pg.html"><b>SVDConv.exe</b></a> for more information.
 
 	
 Each peripheral provides a data type definition with a name that is composed of:
 
   - prefix <b>&lt;<i>device abbreviation&gt;</i>_</b>

+ 4 - 2
CMSIS/DoxyGen/Core/src/UsingTrustZone.txt
Vizualizați fișierul 

@@ -36,7 +36,8 @@ The figure <b>Simplified Use Case</b> shows and embedded application that is spl
 
 
  - <b>Firmware callbacks:</b> code running in the <b>Secure state</b> can execute code in the <b>Non-secure state</b> using call-back function pointers. For example, a communication stack (protected firmware) could use an I/O driver that is configured in user space.
 
  
-<img id="SimpleUseCase" src="SimpleUseCase.png"><CENTER><b>Simplified Use Case</b></CENTER>
 
+\anchor SimpleUseCase
 
+\image html "SimpleUseCase.png" "Simplified Use Case"
 
 
 Program execution in the <b>Secure state</b> is further protected by TrustZone hardware from software failures.
 
 For example, an ARMv8-M system may implement two independent SYSTICK timers which allows to stop code execution 
@@ -65,7 +66,8 @@ The system supports two separate interrupt vector tables for secure and non-secu
 
 This interrupt assignment is controlled during <b>Secure state</b> code execution via the NVIC 
 (nested vector interrupt controller).
 
 
-<img id="MemoryMap_S" src="MemoryMap_S.png"><CENTER><b>Secure Memory Map</b></CENTER>
 
+\anchor MemoryMap_S
 
+\image html "MemoryMap_S.png" "Secure Memory Map"
 
 
 The figure <a href="#MemoryMap_NS"><b>Non-Secure Memory Map</b></a> shows the memory view for the Non-secure state. This memory view is identical
 
 to the traditional Cortex-M memory map. Access to any secure memory or peripheral space triggers the secure exception

+ 1 - 10
CMSIS/DoxyGen/DAP/src/dap.txt
Vizualizați fișierul 

@@ -66,18 +66,9 @@ CMSIS-DAP compliant Debug Units must be validated using the scripts provided in
 
 
 <hr>
 
 
-License
 
-=======
 
-
 
-The CMSIS-DAP is provided free of charge by ARM and can be freely distributed as part of 
-Cortex-M processor-based Debug Units that are stand-alone or integrated evaluation boards.
 
-used for all Cortex-M based devices. 
-View the <a href="..\..\..\DAP\CMSIS-DAP EULA.pdf">LICENCE AGREEMENT for CMSIS-DAP</a> in detail.
 
-
 
-<hr>
 
 */
 
 /** 
-\page rev_hist_dap Revision History of CMSIS-DAP
 
+\page dap_revisionHistory Revision History of CMSIS-DAP
 
 
 <table>
 
     <tr>

+ 0 - 1
CMSIS/DoxyGen/Doxygen_Templates/cmsis_header.html
Vizualizați fișierul 

@@ -14,7 +14,6 @@
 
 $treeview
 
 $search
 
 $mathjax
 
-<link href="$relpath$stylsheetf" rel="stylesheet" type="text/css" />
 
 </head>
 
 <body>
 
 <div id="top"><!-- do not remove this div, it is closed by doxygen! -->

+ 2 - 2
CMSIS/DoxyGen/Driver/src/Driver_CAN.c
Vizualizați fișierul 

@@ -11,8 +11,8 @@ The node may also be a gateway allowing a standard computer to communicate over
 
 Devices are connected to the bus through a host processor, a CAN controller, and a CAN transceiver.
 
 
 
-The CAN Driver API allows to implement CAN Interfaces that conform to the following 
-<a href="http://www.bosch-semiconductors.de/en/ubk_semiconductors/ip_modules_3/produkttabelle_ip_modules/can_literature_1/can_literature.html" target="_blank">
 
+The CAN Driver API allows to implement CAN Interfaces that conform to the  
+<a href="http://www.bosch-semiconductors.com/" target="_blank">
 
 CAN specifications available from BOSCH</a>:
 
   - CAN 2.0B: CAN Specification 2.0B (released Sep. 1991) which is now superseded by ISO 11898-1.
 
   - CAN FD: CAN with Flexible Data Rate introduced in 2012 (released April 17th, 2012).

+ 28 - 28
CMSIS/DoxyGen/General/src/introduction.txt
Vizualizați fișierul 

@@ -127,11 +127,12 @@ View the <a href="LICENSE">Apache 2.0 License</a>.
 
 \section CM_Pack_Content ARM::CMSIS Pack
 
 
 The <b>ARM::CMSIS</b> Pack contains the following:
 
-|File/Directory    |Content                                                                           |
 
-|:-----------------|:---------------------------------------------------------------------------------|
 
-|\b ARM.CMSIS.pdsc |Package description file                                                          |
 
-|\b CMSIS          |\ref CM_Components "CMSIS components" (see below)                                 |
 
-|\b Device         |ARM reference implementations of Cortex-M devices                                 |
 
+
 
+File/Directory    |Content                                                                           
+:-----------------|:---------------------------------------------------------------------------------
 
+\b ARM.CMSIS.pdsc |Package description file                                                          
+\b CMSIS          |\ref CM_Components "CMSIS components" (see below)                                 
+\b Device         |ARM reference implementations of Cortex-M devices                                 
 
 CMSIS Directory
 
 ---------------
 
@@ -139,20 +140,20 @@ 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 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 Version 1</b></a> along with RTX reference implementation                         |
 
-|\b RTOS2                  |<a href="../../RTOS2/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___i_t_m___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)|
 
+Directory                 |Content                                                                                                                                  
+:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------
 
+\b Documentation          |This documentation                                                                                                                       
+\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 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>
 
 */
 
@@ -165,15 +166,14 @@ index.html file for this documentation, and the following sub-directories:
 
 The following table shows the overall high-level history of the various CMSIS releases.
 
 In addition, each CMSIS component has its own release history:
 
 
-- <a href="../../Core/html/core_revision_history.html"><b>CORE Revision History</b></a>
 
-- <a href="../../DAP/html/rev_hist_dap.html"><b>DAP Revision History</b></a>
 
-- <a href="../../Driver/html/driver_revision_history.html"><b>Driver Revision History</b></a>
 
-- <a href="../../DSP/html/_change_log_pg.html"><b>DSP Revision History (Change Log)</b></a>
 
-- <a href="../../Pack/html/pack_revision_history.html"><b>Pack Revision History</b></a>
 
-- <a href="../../RTOS/html/rtos_revision_history.html"><b>RTOS v1 Revision History</b></a>
 
-- <a href="../../RTOS2/html/rtos_revision_history.html"><b>RTOS v2 Revision History</b></a>
 
-- <a href="../../RTX/html/rtx_revision_history.html"><b>RTX Revision History</b></a>
 
-- <a href="../../SVD/html/svd_revision_history.html"><b>SVD Revision History</b></a>
 
+- <a href="../../Core/html/core_revisionHistory.html"><b>CORE Revision History</b></a>
 
+- <a href="../../DAP/html/dap_revisionHistory.html"><b>DAP Revision History</b></a>
 
+- <a href="../../Driver/html/driver_revisionHistory.html"><b>Driver Revision History</b></a>
 
+- <a href="../../DSP/html/ChangeLog_pg.html"><b>DSP Revision History (Change Log)</b></a>
 
+- <a href="../../Pack/html/pack_revisionHistory.html"><b>Pack Revision History</b></a>
 
+- <a href="../../RTOS/html/rtos_revisionHistory.html"><b>RTOS v1 Revision History</b></a>
 
+- <a href="../../RTOS2/html/rtos_revisionHistory.html"><b>RTOS v2 Revision History</b></a>
 
+- <a href="../../SVD/html/svd_revisionHistory.html"><b>SVD Revision History</b></a>

+ 9 - 9
CMSIS/DoxyGen/Pack/src/flash_algorithms.txt
Vizualizați fișierul 

@@ -113,15 +113,15 @@ However, the Flash programming algorithm of a project can be changed manually at
 
 \page algorithmFunc Algorithm Functions
 
 
 The following functions are available for creating new Flash programming algorithms:
 
-|Function Name   |Indication|Description|
 
-|----------------|----------|-----------|
 
-|\ref BlankCheck |optional  |Check and compare patterns.|
 
-|\ref EraseChip  |optional  |Delete entire Flash memory content.|
 
-|\ref EraseSector|mandatory |Delete Flash memory content of a specific sector.|
 
-|\ref Init       |mandatory |Initialize and prepare device for Flash programming.|
 
-|\ref ProgramPage|mandatory |Write the application into the Flash memory.|
 
-|\ref UnInit     |mandatory |De-initialize the microcontroller after one of the Flash programming steps.|
 
-|\ref Verify     |optional  |Compare Flash memory content with the program code.|
 
+Function Name    |Indication |Description 
+-----------------|-----------|-----------
 
+\ref BlankCheck  |optional   |Check and compare patterns.
 
+\ref EraseChip   |optional   |Delete entire Flash memory content.
 
+\ref EraseSector |mandatory  |Delete Flash memory content of a specific sector.
 
+\ref Init        |mandatory  |Initialize and prepare device for Flash programming.
 
+\ref ProgramPage |mandatory  |Write the application into the Flash memory.
 
+\ref UnInit      |mandatory  |De-initialize the microcontroller after one of the Flash programming steps.
 
+\ref Verify      |optional   |Compare Flash memory content with the program code.
 
 
 <p>&nbsp;</p>
 
 <hr>

+ 1 - 1
CMSIS/DoxyGen/Pack/src/pack_check.txt
Vizualizați fișierul 

@@ -101,7 +101,7 @@ packChk.exe MyVendor.MVCM3.pdsc -x M304 -x M331        // option repeated
 
 
 \section packChkMessages Error and Warning Messages
 
 
-[SVDConv.exe]: ../../SVD/html/svd__s_v_d_conv_pg.html
 
+[SVDConv.exe]: ../../SVD/html/svd_SVDConv_pg.html
 
 
 The following table shows the errors and warnings issued by packChk.

+ 2 - 2
CMSIS/DoxyGen/Pack/src/pack_dfp.txt
Vizualizați fișierul 

@@ -130,7 +130,7 @@ an embedded application:
 
   contain stack and heap configurations for the user application.
 
 - \c system_<device>.c and \c system_<device>.h with general system configuration information (i.e. for clock and BUS setup).
 
 - \c <device.h> gives access to processor core and all peripherals. This file should be generated out of the
 
-  \ref cp_SVD "SVD" file using <a href="../../SVD/html/svd__s_v_d_conv_pg.html"><b>SVDConv.exe</b></a> to ensure consistency
 
+  \ref cp_SVD "SVD" 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.
 
 
 \image html SystemStartupFiles.png  "System and startup files in relation to user code"
 
@@ -219,7 +219,7 @@ microcontrollers, in particular the memory mapped registers of the peripherals.
 
 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__s_v_d_conv_pg.html"><b>SVDConv.exe</b></a> that
 
+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.
 
 
 \image html SVDFlow.png "SVD file conversion flow"

+ 1 - 1
CMSIS/DoxyGen/RTOS2/src/cmsis_os.txt
Vizualizați fișierul 

@@ -164,7 +164,7 @@ int main (void) {                                // program execution starts her
 
 CMSIS-RTOS v2 provides multiple API functions:
 
   - \subpage RTOS_API2 is the new C function API that support dynamic object creation, ARMv8-M, and multi-processor
 
     communication.
 
-  - <a class="el" href="../../RTOSv1/html/_function_overview.html">CMSIS-RTOS C API Version 1</a> is a C function API the is
 
+  - <a class="el" href="../../RTOS/html/functionOverview.html">CMSIS-RTOS C API Version 1</a> is a C function API the is
 
     backward compatible with CMSIS-RTOS v2.
 
   - \subpage RTOS_APICPP is a C++ class function API.

+ 1 - 1
CMSIS/DoxyGen/RTOS2/src/cmsis_os2.txt
Vizualizați fișierul 

@@ -104,7 +104,7 @@ File/Folder                  | Content
 
 CMSIS-RTOS v2 provides multiple API functions:
 
   - \subpage rtos_api2 is the new C function API that support dynamic object creation, ARMv8-M, and multi-processor
 
     communication.
 
-  - <a class="el" href="../../RTOSv1/html/_function_overview.html">CMSIS-RTOS C API Version 1</a> is a C function API the is
 
+  - <a class="el" href="../../RTOS/html/functionOverview.html">CMSIS-RTOS C API Version 1</a> is a C function API the is
 
     backward compatible with CMSIS-RTOS v2.
 
   - \subpage rtos_apicpp is a C++ class function API.