2008-06-18 08:29:00 BF561 EZ-KIT Lite (A-V & USB-LAN EZ-Extender), problems with blackfin_cam-driver
Thomas Langås (NORWAY)
Message: 57521
I'm using this setup:
* BF561 EZ-Kit Lite
* A-V EZ-Extender
* USB-LAN Ez-extender
* Micron MT9T001 Head Board connectex to the A-V EZ-extender
I've written my own MT9T001-driver based on the existing drivers under the
blackfin_cam-framework.
I'm trying to use ffmpeg to grab some frames from the camera, and I'm having
problems with receiving data (at all). I can read / write to the i2c-bus
(with minor errors coming and going), but no data from PPI it seems.
Any pointers? I've read the EE-258-note, but I don't fully understand
the part about switches (I don't understand the notations used for
switch-settings when it's talking about "SW2: 6 > off", for instance).
Any help would be greatly appreciated!
DEBUG-log:
bcap_open called
bcap_open:
bcap open setting PPI done
i2c-adapter i2c-0: master_xfer[0] W, addr=0x5d, len=3
i2c-adapter i2c-0: sendbytes: error - bailout.
i2c-adapter i2c-0: master_xfer[0] W, addr=0x5d, len=3
setting PPI to 2048x1536
specified video device opened sucessfullly
VIDIOCGCAP ioctl called
setting 'type of interface' to 0x00000101
setting 'name' to Blackfin CMOS Camera
setting 'channels' to 1
setting 'audios' to 0
setting 'maxwidth' to 2048
setting 'maxheight' to 1536
setting 'minwidth' to 80
setting 'minheight' to 60
VIDIOCGAUDIO called
device does not support audio
VIDIOCSAUDIO called
device does not support audio
VIDIOCGPICT called
VIDIOCSPICT called
not a valid depth (12)
VIDIOCSPICT called
not a valid depth (16)
VIDIOCSPICT called
not a valid depth (16)
VIDIOCSPICT called
not a valid depth (16)
VIDIOCSPICT called
not a valid depth (24)
VIDIOCSPICT called
not a valid depth (16)
VIDIOCSPICT called
VIDIOCGMBUF called (16928209)
capture 3145728 byte, 2048x1536 (WxH) frame
bcap_mmap: vm mapped to [0x00001000-0x00301000]
VIDIOCMCAPTURE(0) called (16928213)
i2c-adapter i2c-0: master_xfer[0] W, addr=0x5d, len=3
i2c-adapter i2c-0: sendbytes: error - bailout.
i2c-adapter i2c-0: master_xfer[0] W, addr=0x5d, len=3
setting PPI to 640x480
capture 307200 byte, 640x480 (WxH) frame
grabbing frame 0 [0x00001000]
bcap_ppi2dma: reading 307200 bytes (640x480) into [0x00001000]
bcap_ppi2dma: done read in 307200 bytes for [0x00001000-0x0004c000]
VIDIOCMCAPTURE(1) called (16928225)
capture 307200 byte, 640x480 (WxH) frame
PPI busy with [0x00001000] - ISR will capture to [0x03c01000] later
VIDIOCSYNC(0) called (16928265)
--
Thomas
QuoteReplyEditDelete
2008-06-18 08:44:47 Re: BF561 EZ-KIT Lite (A-V & USB-LAN EZ-Extender), problems with blackfin_cam-driver
Mike Frysinger (UNITED STATES)
Message: 57522
your board has switches. they have labels (like SW2). most switches are in sets and have individual numbers (like 6).
QuoteReplyEditDelete
2008-06-18 17:56:53 Re: BF561 EZ-KIT Lite (A-V & USB-LAN EZ-Extender), problems with blackfin_cam-driver
Thomas Langås (NORWAY)
Message: 57538
Yes, I know that, but I don't see what he mean with "6 > off". In one of the other cases he says "1 > off, 2 = off" (when he's talking about SW3, the boot-mode switch). So, when he says 2=off, I get what he wants, but it's the "X > off" that I don't get.
Also, I've tried reading the manuals for the cards, setting up the switches and jumpers the way I think they should, but it's obviously not correct, since there seems to be some issues with the driver being able to read anything from the PPI-bus. So, any pointers on what/where to look or scope would be appreciated. Also, should I send in the mt9t001-driver for you to include in the tree?
--
Thomas
QuoteReplyEditDelete
2008-06-18 20:48:35 Re: BF561 EZ-KIT Lite (A-V & USB-LAN EZ-Extender), problems with blackfin_cam-driver
Mike Frysinger (UNITED STATES)
Message: 57541
i dont think there's any difference between "6 > off" and "6 = off". but ive never read said app note because we dont support said addon board.