i.MX93 Configuration

i.MX93 Configuration

The i.MX93 features a simplified pipeline compared to the i.MX95. While it shares similar concepts (CSI Device and Crossbar), key differences include:

• No Formatter: Data flows directly from CSI to Crossbar without intermediate formatting
• Single CSI Port: Typically only one CSI input available
• Fewer ISI Channels: Limited to 1-2 ISI processing channels

Visualizing the Architecture

As shown in the actual media graph, data flows from the Sensor to the CSI Device, then through a Crossbar switch before reaching the ISI.

YAML Configuration Example

Correctly configuring the i.MX93 requires setting up both the CSI Device and the Crossbar. You can find more examples in our GitHub Repository.

Routes vs MediaLinks

• Routes: Configure internal SoC data paths (Crossbar routing between pads)
• MediaLinks: Establish external device connections (Sensor → CSI interface)

Routes:
  # Route through the Crossbar (Input Pad 2 -> Output Pad 5)
  - device: "crossbar"
    links: 
      - {src: "2/0", dst: "5/0", enable: 1}

MediaLinks:
  # Link external sensor to the CSI port
  # Device naming: "<sensor_type> <i2c_bus>-<i2c_addr>:<pad>"
  # Example: "tevs 1-0048" = TEVS sensor on I2C bus 1, address 0x48
  - {src: "tevs 1-0048:0", dst: "csidev-4ae00000.csi:0", enable: 1}

Sensor Device Naming Convention

Component	Example	Description
Sensor Type	tevs	TechNexion camera module identifier
I2C Bus	1	I2C bus number
I2C Address	0048	Hexadecimal I2C address (0x48)
Pad	:0	Output pad number