Skip to content

ClearUI C10 — Fusion 6 Multiboot Preview

Choose a tag to compare

View all tags
@killcity killcity released this 10 Sep 23:12
clearui-c10
1d2395b

ClearUI C10 — Fusion 6 multiboot preview

Experimental UV-K1 build based on F4HWN Fusion 6.0.0. This release contains the
same C10-test binary used in the initial on-radio trial, not a newly rebuilt image.
The existing C8c standalone release remains available.

New in this preview

  • Fusion 6 multiboot support: run ClearUI from a user slot alongside compatible
    Fusion, FieldOps, Labs or Transfer editions.
  • Configuration-bank selection under System → Configuration bank.
  • Bank-local ClearUI memories, settings and long group names. ClearUI no longer
    needs to program Main's configuration when running in a separate user bank.
  • A dedicated C10 CHIRP module based on the official v6.0.0 driver, with firmware
    identity checks and updated side-key action mappings.
  • An offline migration tool for legacy ClearUI memories and named groups.
  • Retains the ClearUI VFO layouts, named-group browsing, contextual menus,
    waterfall controls and HF listening mode from the local C9b development baseline.

Download and install

Download clearui-c10-multiboot-test.zip for the firmware, C10 CHIRP module,
migration tool, instructions, checksums, licenses and exact source archive.
Individual firmware and driver files are also attached.

  1. Back up your radio image and calibration first. Keep a known-good recovery image.
  2. With a compatible multiboot firmware running normally, open UV Studio's
    Multiboot section and refresh the slots.
  3. Load ClearUI-C10-test-UV-K1.bin, choose an unused user slot (1–4), and use
    Write to slot. Do not use ordinary flashing if your intent is to preserve
    the existing Main firmware and add ClearUI alongside it.
  4. Hold Menu while powering on, select ClearUI and confirm. Never interrupt power
    while a firmware is being restored.
  5. Keep ClearUI on its separate configuration bank. Slot 1 normally uses bank 1;
    Main normally uses bank 0. Your Fusion channels will not automatically appear
    in a fresh ClearUI bank. That does not mean they have been erased.

Main is the automatically maintained backup of the normally flashed firmware,
not necessarily Fusion. Calibration and the startup logo are shared across banks.

CHIRP and memory migration

Use clearui-multiboot-c10.py with this release, not the C8 or standard Fusion
driver. Select Quansheng → UV-K1 & UV-K5 V3 (ClearUI Multiboot C10).
The inherited model label does not establish UV-K5 V3 hardware validation.

Download a fresh image from C10 in its dedicated bank, then run:

python3 migrate_clearui_multiboot.py old-clearui.img fresh-c10.img migrated-c10.img

The tool copies legacy ClearUI memory channels, names, group memberships, group
names, receive-only and persistent-skip flags. It clears temporary skips and
preserves the fresh target's global settings, VFO state, calibration, logo and
metadata. Reconfigure display preferences and side keys separately. It does not
accept an arbitrary stock Fusion image as the legacy source. Review the migrated
image before uploading it while C10 is running in its separate bank.

Test status and known issues

  • ClearUI and reference Fusion builds pass, with all 13 host test suites passing.
  • The RAM-resident multiboot restore routine passes build-time isolation checks.
  • Initial user testing reports that C10 runs from slot 1 and that Fusion's
    channels remain visible when returning to Main. This is not a complete hardware
    validation or a verified CHIRP write-isolation test.
  • The inherited voltage startup screen still displays F4HWN v6.0.0. Its long
    C10 edition label has a known rendering/bounds defect and may appear misplaced.
    This has not been fixed in the attached, unchanged test binary.
  • A scope-like display in a VFO pane was reported but has not yet been identified
    or reproduced. Dual-watch signal-meter behavior still needs hardware testing.
  • Included package metadata marks hardware validation false, and its instructions
    describe the pre-trial state. The limited on-radio observations above are the
    latest status; neither constitutes a completed validation cycle.

Source commit: 1d2395baf9e4024fea278a08aa1eadf40aac76a8.
Binary size: 113,088 bytes.
Firmware SHA-256: 22feec0cd72d73694fd55091d048d8da09626e35f6efc93deaf006bc848395c5.

Safety and licensing

Experimental firmware. Use at your own risk. It may brick the radio, lose
configuration or calibration, or behave unexpectedly, including on transmit.
No warranty is provided. To the fullest extent permitted by applicable law,
maintainers and contributors disclaim liability for damage, losses, interference
and unlawful use. You are responsible for licenses, authorizations and lawful
operation. This disclaimer does not override rights or liabilities that cannot
legally be excluded. Read the included SAFETY.md before installation.

For the PY32-based UV-K1; do not flash onto older DP32G030 UV-K5/UV-K6 hardware.
No personal channels or calibration are included. Public-safety channels are not
automatically identified or made receive-only by flashing this firmware.

Upstream copyright and license notices are retained. Firmware and bundled
components remain subject to their respective included licenses.

Upstream release: https://github.com/armel/uv-k1-k5v3-firmware-custom/releases/tag/v6.0.0
UV Studio: https://armel.github.io/uvstudio/

Assets 8
Loading