Repository navigation
Hi3516CV300_jxf22_i2c QueryExposureInfo error #2530
Description
Hi!
Camera with chip Hi3516CV300, sensor jxf22_i2c, 8mb
It doesn't work after flashing.
The factory firmware is working fine(attached in the file).
factory_backup-hi3516cv300-nor8m.zip
ipctool info:
chip:
vendor: HiSilicon
model: 3516CV300
board:
vendor: OpenIPC
version: 2.5.04.10
possible-IR-cut-GPIO: 66
ethernet:
mac: "00:12:17:95:cd:f0"
u-mdio-phyaddr: 1
phy-id: 0x001cc816
d-mdio-phyaddr: 0
rom:
- type: nor
block: 64K
partitions:
- name: boot
size: 0x40000
sha1: b9e93d92
- name: env
size: 0x10000
sha1: 99d5c6ff
contains:
- name: uboot-env
offset: 0x0
- name: kernel
size: 0x200000
sha1: 066877cc
- name: rootfs
size: 0x500000
path: /,squashfs
sha1: f2f11dcb
- name: rootfs_data
size: 0xb0000
path: /overlay,jffs2,rw
size: 8M
addr-mode: 3-byte
ram:
total: 64M
media: 32M
firmware:
kernel: "3.18.20 (Thu Apr 10 22:43:33 UTC 2025)"
toolchain: buildroot-gcc-13.3.0
sdk: "Hi3516CV300_MPP_V1.0.4.0 B050 Release (Jun 3 2018, 21:42:04)"
sensors:
- vendor: Silicon Optronics
model: JXF22
control:
bus: 0
type: i2c
addr: 0x80
vicap-state: down
Majestic error:
Majestic Lite for HiSilicon, version master+2ca6c07, built on 2025-04-09
09:00:57 < majestic> [watchdog] watchdog_start@94 Detected Hisilicon Watchdog
09:00:57 < majestic> [watchdog] watchdog_start@115 Watchdog timeout set to 300 seconds
09:00:57 < majestic> [ httpd] start_web_server@371 Set server path: /var/www
09:00:57 < majestic> [ httpd] new_http_server@359 HTTP server started on 0.0.0.0:80
09:00:57 < majestic> [ main] init_sdk@66 Loading main configuration: /etc/majestic.yaml
09:00:57 < majestic> [ sdk] start_sdk@387 Using /etc/sensors/jxf22_i2c_dc_1080p_line.ini sensor configuration file
09:00:57 < majestic> [ sdk] start_sdk@392 App was built with MPP version: Hi3516CV300_MPP_V1.0.4.0.B050 Release
09:00:57 < majestic> [ sdk] start_sdk@397 Current MPP version: HI_VERSION=Hi3516CV300_MPP_V1.0.4.0 B050 Release
09:00:58 < majestic> [ sdk] start_sdk@425 sensor jxf22
09:00:58 < majestic> [ sdk] start_sdk@429 input_mode CMOS, WDR NONE
09:00:58 < majestic> [ sdk] start_sdk@434 dev [1920x1080]@0x0 25fps, BGGR
09:00:58 < majestic> [ sensor] try_to_load@19 trying to load /usr/lib/sensors/libsns_jxf22_i2c_dc.so
09:00:58 < majestic> [ hal] hisi_free_mem_ex@753 Free MMZ mem before allocation: 32684KB
09:00:58 < majestic> [ sdk] dump_vb_configuration@2202 VB configuration:
09:00:58 < majestic> [ sdk] dump_vb_configuration@2205 [0]: 3110400 x 3
09:00:58 < majestic> [ sdk] dump_vb_configuration@2205 [1]: 4147200 x 1
09:00:58 < majestic> [ sdk] dump_vb_configuration@2205 [2]: 622080 x 1
09:00:58 < majestic> [ hal] hisi_free_mem_ex@753 Free MMZ mem after allocation: 18896KB
09:00:58 < majestic> [ sdk] init_sensor@2405 Sensor driver loaded
09:00:58 < majestic> [ sdk] init_vi@2867 SDK is in 'offline' mode
09:00:58 < majestic> [ puts] linear mode
09:00:58 < majestic> [ puts] Init dev i2c_0!
09:00:58 < majestic> [ puts] ------------- f22 1080p 30fps init ok![16CV300] by gjj --------2016.12.19--------
09:00:58 < majestic> [ hal] HiSi_HAL_SetAeTime@893 Exposure: 250ms (4fps), aGain: 32768, dGain: 1024, ispGain: 1024, mode: slow_shutter
09:00:58 < majestic> [ sdk] log_venc_chn@1272 h264 704x576@10fps 4096kbit 10gop
09:00:58 < iq_monitor> [ sdk] monitor_thread@314 Loading IQ profile /etc/sensors/iq/jxf22.ini
09:00:58 < majestic> [ sdk] create_vpss_chn@1002 venc_chn: 0, vpss_grp: 0, vpss_chn: 0
09:00:58 < majestic> [ sdk] start_video@1944 venc took 1484KB of MMZ [198]
09:00:58 < majestic> [ sdk] log_venc_chn@1272 h264 704x576@15fps 1024kbit 15gop
09:00:58 < majestic> [ sdk] create_vpss_chn@1002 venc_chn: 1, vpss_grp: 0, vpss_chn: 1
09:00:58 < majestic> [ sdk] start_video@1944 venc took 1484KB of MMZ [198]
09:00:58 < majestic> [ sdk] log_venc_chn@1272 MJPEG 704x576@5fps 50q
09:00:58 < majestic> [ sdk] create_vpss_chn@1002 venc_chn: 2, vpss_grp: 0, vpss_chn: 2
[Func]:HI_MPI_ISP_QueryExposureInfo [Line]:920 [Info]:Get Active Stat Buffer Err
09:00:58 < iq_monitor> [ sdk] monitor_thread@333 Query exposure info
09:00:58 < iq_monitor> [ sdk] monitor_thread@333 Unknown error code FFFFFFFF
09:00:58 < majestic> [ sdk] start_mjpeg@1397 mpeg_enc took 2052KB of MMZ [2040]
09:00:58 < majestic> [ sdk] start_sdk@551 HiSilicon SDK started
09:00:58 < majestic> [ hal] hisi_free_mem_ex@753 Free MMZ mem finally: 9588KB
09:00:58 < majestic> [ rtsp] rtsp_init@28 RTSP server started on port 554
[Func]:HI_MPI_ISP_QueryExposureInfo [Line]:920 [Info]:Get Active Stat Buffer Err
09:00:59 < majestic> [himetric] dump_sdk_metrics@70 HI_MPI_ISP_QueryExposureInfo
09:00:59 < majestic> [himetric] dump_sdk_metrics@70 Unknown error code FFFFFFFF
09:01:00 < majestic> [ sdk] venc_read@922 Timeout from venc channel 0
09:01:00 < majestic> [ sdk] venc_read@922 Timeout from venc channel 1
[Func]:HI_MPI_ISP_QueryExposureInfo [Line]:920 [Info]:Get Active Stat Buffer Err
09:01:01 < majestic> [himetric] dump_sdk_metrics@70 HI_MPI_ISP_QueryExposureInfo
09:01:01 < majestic> [himetric] dump_sdk_metrics@70 Unknown error code FFFFFFFF
Activity
widgetii commentedon Oct 4, 2026
Majestic starts and the sensor reports a successful init, but the video input never receives a frame (
vicap-state: downin ipctool), so the fault is in how the JXF22 is brought up on Hi3516CV300: the load script's pinmux and clock, the sensor.ini, or the DC versus MIPI variant. Those live in the firmware tree, so this is moving to OpenIPC/firmware.openipc-ai commentedon Oct 15, 2026
The log points at how the sensor is wired up at boot, not at the streamer: the JXF22 driver loads and reports
init ok, but the video input never receives a frame (vicap-state: down), and theQueryExposureInfoandTimeout from vencerrors all follow from that.On first boot the sensor is auto-detected and stored in the U-Boot environment as
jxf22_i2c. Inload_hisiliconfor hi3516cv300, thejxf22_i2centry sets the sensor pins up for MIPI (with clocks copied from the hi3516ev100 profile). The only JXF22 driver and profile shipped for this chip are for the parallel (DC) variant, which thejxf22_i2c_dcentry wires correctly. With MIPI pinmux, the parallel data lines never reach the video input, which would give exactly this picture.Could you try this and report back?
If the picture comes up after that, we'll correct the
jxf22_i2centry so auto-detection gets it right. If it still fails, please attachlogreadandipctooloutput from after the reboot. We don't have a Hi3516CV300 with this sensor to test on ourselves, so your result decides the fix.