Compiler/TDA4VM: ADAS camera

Guoxun

Intellectual 670 points

Part Number: TDA4VM

Tool/software: TI C/C++ Compiler

I want to develop ADAS on TDA4VM with new camera (maybe the driver is not included in SDK) .

How to add the driver needed by new camera into the code?

How to call the driver? Can I call driver and get image data for ADAS like demo "Single Camera VPAC Application"?

Is the relationship between application and driver like : application call API from vision_apps like
appInitImageSensor to call the driver IM_SENSOR_CMD_PWRON to power on the camera,

appStartImageSensor to call the driver IM_SENSOR_CMD_STREAM_ON to get stream from camera?

How can API (like appRemoteServiceRun) get the driver of new camera(the driver not included in the RTOS sdk)?

over 4 years ago

0 Dwarakesh Radhakrishnan over 4 years ago

Guru 13660 points

Hi,

Please check this post and see if it is of help : https://e2e.ti.com/support/processors/f/791/p/966961/3574528#3574528

0 Mayank Mangla over 4 years ago in reply to Dwarakesh Radhakrishnan

TI__Mastermind 24525 points

Here is a document explaining the process step by step.

http://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos_auto/docs/user_guide/developer_notes_image_sensor.html

Please let us know if you have further questions.

0 Guoxun over 4 years ago in reply to Dwarakesh Radhakrishnan

Intellectual 670 points

Hi,

This html solve most of the questions, and one is unclear.

What's the relation between application and driver api ?

Application call vision API (like appInitImageSensor and appRemoteServiceRun), and vision API call driver API (like AR0820_StreamOn called by IssSensor_PowerOn)？

Is the driver for sensor, deserializer/serializer ? that means: AR0820_PowerOn can powerOn sensor, deserializer ,serializer or all?

Thanks,

Guoxun

0 Dwarakesh Radhakrishnan over 4 years ago in reply to Guoxun

Guru 13660 points

What's the relation between application and driver api

Yes as you have understood, the application runs in the A72 core. The sensor driver is part of R5F core running TI RTOS. The calls like appInitImageSensor, appStartImageSensor and appStopImageSensor are called from A72 linux application. The communication between the A72 core and R5F core is through IPC(Inter Processor Communication). So A72 core in turn calls appRemoteServiceRun for Init,start and stop sensor APIs as mentioned above. The R5 core would have registered the service to handle the IPC commands for init, start and stop. So thats how it reaches the Sensor Driver in the R5 core.

example : appStartImageSensor() [A72 core] -> appRemoteServiceRun(IM_SENSOR_CMD_STREAM_ON)[A72 core] ->ImageSensor_RemoteServiceHandler(IM_SENSOR_CMD_STREAM_ON)[R5 core]->IssSensor_Start()[R5 core]->AR0820_StreamOn()[R5 core]

Is the driver for sensor, deserializer/serializer ? that means: AR0820_PowerOn can powerOn sensor, deserializer ,serializer or all?

Yes, there is no clear demarcation of Serializer and Deserializer drivers and Sensor drivers. There is sensor driver and the Deserializer init/configuration/deinit and Serializer init/confiuration/deinit are part of the sensor driver.

0 Guoxun over 4 years ago in reply to Dwarakesh Radhakrishnan

Intellectual 670 points

Got it.

Thanks.

0 Brijesh Jadav over 4 years ago in reply to Guoxun

TI__Guru**** 475555 points

Thanks Guaoxun. I am closing this thread.

Regards,

Brijesh

Processors

Processors forum

Compiler/TDA4VM: ADAS camera