Skip to content

Troubleshooting

akadata edited this page Feb 14, 2026 · 3 revisions

Troubleshooting

Emulator hangs or boots to CLI only

  • Enable logging and capture a trace:
./emulator --log boot.log --debug-level debug
  • Check for ROM write attempts or DMA into unmapped regions.

UAE JIT bring-up stuck after init

  • Current state and handoff checklist:
  • Build only the JIT integration target:
make USE_UAE_JIT=1 uae-jit
  • Run minimal JIT test:
PISTORM_ENABLE_QUEUE=0 ./emulator --jit
  • If needed, enable bridge trace:
PISTORM_UAE_JIT_TRACE=1 PISTORM_ENABLE_QUEUE=0 ./emulator --jit
  • If build/link state looks stale:
make clean
make USE_UAE_JIT=1 uae-jit

No A314 services

  • Verify env vars (PISTORM_ROOT, PISTORM_A314, PISTORM_DATA, A314_SHARED).
  • Check /opt/pistorm64/a314/ for installed services.

PiSCSI not detected

  • Confirm PiSCSI ROM is loaded.
  • Validate HDF paths and filesystem handlers.
  • Verify Z2 autoconfig addresses in logs.

RTG issues

  • Rebuild with USE_RAYLIB=0 to test headless mode.
  • Confirm RTG memory map range is present in config.

Clone this wiki locally