Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Updated READMEs regarding RAM image support

Browse source
This commit is contained in:
Jeff Parsons 2016-10-17 11:18:18 -07:00 • committed by Jeff Parsons
commit 5f3694133a
4 changed files with 26 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

14
devices/pc8080/ram/README.md
View file

@ -7,15 +7,17 @@ permalink: /devices/pc8080/ram/
8080-Based RAM Images
---------------------
RAM images are added to machines by including a *<ram>* component in the machine XML configuration file
with the *file* attribute set to the filename of the image; eg:
RAM images are added to machines by including a `<ram>` component in the machine XML configuration file
with the *file* attribute set to the filename of the image, along with optional *load* and *exec* addresses; eg:
```xml
<ram id="romH" addr="0x0000" size="0x0800" file="/devices/pc8080/rom/invaders/INVADERS-H.json"/>
<ram id="ram64K" addr="0x0000" size="0x10000" file="/devices/pc8080/ram/exerciser/8080EX1.json" load="0x100" exec="0x100"/>
```
The project currently contains the following 8080-based ROMs:
If no *load* address is specified, the `<ram>` component relies on the "load" property of the JSON-encoded RAM image;
otherwise, the starting RAM address is used. If no *exec* address is specified, the CPU will begin execution at its usual
reset address.
The project currently contains the following 8080-based RAM images:
* [8080 Exerciser Tests](exerciser/)
* [Space Invaders (1978)](invaders/)
* [DEC VT100 Terminal](vt100/)

11
devices/pc8080/rom/README.md
View file

@ -1,21 +1,20 @@
---
layout: page
title: 8080-Based ROMs
title: 8080-Based ROM Images
permalink: /devices/pc8080/rom/
---
8080-Based ROMs
---
8080-Based ROM Images
---------------------
ROMs are added to machines by including one *[ROM](/docs/pcx86/rom/)* component in the machine XML configuration file
ROMs are added to machines by including one `<rom>` component in the machine XML configuration file
for each ROM in the machine; eg:
```xml
<rom id="romH" addr="0x0000" size="0x0800" file="/devices/pc8080/rom/invaders/INVADERS-H.json"/>
```
The project currently contains the following 8080-based ROMs:
The project currently contains the following 8080-based ROM images:
* [8080 Exerciser Tests](exerciser/)
* [Space Invaders (1978)](invaders/)
* [DEC VT100 Terminal](vt100/)

13
devices/pdp11/ram/README.md
View file

@ -7,5 +7,18 @@ permalink: /devices/pdp11/ram/
PDP-11 RAM Images
-----------------
RAM images are added to machines by including a `<ram>` component in the machine XML configuration file
with the *file* attribute set to the filename of the image, along with optional *load* and *exec* addresses; eg:
```xml
<ram id="ram" addr="0x0000" size="0x4000" file="/devices/pdp11/ram/bootstrap/bootstrap.json" load="0x3FE4" exec="0x3FE4"/>
```
If no *load* address is specified, the `<ram>` component relies on the "load" property of the JSON-encoded RAM image;
otherwise, the starting RAM address is used. If no *exec* address is specified, the CPU will begin execution at its usual
reset address.
The project currently contains the following PDP-11 RAM images:
* [PDP-11 Boot Demo](bootdemo/)
* [PDP-11 Bootstrap Loader](bootstrap/)

1
modules/pc8080/lib/rom.js
View file

@ -65,7 +65,6 @@ function ROM8080(parmsROM)
this.addrROM = parmsROM['addr'];
this.sizeROM = parmsROM['size'];
/*
* The new 'alias' property can now be EITHER a single physical address (like 'addr') OR an array of
* physical addresses; eg: