Skip to content

Hi3516CV610 (cv6xx): os04d10 detected but never streams — V5 sensor reg-init not triggered (mipi_rx "no data input at phy") #2218

Description

@operatech-fr

Hardware

  • SoC: Hi3516CV610, DDR2-64M binning (bdinfo DRAM = 0x04000000 = 64 MB)
  • Board: H4-50POM-S/W/BT
  • Sensor: OmniVision OS04D10 (4MP, MIPI 2-lane 720Mbps, 10-bit linear, Bayer BGGR)
  • NOR flash 16 MB

Firmware flashed (release "latest")

  • boot-hi3516cv610-10b-nor.bin (10b = ddr2-64m per image.yml)
  • firmware.bin.hi3516cv6xx (from openipc.hi3516cv6xx-nor-ultimate.tgz)

Boots fine, persists. ipcinfo -s = os04d10, driver libsns_os04d10.so present.

Problem

No /etc/sensors config ships for cv6xx, so majestic segfaults on No matches for 'os04d10'.
I wrote a V4-style INI and majestic V5 parses it fine: MIPI attr set, VI/VPSS online, SDK started, RTSP up.

But the sensor never streams:

  • Its reg_init ("== os04d10 ... Init OK! ==") is never printed at runtime, while other driver [puts] do print → the sensor init callback is never invoked.
  • /proc/umap/mipi_rx: sensor_clk=Y, mipi_clk=Y, but all data lanes 0x0, vsync_cnt=0, clk lane in LP00 → "no data input at the phy module".
  • VENC chn0 "Timeout" in a loop, no frames.

This is not an INI issue. Working INI + full report available. Happy to test builds.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions