Skip to content

Commit

Permalink
Referring to video driver event
Browse files Browse the repository at this point in the history
  • Loading branch information
vovamarch committed Jun 18, 2024
1 parent f61c727 commit 3c4cce7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion DoxyGen/simulation/src/Ref_video.txt
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ The execution flow for video input on channel 0 is explained in the diagram belo
7. With step 6 completed, a loop of frame reading is started:
- 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 VSI interrupt check can be used as well.
- \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() .
- 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.
Expand Down

0 comments on commit 3c4cce7

Please sign in to comment.