Guides:MAME - driver - apple2p
Apple II
Introduction
There are a few variants of this machine
| For general information on the MESS project and how to use it including external references see the dedicated MESS Page |
Prerequisites
- Appropriate MAME setup
Apple Super Serial Card
Start the MAME apple2p with the ssc slot device with a null_modem attached to it attached. Configure a bitbanger device. To test the configuration we will output to a file on the host OS. The key to getting this to work is to ensure the slot device config matches the bitbanger device configuration within MAME.
mame apple2p -v -w -nomax -sl1 ssc -sl1:ssc:rs232 null_modem -bitb a2out.txt -flop1 dos33.dsk
In the MAME (for this test only) due to high ascii output (see references)
- Dip Switches (slot device)
* Mode: Communications Mode * Baud Rate: 9600 * End of Line: Don't add LF after CR * Parity: None * Data Bits: 7 * Stop Bits: 1 * Interrupts: On
- Machine Configuration (null_modem/bitb device)
* Flow Control: off * Data Bits: 7 * Parity: None * RX Baud: 9600 * Stop Bits: 1 * TX Baud: 9600
Let the apple2p machine boot DOS 3.3 you will be presented with a "]" prompt
To begin outputting to your file at the prompt type "PR#n" where n is the slot number you attached the ssc device too. Everything after this should display in the file
If the version of DOS you use does not output a linefeed after CR change the "End of Line option" option in the dip settings.
ADTPro
ADTPro supports bootstrapping a machine and/or transfer data between machines. It is a server(+gui) application written in Java that can be run in multiple modes of operation to support the widest range of scenarios
We will use localhost mode (serial over ip)
ensure the MAME device slot matches the ADTPro configured ssc slot otherwise it can hang start up
Sending/Receiving Files
TBA
Troubleshooting
is bitb listening
On the MAME host machine, check MAME is listening on the socket you configured
$ ss -lnp | grep mame
tcp LISTEN 0 0 0.0.0.0:10000 0.0.0.0:* users:(("mame",pid=1032959,fd=31))
traffic flow on your bitb port =
using tcpdump look for traffic flow on your listening port between both endpoints of the connection
# tcpdump -i ens192 port 10000 tcpdump: verbose output suppressed, use -v[v]... for full protocol decode listening on ens192, link-type EN10MB (Ethernet), snapshot length 262144 bytes