Skip to main content

FAQs for CCG3-8M

This document contains all the frequently asked questions related to the CCG3-8M. This will be very helpful if you are suffering from any issues when using the CCG3-8M.

Common Issues and Solutions​

Q1: How to Resolve Script Execution Errors?​

Problem Description: When encountering step1 timeout errors during module loading, you may see error messages similar to:

Loading PCIe driver...insmod: ERROR: could not insert module ../xdma_v412/xdma.ko: Invalid module format
Error: PCIe driver did not load properly.
FAILED

Solution: Execute the following commands in sequence to clean and rebuild:

make clean
make

Additional Notes:

  • Ensure all dependencies are properly installed
  • Verify kernel compatibility with the driver version
  • Check system logs for detailed error information

Q2: Camera Initialization Configuration for Different Camera Types​

Problem Description: When connecting different types of cameras, the initialization script parameters need to be configured according to the specific camera model.

Solution: Modify the configuration file pcie_init_cardx.sh based on your camera type:

Configuration Parameters:

  • camera_serdes_type[0] - Camera type identifier
  • Values:
    • 0: GMSL camera (indicates connected camera is GMSL type)
    • 1: GMSL2(6G) camera (indicates connected camera is GMSL2 6G type)
    • 2: GMSL2F(3G) camera (indicates connected camera is GMSL2F 3G type)

Example Configuration:

# For GMSL camera configuration
camera_serdes_type[0]=1
camera_serdes_type[1]=1
camera_serdes_type[2]=1
camera_serdes_type[3]=1
camera_serdes_type[4]=1
camera_serdes_type[5]=1
camera_serdes_type[6]=1
camera_serdes_type[7]=1

Q3: How Do Image Capture Cards Achieve Synchronization?​

Method 1 (Recommended): For detailed instructions, please Refer to the links below

-Network Topology Diagram1

Connection Requirements:

  1. Primary Connection: ETH0 on master node (IPC) connects to CCG3 capture card (slave)
  2. GPS Integration: GPS module connects to the capture card for timing synchronization
  3. PTP Protocol: Enables precise time synchronization between devices

Method 2: For detailed instructions, please Refer to the links below

-Network Topology Diagram2

Q4: PPS External Trigger Configuration​

TTL Trigger Usage Method 1: The capture card's [GPS] interface defines the following 2 interfaces (red and green) for connecting an external TTL trigger square wave, and configuring the corresponding script parameters.

Pin Configuration Table:

Red PinWhite PinGreen PinBlue PinBlack PinBlack Pin
PPS PinUART_RXGND-UART_TXGND

TTL Trigger Configuration Details:

<file name：pcie_init_cardx.sh>
# Trigger mode config {0:no trigger; 1:reserved; 2:inner trigger; 3:external trigger}
card_trigger_signal_mode               "3"

# Card external signal input fps config.
# Camera external output fps config.
# The following two configurations are valid only when card_trigger_signal_mode is "3".
card_external_signal_input_fps         "1" Hz
camera_external_output_fps             "20" Hz

# Camera inner output fps config
camera_inner_output_fps                "30" Hz

TTL Trigger Usage Method 2: If there is no external TTL trigger available, the capture card can internally generate a variable TTL trigger (only applicable for camera synchronization on a single capture card). These settings can be flexibly configured through script parameters (as shown in the red settings below: indicating the generation of a 30Hz synchronization TTL signal from within the capture card).

<file name：pcie_init_cardx.sh>
# Trigger mode config {0:no trigger; 1:reserved; 2:inner trigger; 3:external trigger}
card_trigger_signal_mode               "2"

# Card external signal input fps config.
# Camera external output fps config.
# The following two configurations are valid only when card_trigger_signal_mode is "3".
card_external_signal_input_fps         "1" Hz
camera_external_output_fps             "20" Hz

# Camera inner output fps config
camera_inner_output_fps                "30" Hz