- 您現(xiàn)在的位置：買(mǎi)賣(mài)IC網(wǎng) > PDF目錄98071 > S82451KX (INTEL CORP) SPECIALTY MICROPROCESSOR CIRCUIT, PQFP144 PDF資料下載
參數(shù)資料
| 型號(hào)： | S82451KX |
| 廠商： | INTEL CORP |
| 元件分類(lèi)： | 微控制器/微處理器 |
| 英文描述： | SPECIALTY MICROPROCESSOR CIRCUIT, PQFP144 |
| 封裝： | QFP-144 |
| 文件頁(yè)數(shù)： | 147/180頁(yè) |
| 文件大?。?/td> | 1094K |
| 代理商： | S82451KX |
第1頁(yè)第2頁(yè)第3頁(yè)第4頁(yè)第5頁(yè)第6頁(yè)第7頁(yè)第8頁(yè)第9頁(yè)第10頁(yè)第11頁(yè)第12頁(yè)第13頁(yè)第14頁(yè)第15頁(yè)第16頁(yè)第17頁(yè)第18頁(yè)第19頁(yè)第20頁(yè)第21頁(yè)第22頁(yè)第23頁(yè)第24頁(yè)第25頁(yè)第26頁(yè)第27頁(yè)第28頁(yè)第29頁(yè)第30頁(yè)第31頁(yè)第32頁(yè)第33頁(yè)第34頁(yè)第35頁(yè)第36頁(yè)第37頁(yè)第38頁(yè)第39頁(yè)第40頁(yè)第41頁(yè)第42頁(yè)第43頁(yè)第44頁(yè)第45頁(yè)第46頁(yè)第47頁(yè)第48頁(yè)第49頁(yè)第50頁(yè)第51頁(yè)第52頁(yè)第53頁(yè)第54頁(yè)第55頁(yè)第56頁(yè)第57頁(yè)第58頁(yè)第59頁(yè)第60頁(yè)第61頁(yè)第62頁(yè)第63頁(yè)第64頁(yè)第65頁(yè)第66頁(yè)第67頁(yè)第68頁(yè)第69頁(yè)第70頁(yè)第71頁(yè)第72頁(yè)第73頁(yè)第74頁(yè)第75頁(yè)第76頁(yè)第77頁(yè)第78頁(yè)第79頁(yè)第80頁(yè)第81頁(yè)第82頁(yè)第83頁(yè)第84頁(yè)第85頁(yè)第86頁(yè)第87頁(yè)第88頁(yè)第89頁(yè)第90頁(yè)第91頁(yè)第92頁(yè)第93頁(yè)第94頁(yè)第95頁(yè)第96頁(yè)第97頁(yè)第98頁(yè)第99頁(yè)第100頁(yè)第101頁(yè)第102頁(yè)第103頁(yè)第104頁(yè)第105頁(yè)第106頁(yè)第107頁(yè)第108頁(yè)第109頁(yè)第110頁(yè)第111頁(yè)第112頁(yè)第113頁(yè)第114頁(yè)第115頁(yè)第116頁(yè)第117頁(yè)第118頁(yè)第119頁(yè)第120頁(yè)第121頁(yè)第122頁(yè)第123頁(yè)第124頁(yè)第125頁(yè)第126頁(yè)第127頁(yè)第128頁(yè)第129頁(yè)第130頁(yè)第131頁(yè)第132頁(yè)第133頁(yè)第134頁(yè)第135頁(yè)第136頁(yè)第137頁(yè)第138頁(yè)第139頁(yè)第140頁(yè)第141頁(yè)第142頁(yè)第143頁(yè)第144頁(yè)第145頁(yè)第146頁(yè)當(dāng)前第147頁(yè)第148頁(yè)第149頁(yè)第150頁(yè)第151頁(yè)第152頁(yè)第153頁(yè)第154頁(yè)第155頁(yè)第156頁(yè)第157頁(yè)第158頁(yè)第159頁(yè)第160頁(yè)第161頁(yè)第162頁(yè)第163頁(yè)第164頁(yè)第165頁(yè)第166頁(yè)第167頁(yè)第168頁(yè)第169頁(yè)第170頁(yè)第171頁(yè)第172頁(yè)第173頁(yè)第174頁(yè)第175頁(yè)第176頁(yè)第177頁(yè)第178頁(yè)第179頁(yè)第180頁(yè)
PRELIMINARY
61
A
82454KX/GX (PB)
3.3
PCI Bus Interface
The PB has a standard master/slave PCI bus interface. All legal PCI (PCI specification 2.0) bus transactions
are supported. PCI cycle termination and error logging/reporting are discussed in the Data Integrity and Error
Handling section. The PCI arbitration unit is not implemented in the PB.
PCI Locks. Systems which support PCI initiate locks (either inbound locks or peer-to-peer) must configure the
arbiter for full bus locks rather than resource locks. The PB will not recognize resource locks made by peer-to-
peer accesses. When a PCI master asserts LOCK# while targeting the PB, the locked PCI transactions are
converted to locked host bus transactions. The host bus lock continues as long as the PCI master asserts
LOCK# for exclusive access to the PB. The host bus lock is assisted by the bridge continuing to assert BPRI#
as long as the PCI bus is asserting resource lock to the bridge. Additional locked CPU transactions are issued
if the PCI master continues to burst.
In systems in which target abort reporting is disabled, the write portion of a lock will be committed even when
the read portion is aborted.
NOTE:
Locks that cross cache line boundaries initiated on the PCI bus will not generate a SPLCK# signal on the
host bus. This should be understood by all host bus agents. Neither the PB nor the MC require SPLCK#
assertion.
Host Bus Locks. Any transactions that target the bridge during a host bus lock are converted into a similar PCI
lock transaction. The lock on the PCI bus is held until the host bus lock is released. Locks over the Frame
Buffer region can be disabled through a mode bit in the PCI Frame Buffer Range Register.
NOTE:
Locks that split across PCI host bus device boundaries (originate to one device and complete to another)
are only supported for shadowed memory, and then only behind the compatibility PB. Shadowed memory
is memory mapped for read only or write only in the MC and the opposite way in the PB. An update may
be required for older non-PCI 2.0 compliant device drivers to comply with this. Since the revision 2.0 of the
PCI specification does not allow locks to cross device boundaries, this will not be an issue with new device
drivers.
Indivisible Operations. CPU initiated read operations that cross a Dword boundary (e.g., Read 8 Bytes, Read
16 Bytes, etc.) are indivisible operations on the host bus. However, since the PCI protocol allows a target
device to disconnect at any point in a transfer sequence, these operations must be locked indivisible on the PCI
bus. The PB optionally locks all CPU initiated reads that cross a Dword boundary. This mode is enabled by
setting the Lock Atomic Reads in the PB Configuration Register. CPU initiated Write operations (e.g., Write 8
Bytes, Write 16 Bytes, etc.) are indivisible operations on the host bus. However, these accesses can not be
made indivisible on the PCI bus because the PCI Specification states that the first transaction of a locked
operation must be a read. Therefore, software must not rely upon the atomicity of CPU initiated write transac-
tions greater then 32 bits once they are translated to the PCI bus.
Software Generated Special Cycles. This optional feature is not supported by the 450KX/GX PCIset.
相關(guān)PDF資料 |
PDF描述 |
|---|---|
| S83296SA | 16-BIT, MROM, 40 MHz, MICROCONTROLLER, PQFP100 |
| SB83296SA | 16-BIT, MROM, 40 MHz, MICROCONTROLLER, PQFP100 |
| S83C196MH | 16-BIT, MROM, 16 MHz, MICROCONTROLLER, PQFP80 |
| S83C51FB-BB44 | 8-BIT, MROM, 24 MHz, MICROCONTROLLER, PQFP44 |
| S83C51FC-5B44 | 8-BIT, MROM, 16 MHz, MICROCONTROLLER, PQFP44 |
相關(guān)代理商/技術(shù)參數(shù) |
參數(shù)描述 |
|---|---|
| S82452KX | 制造商:未知廠家 制造商全稱(chēng):未知廠家 功能描述:Data Path Controller |
| S82453KX | 制造商:未知廠家 制造商全稱(chēng):未知廠家 功能描述:DRAM Controller |
| S82454KX | 制造商:未知廠家 制造商全稱(chēng):未知廠家 功能描述:PCI Bus Interface/Controller |
| S8248P12NF | 功能描述:ANTENNA 824-896MHZ 8DBI N FML RoHS:是 類(lèi)別:RF/IF 和 RFID >> RF 天線 系列:* 標(biāo)準(zhǔn)包裝:1 系列:* |
| S82510 DIE | 制造商:Intel 功能描述: |
發(fā)布緊急采購(gòu)，3分鐘左右您將得到回復(fù)。