Jelajahi Sumber

DoxyGen: Updated all references/links to keil.com to use https instead of http.

Change-Id: I2589b0de59fb0f20bef11ed031771ed995b24855
Jonatan Antoni 6 tahun lalu
induk
melakukan
1e953d06cf

+ 2 - 2
CMSIS/DoxyGen/Build/src/General.txt

@@ -715,14 +715,14 @@ Running CMSIS-Build
   MyProject.cpdsc validates
   CMSIS Build (cbuildgen) 0.1.1 (Dec 12 2019, 14:36:01)
   Copyright (C) 2019 ARM Ltd and ARM Germany GmbH. All rights reserved.
-  M654: URL 'http://www.keil.com/pack/ARM.CMSIS.5.6.0.pack' was added to the list of missing packages.
+  M654: URL 'https://www.keil.com/pack/ARM.CMSIS.5.6.0.pack' was added to the list of missing packages.
   M650: Setup run successfully.
   dos2unix: converting file MyProject.cpinstall to Unix format...
   CMSIS Pack installation utility (cpinstall.sh) 0.1.0 (Mon, Dec 16, 2019  3:12:37 PM)
   Copyright (C) 2019 ARM Ltd and ARM Germany GmbH. All rights reserved.
   info: reading file: MyProject.cpinstall
   dos2unix: converting file MyProject.cpinstall to Unix format...
-  http://www.keil.com/pack/ARM.CMSIS.5.6.0.pack
+  https://www.keil.com/pack/ARM.CMSIS.5.6.0.pack
   ######################################################################## 100.0%#=#=#
   info: ARM.CMSIS.5.6.0.pack installing into /c/project/MyPackRepo/ARM/CMSIS/5.6.0
   pack installation completed successfully

+ 1 - 1
CMSIS/DoxyGen/DAP/src/dap_config.txt

@@ -27,7 +27,7 @@ requirements:
 CMSIS-DAP Firmware
 ------------------
 The CMSIS-DAP Firmware can be configured for a new Debug Unit using at least the 
-<a href="http://www.keil.com/mdk5" target="_blank">Keil MDK-Plus or MDK-Professional Edition</a>.
+<a href="https://www.keil.com/mdk5" target="_blank">Keil MDK-Plus or MDK-Professional Edition</a>.
 Reference implementations are provided as source code with complete project files
 and may be used as starting point for the firmware deployment to a new Debug Unit.
 

+ 1 - 1
CMSIS/DoxyGen/Driver/src/General.txt

