Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:Atari Jaguar ROM image

From ReverseEngineering.wiki
Format
Extensions .jag, .rom, .j64, .abs, .cof
Endianness big
On this wiki Facts · Code · Notes · Topics

Atari Jaguar cartridge dumps (.jag, .rom, .j64): raw ROM mapped at 0x800000, normally a whole number of megabytes, with a universal header at +0x400 (marker 0x04040404, 32-bit start address at +0x404); other loadable file types are ABS/COFF, Jag Server and DRI executables.

Cartridge image

A cartridge dump is the ROM itself, mapped by the console at 0x800000 (68000 address space, see Platform:Atari Jaguar). The Virtual Jaguar loader (src/core/file.c, ParseFileType) takes a file whose size is a multiple of 1 MiB (or exactly 128 KiB, the Memory Track size) as a ROM.

Universal header

Commercial carts carry a header at ROM offset 0x400. Virtual Jaguar (file.c, jaguar.c):

  • offset 0x400: the 32-bit marker 0x04040404;
  • offset 0x404: a 32-bit start address (the 68000 entry); the emulator uses it when its low 24 bits are even and fall into RAM below 0x200000, the cartridge area 0x800000-0xDFFEFF or the boot ROM area 0xE00000-0xE1FFFF, otherwise it falls back to 0x800000. A value of 0xFFFFFFFF (erased header) makes it enter at 0x802000 if code looks valid there.

Unverified: the bytes around 0x400-0x41F also hold the boot-ROM signature text ("ATARI APPROVED DATA HEADER" style) that the console BIOS checks; the loader above does not read it.

A native image does not usually carry a header at 0x000: homebrew ROMs and the ALPINE boards start code at offset 0x2000 (address 0x802000) with the header slot at 0x400 empty or erased (Virtual Jaguar issue notes in file.c).

Copier header

Some dumps have 512 extra bytes in front. Virtual Jaguar strips them when the payload has the 0x04040404 marker at +0x400 and the file is N MiB plus 512 bytes (or a small homebrew with the marker at 0x600 but not at 0x400).

Mirroring

A 2 MiB ROM repeats at 0xA00000 and 0xC00000 because the cart decodes only the address lines it needs; the emulator copies this from the MiSTer core (comment in file.c).

Other file types

ParseFileType recognises by first bytes: 60 1B ABS/COFF type 1, 01 50 ABS/COFF type 2, 60 1A with JAG at offset 0x1C a Jag Server upload, other 60 1A files as an Atari ST DRI (GEMDOS) executable with a 0x1C-byte header.

Related

Platform:Atari Jaguar.

Code & repositories

  • https://github.com/libretro/virtualjaguar-libretro @ aaf09407217ce9e3b0f68108ea6af33665a31a08 · license: GPL-3.0 (declared by the contributor; GitHub's detector did not recognize LICENSE)
    Virtual Jaguar core: cartridge loader with universal header detection, file type sniffing, memory decoder
    Tested on: source read, not run: read the source, not built · checked 2026-10-18