You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -70,78 +70,41 @@ The table below provides information about the changes delivered with specific v
70
70
/**
71
71
\page setup Setup
72
72
73
-
\section step1 Step 1: Create an MDK project for your target microcontroller device
74
-
75
-
76
-
\section step2 Step 2: Add the required software components
77
-
78
-
For proper operation, add the following software components in the <b>Manage Run-Time Environment</b> window:
79
-
- <b>CMSIS Driver Validation: Framework</b>
80
-
- <b>CMSIS Driver Validation: driver</b>, driver interfaces to be tested
81
-
- <b>CMSIS Driver: driver</b>, driver implementations to be tested
82
-
- <b>CMSIS: RTOS2 (API): Keil RTX5</b>
83
-
- <b>Compiler: I/O: STDOUT</b>, variant \b ITM (if your hardware does not support ITM select \b EVR to use Event Recorder instead of ITM)
84
-
- Resolve any unresolved component dependencies
85
-
86
-
87
-
\section step3 Step 3: Add the application's main file (main.c)
88
-
89
-
Right-click <b>Source Group 1...</b> and select <b>Add New Item to Group</b>, select <b>User Code Template</b> and choose the
90
-
<b>CMSIS-RTOS2 'main' function</b> file from <b>CMSIS: RTOS2:Keil RTX5</b>.
91
-
92
-
Add this include:
93
-
\code
94
-
#include "cmsis_dv.h"
95
-
\endcode
96
-
97
-
In the <c>app_main</c> function, create the \c cmsis_dv thread, before endless <c>for</c> loop:
98
-
\code
99
-
osThreadNew(cmsis_dv, NULL, NULL);
100
-
\endcode
101
-
to run all the tests that you have chosen in the next step.
102
-
103
-
104
-
\section step4 Step 4: Configure the interface settings and tests in related DV_interface_Config.h files
105
-
106
-
Each interface has a related <b>DV_<i>interface</i>_Config.h</b> file, where <i>interface</i> represents interface's acronym or abbreviation.<br>
107
-
For example for Serial Peripheral Interface (SPI) related config file name is DV_SPI_Config.h.
108
-
109
-
For details on interface specific configuration and test selection please check the Configuration section in the
110
-
<a class="el" href="./topics.html">Reference</a> of the related interface.
111
-
112
-
113
-
\section step5 Step 5: Configure the Heap memory
73
+
Using the [Arm CMSIS Solution](https://marketplace.visualstudio.com/items?itemName=Arm.cmsis-csolution) VS Code extension,
74
+
create a new solution from **template**:
114
75
115
-
Depending on the buffer sizes used for data transfer tests the heap size has to be adjusted to provide enough memory for these
116
-
buffers to be allocated.<br>
117
-
Depending on how heap is configured in your system, open your <b>startup_\<device\>.s</b> or <b>startup_\<device\>.c</b> file from the \b Device group in the \b Project window
118
-
or use a <b>linker script</b> to adjust the heap size.<br>
119
-
Set the <b>heap size</b> to minimum of <b>16384</b> bytes.
76
+
\section step1 Step 1: In the **CMSIS** extension, click **Create a New Solution**.
77
+
\image html server_new_sol_create.png
120
78
121
-
For details on heap requirements please refer to the \ref heap_req "Heap Memory requirements" documentation.
79
+
\section step2 Step 2: Select the **Target Board**.
122
80
81
+
\section step3 Step 3: Under **Templates, Reference Applications, and Examples**, select **Driver Validation (CMSIS-Driver Validation application)**.
82
+
\image html driver_validation_new_sol_template.png
123
83
124
-
\section step6 Step 6: Configure the CMSIS-RTOS2 (Keil RTX5)
84
+
\section step4 Step 4: Choose **Solution Base Folder**, click **Create**.
85
+
\image html driver_validation_new_sol_create.png
125
86
126
-
Open <b>RTX_Config.h</b> and set:
127
-
- <b>System Configuration: Global Dynamic Memory size [bytes]</b> to \a 16384
\section step5 Step 5: Select the **Board Layer** that provides **required CMSIS Driver**, click **OK**.
88
+
\image html driver_validation_new_sol_layer.png
129
89
130
-
For details on CMSIS-RTOS2 requirements please refer to the \ref rtos2_req "CMSIS-RTOS2 requirements" documentation.
90
+
\section step6 Step 6: In the **Manage Solution**, under **Build Type** select desired Driver for validation, click **Save**.
91
+
\image html driver_validation_build_type.png
131
92
132
-
\section step7 Step 7: Configure the Device
93
+
\section step7 Step 7: Configure the Driver Tests in appropriate **DV_..._Config.h** file.
133
94
134
-
Depending on your device, you might have different pin/hardware configuration options. Usually, you can configure the device
135
-
using the \c RTE_Device.h file from the \b Device group or with a vendor provided pin configuration tool.
136
-
Enable all interfaces you wish to test and make all necessary pin-out changes required by your actual board layout (consult the board schematics).<br>
137
-
You can check the provided \ref examples "examples" as a reference point.
138
-
139
-
For a robust test with good coverage, implement various targets with different settings:
140
-
- Use <b>non-DMA (IRQ)</b> and <b>DMA</b> configurations if they are available on the driver
141
-
- Use different compiler <b>optimization levels</b> in the
142
-
<a href="http://www.keil.com/support/man/docs/uv4/uv4_dg_adscc.htm" target="_blank">C/C++ tab</a> of the
143
-
<b>Options for Target</b> dialog
95
+
> **Note:** `...` in **DV_`...`_Config.h** file depends on the driver being validated; for example, for Ethernet, the file would be **DV_ETH_Config.h** file.
144
96
97
+
For validation configuration of specific driver check respective driver documentation:
0 commit comments