This commit is contained in:
dschmenk 2013-09-11 14:11:45 -07:00
commit b587eff287
2 changed files with 29 additions and 10 deletions

View File

@ -8,7 +8,12 @@ Apple II Pi works by connecting an Apple II to a Raspberry Pi using a RS232 seri
Installing and configuring the Apple II: You will need an Apple //c or Apple //e w/ SuperSerial Card. An Apple II Mouse is recommended for that full-on retro feel, but not required. Download and install the A2PI.PO disk image onto a 5 1/4 floppy. ADTPro would be the recommended tool for that operation although once you have the latest apple2pi version running, you can use the included dskwrite and dskread utilities for writing and reading ProDOS floppies.
Installing and configuring the Raspberry Pi: Download the apple2pi project to your Raspberry Pi. Enter the apple2pi/src directory. Compile the daemon and tools with 'make' and copy the results to /usr/local/bin with 'sudo make install'. You will need to disable the Raspbain serial login by editing /etc/inittab and commenting out the line (probably at the very bottom) to look like:<br>
Installing and configuring the Raspberry Pi: Download the apple2pi project to your Raspberry Pi. Enter the apple2pi/src directory. Compile the daemon and tools with 'make' and copy the results to /usr/local/bin with 'sudo make install'. To build the FUSE driver needed to mount ProDOS devices under Linux, you will need the libfuse-dev package installed. Get this from apt-get, aptitude, or whichever package manager you like. Build with 'make fusea2pi' and install with 'sudo make fuse-install'.
The following is no longer neessary as the install script carefully makes all the following adjustments automatically. I left this here so you know what the script is doing.
>You will need to disable the Raspbain serial login by editing /etc/inittab and commenting out the line (probably at the very bottom) to look like:<br>
<code>
\#T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
</code>
@ -18,24 +23,24 @@ You will also want to disable the console messages that go out to the serial por
dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
</code>
If you are using an HDMI port to display video, skip the overscan settings. This was for my monitor and your values may vary (a lot). I adjust the NTSC output so it fits nicely on my //c monitor, I edited the setting in /boot/config.txt such that:
>If you are using an HDMI port to display video, skip the overscan settings. This was for my monitor and your values may vary (a lot). I adjust the NTSC output so it fits nicely on my //c monitor, I edited the setting in /boot/config.txt such that:
<code>
><code>
overscan_left=26<br>
overscan_right=-8<br>
overscan_top=-8<br>
\#overscan_bottom=16<br>
</code>
To run the a2pid daemon automatically at boot time, edit /etc/rc.local and add:
>To run the a2pid daemon automatically at boot time, edit /etc/rc.local and add:
<code>
><code>
/usr/local/bin/a2pid --daemon
</code>
right before the line:
>right before the line:
<code>
><code>
exit 0
</code>
@ -47,7 +52,7 @@ Reboot the Apple II with the newly created floppy in the start-up drive. If eve
Using a2pi: The Apple //c and //e keyboards are pretty minimal compared to modern keyboards, and the Apple II Mouse only has one button. In order to provide most of the funcitonality required of modern OSes, the Open-Apple and Closed-Apple keys are used as modifiers to enhance the keyboard and mouse. On the keyboard, Open-Apple acts just like the Alt key. The Closed-Apple key acts like a Fn key, changing the actual key codes. Currently, the Closed-Apple key will modify the number keys 1-0 as funciton keys F1-F10 and the arrow keys as Left-Arrow=Home, Right-Arrow=End, Up-Arrow=PgUp, Down-Arrow=PgDn. For the mouse, when you click the mouse button by itself, that is the left(default)-click. Open-Apple along with the mouse button will return the right-click, and Closed-Apple along with the mouse button will return the middle-click. If you should ever need to exit a2pi, press Closed-Apple ESC on the Apple II keyboard. This will exit both the code on the Apple II and the Raspberry Pi. This is useful when developing and debugging the drivers/daemons. a2pid can be run directly (not as a daemon) by leaving off the '--daemon' option. Enabling printf's in the code allows one to watch the packets arrive and get processed when run from a network ssh session.
Theory of operation: Apple II Pi works by running code on the Apple II and the Raspberry Pi, talking to each other with a simple protocol. The Apple II basically appears to the Raspberry Pi as an external peripheral, not unlike a USB keyboard and mouse. The Apple II floppy boots into ProDOS and runs a simple machine language program that scans the keyboard, and mouse if present, sending the events out the serial port to the Raspberry Pi. It is a very simple protocol and the serial port is running at 115.2K baud, so it is fast and low overhead. On the Raspberry Pi, a little daemon runs, waiting for packets on the serial port, converts the Apple II events into Linux compatible events, and inserts them into the input subsystem. This daemon also has a socket interface (port 6502) that can be used to access the Apple II memory and execute arbitrary code. Look at a2lib.c for implementation.
Theory of operation: Apple II Pi works by running code on the Apple II and the Raspberry Pi, talking to each other with a simple protocol. The Apple II basically appears to the Raspberry Pi as an external peripheral, not unlike a USB keyboard and mouse. The Apple II floppy boots into ProDOS and runs a simple machine language program that scans the keyboard, and mouse if present, sending the events out the serial port to the Raspberry Pi. It is a very simple protocol and the serial port is running at 115.2K baud, so it is fast and low overhead. On the Raspberry Pi, a little daemon runs, waiting for packets on the serial port, converts the Apple II events into Linux compatible events, and inserts them into the input subsystem. This daemon also has a socket interface (port 6551) that can be used to access the Apple II memory and execute arbitrary code. Look at a2lib.c for implementation.
Enjoy,

View File

@ -15,6 +15,8 @@ This documents the utilities included in the Apple II Pi project. See the proje
-----------------
bload - Load binary file
brun - Run binary file
merlin2text - Convert MERLIN text files to unix text files
text2merlin - Convert unix text files to MERLIN text files
a2lib.c - Simple a2pid connection library
Disk image tools
@ -35,7 +37,7 @@ This documents the utilities included in the Apple II Pi project. See the proje
a2serclk - Raspberry Pi GPCLK for Apple II Pi hardware
a2pid - Apple II Pi Linux daemon
A2Pi.PO
A2PI.PO
3.0 Interactive Tools:
======================
@ -89,7 +91,19 @@ Like bload, brun will load the binary file but will also jump to the loading add
brun <filename> <address> [IP addr]
4.3 a2lib.c:
4.3 merlin2text:
----------------
If you develop on the Apple II, most likely you have had experience with the MERLIN assembler. Great assembler for small projects, but it uses a high ASCII format and spaces instead of tabs. This quick utility quickly reformats the MERLIN text into a unix palatable text file for your favorite editor. Ran as:
merlin2text < <prodosfile> > <unixfile>
4.4 text2merlin:
----------------
REverses the process above to put the text file back on to ProDOS media.
text2merlin < <unixfile> > <prodosfile>
4.5 a2lib.c:
------------
All the tools include a2lib.c as a very poor, cheesy, horrible, etc. way to implement the Apple II Pi daemon API. Only useful if you are looking to write your own tool or modify the code of the existing tools.