Skip to content

x4prosim: BM8563 offset property to set the clock at runtime - #8

Merged
prokrypt merged 1 commit into
x4prosimfrom
claude/project-thread-fcc16q
Oct 15, 2026
Merged

prokrypt merged 1 commit into
x4prosimfrom
claude/project-thread-fcc16q

Conversation

@prokrypt

Copy link
Copy Markdown
Owner

Before: the emulated BM8563 clock could only be set at launch (-rtc base=) or by a guest write, so a run could not move from "clock never set" to "clock set" without NTP, which the sandbox can't reach.

After: qom-set /machine/bm8563 offset <seconds from host time> moves the clock at runtime, like an NTP sync would.

How: a uint64 QOM property on the existing offset field (a build check makes sure time_t is 64-bit). The X4PROSIM.md RTC row documents it. Used to test the CrossDink battery log's clock_set path: started at 2000-01-01, set the offset mid-run, and a clock_set row followed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01G44vPUbRgJCwaepYdHhWs7


Generated by Claude Code

qom-set /machine/bm8563 offset <seconds from host time> moves the RTC the
way an NTP sync would, so a run started with -rtc base=2000-01-01 can
check firmware behavior before and after the clock is set without network
time. Used to test the CrossDink battery log's clock_set path.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G44vPUbRgJCwaepYdHhWs7
@prokrypt
prokrypt merged commit b18d64b into x4prosim Oct 15, 2026
24 checks passed
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.

2 participants