From 8108f26e42dfa98533abb11cbef3789c121e0f33 Mon Sep 17 00:00:00 2001 From: Vladimir Marchenko Date: Tue, 18 Jun 2024 20:48:07 +0200 Subject: [PATCH] Typo fix --- DoxyGen/simulation/src/Ref_video.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DoxyGen/simulation/src/Ref_video.txt b/DoxyGen/simulation/src/Ref_video.txt index bc50339..13695ba 100644 --- a/DoxyGen/simulation/src/Ref_video.txt +++ b/DoxyGen/simulation/src/Ref_video.txt @@ -56,7 +56,7 @@ The execution flow for video input on channel 0 is explained in the diagram belo - A frame is read from the file, and is prepared according to the stream configuration (with crop/resize and color change operations done in the vsi_video_server.py). - The processed frame data is copied to the DMA buffer. - \ref VideoDrv_GetStatus checks if the frame buffer is full, meaning that a complete frame was transferred to the FVP memory. An approach with asynchronous video driver event \ref VIDEO_DRV_EVENT_FRAME can be used as well. - - When video buffer is filled, we can extract the frame from it using \ref VideoDrv_GetFrameBuf() . + - When video buffer is filled, we can extract the frame from it using \ref VideoDrv_GetFrameBuf. - Obtained frame can be now passed to the processing algorithm (for example for object detection). - Release the frame with \ref VideoDrv_ReleaseFrame to enable reception of the next frame. - Repeat the steps above until end of stream is reported in the status.