Other Parts Discussed in Thread: TMDSEVM572X
Hello,
I have an AM572x Evaluation Module TMDSEVM572X with me. I am using TI Camera Module (TMDSCM572X AM57XX Camera Board REV C). And this camera works successfully on Linux PSDK (all versions).
I am trying to open camera preview on Android Processor SDK 4.03. I have also done HAL changes required in my opinion to open a camera preview on 4.03 SDK. I took "jacinto 6 auto evm" as base for doing changes around Camera HAL. Now, I want to test if my HAL changes are correct or not.
However, I am not able to test as I am not getting /dev/video1 node up on my EVM when I flash 4.03 SDK. TI experts have claimed in multiple threads that it is certainly possible to bring /dev/video1 node up with 4.03 SDK. I am attaching references of these threads as follows:
According to this e2e thread - https://e2e.ti.com/support/processors/f/791/p/681672/3085716 , I did dtb changes required to add new camera module in 4.03 SDK
According to this e2e thread (which was also posted by me) - https://e2e.ti.com/support/processors/f/791/t/821863 , I was not getting /dev/video1 node created.
TI locked this thread without resolving my query.
Note that I am only getting /dev/video0 registered as vpe but not /dev/video1 as vip. I think those dtb commits are either incomplete or there is something else.
I am not sure what I am missing here. I am attaching some important outputs for your perusal. Please acknowledge.
I did not use pre-built images as I did those dtb changes. After flashing image on my EVM, I copied both drivers ov1063x.ko and mt9t11x.ko on Android system and manually inserted both of them but got no prints.
am57xevm:/mnt # lsmod Module Size Used by mt9t11x 18837 0 ov1063x 14068 0 pvrsrvkm 288948 43 prueth 15164 0 pru_rproc 12161 5 prueth rpmsg_pru 5140 0 pruss 11442 2 prueth,pru_rproc pruss_intc 7826 5 pru_rproc snd_soc_tlv320aic3x 48807 1 gpio_pca953x 9709 0 tvp5158 7072 0 ov490 5014 0 pixcir_i2c_ts 6920 0 ldc3001_ts 4718 0 goodix 9068 0 input_polldev 4492 1 goodix edt_ft5x06 11534 0 pwm_bl 4714 0 led_bl 2991 0 gpio_backlight 2844 0 leds_tlc591xx 5019 0 panel_dpi 4046 1 connector_hdmi 4197 1 ti_fpd3_serdes 8523 0 encoder_tpd12s015 3933 1 encoder_tc358768 5932 0 dra7_evm_encoder_tpd12s015 5442 0 sd_mod 31226 0 usb_storage 48124 0 scsi_mod 164778 2 sd_mod,usb_storage wlcore_sdio 6907 0 wl18xx 85776 0 wlcore 183653 1 wl18xx
VPE is getting registered but it can not be used for capture.
am57xevm:/ # dmesg | grep vpe [ 4.619785] init: starting service 'exec 1 (/vendor/bin/modprobe -a -d /vendor/lib/modules wl18xx.ko wlcore.ko wlcore_sdio.ko scsi_mod.ko usb-storage.ko sd_mod.ko dra7-evm-encoder. [ 4.701181] init: Command 'exec u:r:vendor_modprobe:s0 -- /vendor/bin/modprobe -a -d /vendor/lib/modules wl18xx.ko wlcore.ko wlcore_sdio.ko scsi_mod.ko usb-storage.ko sd_mod.ko dr. [ 5.145705] vpe 489d0000.vpe: loading firmware vpdma-1b8.bin [ 5.249518] init: Service 'exec 1 (/vendor/bin/modprobe -a -d /vendor/lib/modules wl18xx.ko wlcore.ko wlcore_sdio.ko scsi_mod.ko usb-storage.ko sd_mod.ko dra7-evm-encoder-tpd12s01s [ 6.820615] vpe 489d0000.vpe: Device registered as /dev/video0
am57xevm:/ # dmesg | grep ov1063x
--- no output----
am57xevm:/ # dmesg | grep vip
----- no output -----
ov10635 is driver responsible for my camera, I have confirmed this from results from Linux PSDK.
Thanks & Regards
Devashish
