Radium camera cape failed to capture frame

[Regina Choi]

I recently purchased Radium camera cape with image sensor MT9M114, and it came with Angstrom image with relevant driver. However, I would like the camera cape to work with Debian distro of 3.8.13-bone79.  Since for 3.8.13-bone79, the driver is by default set, ie. CONFIG_SOC_CAMERA_MT9M114=y

After I boot up BBB with my Debian distro + camera cape, it managed to power up the camera cape and the overlay is loaded successfully:

 2: 56:P---L BeagleBone 1.2MP CAMERA CAPE,00A0,RadiumBoards,BB-BONE-CAM-VVDN

And,

# v4l2-ctl --all           
Driver Info (not using libv4l2):
    Driver name   : cssp_camera
    Card type     : cssp_camera
    Bus info      : cssp_camera-000
    Driver version: 3.8.13
    Capabilities  : 0x05000001
        Video Capture
        Read/Write
        Streaming
Format Video Capture:
    Width/Height  : 1280/720
    Pixel Format  : 'YUYV'
    Field         : None
    Bytes per Line: 640
    Size Image    : 153600
    Colorspace    : JPEG (JFIF/ITU601)
Video input : 0 (Camera 0: ok)
Priority: 2


 Unfortunately, when I use try to capture image by:

fswebcam -d /dev/video0 -r 320x240 test.jpeg

--- Opening /dev/video0...
Trying source module v4l2...
/dev/video0 opened.
No input was specified, using the first.
--- Capturing frame...
Timed out waiting for frame!
No frame captured. 


Any idea to overcome the problem very much appreciated. 

[Regina Choi]

   In addition, the dmesg log after the command :

> [19248.404441] cssp-camera 18000000.camera: vidioc_querycap
> [19248.411325] cssp-camera 18000000.camera: vidioc_enum_input
> [19248.411396] cssp-camera 18000000.camera: vidioc_s_input
> [19248.411802] cssp-camera 18000000.camera: vidioc_enum_fmt_vid_cap index=0
> [19248.411849] cssp-camera 18000000.camera: vidioc_enum_fmt_vid_cap index=1
> [19248.412293] cssp-camera 18000000.camera: vidioc_enum_fmt_vid_cap index=2
> [19248.412343] cssp-camera 18000000.camera: vidioc_enum_fmt_vid_cap index=3
> [19248.412396] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.412433] cssp-camera 18000000.camera: Fourcc format (0x4745504a) invalid.
> [19248.429727] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.429778] cssp-camera 18000000.camera: Fourcc format (0x47504a4d) invalid.
> [19248.446089] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.446135] cssp-camera 18000000.camera: Fourcc format (0x31363553) invalid.
> [19248.461699] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.461742] cssp-camera 18000000.camera: Fourcc format (0x33424752) invalid.
> [19248.477336] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.477381] cssp-camera 18000000.camera: Fourcc format (0x33524742) invalid.
> [19248.492129] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.492179] cssp-camera 18000000.camera: Fourcc format (0x34424752) invalid.
> [19248.500991] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.501034] cssp-camera 18000000.camera: Fourcc format (0x34524742) invalid.
> [19248.509667] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.509732] cssp-camera 18000000.camera: vidioc_s_fmt_vid_cap
> [19248.509764] cssp-camera 18000000.camera: vidioc_try_fmt_vid_cap
> [19248.509802] cssp-camera 18000000.camera: width=1280 height=720 byteperline=2560
> [19248.631647] cssp-camera 18000000.camera: vidioc_reqbufs
> [19248.631706] cssp-camera 18000000.camera: queue_setup, count=3, size=1843200
> [19248.653345] cssp-camera 18000000.camera: vidioc_querybuf
> [19248.653539] cssp-camera 18000000.camera: mmap called, vma=0xde024c28
> [19248.653778] cssp-camera 18000000.camera: vma start=0xb6954000, size=1843200, ret=0
> [19248.653848] cssp-camera 18000000.camera: vidioc_querybuf
> [19248.653899] cssp-camera 18000000.camera: mmap called, vma=0xdf602ac8
> [19248.654121] cssp-camera 18000000.camera: vma start=0xb6792000, size=1843200, ret=0
> [19248.654172] cssp-camera 18000000.camera: vidioc_querybuf
> [19248.654219] cssp-camera 18000000.camera: mmap called, vma=0xdf602128
> [19248.654439] cssp-camera 18000000.camera: vma start=0xb65d0000, size=1843200, ret=0
> [19248.654530] cssp-camera 18000000.camera: vidioc_streamon
> [19248.654571] cssp-camera 18000000.camera: start_streaming count=3
> [19248.654611] cssp-camera 18000000.camera: set_capture_enable_no_lock enable=0 val=0x0020
> [19248.790021] cssp-camera 18000000.camera: set_capture_enable_no_lock enable=1 val=0x0020
> [19258.800906] cssp-camera 18000000.camera: close called (dev=video0), file df5598c0
> [19258.800964] cssp-camera 18000000.camera: stop_streaming
> [19258.801010] cssp-camera 18000000.camera: set_capture_enable_no_lock enable=0 val=0x0020
> [19258.890965] cssp-camera 18000000.camera: [dde1a400/0] in flight
> [19258.891018] cssp-camera 18000000.camera: [de388400/1] in flight
> [19258.891054] cssp-camera 18000000.camera: [de086800/2] queued
> [19258.891091] cssp-camera 18000000.camera: buffer_cleanup
> [19258.891119] cssp-camera 18000000.camera: buffer_cleanup
> [19258.891147] cssp-camera 18000000.camera: buffer_cleanup

[Regina Choi]

An update:

I compared the dmesg for debian distro and the working Angstrom distro, I found that the reading the CSSP revision showed a different value, ie:
        val = readw(cam->reg_base_virt + REG_MODE);

produced (in debian):
        cam->rev = val & 0xff;
       
         cam->rev = 0x20;

whereas (in Angstrom):
         cam->rev = 0x05;         


I don't get why the iomem read from CSSP showed different value ?