Skip to content

hi3518ev300_lite_bathhouse: rename to yuancam-dgk423403 - #153

Merged
widgetii merged 1 commit into
masterfrom
hi3518ev300-lite-yuancam-dgk423403
Sep 11, 2026
Merged

hi3518ev300_lite_bathhouse: rename to yuancam-dgk423403#153
widgetii merged 1 commit into
masterfrom
hi3518ev300-lite-yuancam-dgk423403

Conversation

@widgetii

Copy link
Copy Markdown
Member

Summary

  • Renames the hi3518ev300_lite_bathhouse device profile to hi3518ev300_lite_yuancam-dgk423403. The placeholder "Bathhouse" name was a joke/stub; on a physical lab unit of this exact board (HI3518EV300, RTL8188FU_USB, NOR_8M — matches the existing profile's spec) I identified the real OEM branding from /mnt/userdata/config/Factory.bin and SysParam.bin, which both carry a YuanCam* tag, plus the camera's own P2P device id DGK-423403-YZHGE.
  • Fills in the sensor in the README table (?JXH62), identified on hardware via ipctool -s.
  • Updates customizer.sh's fw_setenv upgrade URL to match the renamed release asset name.
  • No functional change to the defconfig: it already builds with BR2_PACKAGE_RTL8188FU_OPENIPC=y only (no r8188eu/mt7601u), which is correct for this board's actual Wi-Fi chip (Realtek RTL8188FU, confirmed via lsusb/lsmod on hardware).
  • Excludes list filename intentionally left as hi3518ev300_lite.list (named after soc+flavor, not the device, per repo convention).

Sensor (JXH62) support isn't wired into hisilicon-opensdk.mk for the hi3516ev200 family yet, so this stays research status in the table rather than claiming video works — that's separate, larger work not included here.

Test plan

  • ./builder.sh hi3518ev300_lite_yuancam-dgk423403 resolves the device tree correctly (defconfig/customizer/excludes all present and named per convention).
  • Full cross-build not run locally (mechanical rename of an existing, previously-building profile; no defconfig content changed).
  • Hardware identification (ipctool -c/-s, lsusb, lsmod, Factory.bin/SysParam.bin strings) performed on a physical lab unit of this board over telnet.

The device is a YuanCam-branded (HQLS/hdwificam OEM) HI3518EV300 board —
confirmed on a lab unit via its Factory.bin/SysParam.bin tags
("YuanCamFactory"/"YuanCamSysparam") and its P2P device id
(DGK-423403-YZHGE). Rename the placeholder "Bathhouse" profile to a
proper vendor-model name and fill in the sensor, identified on hardware
with ipctool as JXH62 (previously "?" in the README table). The
defconfig, customizer.sh and excludes list carry over unchanged except
for the upgrade URL, which now points at the renamed release asset.
@qodo-free-for-open-source-projects

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can switch off images and animations for a plain-text comment

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@qodo-free-for-open-source-projects

Copy link
Copy Markdown

PR Summary by Qodo

Rename Bathhouse profile to YuanCam DGK-423403

⚙️ Configuration changes 📝 Documentation 🕐 10-20 Minutes

Grey Divider

AI Description

• Renames placeholder Bathhouse profile to verified YuanCam DGK-423403 hardware identity.
• Records the hardware-identified JXH62 sensor while retaining research status.
• Aligns firmware upgrade assets with the renamed device profile.
Diagram

graph TD
  A["Builder CLI"] --> B["YuanCam profile"] --> C["Buildroot config"]
  B --> D["Customizer script"] --> E["Upgrade setting"] --> F["Release asset"]
  B --> G["Excludes list"]
  H["Device catalog"] --> B
Loading
High-Level Assessment

The direct profile rename is the appropriate approach because the previous name was only a placeholder and the hardware identity is now verified. Retaining an alias or duplicate profile would preserve misleading naming and create configuration drift; keeping the shared excludes filename unchanged correctly follows the repository's SoC-and-flavor convention.

Files changed (4) +2 / -2

Documentation (1) +1 / -1
README.mdDocument YuanCam identity and JXH62 sensor +1/-1

Document YuanCam identity and JXH62 sensor

• Replaces the placeholder Bathhouse entry with YuanCam DGK-423403 and records the hardware-identified JXH62 sensor. The device remains marked as research because sensor support is not yet integrated.

README.md

Other (3) +1 / -1
hi3518ev300_lite_yuancam-dgk423403_defconfigRename the YuanCam Buildroot defconfig +0/-0

Rename the YuanCam Buildroot defconfig

• Carries the existing HI3518EV300 lite Buildroot configuration into the renamed device profile without changing its package or hardware settings.

devices/hi3518ev300_lite_yuancam-dgk423403/br-ext-chip-hisilicon/configs/hi3518ev300_lite_yuancam-dgk423403_defconfig

customizer.shPoint upgrades to the renamed YuanCam asset +1/-1

Point upgrades to the renamed YuanCam asset

• Updates the boot environment upgrade URL to reference the firmware archive generated for the renamed YuanCam DGK-423403 profile. Existing Wi-Fi and media customization remains unchanged.

devices/hi3518ev300_lite_yuancam-dgk423403/general/overlay/usr/share/openipc/customizer.sh

hi3518ev300_lite.listCarry exclusions into the renamed profile +0/-0

Carry exclusions into the renamed profile

• Retains the existing HI3518EV300 lite exclusion list under the renamed device directory. Its SoC-and-flavor filename remains unchanged by repository convention.

devices/hi3518ev300_lite_yuancam-dgk423403/general/scripts/excludes/hi3518ev300_lite.list

@widgetii
widgetii merged commit 3bd11b9 into master Sep 11, 2026
113 of 117 checks passed
@widgetii
widgetii deleted the hi3518ev300-lite-yuancam-dgk423403 branch September 11, 2026 17:22
openipc-ai pushed a commit that referenced this pull request Sep 11, 2026
… Wi-Fi) (#152)

The first ssc337de_lite device in the tree to ship an excludes list: it prunes 17 of the 18 sensors OpenIPC/sensors builds for infinity6b0 and keeps sc401ai, the board's own.

Wi-Fi is an MT7601U on the vendor STA driver, so the device carries its own /etc/wireless/usb with the gpio 14 power cycle ahead of the modprobe, and execs modprobe so the profile's exit status is the module's rather than an unconditional success. The overlay is registered in .github/firmware-drift.json against the current firmware blob rather than left to drift silently.

Built green on CI before a rebase over #151 and #153, which collided only on the README device table.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant