How to build ov2710 module for hi3518ev200

[0xPIT]

I have an old PTZ camera that comes with a hi3518ev200 and a ov2710 sensor.
The build for this chip works fine but does not include a driver for this sensor.

Using libsns_ov2710.so from the repo for the hi3516ev100, yields:

dlopen "/usr/lib/sensors/libsns_ov2710.so" error: Error relocating /usr/lib/sensors/libsns_ov2710.so: HI_MPI_ISP_SnsRegsCfg: symbol not found

when starting majestic.

Is there a simple way (i.e. w/o setting up a complete cross-compilation environment) to get my hands in the driver + config for a ov2710 that runs in my distribution? If not, how do I build this driver? I can't find the sources + build scripts.

[widgetii]

Hi @0xPIT — transferred this here since the sensor library lives in openhisilicon. Quick technical breakdown of what you hit and what's coming:

Why your attempted shortcut failed. The hi3518ev200 belongs to the V2 chip family (hi3516cv200 chiparch). hi3516ev100 is V3 (hi3516cv300 chiparch). The two ISP SDKs have different sensor-callback ABIs — HI_MPI_ISP_SnsRegsCfg is a V3-only entry point, V2 uses a different callback registration model (sensor_register_callback from hi_sns_ctrl.h). So a V3-built libsns_ov2710.so cannot be loaded on a V2 chip. (Side note: OpenIPC ships no V3 libsns_ov2710.so — only a cv100/V1 binary blob — so wherever you got that .so, it came from outside this org.)

What we have. A complete MIT-licensed V2 OV2710 driver source already exists in the OpenIPC/sensors repo — written specifically for hi3518ev200. We're going to integrate it into openhisilicon under libraries/sensor/hi3516cv200/omnivision_ov2710/ and ship the prebuilt blob via the firmware cv200 osdrv package.

One question for you before we finalize. The source we have is MIPI-mode only (the init sequence sets 0x300f=0xc3, 0x4801=0x0f, etc., and the success print says "1080P30fps(mipi port)"). Could you check how your sensor is wired?

• MIPI: 2 differential lane pairs (4 pins) from sensor flex to SoC, plus clock pair.
• Parallel/DC: 8–10 single-ended VI_DATA lines + HSYNC/VSYNC/PCLK.

If MIPI we're plug-and-play. If parallel we'll need a small register-init delta (we have a known-good cv100 V1 parallel binary to cross-reference). A clear photo of the sensor module and its connector to the SoC would let us tell at a glance.

Will follow up here when we have a test image ready.

[widgetii]

@0xPIT — test build is ready. Since I can't tell from your description whether your OV2710 is wired MIPI or DVP/parallel, I built both variants so you can try one then the other without recompiling.

Download

Pre-built artifacts (no toolchain needed): https://github.com/OpenIPC/openhisilicon/releases/tag/ov2710-test-build-pr71

You'll find:

• openipc.hi3518ev200-nor-lite-ov2710-test.tgz — full firmware image (recommended path)
• libsns_ov2710_mipi.so + libsns_ov2710_dc.so — standalone sensor libs (quick-test path)
• ov2710_i2c_mipi_1080p.ini + ov2710_i2c_dc_1080p.ini + ov2710.ini (IQ) — config files

Path A — full reflash (recommended, most reliable)

1. Download openipc.hi3518ev200-nor-lite-ov2710-test.tgz to your PC.
2. Serve it locally over HTTP (any tool, e.g.):

   cd /path/to/download && python3 -m http.server 8000
   

3. Note your PC's IP on the same LAN as the camera. SSH into the camera (root@<camera-ip>, password is whatever you set; default OpenIPC is 12345).
4. On the camera, download and flash:

   cd /tmp
   wget http://<your-pc-ip>:8000/openipc.hi3518ev200-nor-lite-ov2710-test.tgz
   sysupgrade --kernel=uImage.hi3518ev200 --rootfs=rootfs.squashfs.hi3518ev200 \
              --archive=openipc.hi3518ev200-nor-lite-ov2710-test.tgz -z
   

5. Tell U-Boot which sensor variant to load. Try MIPI first (more common on hi3518ev200):

   fw_setenv sensor ov2710
   reboot
   

6. After reboot, check the result:

   logread | grep -iE 'ov2710|sensor'
   ipcinfo --sensor
   dmesg | tail -40
   

7. If you don't see video on RTSP (rtsp://<camera-ip>:554/stream0), switch to DVP/parallel:

   fw_setenv sensor ov2710_dc
   reboot
   

8. Repeat the checks. One of the two should work depending on your PCB wiring.

Path B — drop-in (no reflash, faster iteration)

Only do this if you want to keep your current firmware and just test the sensor libs. SSH into the camera and:

cd /tmp
wget http://<your-pc-ip>:8000/libsns_ov2710_mipi.so
wget http://<your-pc-ip>:8000/libsns_ov2710_dc.so
wget http://<your-pc-ip>:8000/ov2710_i2c_mipi_1080p.ini
wget http://<your-pc-ip>:8000/ov2710_i2c_dc_1080p.ini
wget http://<your-pc-ip>:8000/ov2710.ini

# install
cp libsns_ov2710_*.so /usr/lib/sensors/
cp ov2710_i2c_*.ini /etc/sensors/
mkdir -p /etc/sensors/iq && cp ov2710.ini /etc/sensors/iq/

# try MIPI first
fw_setenv sensor ov2710
reboot

If no video, swap to DC:

fw_setenv sensor ov2710_dc
reboot

⚠️ Caveat for Path B: pinmux for ov2710_dc (parallel) is only set up by the load_hisilicon script that ships in this test firmware. If your camera is on stock OpenIPC, the ov2710_dc case won't exist and you'll need Path A for the DVP test.

What to report back

For each variant you try, please paste:

1. logread | grep -iE 'ov2710|sensor|mipi' — looking for 1080P30fps(MIPI port) init success or (DVP/parallel port) init success from the sensor lib.
2. dmesg | tail -50 — any I2C / hi_mipi errors?
3. ipcinfo --sensor — does it report ov2710?
4. Whether ffplay rtsp://<camera-ip>:554/stream0 shows video (and roughly what — black, garbled, color shift, OK).
5. A photo of the sensor module / its flex cable to the SoC, if convenient. Helps cross-check the MIPI-vs-parallel guess.

The IQ tuning is a placeholder (copied from ov9750.ini), so colors/gamma will likely be off on the working variant. That's a separate follow-up after we confirm the basic pipeline works.

Thanks for picking this up — you're the first person with hi3518ev200 + OV2710 hardware to test the patch.

[widgetii]

Update — release artifacts simplified. The two .so files are now collapsed into one universal binary that picks MIPI vs DVP/parallel at runtime by reading its own filename via dladdr(). Functionally identical for your test, but the drop-in path (Path B) changes slightly because there's now only one binary to download.

What changed

The release at https://github.com/OpenIPC/openhisilicon/releases/tag/ov2710-test-build-pr71 now ships:

• libsns_ov2710.so — single universal binary (~20 KB stripped)
• libsns_ov2710_mipi.so → symlink to libsns_ov2710.so (created at install time, not in the asset list)
• libsns_ov2710_dc.so → symlink to libsns_ov2710.so (same)
• openipc.hi3518ev200-nor-lite-ov2710-test.tgz — full firmware (already includes the .so + symlinks)

The .so reads its own dlopen path; if the basename contains _dc. it does the parallel-DVP register init, otherwise MIPI. Same on-disk file either way.

Path A — full reflash (unchanged, recommended)

Same as before — full firmware image already contains the .so + both symlinks + both .ini files. Boot, then:

fw_setenv sensor ov2710        # MIPI variant
reboot
# ... if no video ...
fw_setenv sensor ov2710_dc     # DVP/parallel variant
reboot

Path B — drop-in (revised, simpler now)

SSH into the camera and:

cd /tmp
wget http://<your-pc-ip>:8000/libsns_ov2710.so
wget http://<your-pc-ip>:8000/ov2710_i2c_mipi_1080p.ini
wget http://<your-pc-ip>:8000/ov2710_i2c_dc_1080p.ini
wget http://<your-pc-ip>:8000/ov2710.ini

# install one .so, two symlinks
cp libsns_ov2710.so /usr/lib/sensors/
ln -sf libsns_ov2710.so /usr/lib/sensors/libsns_ov2710_mipi.so
ln -sf libsns_ov2710.so /usr/lib/sensors/libsns_ov2710_dc.so

# install configs
cp ov2710_i2c_*.ini /etc/sensors/
mkdir -p /etc/sensors/iq && cp ov2710.ini /etc/sensors/iq/

# try MIPI first
fw_setenv sensor ov2710
reboot

If MIPI doesn't get you video, swap to DC (no need to download anything else):

fw_setenv sensor ov2710_dc
reboot

How to confirm runtime detection picked the right mode

After reboot, logread | grep ov2710 will show one of:

