TDA4VL-Q1: [j7122s] how many cameras(2.5MP) can support on VPAC in sdk 10.0

Hi Sungenben,

I would suggest you to refer to specs for getting VPAC MHz details. 

Yes, in the current SW, context save/restore is not supported. It would be added in the next SDK release.

Regards,

Brijesh

Hi Brijesh 

thank you for reply !

I had seen the data sheet  the VPAC is 600 MHZ , Is it support in SDK 10.1 ? or later version?

best regards

sungenben 

Hi Sungenben,

Yes, it is supported in SDK10.1. 2.5MP 2CH 30fps is around 150MP processing, this can be supported in VPAC. 

Regards,

Brijesh

Hi Brijesh 

today ,we download the SDK10.1 

Hi Brijesh 

today ,we downloaded the sdk 10.1 ,we found that the viss just support one camera .(vx_vpac_viss_target.c)

It didn't modify in sdk 10.1 , please check the sdk as below , we use the SOC_J722S.

best reagrds

sungenben

Hi sungenben,

Let me check with the team.

Regards,

Brijesh

Hi sungenben,

This is done inside the drivers. When we enable glbce by resetting bypass_glbce flag and setting enable_ctx flag in the viss parameters, internally driver will take care of doing this context save and restore. So this is not done in viss node, but taken care inside the driver on J722S.

Regards,

Brijesh

Hi Brijesh

you mean that we can modify the source in the viss source to enable the restore function .and also can use the UDMA in J722S?

best regards

sungenben

Hi Sun genben,

No, i mean this feature is already supported in the driver, we need just to enable few flags, which are by default enabled in multi-camera example. 

UDMA for which purpose?

Regards,

Brijesh

Hi Brijesh 

please tell us how to keep the VPAC parameters by multi-camera ?

In TDA4VL and TDA4VM  , we use the source code  as below 

But In J72SS ,It didn't support , Could you tell us what we to can keep the different VPAC parameters in two cameras 

//source 

static void vhwaVissGlbceRestoreCtx(const tivxVpacVissObj *vissObj)
{
#if !defined(SOC_AM62A) && !defined(SOC_J722S)
#ifdef VHWA_VISS_GLBCE_CTX_SAVE_RESTORE_ENABLE
#ifdef VHWA_VISS_GLBCE_CTX_SAVE_RESTORE_USE_DMA
int32_t status;
#endif
app_udma_copy_1d_prms_t prms;

if ((NULL != vissObj) && (0u != vissObj->ctx_mem_phys_ptr))
{
prms.src_addr = vissObj->ctx_mem_phys_ptr;
prms.dest_addr = vissObj->glbceStatInfo.addr;
prms.length = vissObj->glbceStatInfo.size;
#ifdef VHWA_VISS_GLBCE_CTX_SAVE_RESTORE_USE_DMA
status = appUdmaCopy1D(NULL, &prms);

if (0 != status)
{
VX_PRINT(VX_ZONE_ERROR, "Failed to restore Context !!!\n");
}
#else
memcpy((void*)(uint32_t)prms.dest_addr, (void*)(uint32_t)prms.src_addr, prms.length);
#endif
}
#endif
#endif
}

best regards

sungenben 

Hi Sun genben,

As i said, this is not part of the VISS OpenVX node. It is taken care inside the VISS PDK drivers.

Regards,

Brijesh

Hi Brijesh

when do we can use the VISS OpenVX node  for two cameras ?

best regards

sungenben 

Hi sungenben,

Just make sure that the enable_ctx flag is set to try in tivx_vpac_viss_params_t. Then GLBCE context save and restore will be taken care by the driver. 

Regards,

Brijesh

Hi Brijesh

you mean   if we enable  vissDrvPrms->enableGlbceSaveRestoreCtx = (uint32_t)UTRUE; it can support two cameras .

the GLBCE context save and restore will be done automatically  by the driver . is that right?

best regards

sungenben

Yes, that's correct.