Summary
Requesting a GC2083 sensor driver (libsns_gc2083.so + config) for the hi3516cv6xx (V5) platform. The sensor is extremely common on low-cost Hi3516CV610 "H2" camera modules. On my board everything in the OpenIPC stack works — U-Boot, kernel, overlay, network, web, majestic — and the GC2083 is confirmed alive and correctly identified on I2C. The only missing piece is the sensor library, which isn't in the openhisilicon tree (the CV610 SDK itself ships only sc4336p / gc4023 / sc450ai / sc500ai / sc431hai / os04d10, so GC2083 was a vendor add-on).
Hardware
Board: H2-52PGX, vendor version H2-52PGX_V1.0.4_20241105 (XRS platform)
SoC: Hi3516CV610 (majestic MPP string reports HI3516CV610)
U-Boot env: board=hi3516cv608, sensor=gc2083
DRAM: 64 MB on-package (SiP)
Flash: XM25QH64C 8 MB SPI NOR (JEDEC 20 40 17)
Sensor: GC2083, I2C-0 @ 0x37
MPP version (drivers must match this ABI)
App was built with MPP version: HI3516CV610_MPP_V1.0.2.0.B051 Release
Sensor hardware is confirmed working
After bringing up the MPP stack, the sensor clocks up and answers on I2C, and its chip-ID register reads back the GC2083 ID:
load_hisilicon -i -sensor0 gc2083
mmz_start: 0x42c00000, mmz_size: 20M
hisilicon: Manualy set SENSOR as gc2083
i2cdetect -y -r 0 -> device appears at 0x37
i2ctransfer -y 0 w2@0x37 0x03 0xf0 r2
0x20 0x83 <- GC2083 chip ID (regs 0x03f0/0x03f1)
So clock/power/reset path and I2C are all fine — this is purely a missing userspace sensor driver.
What's missing / current failure
majestic detects the sensor (from sensor=gc2083 env) but has no driver/config:
[sdk] try_sensor_config@3820 SENSOR=gc2083
[sdk] find_sensor_config@3798 No matches for 'gc2083' in /etc/sensors directory
[main] init_sdk@75 Cannot start SDK
/usr/lib/sensors/ on the current cv6xx build ships: gc4023, imx307, os02m10, os04d10, sc431hai, sc4336p, sc450ai, sc500ai, sp2308 — no gc2083.
Request
Could GC2083 be added to the hi3516cv6xx sensor set? GalaxyCore GC4023 is already supported for this exact SoC and would be the natural ABI template (same vendor, same MPP). Happy to test builds on real hardware and provide full logs / I2C dumps.
Side note that may help others
These "H2-52PGX" CV610 modules have on-package 64 MB DDR that none of the released boot-hi3516cv610-*-nor.bin DDR tables match (all fail GSL "table is incorrect"). The boot-hi3516cv608-nor.bin DDR2-64M table boots them correctly (env also reports board=hi3516cv608). Might be worth documenting for other CV610/H2 boards.
Summary
Requesting a GC2083 sensor driver (libsns_gc2083.so + config) for the hi3516cv6xx (V5) platform. The sensor is extremely common on low-cost Hi3516CV610 "H2" camera modules. On my board everything in the OpenIPC stack works — U-Boot, kernel, overlay, network, web, majestic — and the GC2083 is confirmed alive and correctly identified on I2C. The only missing piece is the sensor library, which isn't in the openhisilicon tree (the CV610 SDK itself ships only sc4336p / gc4023 / sc450ai / sc500ai / sc431hai / os04d10, so GC2083 was a vendor add-on).
Hardware
Board: H2-52PGX, vendor version H2-52PGX_V1.0.4_20241105 (XRS platform)
SoC: Hi3516CV610 (majestic MPP string reports HI3516CV610)
U-Boot env: board=hi3516cv608, sensor=gc2083
DRAM: 64 MB on-package (SiP)
Flash: XM25QH64C 8 MB SPI NOR (JEDEC 20 40 17)
Sensor: GC2083, I2C-0 @ 0x37
MPP version (drivers must match this ABI)
App was built with MPP version: HI3516CV610_MPP_V1.0.2.0.B051 Release
Sensor hardware is confirmed working
After bringing up the MPP stack, the sensor clocks up and answers on I2C, and its chip-ID register reads back the GC2083 ID:
load_hisilicon -i -sensor0 gc2083
mmz_start: 0x42c00000, mmz_size: 20M
hisilicon: Manualy set SENSOR as gc2083
i2cdetect -y -r 0 -> device appears at 0x37
i2ctransfer -y 0 w2@0x37 0x03 0xf0 r2
0x20 0x83 <- GC2083 chip ID (regs 0x03f0/0x03f1)
So clock/power/reset path and I2C are all fine — this is purely a missing userspace sensor driver.
What's missing / current failure
majestic detects the sensor (from sensor=gc2083 env) but has no driver/config:
[sdk] try_sensor_config@3820 SENSOR=gc2083
[sdk] find_sensor_config@3798 No matches for 'gc2083' in /etc/sensors directory
[main] init_sdk@75 Cannot start SDK
/usr/lib/sensors/ on the current cv6xx build ships: gc4023, imx307, os02m10, os04d10, sc431hai, sc4336p, sc450ai, sc500ai, sp2308 — no gc2083.
Request
Could GC2083 be added to the hi3516cv6xx sensor set? GalaxyCore GC4023 is already supported for this exact SoC and would be the natural ABI template (same vendor, same MPP). Happy to test builds on real hardware and provide full logs / I2C dumps.
Side note that may help others
These "H2-52PGX" CV610 modules have on-package 64 MB DDR that none of the released boot-hi3516cv610-*-nor.bin DDR tables match (all fail GSL "table is incorrect"). The boot-hi3516cv608-nor.bin DDR2-64M table boots them correctly (env also reports board=hi3516cv608). Might be worth documenting for other CV610/H2 boards.