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.
Ashwimi,
The problem may be related to kernel version. I believe this demo driver was based on an earlier kernel version. Please look at readme file which lists kernel version# applicable to this driver. Please contact third part (3P) Leopard Imaging regarding any problems with LI-3MO2CM device driver with OMAP35xx. They are familiar with camera interface on OMAP35xx and also the ones who developed this demo driver in question.
Leon Luo is Leopard Imaging Conact...His email is leonl@leopardimaging.com
Stephen,
You should also contact Leopard Imaging regarding device driver availability.
@ Stephen Zhang
You can contact the Leon Luo of Leopard Imaging for LI-3M02Cm device driver. I got from him only. His e-mail id is there in the James's reply of the same post.
Regards,
Hi Ashwini,
Sorry for delayed response, somehow I did not receive this forum post to my mail-box before.
If I understand correctly, the patch from leopard which you are referring to is applicable for older revision of EVM's (<=Rev D). If you have EVM revision greater than Rev-E then the patch won't work for you.
And as part of camera sensor support we have successfully supported MT9T111 (3M) and MT9V113 (VGA) for BeagleBoard-XM with Leopard camera module LI-LBCM3M1, you can refer to the code from
http://gitorious.org/beagleboard-validation/linux/commits/beaglebardXM-camwork
As far as driver for MT9T111 is concerned I think it should be more or less be the same, the only thing which is going to change is EVM init code. As far as support for EVM is concerned, I have received Camera module part (LI-LBCM3M1) recently and I am planning to add MT9T111 sensor support on top of OMAP3530EVM, I will keep you posted on this.
Thanks,
Vaibhav
Thanks Vaibhav,
My OMAP3530 EVM revision is Rev-G, and I am using LI-3M02CM camera module with this.
Plz suggest some solution for this.
Regards,
Ashwini
Aswini,
Unfortunately support for LI-3M02CM camera module is not available currently in PSP release which I will be adding soon. We are currently working on new camera framework based on Media-Controller so as part of that I am planning to add support for this sensor module.
Have you tried porting existing code to Rev-G EVM, it should be pretty easy to do that?
Thanks,
Vaibhav
Hi Vaibhav,
could you maybe point to the development branch on arago you may be using for this, probably inside of the ti-psp-omap git tree?
Thanks,
--Gunter
Hi vibhav,
I tried to add camera Module with linux kernel 2.6.29, I patchd it and rebuild the kernel successfully. On porting on EVM, it suppose to generate video0 node in /dev directory for camera sensor, which is not generated.
Regards,
Ashwini
Hello,
While kernel booting the following error log is displayed,
<3>mt9t111 2-003c: Unable to detect mt9t111 sensor
mt9t111 2-003c: Unable to detect mt9t111 sensor
I guess that chip-id missmatch is happening. How do i check whether the controller id set and the id_value which driver is expecting are matching.
Thanks,
Ashwini
Ashwini,
This is indeed I2C address mismatch, this can only be happen -
- If your I2C bus is not clean. This could be due to wrong pad configuration.
- I2C bus is not enabled cleanly, there is one translator sitting in between which you need to enable.
By the way, which source code are you using? I have one baseline which is working on OMAP3EVM (see link below), but has some color issue, you may want to start from there
Thanks,
Vaibhav
Thanks
I have attached my driver code here, i am using OMAP3530 EVM Rev G, my camera is connected to I2C2bus.
I am getting error in mt9t111_detect function, i guess it is reading wrong register.
Kindly suggest what do i do to solve this.
Regards,
Ashwini
Hi,
I downloaded files from :
http://arago-project.org/git/people/vaibhav/ti-psp-omap-video.git?p=people/vaibhav/ti-psp-omap-video.git;a=commit;h=63125f9bc9ebbd9d1a6982f5eba3542c20bdf608
and tried with PSP versions 11 as well as 9, and both gave me Kconfig error.
Which version of PSP i should have to use files directly.
Regards,
Ashwini,
You are trying to get LI3M02 daughter card to work with your Rev G OMAP3 EVM, correct? You have a couple of options:
(a) Port the LI patch which was developed for Rev D EVM. As Vaibhav mentioned this will involve changes in the init source.
(b) Use the initial friendly drop provided in the git tree (link provided by Vaibhav). This is based on 2.6.35-rc5 kernel and has been tested with the same daughter card that you are working on. These source files will not work directly with the previous versions of kernel as it is based on a new framework.
Regards, Punya
---------------------------------------------------------------------------------------------------------------------
Please click the Verify Answer button on this post if it answers your question.
---------------------------------------------------------------------------------------------------------------------
Hi Ashwini,
What is the end goal here? If you want to get something from LI sensor on your display and won't care about the PSP package then you can get the working code which we have tested OMAP3EVM (Rev-G) version of boards.
2084.omap3_evm-cam_defconfig.txt
This should create /dev/videoX (0-to-8) device nodes.
Thanks,
Vaibhav
Thanks for reply,
My final goal is to make on-board camera to work and display video on screen. For the same while rebuilding uImage, during menuconfig i have selected system_type as "OMAP 3530 EVM Expansion slot/on-board Mass Market Daughter Card board support"
I am not interested in daughter card rather interested in using on-board camera, which will help us as we are making similar custom board.
PSP version is not an issue to me. I shall try out suggested solutions and get back.
Thanks and Regards,
Ashwini
Hi Vaibhav,
I tested the same LI sensor on OMAP3EVM (Rev-G) version of boards. The source code downloaded from http://arago-project.org/git/people/?p=vaibhav/ti-psp-omap-video.git;a=shortlog;h=refs/heads/omap3cam-mc-devel . Config is 2084.omap3_5F00_evm_2D00_cam_5F00_defconfig.txt.
But camera can't work. The error message is below.
mt9t111 2-003c: Unable to detectmt9t111sensor
isp_register_subdev_group: Unable to register subdev mt9t111
And kernel didn't create /dev/videoX device.
Can you give me some suggestion?
Thanks,
Hank
Hi Hank,
The obvious reason is, the repository you are referring to is not supporting MT9T111 sensor. I have only supported and validated MT9V113 sensor on it. If you refer to file board-omap3evm-camera.c, you will only see support for MT9V113 sensor available there.
You have to have MT9T11q sensor ported to Media-controller framework and the board file board-omap3evm-camera.c file should be enabling interface for this sensor.
Thanks,
Vaibhav
Hi Vaibhav,
But I saw the file board-omap3evm-camera.c is supporting MT9T111 sensor.
I used the branch "omap3cam-mc-devel" in source code.
And attached file is board-omap3evm-camera.c
Does this source code not support MT9t111 sensor?
Thanks,
Hank,
Sorry for the confusion, actually I was referring to BeagleXM in last reply by mistake.
Yes MT9T111 sensor is working with the "omap3cam-mc-devel" branch (in VGA mode), and I believe it should been working, i suggest checking following options -
- I2C2 pad configuration?
- Can you please probe the cam_mclk clock which is going to sensor?
- I had seen similar issue with BeagleXM, and I fixed it in u-boot, you can try similar fix for OMAP3EVM (attached here)
Note: Please remove the .txt extension from the patch file.
Thanks,
Vaibhav
Hi Vaibhav,
What is I2C2 pad configuration?
I probed the I2C2_SCL and I2C2_SDA , but only High and no change.
I probed the cam_mclk , it didn't have clock out.
I put the LI-3M02CM camera module on J34 connector , and chosen LI-3M02CM on JP1.
Does the OMAPEVM board need to set other configuration?
Thanks,
Hank