Start with a working Jaguar sample
cubanismo's Jaguar SDK provides a maintained environment assembled from original development tools, with build instructions and examples. Its documentation distinguishes emulator use, Skunkboard loading and BJL loading. Reboot's RAPTOR API is another first-party project resource for Jaguar homebrew. Choose the route that matches your development hardware and programming background; neither project name alone promises that an arbitrary executable is a bootable CD.
Build the untouched hello-world example first, preserving tool versions, repository commit and output checksum. Run it with the documented loader and display an obvious version string. If that fails, resolve the environment before adding graphics, audio and file loading. A visible startup marker helps distinguish a failed loader from a program that booted and then crashed.
Treat CD packaging as a separate task
The SDK includes scanned original Atari developer documentation. Read the CD-ROM reference for the selected boot and loading arrangement rather than applying Sega CD or PC data-disc assumptions. A debugger executable, cartridge image and released CD image are different artifacts. Keep their filenames and build targets clearly separated so a test result cannot be attributed to the wrong output.
The original Atari CD schematic is hardware documentation; it is not a disc-authoring specification. Use the software documentation and sample code supplied with your chosen tools for CD calls and disc construction. Preserve the resulting track description and every image file together. If the build uses an external authoring utility, record its exact version and keep its build log.
Test loading and storage deliberately
- Display a startup marker before requesting disc data.
- Load one small asset and validate that its size and checksum match the expected content.
- Report or display a meaningful failure state rather than looping silently.
- Add a controlled audio test and verify that the final image includes its required track or data.
- Add a disposable save and test a normal shutdown and subsequent load.
Do not assume that a Memory Track is present or that space is available. A missing device or unsuccessful write should be handled as a normal user-visible condition. Consult the Memory Track instructions for the original hardware context and the current loader documentation for any emulated storage.
Separate hardware and emulation evidence
Test a cold boot, normal restart and a later disc load on the physical CD unit if you claim physical support. For GameDrive, record firmware and check RetroHQ's CD release information. For an emulator, record its version and exact CD configuration; the Virtual Jaguar libretro project documents its own support. One route passing does not prove the others.
Publish required hardware, media layout, tested configurations, output checksums and a short reproducible sequence. Include licenses for code and assets, retaining third-party notices. Obtain permission before distributing reused game content. Keep known failures in release notes with their last visible marker and exact build. This makes the release usable for players and gives the next developer evidence to improve compatibility.