diff --git a/Documentation/Doxygen/src/DV_USBD.txt b/Documentation/Doxygen/src/DV_USBD.txt index 5dc86e5..1a16716 100644 --- a/Documentation/Doxygen/src/DV_USBD.txt +++ b/Documentation/Doxygen/src/DV_USBD.txt @@ -32,7 +32,7 @@ USB drivers need to be tested against the requirements of the USB standard. The Before using the command verifier tools, make sure that you have an application running with the USB device class that you are going to test. For example, if you want to test the behavior of the USB MSC device class, create a µVision project containing this class. For more information, refer to the -MDK Middleware +MDK Middleware documentation. Then, follow these steps to run the verification tools on a Windows PC: diff --git a/README.md b/README.md index 1758f37..1d865c0 100644 --- a/README.md +++ b/README.md @@ -31,9 +31,9 @@ Basic tests: | Directory/File | Content | | --------------------- | --------------------------------------------------------- | -| [`Boards`](./Boards/) | Driver Validation examples for various boards | | [`Config`](./Config/) | Configuration files for the Driver Validation framework | | [`Documentation`](./Documentation) | Placeholder and source for the offline documentation in the pack | +| [`Examples`](./Examples/) | Driver Validation examples for various drivers | | [`Include`](./Include) | Header files for Driver Validation components | | [`Source`](./Source) | Source files for Driver Validation components | | [`Template`](./Template) | Driver Validation application template | @@ -46,7 +46,7 @@ Basic tests: ## Examples -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). +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). ## Build CMSIS-Driver Validation as Open-CMSIS-Pack diff --git a/Source/DV_SPI.c b/Source/DV_SPI.c index 7044b32..284279e 100644 --- a/Source/DV_SPI.c +++ b/Source/DV_SPI.c @@ -1295,7 +1295,7 @@ Required pin connections for the SPI Server test mode: These tests verify API and operation of the SPI driver management functions. The driver management tests verify the following driver functions -(SPI Driver function documentation): +(SPI Driver function documentation): - \b GetVersion \code ARM_DRIVER_VERSION GetVersion (void); @@ -1691,7 +1691,7 @@ void SPI_PowerControl (void) { These tests verify API and operation of the SPI data exchange functions. The data exchange tests verify the following driver functions -(SPI Driver function documentation): +(SPI Driver function documentation): - \b Send \code 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_ signal which is tested in the Data Exchange tests. The event tests verify the following driver function -(SPI Driver function documentation): +(SPI Driver function documentation): - \b SignalEvent \code void (*ARM_SPI_SignalEvent_t) (uint32_t event); diff --git a/Source/DV_USART.c b/Source/DV_USART.c index a82ce32..8c8b1df 100644 --- a/Source/DV_USART.c +++ b/Source/DV_USART.c @@ -1873,7 +1873,7 @@ Required pin connections for the USART Server test mode with USART Ser These tests verify API and operation of the USART driver management functions. The driver management tests verify the following driver functions -(USART Driver function documentation): +(USART Driver function documentation): - \b GetVersion \code ARM_DRIVER_VERSION GetVersion (void); @@ -2277,7 +2277,7 @@ void USART_PowerControl (void) { These tests verify API and operation of the USART data exchange functions. The data exchange tests verify the following driver functions -(USART Driver function documentation): +(USART Driver function documentation): - \b Send \code int32_t Send (const void *data, uint32_t num); @@ -4499,7 +4499,7 @@ void USART_TxBreak (void) { These tests verify API and operation of the USART modem lines handling functions. The data exchange tests verify the following driver functions -(USART Driver function documentation): +(USART Driver function documentation): - \b SetModemControl \code 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 which is tested in the Data Exchange tests. The event tests verify the following driver function -(USART Driver function documentation): +(USART Driver function documentation): - \b SignalEvent \code void (*ARM_USART_SignalEvent_t) (uint32_t event);