x68000:adding_an_fdx68_to_x68000
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
x68000:adding_an_fdx68_to_x68000 [2018/11/27 02:54] – created leonk | x68000:adding_an_fdx68_to_x68000 [2018/11/30 14:00] – leonk | ||
---|---|---|---|
Line 3: | Line 3: | ||
Original web site: (http:// | Original web site: (http:// | ||
- | __**Background Information:**__ | + | ====== |
The X68000, like many other devices made in the 1990's and earlier, uses ICs that communicate on 5V rails (0V = binary 0, 5V = binary 1). Modern electronics, | The X68000, like many other devices made in the 1990's and earlier, uses ICs that communicate on 5V rails (0V = binary 0, 5V = binary 1). Modern electronics, | ||
Line 9: | Line 9: | ||
The FDX68 is a device that plugs into the Raspberry Pi, and voltage converts between a Pi and X68000 floppy drive port (both internal and/or external). | The FDX68 is a device that plugs into the Raspberry Pi, and voltage converts between a Pi and X68000 floppy drive port (both internal and/or external). | ||
- | __**PreReq:**__ | + | ====== |
* Raspberry Pi 3B or 3B+ | * Raspberry Pi 3B or 3B+ | ||
Line 15: | Line 15: | ||
* FDX68 device (purchase from original maker from above link) | * FDX68 device (purchase from original maker from above link) | ||
* FDX68 interface cable (depending on X68000 unit you have, connector will differ) | * FDX68 interface cable (depending on X68000 unit you have, connector will differ) | ||
- | * Knowledge of Linux (SSH into Pi, start service, run command line utilities to load disk images) | + | * **Knowledge of Linux (SSH into Pi, start service, run command line utilities to load disk images)** |
* Disk images of OS / Games you want to run | * Disk images of OS / Games you want to run | ||
+ | * FDX68 software downloaded and unarchived to a new **fdx68** directory in the rootfs | ||
- | __**Setup and Usage:**__ | + | ====== |
The original author has great instructions found here: http:// | The original author has great instructions found here: http:// | ||
Use google translate to get the details. | Use google translate to get the details. | ||
+ | The following examples will not cover all possible combinations, | ||
+ | * Newer systems have an external switch to select internal floppy drive assignment | ||
+ | * Older systems always assign internal FD 0/1 and you must set FDX68 to 2/3 | ||
+ | * HumanOS can boot from any FD (0/1/2/3) So you can boot from external FD to do things like change SRAM settings or install SASI boot loader | ||
+ | * Single disk games can boot from FD 2/3 | ||
+ | * Multi disk games will look for disk 2+ only on FD 0/1. This might be an issue with older systems that don't allow you to set internal FD assignment | ||
+ | * System will not boot a hard drive if FD0/1 are not present. So you must always have FDX68 running as drive 0/1 or you must have internal drives connected as 0/1 if booting SCSI devices. | ||
+ | |||
+ | ====== X68000 XVI Compact ====== | ||
+ | ===== Connection Method ===== | ||
+ | The external FDD connecter is labelled " | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | When making your own cable to convert from MDR 40 to the 34-pin connector found on the FDX68, the following conversion table should be referenced. The pin assignment for creating the conversion cable is as follows. After soldering the pins, one should confirm they cable is soldered correctly using a voltmeter. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Here's how one connects the FDX68 externally to the X68000 using this custom cable | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Internal FDD are drives 0,1 and FDX68 are drives 2,3 ===== | ||
+ | |||
+ | To use the internal FDD as the first and second boot drives (drive A: and B:) and the FDX68 emulated floppy disk drives as the third and fourth drives (drive C: and D:) do the following. Set the " | ||
+ | |||
+ | The X68000 can still boot a system from the FDX68 as long as no bootable floppies are found in the internal FDDs. It is also important to note that although games will boot from drives 2,3 many multi-disk games will only search for additional floppy disks in drives 0,1. This configuration is useful for booting HumanOS, or single disk games. It is also useful when the FDX68 emulator is not running but you still desire a bootable system. | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | ===== Internal FDD are drives 2,3 and FDX68 are drives 0,1 ===== | ||
+ | |||
+ | To use the FDX68 emulated floppy disk drives as the first and second drives (drive A: and B:) and the internal FDD as the third and fourth disk drives (drive C: and D:) do the following. Set the " | ||
+ | |||
+ | This configuration will allow you to use multi-disk games using the FDX68 FDD emulator with no drive number issues. But the FDX68 must be running at startup. | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | ===== Starting the Floppy Disk Drive emulator ===== | ||
+ | |||
+ | FDX68 can emulate both XDF as well as FDX images. | ||
+ | |||
+ | Let's convert the system disk image of Human 3.02, which was released free of charge in XDF format. For image conversion, we use the //fdxconv// utility. If you run //fdxconv// with no arguments, a simple help screen will display with usage instructions. //fdxconv// automatically determines the conversion process to use by using file extensions of the input and output files. | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | FDX68 version 1.00, Copyright (C) 2017-2018 GIMONS | ||
+ | Floppy image convert utility | ||
+ | |||
+ | Usage: ./fdxconv -i SRCFILE [-n DISKNO] -o DESTFILE | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | Here's an example of converting from XDF to FDX format. Because the original XDF image has only data sectors, it's only 1.2Mb big, but when converted to FDX format it will grow to about 5.5Mb. | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | FDX68 version 1.00, Copyright (C) 2017-2018 GIMONS | ||
+ | Floppy image convert utility | ||
+ | |||
+ | Input file : HUMAN302.XDF | ||
+ | Disk no : 1 | ||
+ | Output file : HUMAN302.FDX | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | -rw-r--r-- 1 pi pi 5505280 | ||
+ | -rw-r ----- 1 pi pi 1261568 August 9 18:53 HUMAN302.XDF | ||
+ | pi@raspberrypi:/ | ||
+ | </ | ||
+ | |||
+ | After successfully converting the system disk of Human 3.02 to FDX format, let's copy this to HUMAN302_A.FDX and HUMAN302_B.FDX and start the //fddemu// emulator with these 2 disk images in the emulated drives (This is just an exercise to show you how to use //fddemu// to emulate 2 disk images. | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | pi@raspberrypi:/ | ||
+ | pi@raspberrypi:/ | ||
+ | FDX68 version 1.00, Copyright (C) 2017-2018 GIMONS | ||
+ | Floppy disk drive emulation | ||
+ | |||
+ | ----+----+----+----------------------------------- | ||
+ | ID | WP | CL | DISK IMAGE | ||
+ | ----+----+----+----------------------------------- | ||
+ | 0 | -- | 00 | HUMAN302_A.FDX | ||
+ | 1 | -- | 00 | HUMAN302_B.FDX | ||
+ | ----+----+---------------------------------------- | ||
+ | </ | ||
+ | |||
+ | As you can see in the picture below, there are no floppies inserted into X68000 Compact and it is booting from the FDX68. After the system has booted, one can use the //drive// command to list what floppy disk drives the X68000 has detected. | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | ===== Swap disks using the command line ===== | ||
+ | |||
+ | The floppy disk drive of the X68000 has extended specifications including a floppy auto eject mechanism. The floppy eject operation can be instructed both using the eject button on the main unit as well as on the command line. For example, the X68000 game A-JAX boots with both a program disk and data disk 1, the program disk automatically ejects after reading the data and asks the user to insert data disk 2. In this example, we will show how to change a floppy disk using the FDX68. First, lets boot A-JAX: | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | [1] 719 | ||
+ | pi@raspberrypi:/ | ||
+ | Floppy disk drive emulation | ||
+ | |||
+ | ----+----+----+----------------------------------- | ||
+ | ID | WP | CL | DISK IMAGE | ||
+ | ----+----+----+----------------------------------- | ||
+ | 0 | ON | 00 | AJAX_P.FDX | ||
+ | 1 | ON | 00 | AJAX_1.FDX | ||
+ | ----+----+---------------------------------------- | ||
+ | |||
+ | pi@raspberrypi:/ | ||
+ | </ | ||
+ | |||
+ | Note that "&" | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | root | ||
+ | root | ||
+ | pi | ||
+ | pi@raspberrypi:/ | ||
+ | </ | ||
+ | |||
+ | Note that the //fddemu// daemon/ | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | ----+----+----+----------------------------------- | ||
+ | ID | WP | CL | DISK IMAGE | ||
+ | ----+----+----+----------------------------------- | ||
+ | 0 | ON | 00 | AJAX_P.FDX | ||
+ | 1 | ON | 00 | AJAX_1.FDX | ||
+ | ----+----+---------------------------------------- | ||
+ | pi@raspberrypi:/ | ||
+ | </ | ||
+ | |||
+ | You can now turn on the X68000 and try to boot AJAX. After loading the disk for a while, you will be prompted to insert another disk as shown below. At this time, the floppy disk in drive 0 is ejected. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | ----+----+----+----------------------------------- | ||
+ | ID | WP | CL | DISK IMAGE | ||
+ | ----+----+----+----------------------------------- | ||
+ | 0 | -- | 00 | EMPTY | ||
+ | 1 | ON | 00 | AJAX_1.FDX | ||
+ | ----+----+---------------------------------------- | ||
+ | pi@raspberrypi:/ | ||
+ | </ | ||
+ | |||
+ | Next, insert A-JAX Data disk 2 using the //fddctl// utility: | ||
+ | |||
+ | < | ||
+ | pi@raspberrypi:/ | ||
+ | pi@raspberrypi:/ | ||
+ | ----+----+----+----------------------------------- | ||
+ | ID | WP | CL | DISK IMAGE | ||
+ | ----+----+----+----------------------------------- | ||
+ | 0 | ON | 00 | AJAX_2.FDX | ||
+ | 1 | ON | 62 | AJAX_1.FDX | ||
+ | ----+----+---------------------------------------- | ||
+ | pi@raspberrypi:/ | ||
+ | </ | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Additional information about disk image format ===== | ||
+ | |||
+ | In the above examples, the floppy disk images were converted to the FDX format prior to usage. The FDX68 FDD emulator //fddemu// can start without converting the image first and supports other images formats, such as XDF or D68 (it automatically converts to FDX in memory) It is important to note that any format outside of FDX will not save back to the disk image. This is convenient for launching applications and games that do not need save feature. If you do require the ability to save back to disk, you will need to convert to FDX first. | ||
+ | |||
+ | ====== X68000 PRO and similar systems ====== | ||
+ | |||
+ | ===== Connection Method ===== | ||
+ | |||
+ | The external floppy disk drive connecter is labelled " | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | When making your own cable to convert from D-SUB 37 to the 34-pin connector found on the FDX68, the following conversion table should be referenced. The pin assignment for creating the conversion cable is as follows. After soldering the pins, one should confirm they cable is soldered correctly using a voltmeter. | ||
+ | |||
+ | ... to do ... | ||
+ | |||
+ | ===== Internal FDD are drives 0,1 and FDX68 are drives 2,3 ===== | ||
+ | |||
+ | It is not possible to change the ID of the built-in floppy disk drives with a switch on the rear. Therefore the internal FDD are always assigned the first and second boot drives (drive A: and B:) and the FDX68 emulated floppy disk drives as the third and fourth drives (drive C: and D:) you must set the FDX68 jumpers to location 2,3 for both DRV and OPT as shown below. | ||
+ | |||
+ | The X68000 can still boot a system from the FDX68 as long as no bootable floppies are found in the internal FDDs. It is also important to note that although games will boot from drives 2,3 many multi-disk games will only search for additional floppy disks in drives 0,1. This configuration is useful for booting HumanOS (to install SASI boot loader into SRAM, or change SRAM configuration), | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Internal FDD are drives 2,3 and FDX68 are drives 0,1 ===== | ||
+ | |||
+ | To use the FDX68 emulated floppy disk drives as the first and second drives (drive A: and B:) and the internal FDD as the third and fourth disk drives (drive C: and D:) do the following. Set the FDX68 jumpers to location 0,1 for both DRV and OPT as following: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Next, you will need to change the jumpers on the built-in floppy disk drives. As soon as you remove the cover of the system, you will see the FDD but the jumper is on the back of the internal floppy disk drive, hidden by the cable and it is hard to see and change it. You will need to remove the floppy disk drive. The jumper is not divided by DRIVE and OPTION like on the FDX68. It will be a green jumper as seen below, change this jumper to position 2 or 3 depending on the drive you are working on (both drives can not be set to the same number) | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | This configuration will allow you to use multi-disk games using the FDX68 FDD emulator with no drive number issues. But the FDX68 must be running at startup. | ||
+ | |||
+ | ===== Starting the Floppy Disk Drive emulator ===== | ||
+ | |||
+ | Using the FDX68 software to emulate the floppy disk drive, mount/ | ||
x68000/adding_an_fdx68_to_x68000.txt · Last modified: 2020/06/25 12:29 by leonk