Files
VCCPlusOSS/docs/development/MCP_BUILD45_VALIDATION.md

30 lines
1.8 KiB
Markdown

# MCP processor selection — build 45
> Technical evidence extract for the VCC Plus white paper. Only reviewed contracts, mechanisms, methods, results and limitations are retained. Original validation dates and configuration limits remain historical; this export is not a new test run.
## Contract and focused qualification
[Processor selection](MCP_PLAYTEST_PROCESSORS.md) documents toolset 8's optional
canonical CPU, MC6809 default, normalized retry identity, actual CPU/mode/MD
reporting and 6309-only debugger registers. CPU selection is fixed for the run;
guest code controls native mode. Existing ownership, executable guards, bank
checks, budgets, keyboard release and retained-media protections remain intact.
- **107 selected XCTest cases passed per host architecture**, arm64 and x86_64
under Rosetta, with zero failures or skips. Suites: `CMOCBuildServiceTests`,
`CMOCVariableDebugTests`, `MCPPlaytestTests` through the VCCMac scheme.
- Real 512 KB guests exercised both CPUs: artifact/global bytes, verified flat
stops, frame/audio metadata, bounded input, retries, cold restart and retention.
A separate authored 6309 guest executed LDW/TFR and LDMD, exposing actual
E/F/W/V/MD values and native mode; a pre-LDMD stop after cold restart proved
MD zero and emulation mode. No host memory/register writes manufactured it.
- Native and Intel/Rosetta helper protocol regressions passed, including toolsets
5/7/8, absent or malformed processor permission, canonical selectors and invalid values.
- The reusable public acceptance fixture/script is checked in. Its new guest
N command compiles with the installed toolchain and executes LDMD only when
deliberately entered in an HD6309 run. Compiler `volatile` support remains
absent and is reported honestly; qualification uses actual observed bytes.