===omnivision ov2710 sensor 1080P30fps(MIPI port) init success!===
===omnivision ov2710 sensor 1080P30fps(DVP/parallel port) init success!===

If the suffix in the print doesn't match what you set in fw_setenv sensor, something is wrong with the symlink wiring. (Path A users shouldn't see this — symlinks are baked into the image.)

The reporting checklist from my previous comment is unchanged.

[0xPIT]

wow, incredible, thanks.
I'm testing now, will report back.

Judging from the flat flex, it does look like parallel, does not look like usual mipi cable.

[0xPIT]

hm, flashing seems stuck since about 30mins, I've pulled the lastest sysupgrade script from the repo:

sysupgrade --kernel=uImage.hi3518ev200 --rootfs=r
ootfs.squashfs.hi3518ev200 --archive=update.tgz -z
OpenIPC System Updater v1.0.49

Vendor  hisilicon
SoC     hi3518ev200
Kernel  11:46:46 2023-10-14
RootFS  master+86b40f3, 2023-10-14

Stop services, sync files, free up memory
Stopping crond: OK
Stopping ntpd: OK
Stopping klogd: OK
Stopping syslogd: OK

Uptime:
 11:46:48 up 0 min,  load average: 0.65, 0.19, 0.06

Memory:
              total        used        free      shared  buff/cache   available
Mem:          26.7M       11.6M        5.8M        6.5M        9.3M        6.6M
Swap:             0           0           0

Processes:
PID   USER     COMMAND
    1 root     init
  692 root     /usr/sbin/rngd -r /dev/urandom
  729 root     udhcpc -x hostname:openipc-hi3518ev200 -A 0 -T 1 -t 1 -R -b -O search -p /var/run/udhcpc.wlan0.pid -i wlan0
  741 root     wpa_supplicant -D nl80211,wext -i wlan0 -c /tmp/wpa_supplicant.conf -B
  777 root     udhcpc -x hostname:openipc-hi3518ev200 -A 0 -T 1 -t 1 -R -b -O search -p /var/run/udhcpc.eth0.pid -i eth0
  788 root     /usr/sbin/dropbear -R -B -k -p 22 -K 300
  793 root     /usr/sbin/httpd httpd -p 85 -f -c /etc/httpd.conf -r Authentication
  982 root     -sh
 1193 root     {sysupgrade} /bin/sh /usr/sbin/sysupgrade --kernel=uImage.hi3518ev200 --rootfs=rootfs.squashfs.hi3518ev200 --archive=update.tgz -z
 1242 root     ps

Unmounting SD card

Firmware
Local archive unpacked


Protected: flashing continues even if this terminal disconnects.

Kernel
Update kernel from uImage.hi3518ev200

[0xPIT]

ok. the web updater could update kernel and rootfs... testing now.

[0xPIT]

unfortunately, neither mipi nor dc variants work.
I've disassembled and again confirmed that the sensor is a ov2710.

both cases report:
May 3 12:48:52 openipc-hi3518ev200 kern.emerg kernel: sensor_type 'ov2710' is error!!!

[0xPIT]

as per your first message, here's the output:

logread | grep -iE 'ov2710|sensor|mipi' -->

root@openipc-hi3518ev200:~# logread | grep -iE 'ov2710|sensor|mipi'
May  3 12:48:52 openipc-hi3518ev200 daemon.info hisilicon: Manualy set SENSOR as ov2710
May  3 12:48:52 openipc-hi3518ev200 kern.emerg kernel: sensor_type 'ov2710' is error!!!
May  3 12:48:52 openipc-hi3518ev200 kern.emerg kernel: The sensor_type 'ov2710' !!!
May  3 12:48:54 openipc-hi3518ev200 kern.info kernel: load sensor_i2c.ko ...OK!
May  3 12:48:54 openipc-hi3518ev200 kern.alert kernel: mipi_init
May  3 12:48:54 openipc-hi3518ev200 kern.emerg kernel: load hi_mipi.ko ...OK!
May  3 12:48:57 openipc-hi3518ev200 user.debug majestic[860]: SENSOR=ov2710
May  3 12:48:57 openipc-hi3518ev200 user.debug majestic[860]: matched sensor config: ov2710_i2c_dc_1080p.ini
May  3 12:48:57 openipc-hi3518ev200 user.debug majestic[860]: matched sensor config: ov2710_i2c_mipi_1080p.ini
May  3 12:48:57 openipc-hi3518ev200 user.err majestic[860]: Several sensor configs matched. Select one of them and
May  3 12:48:57 openipc-hi3518ev200 user.err majestic[860]: set 'isp.sensorConfig' param in config file

