Skip to content

Commit 6b46c3b

Browse files
authored
Update README.md
duplicated playback test section
1 parent beee51b commit 6b46c3b

1 file changed

Lines changed: 4 additions & 28 deletions

File tree

‎ST/B-U585I-IOT02A/README.md‎

Lines changed: 4 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ SDS recording stopped
109109
SDS recording started
110110
```
111111

112-
Each run records two files: `DataInput.<n>.sds` and `DataOutput.<0>.sds` in the folder where SDSIO-Server was started. `<n>` is a sequential number.
112+
Each run records two files: `DataInput.<n>.sds` and `DataOutput.<n>.sds` in the folder where SDSIO-Server was started. `<n>` is a sequential number.
113113

114114
**Check SDS Files**
115115

@@ -139,8 +139,9 @@ For executing the **playback** test, follow the steps below:
139139
6. Press a User button on the ST B-U585I-IOT02A board to start playback of `DataInput` and recording of `DataOutput`.
140140
7. Wait for playback to finish, it will finish automatically when all data from `DataInput.0.sds` SDS file was played back.
141141

142-
The stream `DataInput.<n>.sds` is read back and the algorithm processes this data. The stream `DataOutput.<m>.sds` is written whereby `<m>` is the next available file index.
143-
The files `DataOutput.<n>.sds` and `DataOutput.<m>.sds` should be identical. In this example the file pairs are `DataOutput.0.sds`/`DataOutput.2.sds`, and `DataOutput.1.sds`/`DataOutput.3.sds`.
142+
The stream `DataInput.<n>.sds` is read back and the algorithm processes this data. The stream `DataOutput.<m>.sds` is written whereby `<m>` is the next available file index.
143+
144+
To verify that the SDS component usage on hardware is reliable the two algorithm output data generated during recording and playback: the files `DataOutput.<n>.sds` and `DataOutput.<m>.sds` should be identical, e.g. `DataOutput.0.sds` and `DataOutput.1.sds` should be binary identical.
144145

145146
**Output of SDSIO Server**
146147

@@ -160,31 +161,6 @@ Stream closed: DataInput (DataInput.1.sds).
160161
Stream closed: DataOutput (DataOutput.3.sds).
161162
```
162163

163-
#### Playback
164-
165-
For **playback** test, follow the steps below:
166-
167-
1. Connect USB cable between Host and development board
168-
2. Start the [SDSIO-Server](https://arm-software.github.io/SDS-Framework/main/utilities.html#sdsio-server):
169-
```bash
170-
sdsio-server usb
171-
```
172-
3. Open `SDS.csolution.yml` in Visual Studio Code:
173-
- Select **Target Type**: `STM32U585AIIx`
174-
- Choose **Project Name**: `DataTest` and **Build Type**: `DebugPlay` to playback/record SDS data files.
175-
4. Build and run the application on the hardware.
176-
5. Press a blue button (B3 USER) to start playback and recording.
177-
6. Wait for playback to finish, it will finish automatically when all data from `DataInput.1.sds` SDS file was played back.
178-
179-
**Results**
180-
181-
Result should be one generated file `DataInput.1.sds` in the folder where SDSIO-Server was started.
182-
183-
`DataOutput.1.sds` contains recorded output data of the algorithm using input data played from `DataInput.0.sds` file.
184-
185-
To verify that the SDS component usage on hardware is reliable the two recordings of algorithm output data generated during recording and playback:
186-
`DataOutput.0.sds` and `DataOutput.1.sds` should be binary identical.
187-
188164
## DataTest Project on AVH-FVP Simulation
189165

190166
The DataTest can be also executed on [AVH-FVP](https://github.com/ARM-software/AVH) simulation models using the steps below.

0 commit comments

Comments
 (0)