Introduction
The Mattel Intellivision has a General Instrument CP1610 processor, a 16-bit CPU whose memory is a set of decles: words of ten bits. Cartridge ROM chips are ten bits wide, and the ROM
files of the community store each decle in 16 bits, big-endian, with the upper six bits zero. That is the whole file format of a .bin (also called .int): a run of such words, no header, no
signature, and no load address. Where the words go in the console’s memory comes from a small text file, the .cfg, or from the programmer’s knowledge.
The conventions, as the jzIntv emulator applies them (its loadgame.c, read 2026-11-18): a file is first tried as an Intellicart .rom (a real format with a
header, which this site recognises by its bytes); if that fails and the size is even it is a .bin, and a .cfg with the same name is looked for. jzIntv also tries the suffixes
.rom, .bin, .int and .itv when a name is given without one. The .cfg lists which words go where:
[mapping]
$0000 - $008B = $5000
[vars]
name = "SDK-1600 Hello World"
author = "Joe Zbiciak"
(a real file, made by jzIntv’s assembler: word offsets $0000-$008B of the .bin are placed at address $5000. The [vars] section holds the metadata.)
The explorer takes .int as this format, when the size is even. .bin is not claimed (it means hundreds of other things here), and the .cfg is not read: its mapping decides the base address, so the viewer
starts at $5000, where the default cartridge map begins, and the base address is an option you can change. Open a .bin with Read as, as
Intellivision ROM (headerless).
Software
Structure
0x0000Words: 16-bit big-endian values, a decle in the low ten bits; the first word is placed at the address the.cfggives (usually$5000)whole file, an even size
A cartridge usually begins with an EXEC-friendly header at $5000: six pointers and a few control words that the console’s EXEC reads at boot. It is a convention of the programs, not of the file, and it
is described on the memory map page; the viewer shows what the first words say but does not test that the header is there.
What the viewer shows
- Raw code tab: the table of the raw viewer (the CPU is fixed by the platform, a CP1610) and facts the bytes give: the platform, the share of words whose upper six bits are clear (all of them in a
genuine decle-per-word dump; a different share means the file is not that, or holds data), and, when the base address is
$5000, the six header pointers read ashello.asm’s header layout, each said to be inside the file or not. - The disassembly: every word decoded, in columns, with the CP1610 decoder (SDBD prefixes, the odd-byte misaligned status, the undocumented high bits). Addresses count words: the base address and the entry offset follow that, as the CP1610’s do.
- Names from the memory map: the STIC registers, the sound generators, the Intellicart bank registers, the EXEC vectors, the header.
Not described
Known, not yet covered
- Viewer: the
.cfgfile: its[mapping],[preload],[memattr],[bankswitch]and[vars]sections are documented in jzIntv’sintellicart.txtbut the viewer does not read a neighbouring file (it sees one file), so bank-switched and split cartridges show as one block at the base address you set. - Viewer: the ECS, Intellivoice and JLP expansions, the Locutus and other multi-ROM cartridge types, and the 8-bit packed forms of ROM files.
- Reference: the meaning of the bits of the EXEC header’s flags word; GROM contents (the console GROM is 8 bits wide and is not a cartridge file).
- Viewer: the CP1610 decoder was checked against jzIntv’s disassembler, not against its emulator core (see the CP1610 pages).
Unknown
- Viewer: which address a given
.binis meant for without its.cfg: the default$5000is a convention, not something the file says.
Links
Software
Reference
- The Intellicart .ROM file – the one Intellivision cartridge format with a header
- Memory map, registers and header – the names the viewer uses
- CP1610 instruction set – the decoder
- Raw machine code – the viewer this is built on, and how to reach it