Problem in using Li-Vid365 input board.

Various kinds of video processing systems

Problem in using Li-Vid365 input board.

Postby aziz » Fri Nov 19, 2010 2:06 pm

[Pascal's comment: this topic has been split from a previous subject (see "Booting Leopard365 board using SD card")]

Hi Pascal,

I will do the same in coming few days.

I have got a Composite video input board LI-VI365. I connected it and soldered R196 and R197 resistor as mentioned at many places but still v4l2 src is not working. Do I need to add/change anything to make this work? Can dvsdk_3_10_00_19 be the issue?

Also have you tried connecting a USB modem to the leopard board?

Awaiting reply.

Thanks
Aziz
aziz
 
Posts: 8
Joined: Tue Nov 09, 2010 10:50 pm

Re: Booting Leopard365 board using SD card

Postby pascal » Fri Nov 19, 2010 9:51 pm

Hello Aziz!

First question, tell me about your configuration. Do you have a TV monitor on the composite output
(or DVI if you use this output)?
Now when you boot, do you see the RidgeRun logo on this monitor? If not, then check if the bootargs
are right (i.e. check that if you use a video composite monitor, your args mention "composite".

In my case, I spent a lot of time to make it boot, but once it did, it worked almost at once.

I have still no time to experiment with the new software (3_10_xxx), but I don't think it should change.

I forgot to mention: did you enable the LiVi365 video driver? If not, then you have to configure it.
In make config menus, go to the kernel, and look for the multimedia devices. I don't remember the
exact path in the menus, but you have to enable this driver. The default doesn't work. Once you
enable it, you will get the image probably right away. That was the only missing part in my case.

Pascal
pascal
Site Admin
 
Posts: 231
Joined: Sun Mar 04, 2007 11:47 am

Re: Booting Leopard365 board using SD card

Postby aziz » Sat Nov 20, 2010 12:10 am

Hi Pascal,

Thank you for your reply.

1. I am using DVI and while doing the config I have set the output at DVI and it reflected in the bootargs. But I am not able to see anything on the monitor. The bootargs it says vid0=off and vid1=off and when I check for the video devices it just shows /dev/video3 and /dev/video2. How to I switch on video0 and video1, can this be the root cause?

2. I have enabled the driver, have a look at the screenshot. I am enabling the chip which is present on LI-VI365 board.

3. Have copied my log, if you find anything different then please let me know.
Loading from NAND 256MiB 3,3V 8-bit, offset 0x400000
Image Name: "RR Compressed Linux Kernel"
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2128556 Bytes = 2 MB
Load Address: 81e00000
Entry Point: 81e00000
Automatic boot of image at addr 0x82000000 ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: "RR Compressed Linux Kernel"
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2128556 Bytes = 2 MB
Load Address: 81e00000
Entry Point: 81e00000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................................... done, bo.
Linux version 2.6.32-rc2-ridgerun (mmt1125@mmt1125-desktop) (gcc version 4.2.4) #1 PREEMPT Thu Nov 18 19:33:58 IST 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: DM365 Leopard
Memory policy: ECC disabled, Data cache writeback
DaVinci dm365_rev1.2 variant 0x8
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 13716
Kernel command line: davinci_enc_mngr.ch0_output=DVI davinci_enc_mngr.ch0_mode=720P-60 davinci_display.cont2_bufsize=6291456 vpfe_capture.cont_bufoffset=6291456 )
Unknown boot option `davinci_capture.device_type=4': ignoring
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 54MB = 54MB total
Memory: 50124KB available (3980K code, 385K data, 148K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:245
Console: colour dummy device 80x30
Calibrating delay loop... 147.86 BogoMIPS (lpj=739328)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
DaVinci: 8 gpio irqs
NET: Registered protocol family 16
davinci_serial_init:97: failed to get UART2 clock
bio: create slab <bio-0> at 0
DM365 IPIPE initialized in Continuous mode
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
vpss vpss: dm365_vpss vpss probed
vpss vpss: dm365_vpss vpss probe success
dm365_afew_hw_init
ch0 default output "COMPONENT", mode "720P-60"
VPBE Encoder Initialized
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
LogicPD encoder initialized
Leopard DVI encoder initialized
Switching to clocksource timer0_1
musb_hdrc: version 6.0, cppi-dma, host, debug=0
musb_hdrc: USB Host mode controller at fec64000 using DMA, IRQ 12
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 98
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
davincifb davincifb.0: dm_osd0_fb: 1280x720x16@0,0 with framebuffer size 1800KB
davincifb davincifb.0: dm_osd1_fb: 1280x720x4@0,0 with framebuffer size 1800KB
DM365 IPIPEIF probed
imp serializer initialized
davinci_previewer initialized
davinci_resizer initialized
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
console [ttyS0] enabled
brd: module loaded
console [netcon0] enabled
netconsole: network logging started
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbtest
i2c /dev entries driver
Linux video capture interface: v2.00
ths7303 1-002c: chip found @ 0x58 (DaVinci I2C adapter)
vpfe_init
vpfe-capture: vpss clock vpss_master enabled
vpfe-capture vpfe-capture: v4l2 device registered
vpfe-capture vpfe-capture: video device registered
Leopard: switch to HD imager-MT9P031 video input
mt9p031 1-0048: No MT9P031 chip detected, register read ffffff87
vpfe-capture vpfe-capture: v4l2 sub device mt9p031 register fails
No sub devices registered
vpfe-capture: vpfe capture clocks disabled
vpfe_register_ccdc_device: DM365 ISIF
DM365 ISIF is registered with vpfe.
af major#: 252, minor# 0
AF Driver initialized
aew major#: 251, minor# 0
AEW Driver initialized
Trying to register davinci display video device.
layer=c2141800,layer->video_dev=c2141970
Trying to register davinci display video device.
layer=c2141c00,layer->video_dev=c2141d70
davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
watchdog watchdog: heartbeat 60 sec
davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
No device for DAI tlv320aic3x
No device for DAI davinci-i2s
asoc: tlv320aic3x <-> davinci-i2s mapping ok
ALSA device list:
#0: DaVinci EVM (tlv320aic3x)
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
Clocks: disable unused mmcsd1
Clocks: disable unused spi0
Clocks: disable unused spi1
Clocks: disable unused spi2
Clocks: disable unused spi3
Clocks: disable unused spi4
Clocks: disable unused aemif
Clocks: disable unused pwm0
Clocks: disable unused pwm1
Clocks: disable unused pwm2
Clocks: disable unused pwm3
Clocks: disable unused timer1
Clocks: disable unused timer3
Clocks: disable unused emac
Clocks: disable unused voice_codec
Clocks: disable unused rto
Clocks: disable unused mjcp
davinci_emac_probe: using random MAC addr: 46:fc:86:65:3d:56
emac-mii: probed
Waiting 2sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address 8e73
mmcblk0: mmc0:8e73 SD02G 1.84 GiB
mmcblk0: p1 p2
kjournald starting. Commit interval 5 seconds
EXT3 FS on mmcblk0p1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with writeback data mode.
VFS: Mounted root (ext3 filesystem) on device 179:1.
Freeing init memory: 148K
init started: BusyBox v1.14.2 (2010-11-18 19:37:59 IST)
starting pid 979, tty '': '/etc/rcS'
Starting System
done.

Awaiting reply.

Thanks
Aziz
Attachments
make config driver snapshot.png
make config driver snapshot.png (146.07 KiB) Viewed 1766 times
aziz
 
Posts: 8
Joined: Tue Nov 09, 2010 10:50 pm

Re: Problem in using Li-Vid365 input board.

Postby pascal » Sun Nov 21, 2010 11:42 am

Hello Aziz!

So you don't have output at the monitor, but does it boot normally? I mean, do you
reach the Ridgerun logo on the text terminal? Apparently the log ends normally.

If it ends normally, then try to go to /examples and launch your video application.
If there are errors messages, it will give you some hints about what to do.

Beside this, I cannot be absolutely sure of what you should observe since we don't
have exactly the same environment.

Pascal
pascal
Site Admin
 
Posts: 231
Joined: Sun Mar 04, 2007 11:47 am


Return to Video processing

Who is online

Users browsing this forum: No registered users and 1 guest

cron