Что-то не так?
Пожалуйста, отключите Adblock.
Портал QRZ.RU существует только за счет рекламы, поэтому мы были бы Вам благодарны если Вы внесете сайт в список исключений. Мы стараемся размещать только релевантную рекламу, которая будет интересна не только рекламодателям, но и нашим читателям. Отключив Adblock, вы поможете не только нам, но и себе. Спасибо.Как добавить наш сайт в исключения AdBlock
Оставайся на связи!Хочешь быть всегда в курсе новостей? Подпишись на Twitter! Tweets by @qrzru
HwB: EISA (Tech) Connector
This section is currently based solely on the work by Mark Sokos.
This file is intended to provide a basic functional overview of the EISA Bus, so that hobbyists and amateurs can design their own EISA compatible cards.
It is not intended to provide complete coverage of the EISA standard.
EISA is an acronym for Extended Industry Standard Architecture. It is an extension of the ISA architecture, which is a standardized version of the bus originally developed by IBM for their PC computers. EISA is upwardly compatible, which means that cards originally designed for the 8 bit IBM bus (often referred to as the XT bus) and cards designed for the 16 bit bus (referred to as the AT bus, and also as the ISA bus), will work in an EISA slot. EISA specific cards will not work in an AT or an XT slot.
The EISA connector uses multiple rows of connectors. The upper row is the same as a regular ISA slot, and the lower row contains the EISA extension. The slot is keyed so that ISA cards cannot be inserted to the point where they connect with the EISA signals.
+5, -5, +12, -12
Power supplies. -5 is often not implemented.
Address Enable. This is asserted when a DMAC has control of the bus. This prevents an I/O device from responding to the I/O command lines during a DMA transfer.
Bus Address Latch Enable. The address bus is latched on the rising edge of this signal. The address on the SA bus is valid from the falling edge of BALE to the end of the bus cycle. Memory devices should latch the LA bus on the falling edge of BALE.
Bus Clock, 33% Duty Cycle. Frequency Varies. 8.33 MHz is specified as the maximum, but many systems allow this clock to be set to 10 MHz and higher.
Byte Enable. Indicates to the slave device which bytes on the data bus contain valid data. A 16 bit transfer would assert BE0 and BE1, for example, but not BE2 or BE3.
Channel Check. A low signal generates an NMI. The NMI signal can be masked on a PC, externally to the processor (of course). Bit 7 of port 70(hex) (enable NMI interrupts) and bit 3 of port 61 (hex) (recognition of channel check) must both be set to zero for an NMI to reach the cpu.
Channel Ready. Setting this low prevents the default ready timer from timing out. The slave device may then set it high again when it is ready to end the bus cycle. Holding this line low for too long can cause problems on some systems. CHRDY and NOWS should not be used simultaneously. This may cause problems with some bus controllers.
Command Phase. This signal indicates that the current bus cycle is in the command phase. After the start phase (see START), the data is transferred during the CMD phase. CMD remains asserted from the falling edge of START until the end of the bus cycle.
System Data lines. They are bidrectional and tri-state.
EISA Slave Size 16. This is used by the slave device to inform the bus master that it is capable of 16 bit transfers.
EISA Slave Size 32. This is used by the slave device to inform the bus master that it is capable of 32 bit transfers.
EISA Ready. If this signal is asserted, the cycle will end on the next rising edge of BCLK. The slave device drives this signal low to insert wait states.
I/O size 16. Generated by a 16 bit slave when addressed by a bus master.
I/O Read Command line.
I/O Write Command line.
Interrupt Request. IRQ2 has the highest priority.
Latchable Address lines.
Asserting this signal prevents other bus masters from requesting control of the bus.
Master Acknowledge for slot x: Indicates that the bus master request (MREQx) has been granted.
16 bit bus master. Generated by the ISA bus master when initiating a bus cycle.
Memory/Input-Output. This is used to indicate whether the current bus cycle is a memory or an I/O operation.
Memory Access, 16 bit
Memory Read Command line.
Master Request for Slot x: This is a slot specific request for the device to become the bus master.
Master Burst. The bus master asserts this signal in response to SLBURST. This tells the slave device that the bus master is also capable of burst cycles.
Memory Write Command line.
No Wait State. Used to shorten the number of wait states generated by the default ready timer. This causes the bus cycle to end more quickly, since wait states will not be inserted. Most systems will ignore NOWS if CHRDY is active (low). However, this may cause problems with some bus controllers, and both signals should not be active simultaneously.
Oscillator, 14.318 MHz, 50% Duty Cycle. Frequency varies.
Refresh. Generated when the refresh logic is bus master.
This signal goes low when the machine is powered up. Driving it low will force a system reset.
System Address Lines, tri-state.
System Bus High Enable, tristate. Indicates a 16 bit data transfer.
Slave Burst. The slave device uses this to indicate that it is capable of burst cycles. The bus master will respond with MSBURST if it is also capable of burst cycles.
Standard Memory Read Command line. Indicates a memory read in the lower 1 MB area.
Standard Memory Write Commmand line. Indicates a memory write in the lower 1 MB area.
Start Phase. This signal is low when the current bus cycle is in the start phase. Address and M/IO signals are decoded during this phase. Data is transferred during the command phase (indicated by CMD).
Terminal Count. Notifies the cpu that that the last DMA data transfer operation is complete.
Write or Read. Used to indicate if the current bus cycle is a read or a write operation.Contributor: Joakim Цgren, Mark Sokos Sources: Mark Sokos EISA page
Sources: "Eisa System Architecture, 2nd Edition" by Tom Shanley and Don Anderson, ISBN 0-201-40995-X Please send any comments to Joakim Цgren.