Skip to content

Commit 5375615

Browse files
Minor README.md update (#43)
1 parent f4e86ae commit 5375615

4 files changed

Lines changed: 10 additions & 10 deletions

File tree

Documentation/Doxygen/src/DV_USBD.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ USB drivers need to be tested against the requirements of the USB standard. The
3232
Before using the command verifier tools, make sure that you have an application running with the USB device class that you
3333
are going to test. For example, if you want to test the behavior of the USB MSC device class, create a µVision project
3434
containing this class. For more information, refer to the
35-
<a href="http://www.keil.com/pack/doc/mw/USB/html/_u_s_b__device.html#Creation_Steps" target="_blank">MDK Middleware</a>
35+
<a href="https://arm-software.github.io/MDK-Middleware/latest/USB/usbd_create_app.html" target="_blank">MDK Middleware</a>
3636
documentation.
3737

3838
Then, follow these steps to run the verification tools on a Windows PC:

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,9 @@ Basic tests:
3131

3232
| Directory/File | Content |
3333
| --------------------- | --------------------------------------------------------- |
34-
| [`Boards`](./Boards/) | Driver Validation examples for various boards |
3534
| [`Config`](./Config/) | Configuration files for the Driver Validation framework |
3635
| [`Documentation`](./Documentation) | Placeholder and source for the offline documentation in the pack |
36+
| [`Examples`](./Examples/) | Driver Validation examples for various drivers |
3737
| [`Include`](./Include) | Header files for Driver Validation components |
3838
| [`Source`](./Source) | Source files for Driver Validation components |
3939
| [`Template`](./Template) | Driver Validation application template |
@@ -46,7 +46,7 @@ Basic tests:
4646

4747
## Examples
4848

49-
Folder [`Boards`](./Boards/) contains example projects that show how to use the CMSIS-Driver Validation on a real hardware with available CMSIS-Driver implementations.The examples are also included in CMSIS-Driver Validation Software Pack. Details are explained in [Examples documentation](https://arm-software.github.io/CMSIS-Driver_Validation/main/examples.html).
49+
Folder [`Examples`](./Examples/) contains example projects that show how to use the CMSIS-Driver Validation on a real hardware with available CMSIS-Driver implementations. The examples are also included in CMSIS-Driver Validation Software Pack. Details are explained in [Examples documentation](https://arm-software.github.io/CMSIS-Driver_Validation/main/examples.html).
5050

5151
## Build CMSIS-Driver Validation as Open-CMSIS-Pack
5252

Source/DV_SPI.c

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1295,7 +1295,7 @@ Required pin connections for the <b>SPI Server</b> test mode:
12951295
These tests verify API and operation of the SPI driver management functions.
12961296
12971297
The driver management tests verify the following driver functions
1298-
(<a href="http://www.keil.com/pack/doc/CMSIS/Driver/html/group__spi__interface__gr.html" target="_blank">SPI Driver function documentation</a>):
1298+
(<a href="https://arm-software.github.io/CMSIS_6/latest/Driver/group__spi__interface__gr.html" target="_blank">SPI Driver function documentation</a>):
12991299
- \b GetVersion
13001300
\code
13011301
ARM_DRIVER_VERSION GetVersion (void);
@@ -1691,7 +1691,7 @@ void SPI_PowerControl (void) {
16911691
These tests verify API and operation of the SPI data exchange functions.
16921692
16931693
The data exchange tests verify the following driver functions
1694-
(<a href="http://www.keil.com/pack/doc/CMSIS/Driver/html/group__spi__interface__gr.html" target="_blank">SPI Driver function documentation</a>):
1694+
(<a href="https://arm-software.github.io/CMSIS_6/latest/Driver/group__spi__interface__gr.html" target="_blank">SPI Driver function documentation</a>):
16951695
- \b Send
16961696
\code
16971697
int32_t Send (const void *data, uint32_t num);
@@ -3872,7 +3872,7 @@ These tests verify API and operation of the SPI event signaling, except ARM_SPI_
38723872
signal which is tested in the Data Exchange tests.
38733873
38743874
The event tests verify the following driver function
3875-
(<a href="http://www.keil.com/pack/doc/CMSIS/Driver/html/group__spi__interface__gr.html" target="_blank">SPI Driver function documentation</a>):
3875+
(<a href="https://arm-software.github.io/CMSIS_6/latest/Driver/group__spi__interface__gr.html" target="_blank">SPI Driver function documentation</a>):
38763876
- \b SignalEvent
38773877
\code
38783878
void (*ARM_SPI_SignalEvent_t) (uint32_t event);

Source/DV_USART.c

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1873,7 +1873,7 @@ Required pin connections for the <b>USART Server</b> test mode with <b>USART Ser
18731873
These tests verify API and operation of the USART driver management functions.
18741874
18751875
The driver management tests verify the following driver functions
1876-
(<a href="http://www.keil.com/pack/doc/CMSIS/Driver/html/group__usart__interface__gr.html" target="_blank">USART Driver function documentation</a>):
1876+
(<a href="https://arm-software.github.io/CMSIS_6/latest/Driver/group__usart__interface__gr.html" target="_blank">USART Driver function documentation</a>):
18771877
- \b GetVersion
18781878
\code
18791879
ARM_DRIVER_VERSION GetVersion (void);
@@ -2277,7 +2277,7 @@ void USART_PowerControl (void) {
22772277
These tests verify API and operation of the USART data exchange functions.
22782278
22792279
The data exchange tests verify the following driver functions
2280-
(<a href="http://www.keil.com/pack/doc/CMSIS/Driver/html/group__usart__interface__gr.html" target="_blank">USART Driver function documentation</a>):
2280+
(<a href="https://arm-software.github.io/CMSIS_6/latest/Driver/group__usart__interface__gr.html" target="_blank">USART Driver function documentation</a>):
22812281
- \b Send
22822282
\code
22832283
int32_t Send (const void *data, uint32_t num);
@@ -4499,7 +4499,7 @@ void USART_TxBreak (void) {
44994499
These tests verify API and operation of the USART modem lines handling functions.
45004500
45014501
The data exchange tests verify the following driver functions
4502-
(<a href="http://www.keil.com/pack/doc/CMSIS/Driver/html/group__usart__interface__gr.html" target="_blank">USART Driver function documentation</a>):
4502+
(<a href="https://arm-software.github.io/CMSIS_6/latest/Driver/group__usart__interface__gr.html" target="_blank">USART Driver function documentation</a>):
45034503
- \b SetModemControl
45044504
\code
45054505
int32_t SetModemControl (ARM_USART_MODEM_CONTROL control);
@@ -4828,7 +4828,7 @@ ARM_USART_EVENT_RECEIVE_COMPLETE, ARM_USART_EVENT_TRANSFER_COMPLETE and ARM_USAR
48284828
which is tested in the Data Exchange tests.
48294829
48304830
The event tests verify the following driver function
4831-
(<a href="http://www.keil.com/pack/doc/CMSIS/Driver/html/group__usart__interface__gr.html" target="_blank">USART Driver function documentation</a>):
4831+
(<a href="https://arm-software.github.io/CMSIS_6/latest/Driver/group__usart__interface__gr.html" target="_blank">USART Driver function documentation</a>):
48324832
- \b SignalEvent
48334833
\code
48344834
void (*ARM_USART_SignalEvent_t) (uint32_t event);

0 commit comments

Comments
 (0)