[#4608] video0 is not created in /dev when using VS6524 video camera

Submitted By: Vivi Li

Open Date

2008-11-05 02:55:18 Close Date

2008-11-12 02:04:10

Priority:

Medium Assignee:

Michael Hennerich

Status:

Closed Fixed In Release:

N/A

Found In Release:

N/A Release:

Category:

N/A Board:

N/A

Processor:

N/A Silicon Revision:

Is this bug repeatable?:

Yes Resolution:

Not reproducible

Uboot version or rev.:

Toolchain version or rev.:

toolchain-2008_Oct_10

App binary format:

N/A

Summary: video0 is not created in /dev when using VS6524 video camera

Details:

After install related module of VS6524 video camera, video0 is not created in /dev directory.

Kernel and application config files are attached.

root:/> modprobe i2c-bfin-twi

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc01400

root:/> modprobe blackfin-cam

Linux video capture interface: v2.00

VS6524: i2c driver ready

root:/> lsmod

Module Size Used by

blackfin_cam 9644 0

vs6524 4064 1 blackfin_cam

videodev 27712 1 blackfin_cam

v4l1_compat 11396 1 videodev

i2c_bfin_twi 6048 0

i2c_core 14768 3 blackfin_cam,vs6524,i2c_bfin_twi

root:/> ffmpeg -f video4linux -r 10.0 -s 720x288 -i /dev/video0 -qscale 6 -f mjpeg

configuration: --prefix=/usr --source-path=/home/test/work/cruise/checkouts/uclinux-dist/lib/ffmpeg/build/../ffmpeg-svn-11114-

libavutil version: 49.5.0

libavcodec version: 51.48.0

libavformat version: 52.1.0

built on Nov 5 2008 12:51:37, gcc: 4.1.2 (ADI svn)

[video4linux @ 0x301030]/dev/video0: No such file or directory

/dev/video0: I/O error occured

Usually that means that input file is truncated and/or corrupted.

root:/> ls /dev/

console ptmx ram15 random

cpu_dma_latency pts ram2 rtc0

full ram0 ram3 tty

kmsg ram1 ram4 ttyBF0

log ram10 ram5 urandom

mem ram11 ram6 watchdog

network_latency ram12 ram7 zero

network_throughput ram13 ram8

null ram14 ram9

root:/> dmesg

Linux version 2.6.28-rc2-ADI-2009R1-pre-svn5576 (test@107-local) (gcc version 4.1.2 (ADI svn)) #164 Wed Nov 5 12:56:17 CST 2008

console [early_BFuart0] enabled

early printk enabled on early_BFuart0

Warning: limiting memory to 56MB due to hardware anomaly 05000263

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

fixedcode = 0x00000400-0x00000490

text = 0x00100000-0x0020a560

rodata = 0x0020a560-0x0025aed8

bss = 0x0025aee0-0x0026ae40

data = 0x0026ae40-0x0027a000

stack = 0x00278000-0x0027a000

init = 0x0027a000-0x00798000

available = 0x00798000-0x037ff000

DMA Zone = 0x03e00000-0x04000000

Hardware Trace Active and Enabled

Reset caused by Software reset

Compiled for ADSP-BF537 Rev 0.2

Blackfin Linux support by blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 100 MHz System Clock

boot memmap: 0000000000798000 - 00000000037ff000 (usable)

On node 0 totalpages: 14335

free_area_init_node: node 0, pgdat 002774e0, node_mem_map 0079d000

DMA zone: 112 pages used for memmap

DMA zone: 0 pages reserved

DMA zone: 14223 pages, LIFO batch:3

Normal zone: 0 pages used for memmap

Movable zone: 0 pages used for memmap

NOMPU: setting up cplb tables for global access

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists in Zone order, mobility grouping off. Total pages: 14223

Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart0,57600 console=tty0 console=ttyBF0,57600 ip=10.100.4.50:10.f

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 256 (order: 8, 1024 bytes)

console handover: boot [early_BFuart0] -> real [ttyBF0]

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Kernel managed physical pages: 14335

Memory available: 48984k/65536k RAM, (5240k init code, 1065k kernel code, 447k data, 2048k dma, 7752k reserved)

Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)

Security Framework initialized

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

Blackfin L1 Data A SRAM: 16 KB (15 KB free)

Blackfin L1 Data B SRAM: 16 KB (16 KB free)

Blackfin L1 Instruction SRAM: 48 KB (41 KB free)

net_namespace: 288 bytes

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

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

Setting up Blackfin MMR debugfs

msgmni has been set to 95

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART

brd: module loaded

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=19)@sclk=100MHz)

bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@7

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

TCP cubic registered

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting system clock to 1970-01-01 00:24:52 UTC (1492)

dma_alloc_init: dma_page @ 0x00d08000 - 512 pages at 0x03e00000

IP-Config: Complete:

device=eth0, addr=10.100.4.50, mask=255.255.255.0, gw=10.100.4.174,

host=bf537-stamp, domain=, nis-domain=(none),

bootserver=10.100.4.174, rootserver=10.100.4.174, rootpath=

Freeing unused kernel memory: 5240k freed

PHY: 0:01 - Link is Up - 100/Full

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc01400

Linux video capture interface: v2.00

VS6524: i2c driver ready

root:/>

Follow-ups

--- Michael Hennerich 2008-11-10 07:52:29

I’m pretty sure this is HW configuration bug.

Please describe the HW you are utilizing and the exact Add-On-Cards jumper

configurations.

I tested both sensors/drivers: VS6624, VS6524

Both are fully functional.

root:/> modprobe i2c-bfin-twi

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller,

regs_base@ffc01400

root:/> modprobe blackfin_cam

VS6524: detecting client on address 0x20

VS6524: Firmware Version 1.1

VS6524: Patch Version 0.0

VS6524: V4L driver Blackfin CMOS Camera now ready

VS6524: i2c driver ready

root:/>

root:/> modprobe i2c-bfin-twi

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller,

regs_base@ffc01400

root:/> modprobe blackfin_cam

VS6624: detecting client on address 0x20

VS6624: Firmware Version 0.12

VS6624: Patch Version 0.0

VS6624: V4L driver Blackfin CMOS Camera now ready

VS6624: i2c driver ready

root:/>

-Michael

--- Vivi Li 2008-11-12 02:04:10

I'm sorry it's my mistake. The board is 6624 while the driver is 6524.

It does work. So close this bug.

Thanks!

Files

Changes

Commits

Dependencies

Duplicates

Associations