CP/M 2.2 on the TS2068

A cartridge-booted CP/M environment for TSPico, Oliger-enabled Fuse and your browser.

Release cpm22-v0.1.0 · 64 columns on a normal TS2068 · 80 columns with supported PicoVideo 4.2 · 160KB and 320KB disks

Run CP/M in your browserGet started on hardware or Fuse

The TSPico version loads a disk into banked SRAM using the original 1.00 protocol or compatible TSPico v2.x interfaces. Work in CP/M, assemble the HI example, edit files, or run Planetfall and Zork I. Save your RAMDisk explicitly before power-off. TSPico v2.x direct-SD/native-file support needs the optional CP/M service.

Downloads

TSPico cartridge, preload, games and tools

Fuse/Oliger utilities: matched 160KB and 320KB pairs

Planetfall + Zork I: 320KB Oliger disk and cartridge

Source code

Python disk tools and guides

Direct game files: 320KB DSK + matching cartridge. SHA-256 checksums. Infocom attribution and rights.

Guides

TSPico v1.00, v2.x and disk storage

The same dual-protocol cartridge can boot on original TSPico 1.00 or a supported TSPico v2.x interface. It selects the transport from a validated handshake. TSPico firmware, the TSPico ROM extension and the separate PicoVideo display firmware are different components; upgrading one does not upgrade the others.

SetupHow CP/M accesses its diskHow changes survive power-off
Original TSPico 1.00Loads a 160KB or 320KB image from TAP preload files or a saved set into banked SRAM. CP/M then reads and writes the RAMDisk. It does not directly edit an SD disk image while programs run.Run TPSAVE before switching off. It exports numbered page TAPs plus a descriptor to /CPM/SAVE. The cartridge reloads this saved set directly on the next boot, without PC repacking.
Supported TSPico 2.x interface, without the CP/M serviceUses the TSPico v2.x storage protocol to load or restore a RAMDisk through TAP operations. TSPico v2.x raw-file channels alone do not provide CP/M with a mounted disk.Run TPSAVE. The TSPico v2.x path writes one complete CPMRAM.TAP; TPSAVE SPLIT produces the legacy-compatible chunk set.
Supported TSPico 2.x interface, with the optional CP/M serviceDirect SD mode serves a disk image or a native directory as a CP/M volume. At startup, Enter selects persistent SD, R copies that volume into RAMDisk, and L reloads a saved RAMDisk.Direct SD writes persist through the service. A RAMDisk snapshot remains separate: save it explicitly with TPSAVE; it is not automatically written back to the source SD volume.

The TSPico v2.x implementation was inspected against firmware 2.3.1 / ROM 2.3. These features should not be inferred from every firmware labelled 2.x, or from the board revision alone. Direct SD and native-directory mode require the supplied optional CP/M service; the cartridge package does not install firmware automatically. See the firmware feature matrix and startup guide.

Why use TSPico RAM?

CP/M needs writable low memory. This implementation uses 32KiB of writable DOCK memory alongside upper HOME memory, giving programs a 52,992-byte transient program area. Separate TSPico SRAM holds the disk: twenty 8KiB pages for 160KB, or forty for 320KB. A small resident driver switches disk banks and copies sectors without mapping away the running code or stack.

A RAMDisk is fast working storage, but volatile. Saving a game or editing a file changes the CP/M disk in SRAM; on the RAMDisk path, TPSAVE is the additional step that preserves that disk on the SD card. Existing saved disks take precedence over the factory preload, so replacing preload TAPs does not replace an older saved session.

Oliger disk files and exchanging media

The project supplies standard single-sided 160KB and double-sided 320KB Oliger-compatible .DSK containers, complete CP/M disk .TAP containers, and Python tools for creating disks, copying files and converting between containers. The filesystem bytes are shared across these formats; a cartridge must match the image geometry.

Fuse with the JLO/Oliger interface and the TSRun disk adapter use DSK images. TSPico v2.x with the optional CP/M service can mount compatible DSK/TAP files or expose native files. Original 1.00 reaches the same disk contents through TAP-backed RAMDisk loading and explicit saves. This is disk-image and filesystem compatibility; TSPico is not emulating the Oliger controller hardware.

The 320KB browser player keeps the game disk on A: and the utility disk on B:, with separate open/download controls. TSPico currently exposes one mounted CP/M drive, A:. Save your work before changing its volume. See disk tools and the worked save/reload session.

64 columns, or 80 with PicoVideo v4.2

A standard TS2068 runs the ROM-independent console in 64 columns by 24 rows, using its 512-pixel high-resolution display. The ordinary TSRun player also uses this 64-column display.

With the supported PicoVideo v4.2 hardware and firmware, CP/M detects the text renderer and selects 80 columns by 24 rows. Startup reports PicoVideo 80 column mode enabled. COLUMNS 64 and COLUMNS 80 select the renderer; exit and restart applications after changing width so they read the new setting. Disk contents and the selected colour scheme are preserved.

PicoVideo is optional and independent of the TSPico storage protocol. Older published V4 firmware does not implement the same usable 80-column renderer and can capture banked DOCK writes as display garbage. The v4.2 implementation distinguishes HOME display writes from banked memory traffic. See the PicoVideo setup, compatibility and rollback guide.

Which font does it use?

The public 64-column cartridge uses Daniel Hepper's public-domain font8x8 basic Latin bitmap font, selecting characters 32-127 and converting their bit order for the TS2068 console. It does not contain a font extracted from the TS2068 HOME ROM. That is why its lettering differs from the familiar BASIC screen.

In 80-column mode, character codes and attributes are drawn by PicoVideo's text renderer using the font built into its firmware. That font can differ from the cartridge's 64-column bitmap font. A local build can optionally use a privately supplied TS2068 ROM font; the public downloads retain the public-domain font.

What this work added to the AI development skills

The CP/M work also produced reusable guidance in the TS2068 AI skill collection. These are development instructions, references and helper assets for future projects; the complete CP/M implementation remains the worked example, rather than an implied capability of every baseline library.

The references link the TSPico storage skill, cartridge-development skill and graphics and animation skill. Hardware observations, source inspection and emulator/model checks are identified separately so future work can build on the evidence accurately.

Original TSPico 1.00 has booted and run the games on hardware. Many failure cases, TSPico v2.x SD services and PicoVideo 4.2 are tested with native Z80/protocol models; see the validation notes for limits. This release is CP/M 2.2, leaving a separate path for future 3.x work.