Repository navigation
Description
Report
Sharing the findings from a HeimVision PE3020-W port investigation, following the firmware repository's guidance that retail-device profiles belong in builder. This is early board-support work, not a working builder profile, a flash-ready image or a reproduced regression in a current official release.
Related work:
- Anyka AK3918Ev200 firmware#207: historical Anyka boot/partition discussion, now closed because the old build is obsolete.
- ak3918ev300: OpenIPC U-Boot (anyka) boots on real hardware from RAM, but long
sf readintermittently returns shifted data firmware#2639: the EV300 tracker and TC100/F23 hardware findings. - anyka: EV300 capture -- vendor tunings, ISP lifecycle, MIPI pads and the JX-F23 linux#190: merged EV300 tuning, ISP lifecycle and MIPI/F23 corrections.
These are useful references, but the TC100's sensor, wiring and memory assumptions should not automatically be applied to this board.
Hardware identification
- Camera: HeimVision PE3020-W.
- Photographed SoC marking:
AK3918EN064 / V300-J. - PCB identifier:
AK3919EV300_V601_F37. - Stock runtime board label:
AK3919Ev300(V310). - Working family identification: AK3918 V300 / EV300-family. The exact
EN064andJsuffix meanings have not been verified against an authoritative marking guide. The PCB/runtime labels are not independent proof of an AK3919 package. - Retained stock observations: ARM926EJ-S / ARMv5TEJ, Linux 3.4.35, F37 sensor ID
0x0f37, RTL8188FU Wi-Fi and 8 MiB Macronix NOR (mx25l6405d, JEDEC0xc22017). - DRAM: stock U-Boot reports 64 MiB. This is separate from Linux's usable-memory accounting and the package suffix.
Relevant saved Telnet results
An authenticated read-only stock-camera session on 8 November 2026 recorded the following. These are sanitized values reformatted from the saved structured session record, not a reconstructed verbatim terminal transcript. They describe that observation, not a fresh check today.
Kernel release: 3.4.35
Architecture: armv5tejl
Linux memory accounting:
MemTotal: 30356 kB
MemFree: 7008 kB
Buffers: 2688 kB
Cached: 7412 kB
Slab: 4240 kB
Stock driver bindings:
eth0 -> ak_ethernet
wlan0 -> rtl8188fu
wlan1 -> rtl8188fu
Selected loaded modules:
8188fu, otg_hs, akmci, ak39_top_wdt, ak_info_dump, akcamera
sensor_f35, sensor_f37, sensor_sc2145, sensor_sc2232,
sensor_sc2235, sensor_sc4236, sensor_sh2232
Seven sensor modules were loaded, so sensor_f37 being present is not by itself active-sensor identification. Likewise, stock driver bindings do not validate replacement-kernel drivers, and watchdog-module presence does not establish its armed state.
The same session recorded these partition capacities; all reported an erase size of 65,536 bytes. Physical offsets below were reconciled separately against the retained partition-layout evidence, not inferred from a firmware-upgrade file.
Partition Start End Bytes
boot 0x000000 0x060000 393216
ENV 0x060000 0x070000 65536
MAC 0x070000 0x080000 65536
KERNEL 0x080000 0x200000 1572864
ROOT 0x200000 0x300000 1048576
USR.SQUASH 0x300000 0x780000 4718592
USR.JFFS2 0x780000 0x800000 524288
Total 8388608
Ends are exclusive. These are physical NOR offsets, not offsets within an update package or flashing instructions. Partition metadata and saved backups do not establish a successful restore test.
Concrete size mismatch: 1.5 MiB is the flash kernel slot, not RAM
The official openipc.ak3918ev300-nor-lite.tgz archive inspected on 11 November 2026 was 6,526,789 bytes:
Archive SHA-256:
4d44ffecb91ceffb77616860367d80e35b587b1f9e5430f00b9f7e57e7327bf2
uImage.ak3918ev300:
size: 1638128 bytes
SHA-256: e238a3dc5c7c93c6381e852bc7c54e9a51be95aace59560caa5d64284e4fbafc
rootfs.squashfs.ak3918ev300:
size: 4931584 bytes
SHA-256: 1201cd721aaa274c3146d49b1199f9a6f12532c5c6a02933834df5fd323bffa0
The recorded archive matched the verified official-release digest; the included MD5 checks and kernel header/data CRCs passed. The hashes identify this exact snapshot rather than a moving latest release.
1,638,128 - 1,572,864 = 65,264 bytes over the stock kernel partition. The inspected image's DT uses a generic 2 MiB kernel / 5 MiB rootfs layout, not this camera's stock split. An image fitting an 8 MiB NOR in its intended layout does not mean it fits these individual stock partitions. Trimming userspace/rootfs packages alone cannot fix the separate kernel-slot overflow.
This blocks direct flashing into the existing stock slot. It does not by itself rule out a separately reviewed RAM test or prove that a smaller build is impossible. No validated repartitioning recipe for this board is claimed.
Memory layout is a separate problem
Saved stock-kernel analysis identifies:
- A 30 MiB media pool at
0x80000000–0x81e00000. - A 34 MiB Linux bank, before kernel reservations, at
0x81e00000–0x84000000.
The stock reserved_mem_size sysfs getter returns a compiled 30 MiB constant; that reading alone is not an allocation measurement. The placement above also relies on retained stock platform/ION data. Linux's 30,356 kB MemTotal is not the total physical DRAM or available staging space.
The inspected official kernel instead declares 64 MiB starting at 0x80000000, with a 24 MiB media reservation at 0x81400000, and its zImage decompresses at 0x80008000. Changing only the outer load address does not move that decompression destination into the stock upper bank. The generic layout is not necessarily wrong; mixing assumptions from the two layouts is the problem. Physical loader work areas, inherited DMA and RAM ownership still need qualification.
Results on the physical camera
A custom OpenIPC-derived Linux 4.4.302 diagnostic kernel/root reached a deliberately held PID1 endpoint through a RAM boot. The newer diagnostic container was 1,572,512 bytes, with reported full-transfer CRC32 87ecda6b; the supplied log identified IPC86-DIAG-UART-UNQUALIFIED and reached:
RAMROOT UNPROVISIONED/UNQUALIFIED: management held closed
This test intentionally did not provide a shell, network management or native video. Its serial transcript was incomplete/interleaved, so it does not establish clean UART, complete mount success, sustained stability or absence of every warning. After power-cycling, I confirmed stock discovery and live, updating video returned. This is an observed return to stock operation, not proof of recovery from every failure mode or a full flash-content readback.
Separately, a stock-preserving HTTP-to-RTSP bridge displayed real 640×360 H.264 video in VLC. That uses the vendor capture/encoder and is not evidence of native OpenIPC capture or encoding.
Static and emulator findings
- The retained encoder path uses
AKV_Encoder_*/AL_*and the0x20020000UIO register window, consistent with the Allegro distinction in firmware#2639. - The high-level VI/VENC functions are inside the retained
anyka_ipcexecutable rather than matching exports in its shared media library. A generic SDK wrapper is not a drop-in replacement. - The stock capture interface reports
YUYVwhile using 3/2-byte-per-pixel sizing and compound main/sub buffers. It cannot safely be treated as ordinary packed YUYV without validating the actual pixel layout. - Controlled tests using unchanged official EV300 kernel code and official BusyBox/musl reached a held userspace endpoint in QEMU only, with diagnostic DT/root changes. Normal startup and its overlay erase/format paths were excluded. These are not full official-firmware boots on the camera.
- Anyka sensor/ISP/encoder operation, Wi-Fi and physical DMA/timing are not established by these emulator results. We have no independently decoded native replacement-encoder output.
Still unqualified
- Native F37 capture with correct tuning, format, lane/reset configuration and repeatable stop/restart.
- Native Allegro encoding, correlated completion and decoded output matching known input.
- Capture/encoder buffer ownership, cache coherence and DMA stop behavior.
- Replacement-kernel RTL8188FU operation.
- Exact official-kernel handoff, memory ownership and repeatable recovery.
- A complete builder profile and usable native OpenIPC firmware.
We have not reproduced firmware#2639's original long sf read corruption on this board and are not claiming it is fixed.
Questions for maintainers
- Is there an existing EV300/F37 profile or comparable board that should be the starting point for a PE3020-W profile?
- Is there a maintained EV300 configuration intended to fit a 1,572,864-byte stock kernel slot, or is a separately qualified layout migration the expected route? We have not found a verified current replacement fitting this exact slot.
- Has the shared F2x/F37 driver been validated with F37 tuning since linux#190? Which F37-specific parameters still need independent confirmation?
- Is there a documented transition from this stock lower-media/upper-Linux memory arrangement to the generic OpenIPC layout?
- Is there an active EV300 Allegro encoder effort or licensed low-level implementation to coordinate with?
- Which additional board evidence would be most useful before proposing a minimal device profile?
Activity
openipc-ai commentedon Nov 11, 2026
Thanks for the careful write-up. Answers against the current trees (firmware
9d78191, linuxanyka-ak3918ev300@aa316c2):1. Starting point. No Anyka board has a builder profile yet. The base is firmware's
br-ext-chip-anyka/configs/ak3918ev300_lite_defconfig. It already listsak3919ev300as an alias, shipsRTL8188FU_OPENIPC, and its kernel config builds the sharedSENSOR_F22_F23_F28_F35_F37driver in. The nearest boards anyone has worked on are the TECKIN TC100 (EV300 + JX-F23, firmware#2639, which linux#190 came from) and the Victure PC420 (EV300 + JX-F37, dmesg only). A PE3020-W profile would bedevices/ak3918ev300_lite_heimvision-pe3020w/withbr-ext-chip-anyka/, a customizer and an exclude list.2. The 1,572,864-byte slot. Nothing targets it, and we don't plan to. The kernel is the smaller part of the mismatch. The stock root is split into ROOT (1 MiB) and USR.SQUASH, but the OpenIPC rootfs is one 4.9 MB squashfs, so even a trimmed kernel would leave nowhere to put it. OpenIPC uses its own layout on every platform:
256k(boot),64k(env),2048k(kernel),5120k(rootfs),-(rootfs_data). That is set in the EV300 DT bootargs and matches the OpenIPC U-Boot for this SoC,u-boot-ak3918ev300-nor.bin(219,748 bytes, from theopenipc-anykabranch of OpenIPC/u-boot, in thelatestfirmware release). So the route is to replace U-Boot and repartition, not to fit the stock slots. The vendor env sits at 0x60000 and the OpenIPC env at 0x40000, and the stock boot partition is 384 KiB against OpenIPC's 256 KiB. Take a programmer-level full dump before writing anything.3. F37 since linux#190. It has not been validated. linux#190 was checked against the TC100's F23 reports, and the lab has no EV300 hardware. On F37, nothing in it is specific to that sensor. Still open on the branch:
anyka/isp.conf.S_PARMreturns EINVAL.For the F37 we would need the MIPI lane count and data rate, the I²C address, the reset GPIO and the stock tuning file (
isp_f37*.confor similar from the vendor rootfs).4. Memory layout. No transition is documented, and none is needed once the OpenIPC U-Boot owns the boot. The OpenIPC image assumes the kernel at the bottom (
0x80008000) and the DT's 24 MiB media carve-out at0x81400000. It does not try to coexist with the stock layout, where the media pool is at the bottom and Linux is at the top. As you say, mixing the two layouts is the trap. RAM-booting the OpenIPC kernel from stock U-Boot works only as far as stock U-Boot leaves that memory alone. EV200 has since moved its video memory to amem=-based osmem split (linux#186, firmware#2796), but EV300 hasn't yet.5. Encoder. There is no Allegro encoder driver, and as far as I know nobody is working on one. EV300 also has no osdrv/streamer package in firmware yet (EV200 got
anyka-osdrv-ak3918ev200+ak-camin firmware#2796). The EV300 lite image therefore boots to network/Wi-Fi/V4L2 capture but has no native video stream. A profile for this camera would be honest about that.6. Most useful evidence, in order:
ak3918ev300image under the OpenIPC U-Boot, RAM-booted first.With 1 and 3 a minimal profile (Wi-Fi + GPIOs) is reasonable now. Video still waits on the EV300 osdrv/encoder work.
steezywee commentedon Nov 12, 2026
Update from the physical PE3020-W: we now have native F37 raw capture working in bounded RAM-only OpenIPC tests. Here is the evidence against your requested list, with the remaining gaps called out.
1. Recovery dump and boot environment
/proc/mtdwas empty. Ethernet DHCP and file transfer worked.2. Board GPIO findings
The saved vendor Linux 3.4.35 kernel has board/platform data rather than an exposed runtime device tree. Static decoding and the physical tests give:
-1) in the V310/version-6 sensor descriptorboot0)wifi_power=5,led=5,ir=1The camera is fixed, not PTZ. No motors or SD slot have been found. The IR circuitry is on a daughterboard; observed IR illumination should not be treated as proof of a separate GPIO-controlled IR-LED line.
A relevant conflict: the generic OpenIPC DT used sensor reset GPIO49 and assigned GPIO79 to the audio/speaker path. Our board-specific RAM test uses sensor reset GPIO79 and disables the conflicting audio node. With that combined change, staged sensor IDs stayed
0x0f/0x37through native initialization instead of becoming0xff/0xff. This is a board-specific finding, not a proposed GPIO change for all EV300 cameras.3. F37 interface and tuning
0x40, represented as0x80in the vendor callback; one-byte register addresses and values./usr/local/isp_f37_mipi_1lane.conf, 69,556 bytes, SHA-256:2ed7d02c3fe3dba3e96d31312a7b28d858a796ad0254e5fbc110228c2ae6be5c.sensor_f37.ko: 7,148 bytes, SHA-256:9664d2794421f2244a9ab2cc406a7c18341b8df462dcdfdc632ab6d55efd8340.0a=0f, 0b=37, 12=20, 0e=11, 0f=14, 10=3c, 11=80, 6a=28.The tuning file has been extracted and retained; it is not attached to this comment.
4. Native capture and green-tint progress
Our experimental changes are based on OpenIPC/linux
aa316c2c9cc7f19d69a79e0fe3124112334cc1b4.After the reset correction, explicit full-frame crop and main-only output handling produced real 1920×1080 NV12 frames, 3,110,400 bytes each. The main-only path avoids enabling the secondary output without its buffers. Exposure required warm-up; a bounded capture discarding 125 frames before saving one produced a substantially brighter image.
We also found a statistics-layout mismatch relevant to the reported green tint: at 1080p the ISP configures 24 motion-statistics rows, while the readers assumed 16. In that layout, AWB starts at byte 4640, not 4128; the old read lands inside the motion-statistics tail. The stock implementation selects the offsets by row mode. Updating AWB/AF offsets and motion-statistics readers together substantially reduced the green cast on this camera, without forcing Bayer order or white-balance gains. Residual cool/magenta tint and clipped ceiling-light highlights remain.
These results are raw frame capture, not native Allegro encoding or an RTSP service. Sustained capture, reliable FPS/sequence accounting, stop/restart and DMA/cache lifetime, dual streams, replacement-kernel Wi-Fi, and flash/recovery qualification remain open.
This gives us useful sensor/reset and capture evidence now, while the programmer backup, OpenIPC-U-Boot boot log, and remaining physical GPIO/rate qualification are still outstanding.
openipc-ai commentedon Nov 12, 2026
Thanks, this is a big step. The statistics finding is a real bug in the shared kernel, and I've confirmed it in the source:
ak_isp_vi_set_croppicks 24 motion rows on EV300/EV330 whenever the height divides by 24, while_get_awb_stat_result,_get_af_statand both motion readers were hard-wired to 16. Your 4128 → 4640 is exactly that difference, and with 24 rows the layout fillsDMA_STAT_DATA_SIZE(4800 bytes) to the word.I've opened OpenIPC/linux#199. It keeps the row count
set_cropprogrammed and derives the AF/AWB offsets and the motion loops from it. EV200 stays at 16. It builds for EV200/EV300/EV330, but we have no EV300 hardware to run it on. If you can boot it in place of your own offset change and confirm the cast behaves the same, that would let it merge with an on-camera result attached.On the rest:
ak3918ev300-demb.dts, which other EV300 boards (TC100: reset on 49) depend on. When you're ready, a board DTS that includesak3918ev300-demb.dtsand overrides those two nodes is the right shape.isp_f37_mipi_1lane.confat 69,556 bytes matches the "4.003" layout the loader accepts since zenointel-sd-2n-4g: run the pan/tilt head at 833 us per microstep #190 (the TC100's F23 file is 69,548). Attaching it to OpenIPC/linux or OpenIPC/firmware (an issue or a PR) would let us ship it as the F37 default, the way EV200's tunings ship in/etc/sensor. Vendor tuning blobs are already redistributed there.The OpenIPC U-Boot boot log and the programmer dump are still the gate for anything that writes flash. Everything up to that point can keep going RAM-only.
anyka: EV300/EV330 3A reads AWB and AF from where the ISP wrote them (#…
openipc-ai commentedon Nov 12, 2026
OpenIPC/linux#199 is merged into
anyka-ak3918ev300, the branch the nightly EV300/EV330 kernels build from. Beyond your offsets, it also scales the 3D-NR motion count back to the tunings' 16-row basis, somd_thkeeps its meaning with 24 rows. An on-camera check of a nightly kernel (or of the branch tip) against your own change is still very welcome. If anything differs, it'll be easy to follow up.steezywee commentedon Nov 12, 2026
Original-firmware F37 evidence from a second camera
I have now read another camera running its original firmware with a CH341A programmer. The original full dump is retained privately; this is a different unit from the camera used for the RAM-only development tests, and I am not claiming a tested restore or an OpenIPC-U-Boot qualification.
Attached is an allowlisted engineering-evidence bundle containing only the original F37 tuning file and sensor module, plus a README and checksum manifest:
anyka-f37-allowlisted-evidence.zip
isp_f37_mipi_1lane.conf2ed7d02c3fe3dba3e96d31312a7b28d858a796ad0254e5fbc110228c2ae6be5csensor_f37.ko9664d2794421f2244a9ab2cc406a7c18341b8df462dcdfdc632ab6d55efd8340Both hashes match the files previously extracted from our first camera. The original tuning is included unchanged, rather than the derived tuning used in some RAM tests.
ZIP SHA-256:
693202da743d6ae3436c916060b678f70303744911036354546d05d6f5310c6c.This attachment is not the full dump, not a sanitized firmware image, and not suitable for flashing or recovery. ENV, MAC, writable configuration, credentials and device identifiers are excluded by selecting only these two engineering files. The unmodified programmer dump remains private.
This makes the requested stock tuning and module available for review now. The OpenIPC-U-Boot boot log, independent stock MIPI-rate reconciliation and on-camera comparison against the merged OpenIPC/linux#199 changes remain separate outstanding checks.
openipc-ai commentedon Nov 12, 2026
Thanks, that's exactly what was needed.
isp_f37_mipi_1lane.confandsensor_f37.koall match the SHA-256s you posted.4.003-mp1l-9.7with sensor ID0x0f37, so the loader inak_isp_tuning.caccepts it unchanged.f37_get_parameteranswersGET_MIPI_MHZ= 768,GET_MIPI_LANE= 1, MIPI interface, 3.3 V I/O, andVSYNC_ACTIVE_MS31. Our shared F2x driver has the F37 at 720 Mbps, also 1 lane, so the rate is the one difference. It feeds the THS-SETTLE calculation. Next I'm comparing the stock module's init register table with ours, to confirm the sensor's PLL actually runs at 768 before changing the driver.I'll link both PRs here.
openipc-ai commentedon Nov 12, 2026
Both PRs are up:
anyka-ak3918ev300):sensor_f37.koreports. The F37's register list in the stock tuning sets the PLL to0e=11 0f=14 10=3c 11=80, the values you read live. On EV300, 720 and 768 both give THS-SETTLE 0x89, so your capture shouldn't change.jxf22…jxf37for the part it detects. Until now the kernel never looked in/etc/sensorfor these sensors, and all of them fell back toanyka/isp.conf.anyka-osdrv-ak3918ev300package installs yourisp_f37_mipi_1lane.confunchanged as/etc/sensor/jxf37.conf. I checked it against the kernel's validator: header4.003-mp1l-9.7, ID0x0f37, 2 styles, EV300 module sizes, and 108 sensor register writes.The firmware PR stays a draft until it has run on a camera. Could you RAM-boot a kernel with linux#200, with that file at
/etc/sensor/jxf37.confin your root? The boot log should then containISP tuning /etc/sensor/jxf37.conf, 2 styles(the device prefix may differ). That line, plus whether the picture matches your earlier capture with the stock tuning, is what lets both merge.steezywee commentedon Nov 13, 2026
RAM-only hardware result for linux#200 and the original F37 tuning
We have now run a kernel including OpenIPC/linux#200 on the PE3020-W-V310 camera, with the unchanged original 69,556-byte tuning at
/etc/sensor/jxf37.conf. No fallbackanyka/isp.confwas installed for this test.The requested loader line was observed:
The tuning SHA-256 was:
F37 identification remained valid (
0x0f37). A bounded capture with 125 warm-up frames followed by one saved 1920×1080 NV12 frame completed with exit status 0. The saved frame was 3,110,400 bytes, SHA-256:Picture result: the final capture with the unchanged original tuning looked substantially neutral and good to the camera owner: the strong pink/red cast was largely gone, walls looked neutral and wood looked brown. The lamp highlights were still clipped. This is a visual result report; no image is attached to this comment.
Important limits on the comparison: this was not a controlled, same-boot A/B against the earlier capture. Our RAM kernel also retained the board-specific sensor-reset-on-GPIO79/audio-disabled changes and the capture-path fixes discussed earlier. MMC1 was disabled after it claimed the IR-cut GPIOs 41/42. A bounded day-control pulse completed with both outputs low, but no click was heard and the physical filter position was not independently confirmed. Reboots, lighting/scene changes and that control attempt confound attribution. Earlier tests also included a derived stock-tail tuning; the final result reported above used the original hash shown here, not that derivative.
So we can confirm named original-tuning loading and successful on-camera capture with linux#200, and report a good final picture, but cannot honestly claim isolated PR200-only visual equivalence or a confirmed IR-cut mechanism.
All of this remained RAM-only, with SPI controller/flash initialization blacklisted and an empty MTD listing. This does not qualify the full firmware image, native encoding/RTSP, automatic day/night, flash recovery, or an OpenIPC-U-Boot boot. Those remain separate checks.
steezywee commentedon Nov 13, 2026
Follow-up: supervised IR-cut response on the PE3020-W
We have now observed both directions in the same capture-capable RAM boot: a bounded NIGHT one-shot (GPIO42) and DAY one-shot (GPIO41) each returned status 0 and produced an audible click. Kernel completion logs and output-latch readback confirmed both GPIO41/42 outputs low afterward; cleanup was verified.
A subsequent same-boot IR-remote comparison showed substantially stronger IR bloom in NIGHT than DAY, supporting an optical filtering change in the expected direction. Both NV12 captures were complete at 3,110,400 bytes. This is qualitative evidence only: remote/foreground position and exposure differed, so there is no calibrated attenuation ratio or absolute filter-position measurement.
This extends the prior report beyond the earlier no-click observation. It uses the existing capture image/original tuning, not a new controlled kernel/tuning A/B, and does not establish PR200-only color equivalence. Automatic ADC-driven switching, thresholds/hysteresis, startup behavior and long-term reliability remain unqualified.
Testing remained RAM-only; no flash write or persistent installation. Scene images remain private and are not attached.
steezywee commentedon Nov 13, 2026
Could you point us to the intended RAM-only chainload procedure for the stock
u-boot-ak3918ev300-nor.binfrom vendor U-Boot 2013.10 on this 64 MiB board? In particular, should the ROM-wrapped release be entered directly or does it require a RAM-entry build, and what load/entry addresses and vector mapping should we use? How should resets and the DRAM probe be handled without overwriting the running code or staged images, and how do we keep persistent writes disabled?We haven’t installed OpenIPC U-Boot or repartitioned flash. We have a private CH341A dump from a second original-firmware camera and a verified software dump from the development camera, but not a same-unit programmer recovery qualification.
Would a stock kernel with an explicitly RAM-only diagnostic init be acceptable as an initial log, followed separately by audited stock userspace? We would label it as such.
anyka: JX-F37 at its stock MIPI rate, and per-part tunings for the F2…
openipc-ai commentedon Nov 13, 2026
Thanks, that settles both:
anyka-ak3918ev300(with your result in the commit message), so nightly EV300 kernels name the F37jxf37.ak3918ev300_lite/ak3916ev300_liteship your tuning as/etc/sensor/jxf37.conf.Chainloading the OpenIPC U-Boot from the vendor U-Boot
This comes from the
openipc-anykasource (CLAUDE.md,build.sh,openipc/ak39-image.py) and the released file. Nobody has documented doing it on silicon, so treat it as a procedure to try, not a qualified one.The file.
u-boot-ak3918ev300-nor.binfrom thelatestrelease (219,748 bytes, sha25686bee049…15cc18) is a 512-byte boot-ROM header followed by U-Boot:ANYKA_H3, payload length0x35864, load address0x80E00000;bto offset0x200, so the header also works when entered directly;There is no separate RAM-entry build. The payload is linked at
0x80E00000(SYS_TEXT_BASE) and assumes DDR is already up: no SPL, andlowlevel_initonly ungates clocks and releases resets. That's the state the vendor U-Boot leaves, so the same file works:file[0x200:]at0x80E00000andgo 0x80E00000, or0x80DFFE00andgo 0x80DFFE00.Memory to keep clear (64 MiB part,
PHYS_SDRAM_1_SIZE= 64 MiB;dram_init()probes only within that):0x80700000-0x80800000: early stack and global data (SYS_INIT_RAM_ADDR);0x80E00000+ ~215 KiB: the payload;Run
bdinfoin the vendor U-Boot first and check that itsrelocaddris high in DDR, not at0x80E00000, or the load overwrites the running loader. Stage anything you want to keep at OpenIPC'sbaseaddr,0x82000000.Keeping it from writing flash. This is the important part on a stock layout:
bootdelayis 1 s and the key is Ctrl-C only. The defaultbootcmdisrun bootflash. Atmisc_init_r,firmware_scan()looks for an OpenIPC kernel at flash0x50000, which on your layout is the vendor boot area, so it will setbootfail.bootflashthen runsfwrecovery→fwupd, which tries to fetch images over TFTP andsf erase/sf writethem. With no TFTP server it fails and resets, but don't rely on that: stop at the prompt.saveenv. OpenIPC's environment is at flash0x40000(64 KiB), which is inside your stockbootpartition (0x000000-0x060000). It will report a bad CRC and use the defaults, which is fine, but asaveenvwould overwrite the vendor U-Boot.run fwupd/uk/ur,sf eraseorsf write.firmware_recovery()writes flash on its own if it findsuImage.ak3918ev300.img,rootfs.squashfs.ak3918ev300.imgorscript.txton a FAT card or stick. You said there's no SD slot, so this is just for completeness.sf probe 0andsf readare read-only and fine.The log that's useful is U-Boot's own output up to the prompt (DRAM size, flash ID, the env CRC warning, Ethernet), then
bdinfo,sf probe 0andprintenv. No kernel is needed for it. A stock kernel with a RAM-only diagnostic init doesn't test anything we're unsure of, so I'd skip it. Booting your RAM kernel withbootmfrom0x82000000under this U-Boot is a useful second step.One thing to check before ever writing this U-Boot to flash: the released header's SPI descriptor was taken from a GigaDevice part (JEDEC
c84017), and your flash is a Macronix MX25L6405D (c22017). Chainloading doesn't use it, but the boot ROM does. We'd want to confirm that the ROM reads your flash with that descriptor, or build an image with a matching one, before anything is flashed.anyka-osdrv-ak3918ev300: the JX-F37's stock ISP tuning in /etc/sensor (…
openipc-ai commentedon Nov 13, 2026
OpenIPC/firmware#2830 is merged. From the next nightly,
ak3918ev300_liteandak3916ev300_liteship your tuning as/etc/sensor/jxf37.conf, with a kernel that includes linux#199 and #200. The EV300 image builds at 4828/5120 KB rootfs. The open items are on the bootloader side: the OpenIPC U-Boot chainload log, and the boot ROM's flash descriptor versus your MX25L6405D.4 remaining items
anyka: HeimVision PE3020-W board, the generic EV300 with its own sens…
openipc-ai commentedon Nov 13, 2026
Board support for your camera:
anyka: HeimVision PE3020-W board, the generic EV300 with its own sensor reset linux#204 (merged) adds
ak3918ev300-heimvision-pe3020w.dtson top of the generic EV300 tree. It has your three overrides: sensor reset on GPIO 79 (active low), the codec node off because it also claims 79, and MMC1 off because its pads include the IR-cut GPIOs 41/42. No other image selects it.Add ak3918ev300_lite_heimvision-pe3020w (HeimVision PE3020-W, AK3918EV300, JX-F37, RTL8188FU) #238 adds the builder profile
ak3918ev300_lite_heimvision-pe3020w:rtl8188fu-genericWi-Fi profile;ak3918ev300_lite_heimvision-pe3020w-nor.tgz.It builds locally at uImage 1600/2048 KB and rootfs 4376/5120 KB, so it fits the OpenIPC 8 MB layout.
Two caveats, so expectations are right:
Before flashing, the most useful check is a RAM boot of this image's kernel:
uImage.ak3918ev300from the #238 CI artifact, or from the release once it's merged. Look formodel "HeimVision PE3020-W (AK3918EV300)"and thejxf37.confloader line with the stock device tree replaced. That's the one combination nobody has booted yet.Add ak3918ev300_lite_heimvision-pe3020w (HeimVision PE3020-W, AK3918E…
openipc-ai commentedon Nov 13, 2026
#238 is merged. The next nightly build publishes
ak3918ev300_lite_heimvision-pe3020w-nor.tgz(withuImage.ak3918ev300androotfs.squashfs.ak3918ev300inside) to thelatestandnightlyreleases. That build runs at 03:00 UTC.The check before flashing is the same as before: RAM-boot that
uImage.ak3918ev300and look forHeimVision PE3020-W (AK3918EV300)as the model, plus thejxf37.conftuning line.steezywee commentedon Nov 16, 2026
RAM-boot result from the physical PE3020-W on 2026-11-16: the board-specific official kernel now prints both requested model and tuning-loader lines.
The kernel is the unchanged
uImage.ak3918ev300from the board-profile release archive downloaded on November 16 (kernel build timestamp November 15, 20:42:51 UTC). It was booted with a separate minimal diagnostic RAM root, containing the original F37 tuning file, not the release's normal root filesystem. The diagnostic verifies the model and opens the video device once, retains that descriptor and waits for physical recovery. No STREAMON, capture, encoding or userspace network service was exercised; the tuning-loader message is not proof of image quality or complete tuning application.The actual diagnostic boot arguments are included below. SPI/MMC/watchdog initcalls were blacklisted, and a direct
initrd=argument supplied the RAM root because the vendor loader's prepared tags omitted INITRD2. No flash erase/program orsaveenvcommands were issued; this is not a claim that every pre-diagnostic hardware side effect was ruled out.Below is the complete kernel-boot UART output, including the later USB message, plus the initial and recovery bootloader banners. Only line endings are normalized. Pre-boot transfer/checksum commands and RAM/register inspection output are outside this kernel-boot section and are not included. No kernel-boot lines or sensitive fields were redacted. After physical power-cycle, the fresh stock bootloader prompt was observed again.
Initial bootloader banner:
Complete kernel boot and diagnostic output:
Physical recovery bootloader output:
openipc-ai commentedon Nov 16, 2026
Thanks, this is the result we needed. The released
uImage.ak3918ev300boots on your board with its own device tree (Machine model: HeimVision PE3020-W (AK3918EV300)). The F37 answers on I²C with the GPIO 79 reset (Probing Sensor ID: 0xf37), and the ISP loads/etc/sensor/jxf37.conf. Agreed on the limits you stated: this proves the probe and the tuning load, not image quality.One line that looks like a contradiction but isn't:
#0: Ak ADC DAC pcm input & output module 1still appears withadc_dacdisabled. That card comes fromsound/arm/ak_pcm.c, which registers its own platform device and doesn't use the device tree. The codec driver that would requestspeak-gpios(GPIO 79) is the disabledadc_dacnode, and it didn't probe. The F37 probing and powering on again when the video device opens confirms nothing else holds 79.What this boot left untested, because those initcalls were blacklisted:
ak_spiflash_init): first exercised when the kernel mounts its rootfs from flash.akmci_of_initdidn't run, so this boot couldn't show MMC1 leaving the IR-cut pins alone). Your earlier linux#200 RAM-boot is still the only check of that.So the remaining step is the one that needs your decision: write the OpenIPC U-Boot and the 8 MB layout, then flash this image. Your CH341A dump is the way back.
steezywee commentedon Nov 16, 2026
Thanks for clarifying the remaining released-image checks and the separate ALSA platform-card registration.
A separate milestone is now verified on this camera: a minimal downstream OpenIPC-derived Buildroot RAM root, isolated compatibility runtime and custom RAM kernel completed one bounded real 1920×1080 capture → H.264 → wired RTSP/TCP test. Independent strict decoding verified 396 pictures (16 I / 380 P) over 28.172 seconds of RTP timing, about 14.02 fps. The producer completed 421 frames; the RTSP drop counter reported 18. Physical recovery to the stock loader was observed.
This is NOT a video result from the unchanged released kernel/rootfs or proof of normal full OpenIPC startup. The earlier released-kernel + diagnostic-root boot still proves only the board/sensor probe and tuning-file load. A v4l_querycap capability-metadata warning was nonfatal in this separate RAM run. Protective buffer quarantine remains intentional; physical DMA drain, reusable restart, peak runtime memory and indefinite service remain unqualified.
Your remaining SPI flash/rootfs, MCI1-disable and watchdog checks are still open; this custom RAM test does not close them. No U-Boot, partition-layout or flash changes were made. No private recordings, binary payloads or logs are included here.
openipc-ai commentedon Nov 16, 2026
Good milestone, and noted that it is a separate custom stack, not the release.
The
v4l_querycapwarning is a bug on our side, fixed in OpenIPC/linux#237. Both Anyka camera hosts filledcapabilitiesbut leftdevice_capsempty, and 4.4'sv4l_querycap()WARNs on that every time it is called. The capability bits your application sees don't change.Two questions, since anything you had to change in the kernel to get there is probably something the release kernel needs too:
anyka-ak3918ev300? A patch or a branch link would be enough.anyka: camera hosts report device_caps in VIDIOC_QUERYCAP (#237)
steezywee commentedon Nov 16, 2026
Update from the physical PE3020-W: the official
ak3918ev300_lite_heimvision-pe3020w-nor.tgzdownloaded November 16 (kernel built November 15 at 20:42:51 UTC) now cold-boots from NOR under the installed OpenIPC U-Boot, rather than the earlier diagnostic RAM root.Verified: Linux 4.4.302 reaches the normal OpenIPC shell; the flash-backed squashfs root and writable JFFS2 mount; F37 probes as sensor ID
0x0f37; watchdog registers and MMC0 appears without MMC1; wired DHCP and Dropbear SSH work. Watchdog registration is not a timeout/recovery test, and this does not establish IR-cut operation or image quality.U-Boot read issue: all programmed regions passed byte-for-byte readback under the stock loader. Under the installed OpenIPC U-Boot, a normal 2 MiB kernel-slot read produced CRC32
d6b98befinstead of expected32646e99, withiminforeporting bad data CRC. Reassembling the same slot using 512 reads of 4 KiB produced the expected full-slot CRC and passed the image checksum, twice. A saved small-read boot recipe then succeeded on physical cold boot. This resembles the long-read problem in OpenIPC/firmware#2639; it is a board-tested workaround, not a driver fix. U-Bootresetalso stopped after printing "resetting ..."; physical power cycling was needed.Current userspace: only TCP 22 listens; HTTP/HTTPS/RTSP are not listening. The image does contain BusyBox
httpd, Haserl and WebUI assets in/var/www, but no active HTTP service. Inspection suggests the WebUI expects Majestic's authentication/backend path, so we have not exposed its privileged CGI through barehttpd. No Majestic or RTSP backend was found./dev/video0advertises raw NV12/YUYV, not an encoded stream. No video stream has been verified from this release.The practical goal is RTSP plus a browser management interface, eventually ONVIF. What is the recommended next step now that normal flash boot works?
ak-camis not automatically suitable.We are investigating userspace in parallel without another reflash. Your questions about the earlier custom RAM-kernel delta and buffer quarantine remain separate and unanswered here; this release boot does not establish late DMA after STREAMOFF or explain the earlier precaution.
openipc-ai commentedon Nov 17, 2026
Great result: a cold boot from NOR to a normal OpenIPC shell, with the flash root, JFFS2 overlay, F37 probe, watchdog, MMC0 without MMC1, DHCP and SSH all working.
3. U-Boot first, because the read problem may already be fixed. Which banner does your installed U-Boot print?
2022.10-ge60b740b (Oct 19 2026 …): the build whose SHA25686bee049…you checked on 13 Nov. That build predates ak_sflash: end a read only on TRANSF, as the vendor drivers do u-boot#37 (6675d23f, 20 Oct, "ak_sflash: end a read only on TRANSF, as the vendor drivers do"). Update README.md #37 fixes exactly this symptom: a long read with a 32-bit word repeated, found on the TC100 in ak3918ev300: OpenIPC U-Boot (anyka) boots on real hardware from RAM, but longsf readintermittently returns shifted data firmware#2639. The current release asset is2022.10-g9ff8e687 (Nov 15 2026), SHA2569fc4d149eba57071ad5da58813acb6c81ba5f849bd4338b72829db1bb4df34d8, and it includes Update README.md #37. Whether to rewrite the loader is your call, with the CH341A as the way back. If you do, put the defaultbootcmdback in place of the 4 KiB-read recipe so the normal 2 MiBsf readis what gets tested.g9ff8e687: then Update README.md #37 isn't enough on your Macronixc22017. Please add the CRC and chunk-size results to ak3918ev300: OpenIPC U-Boot (anyka) boots on real hardware from RAM, but longsf readintermittently returns shifted data firmware#2639 rather than opening a new report. It's the same bug on a second board and flash part, and issues are closed on OpenIPC/u-boot.The
resethang (stops afterresetting ...) is separate: please note which build showed it. It belongs in a new issue on OpenIPC/firmware if it survives the current build.1. Web management: no, not on EV300 today. The WebUI in
/var/wwwlogs in by POSTing to/login, and Majestic serves that. Majestic has no Anyka build, so nothing on this image answers it. You were right not to serve the CGIs through bare BusyBoxhttpd: they would run as root with no authentication in front of them. For now SSH is the supported management path. The WebUI files on this image are dead weight until there's a backend.2. Video: there is no OpenIPC EV300 streamer or encoder effort to coordinate with. The EV300 kernel work happens in OpenIPC/linux
anyka-ak3918ev300(capture, ISP, tunings). There is no hardware encoder driver or RTSP/ONVIF userspace for it in OpenIPC. Your compatibility pipeline is the practical interim route. For anything to ship in the OpenIPC image, two things would be needed:anyka-ak3918ev300, which is why I asked about your RAM kernel's delta;ONVIF comes after a working streamer, not before.
ak3918ev300_lite_heimvision-pe3020w: Majestic, with the IR-cut pins (#…
openipc-ai commentedon Nov 17, 2026
The PE3020-W image now has a streamer. Majestic runs on Anyka EV300 and encodes H.264/H.265 and JPEG on the SoC's hardware encoder. Three pieces landed:
http://<camera>/now has a backend;video0.codec h264and the IR-cut pins 41/42.The first image with all of it is tonight's nightly (03:00 UTC):
ak3918ev300_lite_heimvision-pe3020w-nor.tgzinlatest. Nobody has run it on hardware yet, so your camera is the first. Whatever goes wrong, the log is what we need.Before flashing: your installed U-Boot may be the 19 October build with the long-read bug. Either use your 4 KiB-read boot recipe, or update U-Boot first (see my previous comment).
What to check
Kernel, after boot:
It should print one
uio_vcodecline withAllegro encoder at [mem 0x20020000-0x2002ffff], and the ISP pool should be 7 MB.Majestic, in the foreground:
Keep the first ~40 lines. They say how much encoder memory it took, which streams opened at what size and bitrate, and whether the first frame arrived. If it stops there, the last lines are the answer.
Video:
rtsp://root:<password>@<camera>/stream=0(1080p);rtsp://root:<password>@<camera>/stream=1;http://<camera>/image.jpg.A few minutes of the main stream in VLC or ffprobe tells us whether the frame rate holds.
IR-cut:
I set
nightMode.irCutPin1 41andirCutPin2 42from your measurement (41 → day, 42 → night). Which of the two Majestic drives for "night" isn't confirmed on this board. If the filter moves the wrong way, swap them withcli -s .nightMode.irCutPin1 42; cli -s .nightMode.irCutPin2 41and restart Majestic.Stop/restart: run
killall majesticwhile streaming, then start it again. This is where your earlier buffer-quarantine concern would show up. Majestic now releases the encoder on stop, so a second start should work without a reboot.steezywee commentedon Nov 18, 2026
Hardware update on the PE3020-W: the upstream Majestic image now boots from NOR, but video startup is blocked.
Build and installation
nightly-20261117-5fec4d8, merge5fec4d85ca21a5839f2a34a381667a4b67c809d0(the ak3918ev300_lite_heimvision-pe3020w: Majestic, with the IR-cut pins #253 CI artifact, run 44098440117).b0956f093b3f928e77181245f4c3de419a15b8ce; Majesticmaster+bf7058e, built 2026-11-17 13:39.2022.10-ge60b740b. We retained the working 4 KiB-read boot recipe; this does not test the newer loader's long-read fix.Observed on first boot
Linux reaches the flash-backed root/userspace; SSH and HTTP work. F37 probes as
0xf37; Majestic identifies JXF37 and 1920×1080 at 25 fps, then reports:Majestic is actually UID/GID 0, with
CapEff: 0000003fffffffff. TCP 554 is not listening; no RTSP stream or encoded frame has been verified. Majestic owns the 300-second watchdog, so we have not stopped it for the proposed restart test.Working hypothesis, not yet a traced runtime root cause
In the pinned source, ION's
ion_heap_map_user()usesremap_pfn_range()(VM_PFNMAP).mm/pagewalk.c:walk_page_test()skips those mappings through the hole callback, andpagemap_read()has notest_walkoverride. That appears capable of producing zero PFNs even for this privileged process. We have not directly traced the failing allocation to that path.We have kept
mem=64M: the DT separately reserves 7 MiB for ISP and 25 MiB for ION. The legacyrmem: no DRAM above mem=warning alone does not demonstrate a missing video pool.Separately, on the previous November 15 kernel, ordinary
reboothit a NULL dereference at00000004inakpcm_reboot_notify+0x58/0xdc;syncfollowed by SysRqbsuccessfully reset it. We have not tested Linux reboot on this new image, so this is not a regression claim against #253.Could you help with these next steps?
VM_PFNMAPversus pagemap behavior a known incompatibility with this Majestic build? Is there a supported fix or newer matched kernel/Majestic build to test?/etc/custom.ok, while/etc/majestic.yamlis absent. What is the recommended upgrade procedure to apply ak3918ev300_lite_heimvision-pe3020w: Majestic, with the IR-cut pins #253's codec/IR-cut defaults without resetting unrelated configuration?Image quality, streaming, IR-cut operation under Majestic and stop/restart remain untested. The earlier custom RAM-kernel delta and buffer-quarantine questions remain separate; we still have no evidence establishing a late DMA write after STREAMOFF.
steezywee commentedon Nov 18, 2026
Follow-up hardware results: we now have working upstream Majestic video with a RAM-booted patched kernel, not with the unchanged flashed kernel.
What changed and what passed
The test kernel carries four downstream changes: pagemap handling for the ION mapping, NV12 planar-layout handling, three-buffer-backed references, and explicit full-frame input crop. The four-patch uImage is 1,641,824 bytes, SHA-256
8d3cc997adc50bb2e5824d2eeda933c5e6ef038b6a035b80ec56bc740409dee4. A later FLOW build adds diagnostic instrumentation. The pagemap diagnostic now returns native ION PFN0x81b00, versus zero in the baseline. Majestic gets through SDK initialization and serves RTSP/video.A bounded 1920×1080, 25 fps main-stream test independently decoded 751 frames over 30 seconds with zero decode errors. A separate approximately 69.5-second observation saw no new buffer holds or invalid buffer IDs. The 30-second flow diagnostic also saw no new holds (the existing count stayed at 12); completed frames advanced 4882 → 6620 during the longer observation. There were 59 low-buffer warnings during the first three minutes of the earlier run, so this is not a claim that startup is warning-free or that sustained service is qualified. These results do not establish repeatable stop/restart.
Your earlier kernel-delta and buffer-quarantine questions
The older custom RAM/compatibility stack and this newer Majestic test are different builds. The older BOARD2 path explicitly set the crop and used four buffers; our earlier tests also carried the board-specific GPIO79 sensor reset/audio conflict correction, MMC1 disable, main-only capture handling and statistics-layout corrections discussed above. That is a description of verified changes, not yet a complete audited patch series against the current branch. The current RAM test's four changes are listed separately above so they are not mistaken for the older kernel's exact delta.
We have not observed a demonstrated DMA write landing after STREAMOFF. Buffer quarantine was protective while DMA drain/reuse remained unqualified. The current no-new-holds observation does not prove DMA quiescence, and we are not presenting it as evidence that stop/restart is fixed.
Remaining hardware observations and questions
Could you advise:
The patched kernel remains RAM-only; these results do not validate the unchanged installed kernel or justify another flash yet.