You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds a device image for the Misecu XM-63-AI-50W 5MP, reported in OpenIPC/firmware#2853.
The camera
From the reporter's ipcinfo, sysinfo and /proc/mtd in firmware#2853:
SoC XM550, which the firmware builds as xm530 (BR2_OPENIPC_SOC_ALIASES="xm550")
SmartSens SC5332, already handled by load_xiongmai
AltoBeam ATBM6032i USB Wi-Fi (007a:8888), powered through wifi_pdn value=96 (the factory firmware's load chain)
8 MB NOR with the standard 256k/64k/2048k/5120k layout
What this adds
A copy of xm530_lite_anbiux-a8b-3mp (builder#130), which has the same SoC family and radio:
defconfig: the same as the anbiux device, with ATBM60XX (603x, USB) on and MT7601U firmware off.
excludes: drops xm711.ko and compat.ko, the vendor Wi-Fi stack this radio does not use.
customizer: sets wlandev=atbm603x-xm530 (the profile from firmware#2316) and wifipdn=96, plus the upgrade URL. The reporter's night-mode pins are included but commented out (IR LEDs 39, white LEDs 41, IR-cut coils 1 and 2): the board has no light sensor, and the IR-cut coil polarity for majestic is not confirmed yet.
README: a new row, "in progress".
Testing
CI builds the image; check the size line in its log. Not yet run on this camera. The same profile and driver passed on the qemu-bench XM550 twin (WPA2 join, DHCP, ping) when firmware#2316 landed. The reporter's board would be the first real hardware.
• Add an XM550-compatible image for the Misecu XM-63-AI-50W with ATBM603X USB Wi-Fi.
• Configure Wi-Fi power and upgrades while excluding unused modules to fit the 8 MB flash.
• Mark hardware support in progress; night-mode pins remain inactive pending validation.
A separate device profile based on the existing anbiux XM530-family profile fits the repository's device layout and keeps board-specific upgrade settings isolated. Sharing those small files through a new abstraction would add indirection without a clear benefit; hardware validation remains the important next step.
Files changed (4) +103 / -0
Enhancement (1) +72 / -0
xm530_lite_misecu-xm-63-ai-50w_defconfigDefine the XM550-compatible Misecu firmware build+72/-0
Define the XM550-compatible Misecu firmware build
• Adds an XM530-family lite configuration with an XM550 alias, 8 MB flash target, and ATBM603X USB driver. It omits MT7601U firmware and includes the standard Xiongmai and Majestic packages.
1. Wi-Fi factory module chain is not packaged for the camera 📎 Requirement gap≡ Correctness
Description
The new defconfig and exclude list rely only on the OpenIPC ATBM60XX driver and delete xm711.ko
and compat.ko, but the diff adds no factory modules (dwc2/xm_usb0/cfg80211/xm713g), no
/usr/bin/wifi script, and no calibration files. The ticket identifies that factory load chain as
the workaround needed to initialize the ATBM6032i, so the built rootfs would not contain the files
the ticket requires. The PR description says the radio does not use the vendor stack, which departs
from the ticket without evidence; if the ticket's premise still holds, Wi-Fi may fail to initialize
on the first real board, and the author should either package the files or validate the departure on
hardware.
+# This device carries the AltoBeam ATBM6032 (USB) radio; prune the+# wifi stacks it does not use to leave room for the atbm60xx module.+/lib/modules/3.10.103+/xiongmai/xm711.ko+/lib/modules/3.10.103+/xiongmai/compat.ko
Evidence
The exclude list removes xm711.ko and compat.ko and the diff adds no factory Wi-Fi modules,
scripts, or calibration files, so the packaging that rules 2 and 5 require is absent from the
rootfs. The PR's own description says the radio is untested on hardware, so the departure from the
ticket's workaround is unverified.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
Issue description
The PR adds a Misecu XM-63-AI-50W device that relies only on the OpenIPC ATBM60XX driver. It removes xm711.ko and compat.ko via the exclude list and ships no factory Wi-Fi modules, scripts, or calibration files, though the linked ticket (OpenIPC/firmware#2853) says that factory load chain is needed to initialize the ATBM6032i.
Fix Focus Areas
- devices/xm530_lite_misecu-xm-63-ai-50w/general/scripts/excludes/xm530_lite.list[1-4]
- devices/xm530_lite_misecu-xm-63-ai-50w/general/overlay/usr/share/openipc/customizer.sh[12-13]
Recommended Fix
Either place the required factory modules, /usr/bin/wifi, and calibration files under general/overlay/ (not via an overridden BR2_ROOTFS_OVERLAY), confirm them in the built rootfs with unsquashfs, and keep xm711.ko/compat.ko if the chain needs them. Or, if the OpenIPC driver path is intentionally used, state in the README/PR that the factory chain is superseded and cite the evidence. Either way, do not claim Wi-Fi works until the build is verified on hardware.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Tip of the day
💡 Did you know, you can reply 'qodo' on any finding to push back, ask questions, or dig deeper
On Qodo's "factory module chain is not packaged" finding: this is intentional, and I'm not changing it.
The factory modules can't ship here.dwc2.ko, xm_usb0.ko, xm713g.ko, the factory cfg80211.ko and the calibration files were taken from the camera's stock image, and there is no source to rebuild them. OpenIPC does not ship binaries it can't rebuild from source.
The reporter's reason for using them no longer holds. In firmware#2853 they used the factory chain because atbm60xx "does not build against kernel 3.10". It does now: this PR's CI built atbm603x_wifi_usb.ko from source against the xm530 kernel, using the same pinned atbm_60xx revision as builder#130.
The factory cfg80211.ko is what firmware#2316 removed. It overwrites the kernel's own cfg80211, which breaks mac80211. The open driver loads against the kernel's cfg80211, through dwc_otg and wifi_pdn value=$wifipdn in the atbm603x-xm530 profile.
xm711.ko and compat.ko are a different vendor stack, for the XM711 radio. The ATBM chain never loads them.
It is tested on the twin, not on hardware. The image passed on the qemu-bench XM550 twin (WPA2 join, DHCP, ping). It has not run on this camera yet, and the README row says "in progress". I've asked the reporter in firmware#2853 for dmesg and ip addr from their board.
The CI build fits: uImage 1180/2048 KB, rootfs 4096/5120 KB.
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
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.
Adds a device image for the Misecu XM-63-AI-50W 5MP, reported in OpenIPC/firmware#2853.
The camera
From the reporter's
ipcinfo,sysinfoand/proc/mtdin firmware#2853:BR2_OPENIPC_SOC_ALIASES="xm550")load_xiongmaiwifi_pdn value=96(the factory firmware's load chain)What this adds
A copy of
xm530_lite_anbiux-a8b-3mp(builder#130), which has the same SoC family and radio:xm711.koandcompat.ko, the vendor Wi-Fi stack this radio does not use.wlandev=atbm603x-xm530(the profile from firmware#2316) andwifipdn=96, plus the upgrade URL. The reporter's night-mode pins are included but commented out (IR LEDs 39, white LEDs 41, IR-cut coils 1 and 2): the board has no light sensor, and the IR-cut coil polarity for majestic is not confirmed yet.Testing
CI builds the image; check the size line in its log. Not yet run on this camera. The same profile and driver passed on the qemu-bench XM550 twin (WPA2 join, DHCP, ping) when firmware#2316 landed. The reporter's board would be the first real hardware.