target-rc2014

Configures z88dk compilation recipes for the modular RC2014 Z80 and 8085 hardware target.

1.1k|206|Updated Mar 16, 2016
One-click install
npx skills add https://github.com/z88dk/z88dk --skill target-rc2014-z88dk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: target-rc2014
Source: https://github.com/z88dk/z88dk/tree/main/.agents/skills/target-rc2014
Command: npx skills add https://github.com/z88dk/z88dk --skill target-rc2014-z88dk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building C or assembly programs for the modular RC2014 hardware family with z88dk requires choosing the correct C library (classic vs newlib), CPU subtype (Z80 vs 8085), serial CRT variant, and ROM packaging format. This Skill encodes those target-specific defaults and recipes so compilations for +rc2014 succeed without trial and error. ## Core Features & Use Cases - CLIB and subtype mapping: Documents the default sdcc_iy newlib configuration, classic -clib=default builds, and 8085 subtypes (acia85, uart85, basic85) that force -m8085 -clib=rc2014-8085. - Ready-made build recipes: Provides copy-paste zcc +rc2014 command lines for newlib, classic, 8085, and CP/M-style startups with -create-app ROM/ihex packaging. - Boundary guidance: Clarifies that +rc2014 is distinct from +cpm and +hbios targets, preventing misconfigured builds. - Use Case: A developer writing a serial-monitor program for an RC2014 with an 8085 CPU card uses the acia85 subtype recipe to produce a correct ihex ROM image on the first attempt. ## Quick Start Ask the assistant to compile a C file for the RC2014 target with z88dk, for example by requesting a newlib build with the default basic subtype or an 8085 build using the acia85 subtype with ROM output.

Frequently Asked Questions about target-rc2014

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compile a C program for RC2014 with z88dk?

Run zcc with the +rc2014 target, for example: zcc +rc2014 -vn hi.c -o hi -create-app. This uses the newlib sdcc_iy library with the basic subtype by default and produces a ROM/ihex image via appmake.

What is the difference between +rc2014, +cpm, and +hbios targets?

The +rc2014 target builds for the modular RC2014 hardware family with its own config file, while +cpm and +hbios are separate configurations. Use +rc2014 only when the task explicitly targets RC2014 boards, even for its CP/M-style subtype.

How do I build for an 8085 CPU on RC2014 hardware?

Use one of the 8085 subtypes: acia85, uart85, or basic85. These automatically force -m8085 and link the rc2014-8085 classic library, for example: zcc +rc2014 -subtype=acia85 -create-app -vn hi.c -o hi.

Which C library does z88dk use by default for +rc2014?

Bare zcc +rc2014 defaults to the newlib sdcc_iy library with the basic subtype and defines __RC2014 and __Z80. For the classic library, pass -clib=default, which links rc2014_clib and ndos.

What output format does appmake produce for RC2014 builds?

Appmake for +rc2014 typically produces ROM or Intel hex (ihex) images, not CP/M disc images. Serial subtypes like acia, sio, and uart generate ihex output suitable for ROM programmers or monitors.