ci: add hi3516av200_neo QEMU boot matrix row#192
Merged
Conversation
Follow-up to #191 — adds the QEMU smoke-test row for V3A neo that was deferred from that PR while waiting for the firmware nightly to publish openipc.hi3516av200-nor-neo.tgz. That tarball is now in the latest release (firmware run #26432193560). mem=128M is load-bearing: the V3A load_hisilicon defaults os_mem_size=128M so MMZ starts at 0x80000000 + 128M = 0x88000000 and runs 0x88000000-0x9FFFFFFF (384M). A larger kernel mem= (e.g. mem=256M) would claim 0x80000000-0x8FFFFFFF and overlap MMZ at 0x88000000, tripping `ERROR: Conflict MMZ: PHYS(0x88000000, 0x9FFFFFFF) ... MMZ conflict to kernel memory (0x80000000, 0x8FFFFFFF)` on insmod and cascading into "Unknown symbol" across every consumer module. The 32M append used by cv200/av100/cv300 rows would also work but 128M matches the production OS/MMZ split V3A firmware actually ships. Local verification: downloaded openipc.hi3516av200-nor-neo.tgz from latest release, booted via `qemu-system-arm -M hi3516av200 -m 256M -append 'mem=128M ...'` → boots cleanly to `openipc-hi3516av200 login:`, eth0 DHCP via HiGMAC succeeds (lease 10.0.2.15 from 10.0.2.2). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #191 — adds the QEMU smoke-test row for V3A neo that was deferred while waiting for the firmware nightly to publish
openipc.hi3516av200-nor-neo.tgz. That tarball is now in the latest release.mem=128Mis load-bearing: the V3Aload_hisilicondefaultsos_mem_size=128Mso MMZ starts at0x80000000 + 128M = 0x88000000and runs through0x9FFFFFFF(384M). A larger kernelmem=(e.g.mem=256M) would claim0x80000000-0x8FFFFFFFand overlap MMZ at 0x88000000, trippingERROR: Conflict MMZ: PHYS(0x88000000, 0x9FFFFFFF) ... MMZ conflict to kernel memory (0x80000000, 0x8FFFFFFF)on insmod and cascading intoUnknown symbolacross every consumer module. Themem=32Mappend used by cv200/av100/cv300 rows would also work but 128M matches the production OS/MMZ split V3A firmware actually ships.Verification
Downloaded
openipc.hi3516av200-nor-neo.tgzfrom latest release, booted via:qemu-system-arm -M hi3516av200 -m 256M \ -kernel uImage.hi3516av200 \ -initrd rootfs.squashfs.hi3516av200 \ -append "console=ttyAMA0,115200 mem=128M root=/dev/ram0 rootfstype=squashfs" \ -net nic,model=hisi-gmac -net user,net=10.0.2.0/24openipc-hi3516av200 login:udhcpc: lease of 10.0.2.15 obtained from 10.0.2.2🤖 Generated with Claude Code