Radium camera cape failed to capture frame

GoogleGroups
1

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.

2

In addition, the dmesg log after the command :

3

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 ?