IPNC RDK: actual fps is lower than frame rate set in Link param.

Zhao Shui

Hi everyone,

I'm using IPNC RDK ver3.5 and IPNC DM8127.

this is my custom usecase:

camera->sclarlink->ipcVPSSframeout->ipcDSPframein->alg->ipcDSPbitsout->ipcHOSTbitsin.

In sclrLInk,I've already set its output frame rate to 5 fps,but later,when I test my algLink on dsp using Utils_getCurTimeInMsec(), I find it can only handle 2.7 fps on average,but the system can run very smoothly.

So I'm wondering what truly happens to the frames that are not handled by dsp,are they dropped without a error message?

One more question:Is it correct to use Load_getCPULoad() right after the alg is done to show the CPU load on DSP? I search the function on Internet and find its window is set to 500ms, but my core alg(doesn't include getting or putting frame and the tsk) usually takes about 450ms,so the CPU load is often 90%, is that correct?Do I have to increase the window size?If that's ture,how should I do it?

Thank you for your patience.

regards,

Zhao

over 9 years ago

0 Margarita Gashova over 9 years ago

TI__Guru* 80190 points

Hello,

I notified the IPNC team for help.

Best Regards,

Margarita

0 Anand Kulkarni71405 over 9 years ago in reply to Margarita Gashova

TI__Expert 8920 points

Hi,

The scaler link waits till it gets an empty output buffer.

So if your alg link is going to hold the input buffer for long time then scaler link is going to wait more time to get an empty output buffer this in turn causes the camera link to run out of empty output buffer resulting in skipping of the captured frame by the capture driver.

The way you are checking the DSP load should be fine.

Since your algorithm is running almost full time the DSP load of 90% is justified.

regards,

Anand

Processors

Processors forum

IPNC RDK: actual fps is lower than frame rate set in Link param.