Files
StarForth/src
Robert Allan JamesandClaude Sonnet 5 a88c004ecb Artemis Milestone 2g: CBW construction and send for SCSI READ(10)
First real use of the bulk Transfer Rings Configure Endpoint wired up.
xhci_bot_send_read10() builds a 31-byte Command Block Wrapper (USB Mass
Storage Class Bulk-Only Transport spec section 5.1) and submits it as a
single Normal TRB on the bulk OUT ring via a new
xhci_bulk_out_enqueue_and_ring() helper -- a CBW is always exactly one
TRB, so unlike the EP0 helper this one rings its own doorbell rather
than leaving that to a caller assembling a group.

usb_bot_cbw_t is a real struct (every field up to the CDB array is
naturally aligned, and this driver's targets are all little-endian
already assumed everywhere else), but its DMA length is the explicit
USB_BOT_CBW_LENGTH (31) constant, never sizeof(*cbw), since the
compiler may pad the struct to 32 bytes. The SCSI READ(10) CDB itself
is written byte-by-byte since its LBA/Transfer Length fields are
big-endian on the wire, unlike everything else in this driver -- the
one place two byte orders are both live in the same function.

Completion is correlated via the existing pending_transfer_slot_id/
transfer_purpose gate (new XHCI_XFER_CBW_SENT purpose) -- no
ring-specific dispatch needed, since this driver's single-outstanding-
transfer scope already implies which ring produced an event.

This covers construction and send only (one third of a full READ(10):
CBW -> Data-In stage -> CSW) -- reading the Data-In stage and CSW
receive/validation are separate, explicitly not-yet-implemented items.

Verified live via a temporary probe (written, run once, log captured,
reverted per this project's own probe convention) -- all three
architectures, byte-identical: CBW submitted -> CBW send completed,
then a clean disconnect even with the Data-In stage never drained
(confirms no wedge on a dangling BOT transaction). Probe-free
re-verification afterward on all three architectures.

FABRIC-2.md Section X Milestone 2g's CBW checklist item marked done.
Also records a monitoring gotcha hit three times this session: `ls -t`
over the logs/ tree can return a stale leftover log from an earlier
run in the same session -- fixed going forward by reading the log path
off the actual running QEMU process's own command line instead, and a
memory note added so it doesn't recur next session.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R4VMX6VSKCten8nGgaMkq4
2026-08-25 09:07:33 -04:00
..
2026-08-01 07:49:56 -04:00
2026-08-01 07:49:56 -04:00
2026-08-01 07:49:56 -04:00
2026-08-01 07:49:56 -04:00

src/

Hosted StarForth VM implementation (compiled by the root Makefile). Bare-metal kernel sources live in src/starkernel/; FORTH word implementations in src/word_source/; the test harness in src/test_runner/; platform shims in src/platform/.

Entry point / interpreter core

  • main.c — CLI entry point, VM init, DoE mode dispatch.
  • vm.c — interpreter loop, stacks, dictionary state (the central runtime file).
  • vm_api.c — external VM API implementation.
  • vm_bootstrap.c — VM bootstrap initialization.
  • vm_debug.c — debugging utilities.
  • vm_time.c — time-related VM operations.
  • vm_internal.h — internal-only declarations shared across the vm_*.c files, not part of the public include/vm_api.h surface.
  • repl.c — REPL read-eval-print loop.
  • cli.c — CLI argument parsing.
  • io.c — I/O operations.
  • log.c — logging infrastructure.

Memory / dictionary / blocks

  • memory_management.c — dictionary allocator.
  • dictionary_management.c — dictionary allocation and search.
  • dictionary_heat_optimization.c — Loop #1 execution-heat tracking.
  • word_registry.c — word registration system.
  • block_subsystem.c — logical→physical block mapper.
  • blkio_file.c, blkio_ram.c, blkio_factory.c — block I/O backends (file-backed, RAM-backed) and the factory that selects between them.
  • stack_management.c — stack operations.

Physics-driven adaptive runtime (7 feedback loops)

  • physics_runtime.c — main physics coordinator.
  • physics_hotwords_cache.c — Loop #1 hot-words caching.
  • physics_metadata.c — per-word metadata tracking.
  • physics_pipelining_metrics.c — Loop #4 word-transition prediction.
  • physics_execution_hooks.c — execution instrumentation.
  • rolling_window_of_truth.c — Loop #2 circular execution-history buffer.
  • inference_engine.c — Loops #5/#6, statistical inference (window-width, decay-slope).
  • ssm_jacquard.c — L8 Jacquard steady-state mode selector; consumes compudynamics.c for tuning-word/config lookups.
  • compudynamics.c — generic compudynamics module (cd_tuning_word(), cd_tuning_vm()); the score/UCB/reward/weight constants for the L8 adaptive table live here, not in ssm_jacquard.c.
  • heartbeat_export.c — heartbeat metrics export (CSV export function itself not yet implemented — see docs/working/architecture/heartbeat_csv_export.md).

Math / measurement

  • math_portable.c — portable math functions.
  • profiler.c — performance profiling.
  • doe_metrics.c — Design of Experiments metrics (2^7 factorial).

Any .bak file alongside a .c file here (doe_metrics.c.bak, inference_engine.c.bak, vm.c.bak) is a pre-edit backup left by a past maintenance script (see scripts/remove_loop_conditionals.sh), not a build input.