Tool/software:
Hi team ,
Is it possible to access ISP (VISS) registers or where to find the register lists of all the parameters of blocks in VISS to understand the mapping ?
Best Regards,
Sushma Biradar
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hi team ,
Is it possible to access ISP (VISS) registers or where to find the register lists of all the parameters of blocks in VISS to understand the mapping ?
Best Regards,
Sushma Biradar
Hi Sushma,
Each register has its own physical address as you can see in the register manual and it can be accessed via CPU or DMA.
ISP registers of a particular block mapping to the HW
I am not sure what this means as I am not familiar with low level details.
Could you please explain?
Hello Gang,
We were trying to access ISP registers (ex: NSF4 block and its parameters) map them externally and update the values via TCP if possible ,
so we need information of how internally in SDK the registers are being mapped to their respective parameters
Regards,
Sushma Biradar
Hi Sushma,
to access ISP registers (ex: NSF4 block and its parameters) map them externally and update the values via TCP
All ISP register information is available in the TRM package as we discussed above.
Typically, controlling ISP registers directly and externally is not possible.
While some cameras are running and using ISP, they will update the ISP registers frame by frame.
Any other external control of ISP registers would be overridden by the running cameras.
The way we did similar control in tuning tool is indirect.
i.e., external control is applied on a camera's tuning data.
While the camera updates ISP registers before each new image frame, it will use the updated dataset.
we need information of how internally in SDK the registers are being mapped to their respective parameters
This mapping depends on the s/w stack you use, but you probably don't use the TI SDK stack.
In TI SDK, ISP parameters are separately defined and they are passed to tiovx VPAC kernels to be mapped to PDK driver format before calling PDK driver.