dmesg | tail -50 — any I2C / hi_mipi errors? --> no mipi errors other than 
sensor_type 'ov2710' is error!!!
The sensor_type 'ov2710' !!!
sys config init ok!

[0xPIT]

Majestic output:

13:05:47  <       majestic> [     sdk] try_sensor_config@3328        SENSOR=ov2710_dc
13:05:47  <       majestic> [     sdk] find_sensor_config@3296       matched sensor config: ov2710_dc_1080p.ini
13:05:47  <       majestic> [     sdk] start_sdk@384                 Using /etc/sensors/ov2710_dc_1080p.ini sensor configuration file
13:05:47  <       majestic> [     sdk] start_sdk@389                 App was built with MPP version: Hi3518EV200_MPP_V1.0.5.0.B060 Release
13:05:47  <       majestic> [     sdk] start_sdk@394                 Current MPP version: HI_VERSION=Hi3518EV200_MPP_V1.0.5.0 B060 Release
13:05:48  <       majestic> [     sdk] start_sdk@422                 sensor ov2710
13:05:48  <       majestic> [     sdk] start_sdk@426                   input_mode CMOS_18V, WDR NONE
13:05:48  <       majestic> [     sdk] start_sdk@431                   dev [1920x1080]@0x0 30fps, BGGR
13:05:48  <       majestic> [  sensor] try_to_load@19                trying to load /usr/lib/sensors/libsns_ov2710_dc.so
13:05:48  <       majestic> [     hal] hisi_free_mem_ex@753          Free MMZ mem before allocation: 32580KB
13:05:48  <       majestic> [     sdk] dump_vb_configuration@2205    VB configuration:
13:05:48  <       majestic> [     sdk] dump_vb_configuration@2208      [0]: 3110400 x 3
13:05:48  <       majestic> [     sdk] dump_vb_configuration@2208      [1]: 4147200 x 1
13:05:48  <       majestic> [     hal] hisi_free_mem_ex@753          Free MMZ mem after allocation: 19404KB
13:05:48  <       majestic> [     sdk] init_sensor@2408              Sensor driver loaded
13:05:48  <       majestic> [     sdk] init_vi@2870                  SDK is in 'offline' mode
13:05:48  <       majestic> [    puts]                               linear mode
13:05:48  <       majestic> [    puts]                               ======================================================================
13:05:48  <       majestic> [     log] printf@292                    ===omnivision ov2710 sensor 1080P30fps(DVP/parallel port) init success!===
13:05:48  <       majestic> [    puts]                               ======================================================================
13:05:48  <       majestic> [     hal] HiSi_HAL_SetAeTime@893        Exposure: 82ms (12fps), aGain: 32768, dGain: 1024, ispGain: 1024, mode: slow_shutter
13:05:48  <       majestic> [     sdk] log_venc_chn@1275             h264 1920x1080@30fps 4096kbit 30gop
13:05:48  <     iq_monitor> [     sdk] monitor_thread@311            Loading IQ profile /etc/sensors/iq/default.ini
13:05:48  <       majestic> [     sdk] create_vpss_chn@1005            venc_chn: 0, vpss_grp: 0, vpss_chn: 0
13:05:48  <       majestic> [     sdk] start_video@1947                venc took 7200KB of MMZ [1012]
13:05:48  <       majestic> [     sdk] log_venc_chn@1275             MJPEG 1920x1080@5fps 50q 
13:05:48  <       majestic> [     sdk] create_vpss_chn@1005            venc_chn: 1, vpss_grp: 0, vpss_chn: 1
13:05:48  <       majestic> [     sdk] start_mjpeg@1400                mpeg_enc took 2052KB of MMZ [2040]
13:05:48  <       majestic> [     sdk] start_sdk@548                 HiSilicon SDK started
13:05:48  <       majestic> [     hal] hisi_free_mem_ex@753          Free MMZ mem finally: 6072KB
13:05:48  <       majestic> [    rtsp] rtsp_init@28                  RTSP server started on port 554
[Func]:HI_MPI_ISP_QueryExposureInfo [Line]:730 [Info]:Get Active Stat Buffer Err
13:05:49  <     iq_monitor> [     sdk] monitor_thread@330            Query exposure info
13:05:49  <     iq_monitor> [     sdk] monitor_thread@330            Unknown error code A01C8046
13:05:49  <       majestic> [     sdk] venc_read@925                 Timeout from venc channel 0