From: rklosinski <ri...@kl...> - 2012-11-09 08:21:45
|
Im using yocto, and would like to add support for the tvp514x. I assume make menuconfig would be use, but where are the kernel files. -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Nick W. <nic...@gm...> - 2012-11-09 16:59:29
|
Also the TVP515x! On Fri, Nov 9, 2012 at 12:21 AM, rklosinski <ri...@kl...> wrote: > Im using yocto, and would like to add support for the tvp514x. I assume > make > menuconfig would be use, but where are the kernel files. > > > > -- > View this message in context: > http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Richard K. <ri...@kl...> - 2012-11-09 17:02:04
|
After looking at the both, the tvp5151 is much easier to interface, so Im changing to this part (although it only has an 9-bit dac). ________________________________ From: Nick Wernicke [nic...@gm...] Sent: Friday, November 09, 2012 8:59 AM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] adding support for tvp514x Also the TVP515x! On Fri, Nov 9, 2012 at 12:21 AM, rklosinski <ri...@kl...<mailto:ri...@kl...>> wrote: Im using yocto, and would like to add support for the tvp514x. I assume make menuconfig would be use, but where are the kernel files. -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001.html Sent from the Gumstix mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ gumstix-users mailing list gum...@li...<mailto:gum...@li...> https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Nick W. <nic...@gm...> - 2012-11-21 00:52:12
|
I have: -added the tvp514x driver with menuconfig -installed media-ctl by adding it to my gumstix-dsp-image recipe -checked in uboot to make sure that the tvp5147 is on i2c bus 2 (2->3 in linux) and at address 5C -inserted the tvp514x driver to the kernel using insmod -checked that the driver is loaded using lsmod. It is. But there is nothing in /dev/ that would lead me to think the driver is actually set up and able to be linked to a video source. I would assume that there would be some clue in media-ctl -p, but I don't see it. I don't know if there is a log, or some other way to see if the tvp514x driver is correctly installed and working (I think the way I installed it, it just takes up memory). I think this is the question I need to answer: How do I correctly install the tvp514x driver (insmod?), and then tell media-ctl that it needs to link the tvp514x driver to /dev/videoX? On Tue, Nov 20, 2012 at 2:13 PM, rklosinski <ri...@kl...> wrote: > Thanks for the response, I'll try this soon!!! > FYI, for those needing media-ctl, I was able to get it my adding it to my > recipe (i called my gumstix-dsp-image). > > > > > > -- > View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966113.html > Sent from the Gumstix mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: rklosinski <ri...@kl...> - 2012-11-21 00:55:00
|
Have you done an lsmod to see if it shows up? -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966115.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Nick W. <nic...@gm...> - 2012-11-21 02:27:05
|
Yes, it shows up right near the top. What I can't tell is if the driver is able to do anything other than take up space in memory. I am bitbaking i2c-tools right now. When it finishes, I can probe the i2c bus (i think it is bus 3, 5C) and see if the data matches the default values for the tvp5147 in the datasheet. That will at least confirm that the econ tvp514x board and ribbon cable is installed and working. I will post results if they are positive... In the meantime, I'm not entirely sure that I installed the driver correctly, or if I am suppsed to make a script or something to install it at boot. On Tue, Nov 20, 2012 at 4:54 PM, rklosinski <ri...@kl...> wrote: > Have you done an lsmod to see if it shows up? > > > > -- > View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966115.html > Sent from the Gumstix mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: rklosinski <ri...@kl...> - 2012-11-10 13:40:37
|
I got one step closer to getting the drivers generated for tvp514x and tvp5150. I executed bitbake -c menuconfig linuz-sakoman and selected the drivers. It was that easy, EXCEPT it built everything based upon linux-sakoman-3.5 NOT 3.2 as the dsp drivers are. So I either need the dsp drivers in 3.5 land or be able to specify which kernel is build when I use linux-sakoman. I cant figure it out since a linux-sakoman.bb file does not exist (although linux-sakoman-3.2.bb and linux-sakoman-3.5.bb exist). Help please..... -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966015.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: rklosinski <ri...@kl...> - 2012-11-10 17:01:59
|
correction.... I assume I needed 3.2 since my previous attempt generated it. Totally scratching the initial jumpnow method and following the one published on sleepyrobot yielded working gstreamer core. The bitbake -c menuconfig linux-sakoman (then followed by bitbake linux-sakoman) allowed me to get the tvp514x and tvp5150 drivers in the modules file which were copied onto the rootfs. I've yet to test these drivers. So far, streaming from videotestsrc works (gst-launch videotestsrc ! video/x-raw-yuv,width=320,height=240 ! TIVidenc1 codecName=h264enc engineName=codecServer ! rtph264pay pt=96 ! udpsink host=192.168.0.203 port=4000) Although the caspa was connected, and was identifed during boot. I've yet to figure out how to stream from it. Ive tried: gst-launch -v v4l2src ! video/x-raw-yuv,width=320,height=240 ! TIVidenc1 codecName=h264enc engineName=codecServer ! rtph264pay pt=96 ! udpsink host=192.168.0.203 port=4000 and it failed stating /dev/video0 is not a capture device. Other things that needed fixing: I needed to do the following for uboot: ...interrupt the boot nand erase 240000 20000 reset ...interrupt the boot setenv mmcargs setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} mem=96M@0x80000000 mem=128M@0x88000000 root=${mmcroot} rootfstype=${mmcrootfstype} setenv bootsdelay 1 (my personal pref) run mmcargs saveenv reset Im sure there is a more elegant way of setting the memory region (I think jumpnow had a better way) but this worked for now. Im still trying to get the caspa work.... -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966017.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Nick W. <nic...@gm...> - 2012-11-11 22:25:09
|
I haven't done menuconfig in yocto before. When I run bitbake -c menuconfig linux_sakoman it just opens a window for a brief second, then closes the window and says task do_menuconfig: Succeeded. Is there something else I need to do in the environment or something? I'm using Ubuntu 12.10. On Sat, Nov 10, 2012 at 8:20 AM, rklosinski <ri...@kl...> wrote: > correction.... I assume I needed 3.2 since my previous attempt generated > it. > Totally scratching the initial jumpnow method and following the one > published on sleepyrobot yielded working gstreamer core. > > The bitbake -c menuconfig linux-sakoman (then followed by bitbake > linux-sakoman) allowed me to get the tvp514x and tvp5150 drivers in the > modules file which were copied onto the rootfs. I've yet to test these > drivers. > > So far, streaming from videotestsrc works (gst-launch videotestsrc ! > video/x-raw-yuv,width=320,height=240 ! TIVidenc1 codecName=h264enc > engineName=codecServer ! rtph264pay pt=96 ! udpsink host=192.168.0.203 > port=4000) > > Although the caspa was connected, and was identifed during boot. I've yet > to > figure out how to stream from it. Ive tried: > gst-launch -v v4l2src ! video/x-raw-yuv,width=320,height=240 ! TIVidenc1 > codecName=h264enc engineName=codecServer ! rtph264pay pt=96 ! udpsink > host=192.168.0.203 port=4000 > > and it failed stating /dev/video0 is not a capture device. > > Other things that needed fixing: > I needed to do the following for uboot: > ...interrupt the boot > nand erase 240000 20000 > reset > ...interrupt the boot > setenv mmcargs setenv bootargs console=${console} mpurate=${mpurate} > vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y > omapdss.def_disp=${defaultdisplay} mem=96M@0x80000000 mem=128M@0x88000000 > root=${mmcroot} rootfstype=${mmcrootfstype} > > setenv bootsdelay 1 (my personal pref) > run mmcargs > saveenv > reset > > Im sure there is a more elegant way of setting the memory region (I think > jumpnow had a better way) but this worked for now. > > Im still trying to get the caspa work.... > > > > > > > -- > View this message in context: > http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966017.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Nick W. <nic...@gm...> - 2012-11-21 18:42:55
|
So, the website that has the i2c-tools source is broken. No way to debug i2c. I do have the driver module loaded: root@overo:~# lsmod Module Size Used by tvp514x 8613 0 sdmak 4080 0 lpm_omap3530 6797 0 dsplinkk 131408 1 lpm_omap3530 cmemk 22005 0 libertas_sdio 16396 0 libertas 100032 1 libertas_sdio mt9v032 7237 4294967295 omap3_isp 131955 0 cfg80211 170751 1 libertas v4l2_common 8933 3 tvp514x,mt9v032,omap3_isp lib80211 5134 1 libertas firmware_class 6904 2 libertas_sdio,libertas videodev 99128 4 tvp514x,mt9v032,omap3_isp,v4l2_common ads7846 10488 0 media 12714 3 mt9v032,omap3_isp,videodev rfcomm 56119 0 hidp 16251 0 bluetooth 258745 4 rfcomm,hidp rfkill 17524 2 cfg80211,bluetooth ipv6 249350 12 I need to somehow link that driver with the video for linux devices in /dev root@overo:~# ls /dev | grep video video0 video1 video2 video3 video4 video5 video6 I understand that I'm supposed to use media-ctl, but I don't see a video entity for the tvp5147... root@overo:~# media-ctl -p | grep entity - entity 1: OMAP3 ISP CCP2 (2 pads, 2 links) - entity 2: OMAP3 ISP CCP2 input (1 pad, 1 link) - entity 3: OMAP3 ISP CSI2a (2 pads, 2 links) - entity 4: OMAP3 ISP CSI2a output (1 pad, 1 link) - entity 5: OMAP3 ISP CCDC (3 pads, 8 links) - entity 6: OMAP3 ISP CCDC output (1 pad, 1 link) - entity 7: OMAP3 ISP preview (2 pads, 4 links) - entity 8: OMAP3 ISP preview input (1 pad, 1 link) - entity 9: OMAP3 ISP preview output (1 pad, 1 link) - entity 10: OMAP3 ISP resizer (2 pads, 4 links) - entity 11: OMAP3 ISP resizer input (1 pad, 1 link) - entity 12: OMAP3 ISP resizer output (1 pad, 1 link) - entity 13: OMAP3 ISP AEWB (1 pad, 1 link) - entity 14: OMAP3 ISP AF (1 pad, 1 link) - entity 15: OMAP3 ISP histogram (1 pad, 1 link) On Tue, Nov 20, 2012 at 6:26 PM, Nick Wernicke <nic...@gm...> wrote: > Yes, it shows up right near the top. > > What I can't tell is if the driver is able to do anything other than > take up space in memory. I am bitbaking i2c-tools right now. When it > finishes, I can probe the i2c bus (i think it is bus 3, 5C) and see if > the data matches the default values for the tvp5147 in the datasheet. > That will at least confirm that the econ tvp514x board and ribbon > cable is installed and working. I will post results if they are > positive... In the meantime, I'm not entirely sure that I installed > the driver correctly, or if I am suppsed to make a script or something > to install it at boot. > > > On Tue, Nov 20, 2012 at 4:54 PM, rklosinski <ri...@kl...> wrote: >> Have you done an lsmod to see if it shows up? >> >> >> >> -- >> View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966115.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: rklosinski <ri...@kl...> - 2012-11-21 18:52:21
|
Did you follow Chris's instructions? -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966124.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Nick W. <nic...@gm...> - 2012-11-11 22:41:16
|
Nevermind... found it. I had to install libncurses5-dev. On Sun, Nov 11, 2012 at 2:25 PM, Nick Wernicke <nic...@gm...>wrote: > I haven't done menuconfig in yocto before. When I run > > bitbake -c menuconfig linux_sakoman > > it just opens a window for a brief second, then closes the window and says > task do_menuconfig: Succeeded. Is there something else I need to do in the > environment or something? I'm using Ubuntu 12.10. > > > On Sat, Nov 10, 2012 at 8:20 AM, rklosinski <ri...@kl...> wrote: > >> correction.... I assume I needed 3.2 since my previous attempt generated >> it. >> Totally scratching the initial jumpnow method and following the one >> published on sleepyrobot yielded working gstreamer core. >> >> The bitbake -c menuconfig linux-sakoman (then followed by bitbake >> linux-sakoman) allowed me to get the tvp514x and tvp5150 drivers in the >> modules file which were copied onto the rootfs. I've yet to test these >> drivers. >> >> So far, streaming from videotestsrc works (gst-launch videotestsrc ! >> video/x-raw-yuv,width=320,height=240 ! TIVidenc1 codecName=h264enc >> engineName=codecServer ! rtph264pay pt=96 ! udpsink host=192.168.0.203 >> port=4000) >> >> Although the caspa was connected, and was identifed during boot. I've yet >> to >> figure out how to stream from it. Ive tried: >> gst-launch -v v4l2src ! video/x-raw-yuv,width=320,height=240 ! TIVidenc1 >> codecName=h264enc engineName=codecServer ! rtph264pay pt=96 ! udpsink >> host=192.168.0.203 port=4000 >> >> and it failed stating /dev/video0 is not a capture device. >> >> Other things that needed fixing: >> I needed to do the following for uboot: >> ...interrupt the boot >> nand erase 240000 20000 >> reset >> ...interrupt the boot >> setenv mmcargs setenv bootargs console=${console} mpurate=${mpurate} >> vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y >> omapdss.def_disp=${defaultdisplay} mem=96M@0x80000000 mem=128M@0x88000000 >> root=${mmcroot} rootfstype=${mmcrootfstype} >> >> setenv bootsdelay 1 (my personal pref) >> run mmcargs >> saveenv >> reset >> >> Im sure there is a more elegant way of setting the memory region (I think >> jumpnow had a better way) but this worked for now. >> >> Im still trying to get the caspa work.... >> >> >> >> >> >> >> -- >> View this message in context: >> http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966017.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > |
From: Richard K. <ri...@kl...> - 2012-11-11 23:22:52
|
Great. I knew it would be something like that. Do you (or anyone for that matter) have any idea how to set up a stream from the caspa. I see it identified during boot, yet if I try gst-launch v4l2src, it returns with /dev/video0 is not a capture device. So I tried gst-launch v4l2src device=/dev/video1 up to video 6, and no luck. Rich From: Nick Wernicke [mailto:nic...@gm...] Sent: Sunday, November 11, 2012 2:41 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] adding support for tvp514x Nevermind... found it. I had to install libncurses5-dev. On Sun, Nov 11, 2012 at 2:25 PM, Nick Wernicke <nic...@gm...<mailto:nic...@gm...>> wrote: I haven't done menuconfig in yocto before. When I run bitbake -c menuconfig linux_sakoman it just opens a window for a brief second, then closes the window and says task do_menuconfig: Succeeded. Is there something else I need to do in the environment or something? I'm using Ubuntu 12.10. On Sat, Nov 10, 2012 at 8:20 AM, rklosinski <ri...@kl...<mailto:ri...@kl...>> wrote: correction.... I assume I needed 3.2 since my previous attempt generated it. Totally scratching the initial jumpnow method and following the one published on sleepyrobot yielded working gstreamer core. The bitbake -c menuconfig linux-sakoman (then followed by bitbake linux-sakoman) allowed me to get the tvp514x and tvp5150 drivers in the modules file which were copied onto the rootfs. I've yet to test these drivers. So far, streaming from videotestsrc works (gst-launch videotestsrc ! video/x-raw-yuv,width=320,height=240 ! TIVidenc1 codecName=h264enc engineName=codecServer ! rtph264pay pt=96 ! udpsink host=192.168.0.203 port=4000) Although the caspa was connected, and was identifed during boot. I've yet to figure out how to stream from it. Ive tried: gst-launch -v v4l2src ! video/x-raw-yuv,width=320,height=240 ! TIVidenc1 codecName=h264enc engineName=codecServer ! rtph264pay pt=96 ! udpsink host=192.168.0.203 port=4000 and it failed stating /dev/video0 is not a capture device. Other things that needed fixing: I needed to do the following for uboot: ...interrupt the boot nand erase 240000 20000 reset ...interrupt the boot setenv mmcargs setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} mem=96M@0x80000000 mem=128M@0x88000000 root=${mmcroot} rootfstype=${mmcrootfstype} setenv bootsdelay 1 (my personal pref) run mmcargs saveenv reset Im sure there is a more elegant way of setting the memory region (I think jumpnow had a better way) but this worked for now. Im still trying to get the caspa work.... -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966017.html Sent from the Gumstix mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ gumstix-users mailing list gum...@li...<mailto:gum...@li...> https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Nick W. <nic...@gm...> - 2012-11-21 19:12:02
|
Here is the results of my copying Chris: root@overo:~# media-ctl -l '"tvp514x 3-005c":0->"OMAP3 ISP CCDC":0[1]' Unable to parse link: Invalid argument (22) root@overo:~# media-ctl -l '"tvp5147 3-005c":0->"OMAP3 ISP CCDC":0[1]' Unable to parse link: Invalid argument (22) I don't understand how the "[video_decoder_chip] [bus]-[address]" argument is given meaning. Like, Chris typed in "tvp5150 3-005c" and the computer understands what that means. My computer says "Invalid Argument", so it doesn't understand what "tvp5147 3-005c" means. How do I give that argument meaning, or how do I find the list of arguments, in case I am typing it incorrectly? Is there was a file that had a list of attached video decoders? On Wed, Nov 21, 2012 at 10:52 AM, rklosinski <ri...@kl...> wrote: > Did you follow Chris's instructions? > > > > -- > View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966124.html > Sent from the Gumstix mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: rklosinski <ri...@kl...> - 2012-11-21 19:16:40
|
I do not understand the cryptic commands sent using media-ctl. I found this page: http://wiki.openpilot.org/display/Doc/James%27+Notes While its regarding the caspa, it might shed some light on the format of the commands sent. -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966126.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Nick W. <nic...@gm...> - 2012-11-21 19:46:58
|
I *think* have a handle on what the commands mean. I will write it as I understand it and maybe I will shed some light on my deficiency in understanding why my overo and tvp5147 won't work. The tvp5147 is controlled through the i2c bus. It is connected the the DM3730 on i2c bus #3 (bus 3=bus 2 in uboot). It's address is 0x5c. It can communicate in u-boot through the i2c commands. The numbers read back from the chip starting at offset 0 are consistent with the numbers on page 30 of the datasheet. Overo # i2c dev 2 Overo # i2c md 0x5c 0 0000: 00 0f 00 00 23 10 00 00 00 80 80 80 00 00 0e 00 ....#........... So when we say # media-ctl -v -l '"mt9v032 3-005c":0->"OMAP3 ISP CCDC":0[1]' we are saying something like: make data in the memory space for the [mt9v032] driver, controlled by bus [3]-address [005c] go to the input pad memory space for the [OMAP3 ISP CCDC] driver. media-ctl -v -l '"OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]' I think this message makes data in the [OMAP3 ISP CCDC] input pad memory space get put into the output pad space, which is available to v4lsrc, which is used by gstreamer. media-ctl -v -f '"mt9v032 3-005c":0 [SGRBG10 752x480]' media-ctl -v -f '"OMAP3 ISP CCDC":1 [SGRBG10 752x480]' And these messages tell media-ctl to write in the memory for those drivers a variable saying what format the video is in. This information is probably made available to v4l and gstreamer so they can format the video. Now, how to get media-ctl to recognize that there is memory space reserved for the mt9v032 OR the tvp5147... I can't find anything that explains that. On Wed, Nov 21, 2012 at 11:16 AM, rklosinski <ri...@kl...> wrote: > I do not understand the cryptic commands sent using media-ctl. I found this > page: > > http://wiki.openpilot.org/display/Doc/James%27+Notes > > While its regarding the caspa, it might shed some light on the format of the > commands sent. > > > > -- > View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966126.html > Sent from the Gumstix mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Nick W. <nic...@gm...> - 2012-11-22 00:35:24
|
I got a step closer by changing the M next to the tvp5147 to a *. There is a tvp514x represented as well as a mt9v032 in these folders: root@overo:/# find / -name tvp514x /sys/bus/i2c/drivers/tvp514x /sys/module/tvp514x root@overo:/# find / -name mt9v032 /sys/bus/i2c/drivers/mt9v032 /sys/module/mt9v032 But there is no tvp514x in the loaded modules! root@overo:/# lsmod Module Size Used by sdmak 4076 0 lpm_omap3530 6797 0 dsplinkk 131408 1 lpm_omap3530 cmemk 22005 0 libertas_sdio 16396 0 libertas 100032 1 libertas_sdio cfg80211 170751 1 libertas mt9v032 7237 4294967295 <--- This is there, but no tvp514x! lib80211 5134 1 libertas firmware_class 6904 2 libertas_sdio,libertas omap3_isp 131955 0 ads7846 10488 0 rfcomm 56119 0 hidp 16251 0 bluetooth 258745 4 rfcomm,hidp rfkill 17524 2 cfg80211,bluetooth ipv6 249350 12 It has to have something to do with the fact that there is lines in dmesg related to the mt9v032, but not the tvp514x: root@overo:/# dmesg | grep mt9v [ 9.732421] mt9v032 3-005c: Probing MT9V032 at address 0x5c [ 9.745635] mt9v032 3-005c: MT9V032 not detected, wrong version 0x000f [ 9.753662] isp_register_subdev_group: Unable to register subdev mt9v032 root@overo:/# dmesg | grep tvp root@overo:/# The mt9v032 comes after the "starting udev" message. Should I research udev? Are they related? How do I get Linux to see the tvp514x when it boots up? On Wed, Nov 21, 2012 at 11:46 AM, Nick Wernicke <nic...@gm...> wrote: > I *think* have a handle on what the commands mean. I will write it as > I understand it and maybe I will shed some light on my deficiency in > understanding why my overo and tvp5147 won't work. > > The tvp5147 is controlled through the i2c bus. It is connected the > the DM3730 on i2c bus #3 (bus 3=bus 2 in uboot). It's address is > 0x5c. It can communicate in u-boot through the i2c commands. The > numbers read back from the chip starting at offset 0 are consistent > with the numbers on page 30 of the datasheet. > > Overo # i2c dev 2 > Overo # i2c md 0x5c 0 > 0000: 00 0f 00 00 23 10 00 00 00 80 80 80 00 00 0e 00 ....#........... > > So when we say # media-ctl -v -l '"mt9v032 3-005c":0->"OMAP3 ISP CCDC":0[1]' > > we are saying something like: > > make data in the memory space for the [mt9v032] driver, controlled by > bus [3]-address [005c] go to the input pad memory space for the > [OMAP3 ISP CCDC] driver. > > media-ctl -v -l '"OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]' > I think this message makes data in the [OMAP3 ISP CCDC] input pad > memory space get put into the output pad space, which is available to > v4lsrc, which is used by gstreamer. > > media-ctl -v -f '"mt9v032 3-005c":0 [SGRBG10 752x480]' > media-ctl -v -f '"OMAP3 ISP CCDC":1 [SGRBG10 752x480]' > And these messages tell media-ctl to write in the memory for those > drivers a variable saying what format the video is in. This > information is probably made available to v4l and gstreamer so they > can format the video. > > Now, how to get media-ctl to recognize that there is memory space > reserved for the mt9v032 OR the tvp5147... I can't find anything that > explains that. > > On Wed, Nov 21, 2012 at 11:16 AM, rklosinski <ri...@kl...> wrote: >> I do not understand the cryptic commands sent using media-ctl. I found this >> page: >> >> http://wiki.openpilot.org/display/Doc/James%27+Notes >> >> While its regarding the caspa, it might shed some light on the format of the >> commands sent. >> >> >> >> -- >> View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966126.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Renzo <ren...@gm...> - 2012-11-20 21:57:18
|
On 11 November 2012 23:20, Richard Klosinski <ri...@kl...> wrote: > Great. I knew it would be something like that. Do you (or anyone for > that matter) have any idea how to set up a stream from the caspa. I see > it identified during boot, yet if I try gst-launch v4l2src, it returns with > /dev/video0 is not a capture device. So I tried gst-launch v4l2src > device=/dev/video1 up to video 6, and no luck. > Exactly the same problem here.... Does anyone have ideas about where I should start from to sort this out? thanks -- Renzo |
From: Chris W. <whi...@gm...> - 2012-11-20 22:10:18
|
You likely need to use media-ctl utility to set things up. For instance, here is how I setup the tvp5151 on my board: media-ctl -r media-ctl -l '"tvp5150 3-005c":0->"OMAP3 ISP CCDC":0[1]' media-ctl -l '"OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]' media-ctl -f '"tvp5150 3-005c":0 [UYVY2X8 720x480]' media-ctl -f '"OMAP3 ISP CCDC":1 [UYVY2X8 720x480]' Then video is available from /dev/video2... With gstreamer, you would do something like: gst-launch v4l2src device=/dev/video2 ! fakesink -Chris On Tue, Nov 20, 2012 at 3:56 PM, Renzo <ren...@gm...> wrote: > > > > On 11 November 2012 23:20, Richard Klosinski <ri...@kl...> wrote: >> >> Great. I knew it would be something like that. Do you (or anyone for that matter) have any idea how to set up a stream from the caspa. I see it identified during boot, yet if I try gst-launch v4l2src, it returns with /dev/video0 is not a capture device. So I tried gst-launch v4l2src device=/dev/video1 up to video 6, and no luck. > > > Exactly the same problem here.... > > Does anyone have ideas about where I should start from to sort this out? > > thanks > > -- > Renzo > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: rklosinski <ri...@kl...> - 2012-11-20 22:13:39
|
Thanks for the response, I'll try this soon!!! FYI, for those needing media-ctl, I was able to get it my adding it to my recipe (i called my gumstix-dsp-image). -- View this message in context: http://gumstix.8.n6.nabble.com/adding-support-for-tvp514x-tp4966001p4966113.html Sent from the Gumstix mailing list archive at Nabble.com. |