Is this page helpful?

First Steps with Framos FSM:GO Optical Sensor Modules (Linux)

Introduction

This article provides information on how to start working with the FSM:GO Optical Sensor Modules.

Adding a Yocto Project layer is required. Currently it is not possible to use TorizonCore Builder to add this driver.

The following topics will be covered:

• Main Features
• Datasheets
• Hardware Setup
• Compatible Products
• Adding the needed Yocto Project layer
• Runnning a simple demo

For details about using Video4Linux and GStreamer tools to interact with cameras and collect video frames, see Cameras on Toradex System on Modules.

CSI Camera Set 2MP FSM:GO IMX662 Front View

Camera Set 2MP FSM:GO IMX662 connected to the adapter board

CSI Camera 4K 8MP FSM:GO IMX678 Side View

(Double-Click to Zoom)

Main Features

FSM:GO CSI Optical Sensor Modules

IMX662

Camera Module Features

• Sensor: IMX662 from Sony®
• Sensor Resolution and Optical Format: 2MP CMOS Image Sensor. 1/2.8" Optical format
• Sensor Type: 2MP CMOS Electronic Rolling Shutter Sensor

Sensor Features

• Pixel size: 2.9μm x 2.9μm
• Shutter type: CMOS Rolling Shutter
• Focus Type: Fixed focus

IMX676

Camera Module Features

• Sensor: IMX676 from Sony®
• Sensor Resolution and Optical Format: 12MP CMOS Image Sensor. 1/1.6" Optical format
• Sensor Type: 12MP CMOS Rolling Shutter Sensor

Sensor Features

• Pixel size: 2μm x 2μm
• Shutter type: CMOS Rolling Shutter
• Focus Type: Fixed focus

IMX678

Camera Module Features

• Sensor: IMX678 from Sony®
• Sensor Resolution and Optical Format: 8MP 4K (3840 × 2160) CMOS Image Sensor. 1/2.8" Optical format
• Sensor Type: 8MP CMOS Electronic Rolling Shutter Sensor

Sensor Features

• Pixel size: 2.9μm x 2.9μm
• Shutter type: Electronic Rolling Shutter
• Focus Type: Fixed focus

Datasheets

FSM:GO IMX662 datasheet

FSM:GO IMX676 datasheet

FSM:GO IMX678 datasheet

Hardware Setup

What I need to order

You can have the FSM:GO CSI Optical Sensor Modules working with specific Toradex computers on modules and carrier boards. See the compatible products.

An adapter board is also required to connect the Framos Optical Sensor Modules to the Toradex Boards.

The following list describes all components that you should order:

1. Camera Module

Currently the FSM:GO has three options of cameras available:

• FSM:GO IMX662 (2MP/2K optical sensor module) - 58°, 86° and 137°lens angles available.
• FSM:GO IMX676 (12MP/1:1 format optical optical sensor module) - 16°, 92°, 102° and 185°lens angles available.
• FSM:GO IMX678 (8MP/4K optical sensor sensor module) - 54°, 100° and 110°lens angles available.

2. Adapter Board and accessories

You can use the adapter board and the accessories for any of the three camera models described above.

• FPA-A/P24-V0X (adapter board).
• FMA-CBL-FFC24-0.2m-V1A (cable).
• FMA-SCW-01-KIT (screws, nuts, and spacers for adapter board and sensor board fitting).

Where do I order

You can order the Toradex computer on Modules and the carrier boards online in the Toradex Webshop.

You can order the Framos sensor modules and the needed accessories by directly contacting Framos.

info

The flat ribbon cable (used to connect the carrier board and the camera adaptor) is fragile. If your camera does not work, make sure to test the cable connections on the flat cable.

Please refer to the instructions below for connecting the camera module to your specific carrier board.

Connection to Verdin Development Board

danger

Please disconnect any power and USB cables from the board before connecting the flat cable to the MIPI-CSI bus to avoid any damage to the camera!

Connect the camera to the Verdin Development Board, assuring that the flat cable contacts are on the correct side, as indicated in the figures below. The MIPI-CSI Camera Interface is on connector X47.

Board Connected to the Camera Module

Detailed of the connection between camera and board

Flat Cable Connection Detail

(Double-Click to Zoom)

Compatible Products

Hardware

The FRAMOS FSM:GO Optical Sensor Modules are sold together with an adapter board and cables.

The following Toradex carrier boards that support the MIPI CSI-2 interface connect to the camera kits out-of-the-box, hardware-wise:

• Verdin Development Board
• Mallow Carrier Board
• Dahlia Carrier Board

Currently, only the Verdin iMX8M Plus SoM supports those cameras.

Software

To integrate the camera on the software side, you need to add a Yocto Project layer to your image built on top of the Toradex Linux BSP(BSP 6.7.0 and onward supports this camera).

