Topic : Hades Compendium Author : Lonny Pursell Version : HadesFAQ.hyp v1.09 (2/16/2019) Subject : Documentation/FAQ Nodes : 73 Index Size : 2006 HCP-Version : 3 Compiled on : Atari @charset : atarist @lang : @default : Default @help : Help @options : +g -i -s +z @width : 75 @hostname : HIGHWIRE @hostname : CAB @hostname : THING @hostname : STRNGSRV View Ref-FileDocumentation for the Hades as of 01/26/2001 ===================================================================== Software The following programs must be found in the AUTO folder: -FPU_3.PRG : Comprises the following -FPUxx.PRG FPU emulation for 40 and 60s. -UIIHx.PRG Unimplemented Integer Handler for MC68060. -OVFIXx.PRG Keyboard overflow correction -XYTASTAT.PRG Keyboard layout correction. only if "XYTASTAT.INF" is in the AUTO folder. -SCSI SCSI pseudo-DMA routines. (The routines FPUxx.PRG, UIIHx.PRG and SCSI are already implemented in ROM. However, they run faster in RAM!). -Graphics Card Driver: Corresponding to the installed graphics card. The following graphics cards are currently supported: -ET4000 -ET6000 -MACH64 Normally the following programs (NOVA driver from Computerinsel Huber!) -EMULATOR.PRG screen output redirection -EMULATOR.BIB resolution file -MENU.PRG resolution selection, etc. -MENU.INF settings file -STA_VDI.PRG VDI driver -STA_VDI.INF resolution file -NVDI.PRG : possibly (GDOS program or graphics driver) -NOVACAL.PRG : In order to run Calamus in 32k, 16bit and 24bit colors. -Graphics Card ATTENTION: The ETx000 and Mach64 graphics cards come in several different versions. You can only be sure that the corresponding driver will work if you order the graphics card from us!!!!!!!!!!!! a) ET4000 W32 PCI with 1MB to 2MB RAM ET6000 PCI with 2MB to 8MB MDRAM For these cards there are currently two drivers: The NOVA VDI from Computerinsel and NVDI ET4000 from Behne and Behne. - NVDI-ET4000 Due to the custom VMG.PRG the higher pixel clocks (up to 110MHz) of the PCI bus can be used. Disadvantage: NVDI has problems in 256 color modes with the rendering of halftone surfaces (see the way the HADES.ACCs are presented). This is due to the lack of customization of the integrated accelerator of the ET4000/W32 chips. Remedy: If you put GEMRAMH and WINX in the AUTO folder, you not only have better window management, but also no more garbage on the screen with 256 colors. But even at higher color depths, some programs have compatibility problems with the NVDI ET4000. With the patched VMG4000.PRG you can't create any new modes, but rather you have to copy existing ones and modify them manually. Otherwise, some bits needed for initialization are not correctly set. - The NOVA VDI is "cleaner" in this regard and there are no problems in the different color depths. Also the speed is a little faster even though it does not use the special features of the ET4000 W32 yet. For the ET6000 the software supports the special features and this makes it run very fast. Due to the better compatibility we recommned the use of the NOVA VDI. b) Mach64 ISA From Computerinsel there are NOVA drivers for the 2MB DRAM (110MHz), the 2MB VRAM and the 4MB VRAM ISA cards (135MHz pixel clock). Advantage: Higher pixel clock and more memory -> higher resolutions, higher color depth, higher refresh rates and of course higher speed. (the VRAM cards have the faster speed even with higher color depths!!!). c) Mach64 PCI There is a driver from Computerinsel for the 2MB and 4MB VRAM cards. The DRAM cards are not running yet. The advantage compared to the VRAM ISA cards: especially when blitting, there is clearly more speed. (32-bit bus width for the PCI bus instead of 16-bit for the ISA bus!) NOVA VDI + NVDI When using the NOVA VDI you can still use the normal NVDI purely for GDOS. This also speeds up the screen output considerable. Procedure: 1. Install NOVA VDI 2. Install NVDI as normal 3. Remove or rename the NVDIDRVx.SYS drivers (4 items in total) in the GEMSYS folder. 4. Copy the ASSIGN.SYS from the NOVA disk to the boot partition or, if you want to use the existing ASSIGN.SYS file, register all screen drivers as 0xp SCREEN.SYS so that NVDI will use the existing NOVA drivers. 5. Reboot (now with NOVA VDI and NVDI) When booting, the TOS initializes the PCI graphics card first (Mach64 or ETx000) then, if those are not available, the ET4000 ISA and lastly, if that is also not available, the Mach64 ISA. Should none of these be available the screen will stay dark. This means that you will always have a picture when booting and so can then see any possible error messages. It is possible to use a mixed operation ET4000/ISA and Mach64/PCI or ETx000/PCI and Mach64/ISA. Using two types of graphics cards simultaneously on either the ISA or the PCI bus is not possible. - ATI Rage Pro 8MB **************** This graphics card works together with NVDI 5. Simply install NVDI 5 with the ET4000 option. Afterwards, "INSTALL.TOS" from the floppy disk to start the graphics card. That's it. *********************************************************************************** Working sequence of possible AUTO folder programs: -------------------------------------------------- -XBOOT.PRG -MAGXBOOT.PRG -IPRN2.PRG -DRVIN.PRG -MFP.PRG -MFP_TT.PRG -EMULATOR.PRG -FPU_3.PRG -JAR128.PRG -MENU.PRG -PCI_CONF.PRG -BIGDOS.PRG -STA_VDI.PRG -WDIALOG.PRG -NVDI.PRG -CKBD.PRG -RSVX.PRG -HA_ESCC.PRG -MINTNP.PRG -GEMRAM.PRG -WINX.PRG -NOVACAL.PRG -METADOS.PRG The ordering of the associated info- and config- files doesn't matter. Naturally, you don't have to have all these programs installed. That is just the sequence of the possible AUTO folder programs. ********************************************************************************** In the root directory (usually drive C:) there should be -HADES_xx.ACC : Cache management (without this the performance suffers) -HADES_xx.INF : Settings file -NOVA_COL.ACC : Adjustments for the graphics card -NOVA-COL.INF : Info file The alpha and omega for the Hades' performance is the CPU cache of the 68060 and 68040 respectively. So that is why the HADES_xx.ACC becomes the critical control center for the speed of programs. There are 2 different internal caches: - the data-cache is not critical for most programs and therefore as a rule it is usually switched on - the instruction-cache is more critical and must be turned off at program start for programs with self-modifying code. Once the program is fully loaded, the instruction-cache can usually be turned back on. Of course, clean programs can also run with the instruction-cache turned on. HADES_B3.ACC: Cache settings from the file HADES_B.INF are used. HADES_B6.ACC: Cache is only manually affected. Correction for XAIRON. You also have the choice between write-through and copy-back mode. With write-through mode the main memory is also updated directly with each write access to the cache. With copy-back mode the data is not written to main memory until it has changed. This reduces the write accesses to RAM and results in further speed improvements. With the ASCII control file HADES_xx.INF the state of the processor caches can be individually set for each program start. This file can be viewed with any text editor and customized for your own programs. Must read! If there is no entry in the HADES_xx.INF file for a program, then the internal caches are turned off for 1 second when the program starts (Of course, HADES_xx.ACC must be active!!!). So with the appropriate cache settings you should get almost any reasonably clean program running on the Hades. Assembly If the assembly is done by us, then you can be confident that it will work properly. Otherwise, read the following explanations thoroughly! What you must keep in mind when installing the Hades mainboard -------------------------------------------------------------- Paying attention to the following points is absolutely necessary to ensure the later perfect functioning of your Hades. ATTENTION: The installation and start up are done soley at your own risk and should only be carried out by trained and qaulified personnel. Medusa Computer Systems accepts no liability for any consequential damage caused by this or any other related Hades instructions!!! 1. The Hades mainboard has standard PC dimensions and fits into any PC case. So the choice of a case is up to you. The associated power supply should have at least 200W of output power to handle any subsequent RAM expansions. Please check with your case supplier in regards to this. 2. PC mainboards are screwed into the case in various positions. The situation is different with the Hades. CAUTION!!! With the Hades it is absolutely necessary to place paper or plastic washers between the fastening screws and the mainboard so that the conductive tracks in the immediate vicinity of the mounting holes are not damaged. Otherwise, there is a threat to the mainboard of a dangerous short circuit. On the underside, you can eliminate the risk of short circuit by placing double layers of fabric tape over the holes. All you have to do is carefully poke a small hole through the tape strips so that the screws will fit through them. 3. For the interface assignments (MODEM, Floppy, IDE etc.) please refer to the enclosed layout plan. Pin 1 of each cable (Pin 1 is marked in red) must point towards the keyboard connection. 4. The serial interface on the IDE port is not used, as well as the 4 pin header near the floppy ports. The Local Talk interface is not currently supported by the TOS operating system. 5. When installing a floppy drive, make sure it is set to DS0. If in doubt, ask your dealer. 6. On the mainboard, a voltage regulator IC is placed in the vicinity of the PCI slots. Please make sure that it doesn't come into contact with any adjacent cards (short circuit danger) or cables (same by scorching). 7. The power supply connectors on the mainboard are PC compliant; so any PC power supply can be connected as long as it is sufficient in terms of its performance. Please note the enclosed layout plan. 8. Equipping the mainboard with memory modules is extremely simple. So find PS/2 Fast Page SIMMs to use. EDO-SIMMs can also be used! When fitting please pay attention that they have sufficient speed. For the Hades SIMMs of 60ns or faster are necessary. You must populate the memory modules starting with the slot closest to the CPU. The following modules must then be fitted in sequence. 9. The memory stick slots are organized by pairs in so-called "banks". The Hades has four banks of two slots each. The individual banks must always be fitted in full and in pairs. In addition, each bank must be fitted with parts of the same memory size (e.g. two 8MB). So an odd number of SIMM modules or different memory sizes or speeds within each bank is not possible - only a part of the total memory fitted may be recognized under certain circumstances if this requirement is violated. 10. The Hades mainboard is designed for use with the MOTOROLA 68040 as well as the 68060. We supply the mainboard according to the customer's wishes with all settings already done for the respective CPU ordered. No additional settings or changes are required. If you have purchased a Hades with a 68040 CPU, you can retrofit a 68060 later yourself or vice versa if your Hades is too fast for you. - Floppy drive With the Hades you can use any normal PC floppy drive. (DD and HD, 3.5"). A maximum of 2 floppy disks can be managed. Since a new floppy disk controller is used (WD37C65), floppy disks can only be formatted via the operating system or with PUMPUP or ECOPY 1.72. PUMPUP is a shareware formatting program from Claus Brod which offers the most common disk formats and automatically uses only the operating system routines. You can find it on the utility disk. For ECOPY you must deactivate the direct FDC access with: "Options->Drive parameters->Access via: Operating system (BIOS)". WARNING: The new floppy controller only knows PC compatible formats. Higher formatted TOS disks and other special formats such as tricky boot sectors are not supported on the new FDC. This can lead to incompatible installation disks having to be unzipped on a normal ST/TT before being transferred to the Hades using a PC compatible floppy disk. Finally, here are a few general notes: - Hard disk driver Use HDDRIVER 8.01. It works reliably. Other drivers at your own risk!! - BIGDOS Very useful extension allowing the use of larger MSDOS compatible partitions. Contrary to the specification in the associated text, BIGDOS should be started after STA_VDI.PRG or NVDI.PRG in the AUTO folder. Everything else is in the text. - The keyboard reset does not reset the ISA bus variants of the Mach64 graphics cards. This means that in the first phase of the boot process no meaningful screen output is possible and only after the graphics card driver is loaded will the correct image appear again. With a "proper" reset via the reset switch, the boot logo immediately appears. - The high speed of the Modem 2 interface (from 19200 Baud) is set via the low baud rates. For this you need the TOS version from 08/13/96 or newer (check Desktop Info from the Desktop menu). For effective use of this interface we recommend you use HSMODEM and in particular the extra patched version of HA_ESCC (available from your software dealer). - Should the enclosed mouse not function properly, please check first if the switch on the bottom is set to "ATARI". The factory default is usually "AMIGA". - The 68060 CPU is very sensitive in regards to the power supply voltage as, in contrast with the rest of the mainboard, it operates with 3.3V instead of 5V. This means that after switching off the power you have to wait a maximum of 5 minutes before you can turn the Hades back on. Therefore, you should try to use the reset button when possible since the computer can be rebooted immediately. Hardware General ********************************************************************* The Hades is normally shipped with a bus clock frequency of 32MHz, except with the MC68060RC50 where it is 30MHz. The transfer rates in each case are given the required bus clocks. Processor ********************************************************************* As processors the MC68040 or the MC68060 can be used. Both processors have a processor clock double that of the bus clock. However, the MC68060 executes 2 instructions per processor clock cycle. Please note the software differences between the two processors. For example, there is no MOVEP with the MC68060. The details can be found in the corresponding data books. For the MC68040 a 16MHz oscillator must be used and the solder bridge at the bottom left next to the processor must be set to +5V. For the MC68060 the crystal is 15MHz and the bridge must be set at 3.3V. For this also refer to the circuit diagram. The bus clock and the processor frequencies are automatically set from the hardware to 2,4 resp. 8-multiple clock rule. Operating System ********************************************************************* The standard operating system is a custom TOS 3.06 on the Hades board. The operating system is located there in 4 EPROMs. At power on, the TOS first looks on the PCI bus for an ET4000 graphics card, then for an ET6000 and finally a Mach64. Then it checks the ISA bus. If a graphics card is detected, it will output any startup messages. UU Upper Offset +0 high byte D31-D24 MU Middle Upper Offset +1 middle upper D23-D16 ML Middle Lower Offset +2 middle lower D15-D8 LL Lower Offset +3 low byte D7-D0 The Hades starts the operating system with caches switched off and the MMU high. All 4 Transparent Translation Registers (ITT0, DTT0, ITT1, DTT1) are set as follows: Address: 1 to 1 Caches : non-cachable, serialized RAM ********************************************************************* The Hades has only a linear RAM that is registered as ST-RAM. Address range : $00000000 - $3FFFFFFF Bus width : 32 Bit resp. 64 Bit Interleave Minimum size : 4 Megabyte Maximum size : 1 Gigabyte Burst mode : Yes Transfer rate normal : Byte, Word and Long: Read 4 cycles, Write 3 cycles : Line only 1 module : Read 4-4-4-4, Write 3-4-4-4 : Line interleave : Read 4-1-1-1, Write 3-1-1-1 fast (only 060) : Byte, Word and Long: Read 3 cycles, Write 3 cycles : Line interleave : Read 3-1-1-1, Write 3-1-1-1 Cacheable : Yes The memory modules are equipped in pairs and addressed in the interleave mode. If only one module is used then the transfer rate in burst mode drops to about 55%. With EDO SIMMs the transfer rate does not drop even with only one module. EDO SIMMs can only be used with the Hades060. For FPM SIMMs at least 2 modules must always be used as of the revision "RAMROM Fx" (Fast Hades). The memory modules used are the 72-pin SIMM type. Parity is not necessary and will be ignored. You can use them anyway though. Both FPM and EDO RAM can be used. But this requires different XILINX "RAMROM" versions. FPM : RAMROM 7 or 9 or F3 EDO : RAMROM 16 or F4 The SIMM modules must be rated at least 60ns. The following modules can be used: ---------------------------------- Organization Size ------------------------------------ 1Mx32 (or 36 or 40) 4 Megabyte 2Mx32 8 Megabyte 4Mx32 16 Megabyte 4Mx32 byte wide 16 Megabyte 8Mx32 32 Megabyte 16Mx32 64 Megabyte 16Mx32 byte wide 64 Megabyte 32Mx32 128 Megabyte The control circuits can drive a maxium of 96 memory chips! The following memory configurations are possible: ------------------------------------------------- MC3..0 denotes the memory configuration value. MM1 MM2 MM3 MM4 MM5 MM6 MM7 MM8 Size MC3..0(bit) ---------------------------------------------------------------------- 4MB 4MB 8MB 0101 4MB 4MB 4MB 4MB 16MB 0101 8MB 8MB 16MB 0100 8MB 8MB 4MB 4MB 24MB 0100 8MB 8MB 8MB 8MB 32MB 0100 16MB 16MB 32MB 0011 16MB 16MB 4MB 4MB 40MB 0011 16MB 16MB 16MB 16MB 64MB 0011 16MB 16MB 16MB 16MB 4MB 4MB 72MB 0011 16MB 16MB 16MB 16MB 16MB 16MB 96MB 0011 16MB 16MB 16MB 16MB 16MB 16MB 4MB 4MB 104MB 0011 16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 132MB 0011 32MB 32MB 64MB 0010 32MB 32MB 4MB 4MB 72MB 0010 32MB 32MB 16MB 16MB 96MB 0010 32MB 32MB 32MB 32MB 128MB 0010 32MB 32MB 32MB 32MB 4MB 4MB 136MB 0010 32MB 32MB 32MB 32MB 16MB 16MB 160MB 0010 32MB 32MB 32MB 32MB 32MB 32MB 196MB 0010 64MB 64MB 128MB 0001 64MB 64MB 4MB 4MB 136MB 0001 64MB 64MB 16MB 16MB 160MB 0001 64MB 64MB 64MB 64MB 256MB 0001 ...(etc) to 64MB 64MB 64MB 64MB 64MB 64MB 64MB 64MB 512MB 0001 128MB 128MB 256MB 0000 128MB 128MB 4MB 4MB 264MB 0000 128MB 128MB 16MB 16MB 288MB 0000 128MB 128MB 64MB 64MB 384MB 0000 128MB 128MB 128MB 128MB 512MB 0000 ...(etc) to 128MB 128MB 128MB 128MB 128MB 128MB 1024MB 0000 ROM resp. EPROM ********************************************************************* The ROM area is distributed over four EPROMs. Each EPROM comprises one byte. The designation is UU for the upper byte, MU for the middle upper byte, ML for the middle lower byte and LL for the lower byte. In the ROM area is placed the TOS. It has been moved from the usual Atari address $00E00000 to $7FE00000 to make room for the linear RAM. Address : $7FE00000 - $7FFFFFFF Bus width : 32 Bit Minimum size : 512 Kilobyte Maximum size : 2 Megabyte Burst mode : No Transfer rate : 5 cycles Cacheable : Yes Atari compatible I/O devices and other I/O devices ********************************************************************* All I/O devices can only be addressed in the range from $FFF00000 to $FFFFFFFF and no longer in the previous customary range of $00F00000 to $00FFFFFF since the linear RAM is now there. Reading and writing is only possible in supervisor mode. Address : $FFFF8000 - $FFFFFFFF Bus width : 8 Bit resp. 16 Bit Size : 32 Kilobyte Burst mode : No Transfer rate : 4-? cycles Cacheable : No In the folder "UTILITY" you can find a program named "KORR00FF.PRG". If you run this, you can have any unauthorized accesses to $00FFxxxx redirected to the $FFFFxxxx range. Be careful though, since under certain circumstances unwanted corrections can be made if a byte combination happens to look like an I/O address. PCI Bus ********************************************************************* Interrupt Acknowledge on the PCI bus is not possible. The INTA#-INTD# lines of each slot are combined and fed to the TTMFP. Unused memory areas do not trigger a bus error, but after approximately 125us an Auto-Data-TransferAcknowledge is triggered with undefined value. Slot TTMFP connection ---------------------------- PCI1 IO0 Pin 25 PCI2 IO1 Pin 26 PCI3 IO2 Pin 27 PCI4 IO5 Pin 30 DMA from the PCI bus is possible. However, at the moment, only the RAM can be accessed. The REQ# and GNT# lines of PCI3 and PCI4 are connected together and occupy DMA channel 3. Seen from the PCI bus, the RAM is located from $80000000-$BFFFFFFF. Slot DMA channel Priority -------------------------------------------- PCI1 1 highest PCI2 2 medium PCI3 + PCI4 3 lowest PERR# and SERR# are not evaluated. Parity is generated according to PCI specifications but is not controlled. JTAG is not connected. Cache support is not implemented. Special Cycle is not possible. Memory Read Multiple is not possible. Dual Address Cycle is not possible. Memory Read Line is not possible. Memory Write and Invalidate is not possible. Since the PCI bus should not be cacheable due to the cache coherence of the processor, burst accesses do not occur and are therefore not supported at the moment. The Motorola processsors also have a Burst-Longword-Sequence that is not supported by the PCI bus. The following accesses are supported: ------------------------------------- I/O read and write Memory read and write Configuration read and write DMA read and write (no burst) Addresses: Slot Configuration I/O Memory ---------------------------------------------------------------- PCI1 $A008xxxx $Bxxxxxxx $80000000-$8FFFFFFF PCI2 $A004xxxx $Bxxxxxxx $80000000-$8FFFFFFF PCI3 $A002xxxx $Bxxxxxxx $80000000-$8FFFFFFF PCI4 $A001xxxx $Bxxxxxxx $80000000-$8FFFFFFF Bus width : 32 bit resp. 64 bit Configuration size : 64 Kilobyte resp. 256 byte (mirrored) I/O size : 256 Megabyte Memory size : 256 Megabyte Burst mode : No Transfer rate : 3-? cycles Cacheable : partially possible ISA Bus ********************************************************************* DMA is not supported on the ISA bus. All interrupt signals on each slot are combined and fed to the STMFP. Slot STMFP connection ---------------------------- ISA1 IO3 Pin 28 ISA2 IO7 Pin 32 For byte accesses in the I/O area $FFF30000-$FFF3FFFF the bytes are transferred by reading and writing to and from SD0-7, both for high and low byte accesses. This is e.g. necessary for ET4000 graphics cards with NVDI. In the rest of this area, the byte on the other half of the word is also output when writing. I/O address : $FFF00000-$FFF7FFFF Memory address : $FF000000-$FF7FFFFF Bus width : 16 bit I/O size : 8x64 Kilobyte mirrored Memory size : 8 Megabyte Burst mode : No Transfer rate : 5-? cycles Cacheable : Normally no, but possible VME Bus ********************************************************************* The VME bus is in principle built the same as the Atari TT. So bus arbitration and the serial bus are not supported. Only the interrupts 3, 5 and 7 work. They are all vector interrupts. SYSFAIL and BERR are not connected. AM0, AM2 and AM3 are connected to +5V and AM1 to GND. AM4 operates normally. So only the following accesses are possible: -standard supervisor, data area -short supervisor I/O area -interrupt acknowledge 3, 5 and 7 The register $FFFF8717 can be used to mask the interrupts. Bit 7 Mask VME interrupt 7 Bit 5 Mask VME interrupt 5 Bit 3 Mask VME interrupt 3 Setting the bit indicates the interrupt is enabled. At startup, the bits are set to 0 and so the VME interrupts are disabled. Normal : $FE000000-$FEFEFFFF Short : $FEFF0000-$FEFFFFFF Address width : 24 Bit Data bus width : 16 Bit Burst mode : No Transfer rate : 5-? cycles Cacheable : Normally no, but possible SCSI Bus ********************************************************************* The SCSI bus works from the outside just like the TT. However, the data transfer is not done by DMA but is handled by interrupt 2. So do not block it. The whole transfer business is that with a request from the SCSI chip an interrupt 2 is triggered. Then a small routine in the EPROM tries to transport as much data as is ready. For this the interrupt is masked so that no interrupt is triggered by the SCSI in the meantime. If after 10,000 bus errors of 8us=80ms (the routine fully depends on the SCIS and is disrupted by the bus error) no data is transferred to or from the SCSI, then the SCSI transfer interrupt is again enabled and the routine exits. This will continue until all data is transferred or the SCSI is switched off. The register $FFFF8717 is used to control these functions. Bit 0 is connected to the EOP of the SCSI chip and Bit 6 (count is 0) of register $FFFF8715 (SCSI Control). Bit 1 is connected to Bit 7 (Bus Error) of register $FFFF8715 (SCSI Control). This allows the signals missing from the DMA to be set by software. Floppy ********************************************************************* The floppy connection is made with the WD37C65 and is therefore no longer Atari compatible. So you can only use programs that go through the operating system routines for formatting, reading and writing. The data transfer is not by DMA but carried out via interrupt 6 i.e. TTMFP interrupt IO4. For each byte transferred, an interrupt is triggered so do not block the interrupt. Note that for the first floppy drive DS0 must be jumpered. Normally when you get a PC floppy drive DS1 is jumpered. So change that or use floppy cables with twisted wires. - Floppy Drive With the Hades you can use any normal PC floppy drive. (DD and HD, 3.5"). A maximum of 2 floppy disks can be managed. Since a new floppy disk controller is used (WD37C65), floppy disks can only be formatted via the operating system or with PUMPUP or ECOPY 1.72. PUMPUP is a shareware formatting program from Claus Brod which offers the most common disk formats and automatically uses only operating system routines. You can find it on the utility disk. For ECOPY you must deactivate the direct FDC access with: "Options->Drive parameters->Access via: Operating system (BIOS)". WARNING: The new floppy controller only knows PC compatible formats. Higher formatted TOS disks and other special formats such as tricky boot sectors are not supported on the new FDC. This can lead to incompatible installation disks having to be unzipped on a normal ST/TT before being transferred to the Hades using a PC compatible floppy disk. Local Talk and Modem 2 ********************************************************************* These two interfaces are served by a Zilog Z85230. This is the same as the Z8530 used in the Atari TT execpt for a few additional functions. This allows it to be addressed normally via the operating system. Differences between the TT Z8530 and the Hades Z85230: ------------------------------------------------------ PLCK is 14.7456MHz and not 8MHz. TRxTB and TRxTB are connected with 3.7688MHz. Channel A is used as the Local Talk interface and can not be changed. This results in the following values for transfer rates via the XBIOS function 15 "Rsconf" (as of TOS from 08/12/1996): Speed value Baud rate ------------------------------------------------------ 0 19200 ;as before 1 9600 ;as before 2 4800 ;as before 3 3600 ;as before 4 2400 ;as before 5 2000 ;as before 6 1800 ;as before 7 1200 ;as before 8 600 ;as before 9 300 ;as before 10 38400 ;new instead of 200 Baud 11 57600 ;new instead of 150 Baud 12 76800 ;new instead of 134 Baud 13 115200 ;new instead of 110 Baud 14 153600 ;new instead of 75 Baud 15 230400 ;new instead of 50 Baud If dial-up programs do not go through the operating system routines then the baud rates are set incorrectly. So select Modem 2 in the DUN program with the baud rate 19200, so that rest (clock source etc.) will be preset correctly. Then you can use the CPX module "Modem" to set the correct baud rate. However, at this time, the old baud rates (50, 75, etc.) appear in the selection menu of this module so use the table above to set the actual baud rate. SCU ********************************************************************* The SCU is not emulated in the Hades. No functions regarding interrupt control can be used. Hardware Clock ********************************************************************* The Hades contains a hardware clock compatible with the clock built into the Atari TT. ROM Port Card ********************************************************************* The ROM port card is connected to the ISA bus. By means of the accessory, the 3 ROM slots can be turned on and accessed through the MMU at the original address $FA0000 and following. The ROM port selection can also be adjusted automatically by a corresponding entry in the HADES_XX.INF file. However, the memory overlay cuts a hole out of RAM at location $FA0000 ff.. This memory is then lost and in addition the memory space is then divided. If you want to use a ROM port card you can easily register it at start up (through an entry in HADES_xx.INF). It is no longer possible to switch off the ROM port card during operation. Special Port Pin Assignments ********************************************************************* Midi: ----- 9 Pin D-Sub ----------- Pin 1 Midi trough TLR Pin 2 Midi out OLR Pin 3 Midi OLD Pin 4 Midi in 1 ILR Pin 5 Midi LID Pin 6 Midi in 2 IPD Pin 7 GND Pin 8 GND Pin 9 VCC (+5) Local Talk (RS422/423): ----------------------- 9 Pin D-Sub ----------- (RS232 +/-5V Pin) Pin 1 DTR-/HSKO -> DTR 4 + 7 Pin 2 CTS+/HSKI GND 5 Pin 3 TxD- TxD 3 Pin 4 GND GND 5 Pin 5 RxD- RxD 2 Pin 6 TxD+ Pin 7 DCD-/GPI DCD 1 Pin 8 RxD+ GND 5 Pin 9 NC Hades Memory Map ********************************************************************* (rw=read and write, wo=write only, ro=read only) Address Mode Usage --------------------------------------------------------------------- 00000000 - 3FFFFFFF rw 1GB RAM 70000000 - 71FFFFFF wo Memory Configuration Register a20=1 sets MC0=1 -> single-sided module a21=1 sets MC1=1 a22=1 sets MC2=1 a23=1 sets MC3=1 -> only 1 module,no burst 7FE00000 - 7FFFFFFF wo 2MB EPROM 80000000 - 8FFFFFFF rw PCI Memory Area A0010000 - A001FFFF rw PCI 4 Configuration Area A0020000 - A002FFFF rw PCI 3 Configuration Area A0040000 - A004FFFF rw PCI 2 Configuration Area A0080000 - A008FFFF rw PCI 1 Configuration Area B0000000 - BFFFFFFF rw PCI I/O Area FE000000 - FEFEFFFF rw VME Bus Standard Access FEFF0000 - FEFFFFFF rw VME Bus Short Access FF000000 - FF7FFFFF rw ISA Bus Memory Access FF7A0000 - FF7BFFFF ro ROM Port A (with ROM Port card) FF7C0000 - FF7DFFFF ro ROM Port B (with ROM Port card) FF7E0000 - FF7FFFFF ro ROM Port C (with ROM Port card) FFF00000 - FFF2FFFF rw ISA Bus I/O Access. Byte write on both halves of the word. FFF30000 - FFF3FFFF rw ISA Bus I/O Access. Byte write on both halves of the word. Byte read always from SD0-7 (for ET4000 and others) FFF40000 - FFF7FFFF rw ISA Bus I/O Access. Byte write on both halves of the word. FFF00000 - FFF0001F rw IDE Register 0 FFF00020 - FFF0003F rw IDE Register 1 FFF00080 - FFF0009F rw Floppy Controller Chip Select FFF000C0 - FFF000DF rw Floppy Controller Digital Output Register FFF000E0 - FFF000FF wo Floppy Controller Control Register FFFF8000 - FFFF86FF rw Not Used. Dummy access (no bus error!) FFFF8701 rw SCSI Transfer Address high byte FFFF8703 rw SCSI Transfer Address middle upper byte FFFF8705 rw SCSI Transfer Address middle lower byte FFFF8707 rw SCSI Transfer Address low byte FFFF8709 rw SCSI Byte Counter high byte FFFF870B rw SCSI Byte Counter middle upper byte FFFF870D rw SCSI Byte Counter middle lower byte FFFF870F rw SCSI Byte Counter low byte FFFF8710 - FFFF8713 rw SCSI Rest Data Register by SCSI read FFFF8715 rw SCSI Control Register: Bit 7: Bus Error Bit 6: Byte Count is NULL Bit 1: DMA enable (resp. INT 2 active) Bit 0: SCSI write. 0=SCSI read FFFF8717 rw SCSI and Interrupt Control Register: (if=1) Bit 7: VME Interrupt 7 active Bit 5: VME Interrupt 5 active Bit 3: VME Interrupt 3 active Bit 1: Bus Error for SCSI Control Register Bit 0: Byte Count is Null for SCSI Control Register FFFF8800 - FFFF88FF rw ST Sound Chip same as ST and TT FFFF8961 rw Clock Register Select FFFF8963 rw Clock Data Register FFFF8C80 - FFFF8CFF rw SCC Register Allocation like with the TT. Channel A: Local Talk Channel B: Modem 2 FFFFFA00 - FFFFFA3F rw STMFP like with the ST and TT: IO0: Printer Busy IO1: DCD Modem 1 IO2: CTS Modem 1 IO3: Interrupt ISA 1 IO4: Interrupt ACIAs IO5: Interrupt IDE IO6: RI Modem 1 IO7: Interrupt ISA 2 FFFFFA80 - FFFFFABF rw TTMFP like with the TT: IO0: Interrupt PCI 1 IO1: Interrupt PCI 2 IO2: Interrupt PCI 3 IO3: RI Modem 2 IO4: Floppy Interrupt IO5: Interrupt PCI 4 IO6: Clock Interrupt IO7: SCSI Interrupt FFFFFC00 - FFFFFC03 rw Keyboard ACIA FFFFFC04 - FFFFFC07 rw MIDI ACIA -end-