• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 255 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DS90UB933-Q1: Config function in iss_sensors.c file

Muralidharan P V
Intellectual 450 points

Part Number: DS90UB933-Q1

As per our understanding from after changing the modification in the iss_sensor.c file to add new camera we will do the make, the compiled files will be loaded to vision apps from imaging folder but, where the functions like  sensor_config or fusion_board_init inside the iss_sensor.c is getting called from the single_camera_app ?

  • 0
    TI__Mastermind 24525 points

    imaging driver runs on R5F as part of RTOS firmware while single camera app executes on A72 in Linux. Therefore you will not be able to find a direct function call of imaging APIs from the app. The flow is as follows

    1. app_single_cam calls functions (e.g. appInitImageSensor) in app_iss (vision_apps/utils/iss)

    2. app_iss translates application parameters to Remote Proc Messages. Examples are IM_SENSOR_CMD_PWRON, IM_SENSOR_CMD_CONFIG etc.

    3. imaging library has a service listening to commands coming from A72. Please refer to ImageSensor_RemoteServiceHandler in imaging/sensor_drv/src/iss_sensor functions. 

    4. Based on the command received, one or more of the sensor driver functions (e.g. IssSensor_PowerOn, IssSensor_Config) will be called

    5. These functions will then call specific sensor driver handlers which have been registered during sensor initialization time.

    Please let us know if you have any further questions.