SSC377QE/IMX335 - Sensor index and resolutions

[BlueMax]

Hallo,
in Majestic there is this behavior:

Majestic user-defined settings -> SDK output

1440x1080 30fps -> Sensor index 0: 2560x1920@30fps # (30fps, 4:3, scaled to 1440x1080 properly)
1920x1080 30fps -> Sensor index 0: 2560x1920@30fps # (30fps, 4:3 stretched to 16:9)
1920x1080 60fps -> Sensor index 1: 2560x1920@60fps # (30fps only, 4:3 stretched to 16:9)
1920x1080 120fps -> Sensor index 3: 1920x1080@120fps # (60fps only, crop mode)
1280x720 60fps -> Sensor index 1: 2560x1920@60fps
1280x720 120fps -> Sensor index 3: 1920x1080@120fps
??? x ??? ?? fps -> Sensor index 2: (unknown)

Are these resolution modes hard-coded into the drivers? It looks kinda wrong (120fps results in 60fps, no difference between index 0+1, crop masks not working, etc). I've just checked 1920x1080@60fps in Divinus and it resulted in the same behavior (30fps only, stretched).

I've noticed that the sensor iqfiles (/etc/sensors/imx335.bin) of SSC30KQ/IMX335 are not compatible with SSC377QE. The older ones (also shipped with OpenIPC companion) are 86.7KB in size and the SSC377QE are 135KB or 145KB. Loading the older ones into SSC377QE results in gray picture only. So, there is definitely a difference between SSC30KQ.

I've picked this board (IM50Q01) as i thought the IMX335 would be a well supported chip by OpenIPC (providing the same proper modes with 60/120fps) but this seems to be a completely different system (compared to SSC30KQ). It is flagged as "recommended SoC" by OpenIPC. I wouldn't second that in this state.

Can you shed some light into the current state of SSC337QE boards? Are they too new or still WIP? Or is it just me doing something wrong here?

[wberube]

One thing for sure, SSC30KQ and SSC377QE belong to different hardware generations; you can refer to this issue for additional context. Their ISP (Image Signal Processor) pipelines are fundamentally different, which explains why the calibration (IQ) files are incompatible—the newer architecture requires entirely different register mappings.

The sensor indexes identify specific modes hard-coded within the driver. These modes are responsible for the scaling and cropping logic that enables the exotic parameters you may have seen shared in Telegram groups. These drivers are typically closed-source binary blobs provided by the vendor, but I have already seen a user share custom drivers that pushed the frame rate up to 100 fps on the latter.

That said, the infinity6c platform is still relatively new compared to the older but mature infinity6e. While the hardware is recommended for its potential, the software support for high-frame-rate modes is still very much a work in progress.

[BlueMax]

So, looks like i need to get into Telegram groups somehow. Thanks.

Edit: If you stumble upon that custom driver somewhere please let me know. I don't have access to Telegram.