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.

TDA4VEN-Q1: TDA4VEN-Q1: ISP Pipeline Customization and Access to RAWFE/NSF4 Implementation

Part Number: TDA4VEN-Q1

Dear TI Team,

I have two questions regarding the ISP pipeline implementation:

  1. For internal ISP interface functions such as rawfe_main() and nsf4_main(), is it possible to access or view their source code implementation? Or are these modules fully encapsulated within the VPAC/VISS hardware or closed libraries?
  2. Besides AE (which can be rebuilt or customized), is it possible to modify or rebuild other ISP modules (e.g., NSF4, RAWFE, etc.)? Additionally, is there any supported way to insert a custom ISP module into the pipeline, for example within or alongside rawfe_main()?

We would like to better understand the flexibility of the ISP pipeline for customization. We look forward to your response. 

  • For internal ISP interface functions such as rawfe_main() and nsf4_main(), is it possible to access or view their source code implementation? Or are these modules fully encapsulated within the VPAC/VISS hardware or closed libraries?

    Do you mean in the HW? I dont think we have such APIs in the HW. 

    For emulation mode, these are implemented in the library, which can't be shared.

    Besides AE (which can be rebuilt or customized), is it possible to modify or rebuild other ISP modules (e.g., NSF4, RAWFE, etc.)? Additionally, is there any supported way to insert a custom ISP module into the pipeline, for example within or alongside rawfe_main()?

    Again, if they are in HW, can't be rebuild.. For emulation mode, they are shared only in library form. 

    Regards,

    Brijesh