@@ -441,7 +441,7 @@ Further driver reference implementations are available in Device Family Packs (D
 /**
 \page driverValidation Driver Validation
 
-The <a href="http://www.keil.com/pack/" target=_blank>Software Pack</a> named <b>ARM::CMSIS-Driver_Validation</b> contains the following:
+The <a href="https://www.keil.com/pack/" target=_blank>Software Pack</a> named <b>ARM::CMSIS-Driver_Validation</b> contains the following:
 
  - Source code of a CMSIS-Driver Validation Suite along with configuration file.
  - Documentation of the CMSIS-Driver Validation Suite.

+ 1 - 1
CMSIS/DoxyGen/Pack/src/flash_algorithms.txt

@@ -27,7 +27,7 @@ settings are required. Follow these steps to create and configure a new Flash pr
 
 \note
 - Creating a Flash programming algorithm with
-  <a class="el" href="http://www.keil.com/arm/selector.asp" target="_blank">MDK-Lite</a> is not supported.
+  <a class="el" href="https://www.keil.com/arm/selector.asp" target="_blank">MDK-Lite</a> is not supported.
 - Flash programming algorithms use <b>Read-Only Position Independent</b> and <b>Read-Write Position Independent</b> program
   code. These options are set in the dialogs \b Project - <b>Options for Target</b> - \b C/C++ and \b Project -
   <b>Options for Target</b> - \b Asm.

+ 2 - 2
CMSIS/DoxyGen/Pack/src/pack_boards.txt

@@ -23,7 +23,7 @@ A BSP is typically provided by a Board Vendor and is used to
 <b>extend development tools</b> with support for development boards. In general, the BSP enables Board Vendors to
 distribute tool independent board support for their development platforms.\n
 BSPs can also be used to provide information for the display on <b>web sites</b>. One example is the new boards page on
-<a class=el href="http://www.keil.com/boards2/" target="_blank">www.keil.com/boards2/</a>:
+<a class=el href="https://www.keil.com/boards2/" target="_blank">www.keil.com/boards2/</a>:
 
 \image html BoardsSectionMCB1500.png "Board information on a web site extracted from a BSP"
 
@@ -32,7 +32,7 @@ BSPs can also be used to provide information for the display on <b>web sites</b>
 
 <b>Preparations</b>
 -# Install the Software Pack
-   <a class=el href="http://www.keil.com/dd2/arm/armcm3/" target="_blank">Keil::ARMCortex_DFP</a> as this
+   <a class=el href="https://www.keil.com/dd2/arm/armcm3/" target="_blank">Keil::ARMCortex_DFP</a> as this
    will be required for the BSP to function properly.
 -# Create a working directory on your PC, for example <b>C:\\temp\\working_bsp</b>.
 -# Go to the directory <b>\\CMSIS\\Pack\\Tutorials</b> available in the \b ARM::CMSIS Pack installation. Please

+ 2 - 2
CMSIS/DoxyGen/Pack/src/pack_dbg_setup_tutorial.txt

@@ -615,7 +615,7 @@ Figure below shows how the typically available reset options map to the correspo
 
 \image html dbg_uVision_reset_options.png
 
-Detailed meanings for available options are explained in the documentation of corresponding debug adapter. For example for ULINKpro <a href="http://www.keil.com/support/man/docs/ulinkpro/ulinkpro_ctx_debug.htm#/connect" target="__blank"><b>Connect & Reset Options</b></a>
+Detailed meanings for available options are explained in the documentation of corresponding debug adapter. For example for ULINKpro <a href="https://www.keil.com/support/man/docs/ulinkpro/ulinkpro_ctx_debug.htm#/connect" target="__blank"><b>Connect & Reset Options</b></a>
 
 \section dbg_uVision_dbgconf Debug configuration file (*.dbgconf)
 
@@ -655,7 +655,7 @@ Figure below shows how the options "with Pre-reset" and "under Reset" map to the
 
 \image html dbg_uVision_connect_options.png
 
-Detailed explanation for available options are can be found in the documentation of corresponding debug adapter. For example for ULINKpro <a href="http://www.keil.com/support/man/docs/ulinkpro/ulinkpro_ctx_debug.htm#/connect" target="__blank"><b>Connect & Reset Options</b></a>
+Detailed explanation for available options are can be found in the documentation of corresponding debug adapter. For example for ULINKpro <a href="https://www.keil.com/support/man/docs/ulinkpro/ulinkpro_ctx_debug.htm#/connect" target="__blank"><b>Connect & Reset Options</b></a>
 
 \ref dbg_sqns_uvision_dbg_setting_reset explains the \b Reset dropdown menu in the same area and its mapping to the reset types used in \ref usage_of_sequences.
 

+ 6 - 6
CMSIS/DoxyGen/Pack/src/pack_dfp.txt

@@ -9,7 +9,7 @@ typical content of a DFP is:
   - \ref cp_Components "Software Components" that configure the device and basic device drivers, in particular:
     - CMSIS-compliant \ref cp_System_Startp required to setup the C run-time library, device clock, and memory interface.
     - Peripheral Driver Interfaces that provide software routines for physical device peripherals used by middleware stacks.
-      Drivers may adhere to the <a class=el href="http://www.keil.com/cmsis/driver" target="_blank">CMSIS-Driver</a> standard.
+      Drivers may adhere to the <a class=el href="https://www.keil.com/cmsis/driver" target="_blank">CMSIS-Driver</a> standard.
   - One or more \ref cp_SVD "System View Description Files" describing the programmer's view of the device's
     peripherals.
   - \ref cp_FlashProgrammingAlgorithm for erasing and downloading code into on-chip Flash.
@@ -27,7 +27,7 @@ A \ref pdsc_devices_pg "Device Family Pack (DFP)" may be provided by a Silicon V
 tools with support for new devices. In general, the DFP enables Silicon Vendors to distribute tool independent device
 support for their device families.\n
 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 class=el href="http://www.keil.com/dd2/" target="_blank">www.keil.com/dd2/</a>:
+<a class=el href="https://www.keil.com/dd2/" target="_blank">www.keil.com/dd2/</a>:
 
 \anchor DevWebSite
 \image html DeviceDatabase2.png "Device information on a web site extracted from a DFP"
@@ -214,7 +214,7 @@ We will address this problem in the next section.
 
 \section cp_SVD System View Description File
 
-<a class=el href="http://www.keil.com/cmsis/svd" target="_blank">CMSIS-SVD</a>
+<a class=el href="https://www.keil.com/cmsis/svd" 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
@@ -285,7 +285,7 @@ able to see the SVD file included in your project:
 \image html SVDIncluded.png "Project with SVD file"
 
 \note For more information on CMSIS-SVD, please visit
-<a class=el href="http://www.keil.com/cmsis/svd" target="_blank">www.keil.com/cmsis/svd</a>
+<a class=el href="https://www.keil.com/cmsis/svd" target="_blank">www.keil.com/cmsis/svd</a>
 </li>
 </ol>
 
@@ -309,7 +309,7 @@ name, for example MVCM3XXX_16.uvproj.
 Open the project with uVision. The selected target (Cortex-M) is fine for the device.
 
 \note Creating a Flash programming algorithm with
-      <a class=el href="http://www.keil.com/arm/selector.asp" target="_blank">MDK-Lite</a> is not supported.
+      <a class=el href="https://www.keil.com/arm/selector.asp" target="_blank">MDK-Lite</a> is not supported.
 </li>
 <li>
 Open the dialog <b>Project - Options for Target - Output</b> and change the content of the field <b>Name of Executable</b>
@@ -511,7 +511,7 @@ Add the following lines to the PDSC file in the \elem{components} section:
 \endcode
 \note 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 class=el href="http://www.keil.com/cmsis/driver" target="_blank">CMSIS-Driver</a> specification. Thus, they are added to
+<a class=el href="https://www.keil.com/cmsis/driver" target="_blank">CMSIS-Driver</a> specification. Thus, they are added to
 the Cclass <b>CMSIS Driver</b>.
 </li>
 <li>

+ 6 - 6
CMSIS/DoxyGen/Pack/src/pack_index.txt

@@ -29,10 +29,10 @@ It is the vendor's obligation to update this file whenever:
 
 <index schemaVersion="1.0.0" xs:noNamespaceSchemaLocation="PackIndex.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance">
   <vendor>MyVendor</vendor>
-  <url>http://www.MyVendor.com/pack/</url>
+  <url>https://www.MyVendor.com/pack/</url>
   <timestamp>2017-01-25T15:00:10.7300074+00:00</timestamp>
   <pindex>
-    <pdsc url="http://www.MyVendor.com/pack/mypack/" vendor="MyVendor" name="MyPack" version="1.1.0"/>
+    <pdsc url="https://www.MyVendor.com/pack/mypack/" vendor="MyVendor" name="MyPack" version="1.1.0"/>
     ...
   </pindex>
 </index>
@@ -45,7 +45,7 @@ Each individual pack is referenced by the attributes:
 - \c version = the version number of the latest available release for the pack.
 
 The package index file for the CMSIS-Pack compliant packs, hosted on www.keil.com can be found here:
-<a href="http://www.keil.com/pack/Keil.pidx">www.keil.com/pack/Keil.pidx</a>
+<a href="https://www.keil.com/pack/Keil.pidx">https://www.keil.com/pack/Keil.pidx</a>.
 
 The benefit of a single package index file is, that this file only needs to be exchanged once and can be polled for updates
 and additions of packs by a vendor. To add a vendor's packs to the public list maintained on www.keil.com, send an email to
@@ -77,14 +77,14 @@ packs.
 \endcode
 
 The latest index file of CMSIS-Packs belonging to vendor="ARM" and vendor="Keil" that are hosted on www.keil.com/pack 
-is maintained here: <a href="http://www.keil.com/pack/Keil.pidx">www.keil.com/pack/Keil.pidx</a>
+is maintained here: <a href="https://www.keil.com/pack/Keil.pidx">https://www.keil.com/pack/Keil.pidx</a>
 
 ARM also maintains a flat list of all CMSIS-Pack compliant packs reported to ARM here:
-<a href="https://www.keil.com/pack/index.pidx">www.keil.com/pack/index.pidx</a>
+<a href="https://www.keil.com/pack/index.pidx">https://www.keil.com/pack/index.pidx</a>
 
 The vendor index file containing references to the package index files (or optionally PDSC files) used for compiling this
 summary index file are listed in the Keil.vidx file and can be downloaded from here:
-<a href="https://www.keil.com/pack/Keil.vidx">www.keil.com/pack/Keil.vidx</a>
+<a href="https://www.keil.com/pack/Keil.vidx">https://www.keil.com/pack/Keil.vidx</a>
 
 Based on these publicly available index files, everyone is equally positioned to create an index of available packs and their
 latest versions.

+ 1 - 1
CMSIS/DoxyGen/Pack/src/pack_publish.txt

@@ -96,7 +96,7 @@ ensure that the pack is found by a \ref cp_KeilComPack "Pack Index Service", fol
 
 Tool, software, or silicon vendors may provide a web infra-structure that lists packs that are available from multiple vendors.
 Companies like Arm or IAR provide a \ref cp_KeilComPack "Pack Index Service" that uses either a \elem{vendor}.\elem{name}.pdsc or a
-\elem{vendor}.pidx file to obtain the latest pack versions.  This information is used to make the packs available in the development tools (via a <b><a href="http://www.keil.com/mdk5/packinstaller/">Pack Installer</a></b>) and/or to publish information on certain web pages, for example a <b><a href="https://developer.arm.com/embedded/cmsis/cmsis-packs/devices" target="_blank">device list</a></b>.
+\elem{vendor}.pidx file to obtain the latest pack versions.  This information is used to make the packs available in the development tools (via a <b><a href="https://www.keil.com/mdk5/packinstaller/">Pack Installer</a></b>) and/or to publish information on certain web pages, for example a <b><a href="https://developer.arm.com/embedded/cmsis/cmsis-packs/devices" target="_blank">device list</a></b>.
 
 The following diagram explains how these services are working behind the scene. 
 

+ 4 - 4
CMSIS/DoxyGen/Pack/src/pack_swcomponents.txt

@@ -56,13 +56,13 @@ PACK.xsd file into the working directory):
       <url>file:///c:/temp/working</url>
       \endverbatim
     - It is important to understand how the \<url\> element works. If you specify a URL, for example
-      <a href="http://www.keil.com/pack/" target="_blank">http://www.keil.com/pack</a>,
+      <a href="https://www.keil.com/pack/" target="_blank">https://www.keil.com/pack</a>,
       then you have to make the PDSC file and the corresponding Pack file(s) available for download at that exact location.
       The naming of the files follow the standard naming rules. For example, the ARM::CMSIS PDSC and Pack files are available
       here:\n
-      <a href="http://www.keil.com/pack/ARM.CMSIS.pdsc" target="_blank">http://www.keil.com/pack/ARM.CMSIS.pdsc</a> and \n
-      <a href="http://www.keil.com/pack/ARM.CMSIS.4.3.0.pack" target="_blank">http://www.keil.com/pack/ARM.CMSIS.4.3.0.pack</a> and \n
-      <a href="http://www.keil.com/pack/ARM.CMSIS.4.2.0.pack" target="_blank">http://www.keil.com/pack/ARM.CMSIS.4.2.0.pack</a> and ... \n
+      <a href="https://www.keil.com/pack/ARM.CMSIS.pdsc" target="_blank">https://www.keil.com/pack/ARM.CMSIS.pdsc</a> and \n
+      <a href="https://www.keil.com/pack/ARM.CMSIS.4.3.0.pack" target="_blank">https://www.keil.com/pack/ARM.CMSIS.4.3.0.pack</a> and \n
+      <a href="https://www.keil.com/pack/ARM.CMSIS.4.2.0.pack" target="_blank">https://www.keil.com/pack/ARM.CMSIS.4.2.0.pack</a> and ... \n
       At the specified location, you need to have one (unversioned) PDSC file and can have multiple versioned Pack files,
       but at least the latest one.
 - \ref element_package "<supportContact>" may provide an email address or web page URL for Pack specific questions/problems

+ 3 - 3
CMSIS/DoxyGen/RTOS/src/cmsis_os.txt

@@ -541,7 +541,7 @@ towards the Cortex-M processors. Optional features may be for example
 /**
 \page rtosValidation RTOS Validation
 
-Arm offers a <a class=el href="http://www.keil.com/pack" target="_blank">Software Pack</a> for the CMSIS-RTOS Validation.
+Arm offers a <a class=el href="https://www.keil.com/pack" target="_blank">Software Pack</a> for the CMSIS-RTOS Validation.
 The <b>ARM::CMSIS-RTOS_Validation</b> Pack contains the following:
 
  - Source code of a CMSIS-RTOS Validation Suite along with configuration file.
@@ -671,7 +671,7 @@ CMSIS-RTOS RTX uses the following \#defines.
 \section KernelTimer RTX Kernel Timer Tick and Thread Management
 
 By default, CMSIS-RTOS RTX uses the Cortex-M
-<a href="http://www.keil.com/support/man/docs/gsac/GSAC_SYSTICKtimer.htm" target="_blank">SysTick</a> timer to generate
+<a href="https://www.keil.com/support/man/docs/gsac/GSAC_SYSTICKtimer.htm" target="_blank">SysTick</a> timer to generate
 periodic interrupts for the RTX kernel timer tick. CMSIS-RTOS provides \ref CMSIS_RTOS_TimerMgmt functions and several
 CMSIS-RTOS functions have a timeout parameter. This periodic RTX kernel timer tick interrupt is used to derive the required
 time interval. CMSIS-RTOS RTX also provides configuration options for a alternative timer and tick-less operation. Refer to
@@ -1620,7 +1620,7 @@ The tutorial is an excerpt of Trevor Martin's book
 It is accompanied by a Pack file that contains the example projects that are discussed in the tutorial.
 
 The tutorial is available as a Software Pack from
-<a href="http://www.keil.com/dd2/pack" target="_blank">http://www.keil.com/dd2/pack</a>. On the page, browse to \b Hitex and
+<a href="https://www.keil.com/dd2/pack" target="_blank">https://www.keil.com/dd2/pack</a>. On the page, browse to \b Hitex and
 select the Pack described as "An Introduction to using CMSIS RTOS for Cortex-M Microcontrollers". Download and install the
 Pack which contains all example projects referenced in the
 <a class="el" href="CMSIS_RTOS_Tutorial.pdf">CMSIS_RTOS_Tutorial.pdf</a>.

+ 6 - 6
CMSIS/DoxyGen/RTOS2/src/cmsis_os2.txt

@@ -137,7 +137,7 @@ The steps to create a microcontroller application using RTX5 are:
 - Create a new project and select a microcontroller device.
 - In the Manage Run-Time Environment window, select <b>CMSIS\::CORE</b> and <b>CMSIS\::RTOS2 (API)\::Keil RTX5</b>. You can
   choose to either add RTX as a library (Variant: \b Library) or to add the full source code (Variant: \b Source - required
-  if using the <a href="http://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a>):
+  if using the <a href="https://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a>):
 
    \image html manage_rte_output.png
 
@@ -214,7 +214,7 @@ If you require some of the \ref rtx5_specific "RTX specific functions" in your a
 \section cre_rtx_proj_er Add Event Recorder Visibility
 
 \ifnot FuSaRTS
-RTX5 interfaces to the <a href="http://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a> 
+RTX5 interfaces to the <a href="https://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a> 
 to provide event information which helps you to understand and analyze the operation.
 
 - To use the Event Recorder together with RTX5, select the software component <b>Compiler:Event Recorder</b>.
@@ -576,7 +576,7 @@ void osRtxIdleThread (void) {
 
 \note
 \c __WFE() is not available in every Arm Cortex-M implementation. Check device manuals for availability. 
-The alternative using \c __WFI() has other issues, please take note of http://www.keil.com/support/docs/3591.htm as well.
+The alternative using \c __WFI() has other issues, please take note of https://www.keil.com/support/docs/3591.htm as well.
 
 \section rtx_os_h RTX5 Header File
 
@@ -716,7 +716,7 @@ using the CMSIS-RTOS RTX kernel. The configuration options are explained in deta
 - \ref semaphoreConfig provides several parameters to configure the \ref CMSIS_RTOS_SemaphoreMgmt functions.
 - \ref memPoolConfig provides several parameters to configure the \ref CMSIS_RTOS_PoolMgmt functions.
 - \ref msgQueueConfig provides several parameters to configure the \ref CMSIS_RTOS_Message functions.
-- \ref evtrecConfig provides several parameters to configure RTX for usage with <a href="http://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a>.
+- \ref evtrecConfig provides several parameters to configure RTX for usage with <a href="https://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a>.
 
 The file "RTX_Config.c" contains default implementations of the functions \ref osRtxIdleThread and \ref osRtxErrorNotify. Both functions
 can simply be overwritten with a customized behavior by redefining them as part of the user code.
@@ -984,7 +984,7 @@ The total storage size reserved for all queues is configured in \c OS_MSGQUEUE_D
 
 \section evtrecConfig Event Recorder Configuration
 
-This section describes the configuration settings for the <a href="http://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank">Event Recorder</a>
+This section describes the configuration settings for the <a href="https://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank">Event Recorder</a>
 annotations. The usage requires the source variant of RTX5; refer to \ref cre_rtx_proj_er for more information.
 
 \subsection evtrecConfigGlobIni Global Configuration
@@ -1593,7 +1593,7 @@ The RTX5 C source files use <b><a class=el href="http://www.misra.org.uk/" targe
 
 For MISRA validation, <b><a class=el href="http://www.gimpel.com/" target="_blank">PC-lint</a></b> V9.00L is used with configuration for Arm Compiler V6.9.
 The PC-Lint validation setup is part of the project file <b>.\\CMSIS\\RTOS2\\RTX\\Library\\ARM\\MDK\\RTX_CM.uvprojx</b> as shown below. 
-Refer to <b><a class=el href="http://www.keil.com/support/man/docs/uv4/uv4_ut_pclint_validation.htm" target="_blank">Setup for PC-Lint</a></b> for more information.
+Refer to <b><a class=el href="https://www.keil.com/support/man/docs/uv4/uv4_ut_pclint_validation.htm" target="_blank">Setup for PC-Lint</a></b> for more information.
 
 \image html "PC-Lint.png" "Running PC-Lint within MDK - uVision"
 

+ 1 - 1
CMSIS/DoxyGen/RTOS2/src/rtx_evr.txt

@@ -3,7 +3,7 @@
 \ingroup rtx5_specific 
 \brief RTX5 Event Recorder functions
 \details
-RTX5 interfaces to the <a href="http://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a> 
+RTX5 interfaces to the <a href="https://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a> 
 to provide event information which helps you to understand and analyze the operation.
 
 To use the Event Recorder together with RTX5, it is required to create an image that generates event information. 

+ 1 - 1
CMSIS/DoxyGen/RTOS2/src/rtx_os.txt

@@ -11,7 +11,7 @@ The RTX5 kernel can be customized for different application requirements:
   
 - The function \ref osRtxErrorNotify may be extended to handle system runtime errors.
 
-RTX5 interfaces to the <a href="http://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a> 
+RTX5 interfaces to the <a href="https://www.keil.com/pack/doc/compiler/EventRecorder/html/index.html" target="_blank"><b>Event Recorder</b></a> 
 and provides event information that helps to analyze the operation. Refer to \ref rtx_evr for more information.
 
 

+ 1 - 1
CMSIS/DoxyGen/RTOS2/src/validation.txt

@@ -1,7 +1,7 @@
 /**
 \page rtosValidation RTOS Validation
 
-Arm offers a <a class=el href="http://www.keil.com/pack" target="_blank">Software Pack</a> for the CMSIS-RTOS Validation.
+Arm offers a <a class=el href="https://www.keil.com/pack" target="_blank">Software Pack</a> for the CMSIS-RTOS Validation.
 The <b>ARM::CMSIS-RTOS_Validation</b> Pack contains the following:
 
  - Source code of a CMSIS-RTOS Validation Suite along with configuration file.