Linux/TDA2PXEVM: Enabling LDC Feature in HLOS Usecase

Hi Kim,

The fundamental idea that allows control of links running on M4 from HLOS/usecase is based on following

On M4 side, there is system command handler implemented in \apps\src\rtos\common\chains_main_linux.c in function AppCtrl_cmdHandler ()
refer command "APP_CTRL_LINK_CMD_ISS_DEFAULT_CONFIG"

From HLOS side, an command is sent to M4 side. \apps\src\hlos\adas\src\usecases\iss_capture_isp_display\chains_issIspSimcop_Display.c
refer command "APP_CTRL_LINK_CMD_ISS_DEFAULT_CONFIG"

To update the LDC table
1. Add a new command
2. On M4/RTOS implement command handler for this new command
2.1. One could refer RTOS based usecases to determine required parameters for LUT update
3. One could use command argument to provide the required LDC paramters
3.1. Ensure to provide the physical address (of both the structure and pointers within the structures)

Regards,
Sujith

Hi Sujith,

Thanks for your reply.

I already tested LDC in hlos usecase using command "APP_CTRL_LINK_CMD_ISS_DEFAULT_CONFIG".
My issue is that the static memory address of mesh lut in rtos is changed when simcop link is working. Thanks for your previous support, it may be solved.

The LDC is a very basic feature in TDA product. If it is implemented at customer side, there will be some code conflicts with future release of vision sdk.

Do you have a plan for supporting LDC in hlos usecase in vision sdk?

Thanks.

Hi Sujith,

Ok, I got it.
I'd like to get support from you if there are issues when implementing additional LDC features.

By the way, could you checkout below issue? It's about address conversion of virtual to physical in IPU.
e2e.ti.com/.../718643

Thanks.