TDA3MV: How to ensure that the image flow is always smooth when DSP or EVE is busy?

YiTing

Part Number: TDA3MV

Hi,

I use PROCESSOR_SDK_VISION_03_04_00_00 in the custom board.

In fast_boot_iss_capture_isp_simcop_pd_display, if the calculation of DUP Q2 is not fast enough, the image will be dropped in Issm2misp.

How to ensure that the image flow is always smooth when DSP or EVE is busy?

Can I use workQ achieve it?

over 3 years ago

0 Gaviraju Doddabettahalli Bettegowda over 3 years ago

TI__Genius 14305 points

Hi,

Please share the logs with statistics.

Thanks

Gaviraju

0 Brijesh Jadav over 3 years ago in reply to Gaviraju Doddabettahalli Bettegowda

TI__Guru**** 399260 points

Hi,

Well you need to control it in the usecase. For example, if a component takes more than 33ms, then next frame needs to be finished in remaining time or needs to be dropped.. This needs to be controlled by application.

Rgds,

Brijesh

0 YiTing over 3 years ago in reply to Brijesh Jadav

Expert 1200 points

Hi,

There are currently modified links in use such as pictures.

ALG runs in ALG_FrameCopy, when ALG is busy issM2mResizer will drop frame.

My opinion DUP Q0 should not be affected by ALG.

0 Gaviraju Doddabettahalli Bettegowda over 3 years ago in reply to YiTing

TI__Genius 14305 points

Hi,

This is expected output because ALG_FrameCopy link is taking more time to process each frame, so the buffer is not returning to the "issM2mResizer" link immediately. when the output buffer is not available in the queue, obviously the frame will drop in the "issM2mResizer" link.

Note: The Dup link will not copy the pixel data, duplicating only buffer pointer address & it's creating two output queue Q0 & Q1 then passing same buffer pointer

In link & chain, if one of the link becomes busy then it will affect the FPS value, so please try to optimize the link which is taking more time to process.

Thanks

Gaviraju

0 YiTing over 3 years ago in reply to Gaviraju Doddabettahalli Bettegowda

Expert 1200 points

Hi Gaviraju,

I checked DUP LINK, it just copy System_Buffer info from previous link.

I have two quetion below:

Q1 :

Does Sync, gate, ipc in/out and merge link do not copy the pixel data link dup link?

Q2 :

Why do I draw pictures on the frame copy link output buffer,

The received picture has not been changed in dup link Q0?

0 Gaviraju Doddabettahalli Bettegowda over 3 years ago in reply to YiTing

TI__Genius 14305 points

Hi,

1) Yes, the link Sync, gate, ipc in/out, merge, and dup link do not copy the pixel data. Please refer to the below document for understanding the links & chain framework architecture.

file: vision_sdk/docs/Architecture/VisionSDK_SW_Architecture_Overview.pdf

file: vision_sdk/docs/Architecture/VisionSDK_SW_Architecture_Details.pdf

2) I could not see the drawn picture on the frame copy link output buffer in the chain you have created.

Thanks

Gaviraju

Processors

Processors forum

TDA3MV: How to ensure that the image flow is always smooth when DSP or EVE is busy?