SpezVision SVI-252B K202 on board BLK16CV-0323-38X38-V1.01: HiSilicon Hi3516CV200, Sony IMX323 on the I2C/DC 1080p configuration, 8 MiB SPI NOR, wired Ethernet only. The board's day/night path is what needs describing. The hardware daylight sensor is GPIO3_0 (legacy HiSilicon numbering 24) and the bistable IR-cut filter is GPIO4_2 / GPIO4_1 (34 and 33), which the customizer seeds into majestic. GPIO3_0 has to be muxed to function 0 at 0x200f0034 before it can be read, and load_hisilicon's imx323 branch does not touch that register, so the board ships a muxes.sh for it — S30customizer runs that on every boot, independently of which streamer is in use, so the pin contract holds for anything running on the camera. No backlightPin is set: a separate software-controlled IR illuminator GPIO was not proven on this board. Rather than forking the whole hi3516cv200.generic.config into the device directory the way the other CV200 profile does, the board carries a kernel config fragment naming only its own hardware facts — no SD/MMC socket, no Wi-Fi radio, no used USB path, NOR only — so it keeps tracking upstream kernel changes instead of shadowing them. This is the first device here to use BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES. Together with an exclude list trimmed to the one sensor this camera has, the image lands at 3956736 B of rootfs, leaving 1256 KB of rootfs headroom and 524 KB of kernel headroom on the 8 MiB layout. Tested on physical hardware by the author: builds, flashes and boots, with IMX323 video, Ethernet, the hardware daylight sensor and automatic IR-cut switching all working. A brief purple frame can still appear during the colour-to-grayscale transition; that is tracked upstream in OpenIPC/majestic#325 and no board-specific workaround is carried here.
3 lines
132 B
Plaintext
3 lines
132 B
Plaintext
# SVI-252B K202 has no removable storage.
|
|
# Override OpenIPC's common /etc/modules (vfat, exfat), so S35modules loads nothing here.
|