Torizon supports the camera starting from version 6.7.0, when compiling your Torizon OS image using Yocto to add the necessary dependencies. Out-of-the-box support on Torizon OS standard images is coming soon.

Add Yocto Project Layer

To enable the camera modules, you will need to add a Yocto Project layer provided by Toradex to your Yocto Project environment.

info

The layer will be provided by Toradex soon. If you need more information, you can request it in our community.

1. Setup Environment

   To get your environment set, read and follow the steps presented in Build a Reference Image with Yocto Project/OpenEmbedded. Stop following the steps before starting the build with bitbake. Once the environment is set up, you can proceed with the instructions.

   With your environment setup, you should have the build directory organized with the following structure:

   ..
   ├── build
   │   └── conf
   │       ├── bblayers.conf
   │       ├── local.conf
   │       └── templateconf.cfg
   ├── export
   └── layers
       ├── meta-arm
       ├── meta-freescale
       ├── meta-freescale-3rdparty
       ├── meta-freescale-distro
       ├── meta-openembedded
       ├── meta-qt5
       ├── meta-ti
       ├── meta-toradex-bsp-common
       ├── meta-toradex-demos
       ├── meta-toradex-distro
       ├── meta-toradex-nxp
       ├── meta-toradex-ti
       ├── meta-yocto
       └── openembedded-core

2. Add Layer (Coming Soon)

   2.1. Clone the repository:

   $ git clone https://github.com/toradex/meta-framos.git ../layers/meta-framos

   2.2. Add the layer:

   $ bitbake-layers add-layer ../layers/meta-framos

3. Build Image

   We recommended to build the reference multimedia image, so that the camera functionality can be easily tested with GStreamer.

   To build this image, run:

   $ bitbake tdx-reference-multimedia-image

4. Install the Image

   After a successful build, the image will be in the build/deploy/images/<MACHINE> directory.

   The article Toradex Easy Installer provides detailed instructions on how to install images using the Toradex Easy installer.

Camera Usage

To test the camera, it is recommended to use a display, in order to be able to visualize the captured image.

Connect to the SoM

To follow the next steps, you will need to connect to the SoM after the image is installed. This can be done either via SSH or serial terminal.

Find the Device

To check which /dev/video* is a capture device, the Video4Linux Control (v4l2-ctl) application from the v4l2-utils package can be used.

List the video devices:

# ls /dev/video*
/dev/video0  /dev/video1  /dev/video2

Show information about the capture device on /dev/video2:

# v4l2-ctl -d2 -D
Driver Info:
        Driver name      : viv_v4l2_device
        Card type        : VIV
        Bus info         : platform:viv0
        Driver version   : 5.15.148
        Capabilities     : 0x84201001
                Video Capture
                Video Capture Multiplanar
                Streaming
                Extended Pix Format
                Device Capabilities
        Device Caps      : 0x04200001
                Video Capture
                Streaming
                Extended Pix Format
Media Driver Info:
        Driver name      : vvcam-video
        Model            : viv_media
        Serial           :
        Bus info         :
        Media version    : 5.15.148
        Hardware revision: 0x00000000 (0)
        Driver version   : 5.15.148
Interface Info:
        ID               : 0x03000003
        Type             : V4L Video
Entity Info:
        ID               : 0x00000001 (1)
        Name             : viv_v4l20
        Function         : V4L2 I/O
        Pad 0x01000002   : 0: Sink, Must Connect
          Link 0x02000010: from remote pad 0x1000008 of entity 'vvcam-dwe.0' (V4L2 I/O): Data, Enabled

info

Note that the video device can be in any of the listed video devices. So, check all of them to make sure to use the right one in the pipeline.

To view the video output, run a GStreamer pipeline on the terminal:

# gst-launch-1.0 -v v4l2src device=/dev/video2 ! video/x-raw,width=1920,height=1080,framerate=60/1 ! videoconvert ! waylandsink

Click here to see the Gstreamer command output

gst-launch-1.0 -v v4l2src device=/dev/video2 ! video/x-raw,width=1920,height=1080,framerate=60/1  ! waylandsink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0.GstPad:src: caps = video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)60/1, format=(string)YUY2, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, colorimetry=(string)bt709
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:src: caps = video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)60/1, format=(string)YUY2, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, colorimetry=(string)bt709
/GstPipeline:pipeline0/GstWaylandSink:waylandsink0.GstPad:sink: caps = video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)60/1, format=(string)YUY2, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, colorimetry=(string)bt709
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:sink: caps = video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)60/1, format=(string)YUY2, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, colorimetry=(string)bt709
Redistribute latency...
^Chandling interrupt.
Interrupt: Stopping pipeline ...
Execution ended after 0:00:32.699767524
Setting pipeline to NULL ...
Total showed frames (1907), playing for (0:00:32.699756774), fps (58.318).
Freeing pipeline ...

Having trouble?

Please contact our technical support. Various options for technical support are mentioned in the article below.

• Technical Support Channels