View PM7375_1563876.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface pmc-sierra, inc. 105 - 8555 baxter place burnaby, bc canada v5a 4v7 (604) 415-6000 PM7375 revision f device errata issue 4: december, 1997
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface i
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface i contents 1. introduction ................................................................................................................. ............................ 2 1.1. d evice i dentification ............................................................................................................................. 2 1.2. r eferences ............................................................................................................................... .................. 2 2. lasar-155 revision f anomalies .............................................................................................. ........ 3 2.1. (fixed) pcid c ontroller s ynchronization ............................................................................... 3 2.2. (fixed) pci problem d uring t arget b urst ................................................................................. 3 2.3. (fixed) pci b us r elease problem ................................................................................................... 3 2.4. (fixed) cru d iagnostic l oopback ................................................................................................ 3 2.5. (fixed) ad[15:8] b yte c orruption .................................................................................................. 3 2.6. (fixed) pci b us d evice s elect (idsel) problem ........................................................................ 3 2.7. (fixed) r etry t ransaction a fter a t arget a bort ................................................................. 3 2.8. (fixed) pci b us l ock - up d uring b urst r ead t ransaction .................................................... 3 2.9. (fixed) i ncorrectly s ets the p arity e rror .............................................................................. 3 2.10. (fixed) i ncorrect rmdr s tatus f ield for crc-10 ................................................................... 4 2.11. (fixed) t ransmit b uffer m ust b e dword in s ize .................................................................... 4 2.12. r ace c ondition in r eference q ueues ........................................................................................... 4 2.13. req# is asserted during i dle s tate after target disconnect ............................................ 6 2.14. lasar-155 c hanges stop# during the current data phase ................................................. 9 2.15. t ransaction without driving the address and command bus ......................................... 10 2.16. lasar-155 still acts as master after a t arget a bort and soe_e=1 .............................. 10 2.17. b urst read of lasar-155 pci registers causes dma error ............................................... 11 2.18. t hermal c onsiderations ................................................................................................................ 11 2.19 b oundary s can ............................................................................................................................... ... 11 contacting pmc-sierra.......................................................................................................... ..................... 13
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 2 1. introduction this document is the device errata sheet for the revision f of the PM7375 lasar-155?. this document is not the errata sheet for the lasar-155 long form datasheet (pmc-931127). 1.1. device identification this document applies only to revision f of PM7375 lasar-155. as illustrated in figure 1.1, the revision code is marked on the face of the device. the lasar-155 revision f is either package in a 208-pin mqfp or a 208-pin slugged pqfp. figure 1.1: lasar-155 branding format. 1 52 53 208 104 105 156 157 revision code PM7375-sc-p cb612922 f m9615 tm . . . . . . l asar- 155 1.2. references ? pmc-931127, local atm segmentation and reassembly & physical layer interface, issue 4, september, 1996. ? pmc-951042, lasar-155 network interface card (nic) optical reference design, issue 2, april, 1996. pci special interest group, pci local bus specification, june 1, 1995, version 2.1.
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 3 2. lasar-155 revision f anomalies this section describes any anomalies associated with revision f of the lasar-155. for each anomaly, the known work-around and the operating constraints, with and without the work-around, are also described. 2.1. (fixed) pcid controller synchronization this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.2. (fixed) pci problem during target burst this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.3. (fixed) pci bus release problem this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.4. (fixed) cru diagnostic loopback this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.5. (fixed) ad[15:8] byte corruption this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.6. (fixed) pci bus device select (idsel) problem this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.7. (fixed) retry transaction after a target abort this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.8. (fixed) pci bus lock-up during burst read transaction this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.9. (fixed) incorrectly sets the parity error this problem was first reported in pmc-960529 issue 2 has been fixed in rev f.
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 4 2.10. (fixed) incorrect rmdr status field for crc-10 this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.11. (fixed) transmit buffer must be dword in size this problem was first reported in pmc-960529 issue 2 has been fixed in rev f. 2.12. race condition in reference queues description there is a possibility of a race condition when the lasar-155 inserts a new element into the following queues: ? receive management descriptor reference (rmdr) ready queue, ? receive packet descriptor reference (rpdr) ready queue, or ? transmit descriptor reference (tdr) free queue. the race condition is that the write_pointer may be incremented before the element is fully written into the queue. when this occurs, the last queue element is invalid until the write operation is fully completed. this is illustrated in the example below: figure 2.1: queue race condition example. start_pointer end_ poi nt er read_pointer wr it e_ point er . reference qu eu e start_pointer end_ poi nt er read_ pointer wr i t e_ point er . reference qu eu e invalid start_pointer end_ poi nt er read_ pointer wr i t e_ point er . reference qu eu e t ime t t ime t +1 t ime t + 2 ? at "time t", the lasar-155 is ready to insert a new element into the reference queue. ? at "time t+1", the write_pointer is increment before the new element is written into the queue. as a result, the position referenced by the write_pointer contains invalid data. ? at "time t+2", the new element is added. now the position referenced by the write_pointer contains valid data.
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 5 work around to ensure that only valid queue elements are read, the device driver first marks all queue elements as "unused". this is done when initializing the queues. when there is a notification that one or more elements are inserted into the queue, the device driver checks whether the queue element is "unused". if it is marked as "unused", the device driver will read the same position again until the new element is added. this is illustrated in the following example: figure 2.2: work around to queue race condition. start_pointer end_ poi nt er read_pointer wr it e_ point er . reference qu eu e unus ed unus ed unus ed unus ed unus ed unus ed t ime t t ime t +1 t ime t + 2 start_pointer end_ poi nt er read_pointer wr it e_ point er . reference qu eu e unus ed unus ed unus ed unus ed unus ed unus ed start_pointer end_ poi nt er read_ pointer wr i t e_ point er . reference qu eu e unus ed unus ed unus ed unus ed unus ed ? at "time t", the lasar-155 is ready to insert a new element into the reference queue. all the unused elements are marked "unused". ? at "time t+1", the write_pointer is increment before the new element is written into the queue. as a result, the position referenced by the write_pointer still contains the "unused" tag. ? at "time t+2", the new element is added. now the position referenced by the write_pointer contains valid data. it is recommended that the "unused" be defined as "fffff". operating constraints with work around none. operating constraints without work around there is a possibility that the queue element may contain invalid data.
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 6 2.13. req# is asserted during idle state after target disconnect description after a target disconnect, the lasar-155 does not deassert the req# for two clock cycles when it should. according to the pci 2.1 specification, when the current data transaction is terminated by the target, either retry or disconnect, the master must deassert its req# for a minimum of two clock cycles. these two clock cycles are defined as follows: the first clock cycle being when the bus transitions to the idle state (at the end of the transaction where stop# is asserted) and the second either one clock cycle before or one clock cycle after the idle state. the lasar-155 correctly deasserts req# for one clock cycle before the idle state and then incorrectly reasserts the req# during the idle state. figure 2.3 after a target disconnect the req# is asserted during idle state. devsel# irdy# trdy# stop# req# req# should be asserted here req# is asserted work around the impact of this problem depends on the arbitration scheme used. this problem should not affect normal operation of the pci bus. typical arbitration schemes use a combination of agent priority and round robin access. the lasar-155 will request the bus one clock cycle earlier than it should. however, other agents will still have access to the bus via the round robin arbitration. a typical arbitration example that implements a fairness algorithm is found in the pci local bus specification 2.1. this example assumes a two level bus architecture with the higher priority agents attached to level 1 (low latency or greater bandwidth). second level agents have equal access to the bus with respect to other second level agents. however, second level agents, as a group, have equal access to the bus as level one agents as shown in the following example:
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 7 figure 2.4 typical pci bus arbitration using a "fairness algorithm" agent b agent a level 2 level 2 agent y agent x agent z level 2 first level: agent a, agent b, and level 2 ( where level 2 is the next level 2 agent requesting the bus. second level: agent x, agent y, agent z if all agents have their req# lines asserted then the agents accessing the bus would be as follows: a, b, level 2 (this time it is x) a, b, level 2 (this time it is y) a, b, level 2 (this time it is z) normal operation should not be affected with the appropriate use of a fairness algorithm for bus arbitration. operating constraints with work around none
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 8 operating constraints without work around there is a possibility that the lasar-155 would unfairly request access to the bus.
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 9 2.14. lasar-155 changes stop# during the current data phase description during a target termination (retry and disconnect termination) the assertion of stop# must be asserted at the beginning of the data phase (for a target retry and target disconnect) or at the end of the data phase (target disconnect). the lasar-155 changes stop# after the beginning of the data phase but before the end of the data phase when a parity error on the address phase and 3 wait states on irdy#. work around there is no work around required. according to the pci local bus 2.1 specification, once the master (assertion of irdy#) or target (assertion of trdy# or stop#) has committed to the current data transfer, they cannot stop the data transfer until the data phase is complete. therefore, even if stop# is asserted in the middle of the data phase, the current data transfer is completed before the master or target will end the transaction. operating constraints with work around none operating constraints without work around none
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 10 2.15. transaction without driving the address and command bus description during a multiple transaction when the bus is parked on the lasar-155, the address of the second transfer is not properly synchronized with the frame# assertion during the address phase. work around this error does not occur if the bus is not parked on the lasar-155. an alternative is to program the arbiter to park the bus on itself and not on the lasar-155. operating constraints with work around none operating constraints without work around the pci bus may lock-up if the bus is parked on the lasar-155 2.16. lasar-155 still acts as master after a target abort and soe_e=1 description during a target abort, the lasar-155 continues acting as a pci master and completes transmission of the pdu. this also occurs when soe_e = 1. work around there is no work around. a target abort is generated when the target determines that the master has requested a transaction that the target is incapable of completing or has determined that a fatal error has occurred. this is a serious error where the target indicates that the transaction must be stopped and it does not want the master to repeat the request again. the lasar-155 should stop the transaction after a target abort, however, by completing transmission of the pdu, the lasar-155 does not stop operation gracefully when there is a major system error. a target abort will require that the system be reset regardless of how the lasar-155 completes the transaction. operating constraints with work around none operating constraints without work around none
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 11 2.17. burst read of lasar-155 pci registers causes dma error description a burst read of registers in the range 0x310 - 0x3b4 h during lasar-155 dma access corrupts the state of the internal dma engine. as a result the lasar-155 performs a master abort and generates a serri interrupt. after the failure, the mabt bit is set high and the system may require a hardware reset. work around there is no problem when the above registers are accessed with single data phase transactions. these transactions must be out of sequence or from higher address to lower address to avoid bursts. operating constraints with work around none operating constraints without work around the lasar-155 may cause the system to crash as a result of a serri error. 2.18. thermal considerations description the lasar-155 may require heat sinking in certain applications. please consult pmc's application note: pmc-970394 heat sinking and the lasar-155. 2.19 boundary scan description and work around the bi-directional multi-purpose port of the of the rdat[7:0], rsoc, tdat[15:0] and tsoc signals is non-compliant with the boundary scan standard in the input direction. to make them fully bidirectional, two external inputs, outside the boundary scan cell chain, need to be controlled as indicated in the following table (in addition to the rdatenb and tdatenb cells). consequently, the boundary scan file, to be provided by pmc-sierra will be a subset of the full boundary scan file. input pins value on sysclk value on rxphybp rsoc l h
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 12 rdat l h tsoc l x tdat l x notes
downloaded by vinve fu of olivetti on thursday, 19 september, 2002 10:21:19 pm errata pmc-sierra, inc. PM7375 lasar-155 pmc960529r4 issue 4 saturn user network interface 13 contacting pmc-sierra pmc-sierra, inc. 105-8555 baxter place burnaby, bc canada v5a 4v7 tel: (604) 415-6000 fax: (604) 415-6200 document information: document@pmc-sierra.com corporate information: info@pmc-sierra.com applications information: apps@pmc-sierra.com web site: http://www.pmc-sierra.com ____________________________________________________________________________________________ seller will have no obligation or liability in respect of defects or damage caused by unauthorized use, mis-use, accident, external cause, installation error, or normal wear and tear. there are no warranties, representations or guarantees of any kind, either express or implied by law or custom, regarding the product or its performance, including those regarding quality, merchantability, fitness for purpose, condition, design, title, infringement of third- party rights, or conformance with sample. seller shall not be responsible for any loss or damage of whatever nature resulting from the use of, or reliance upon, the information contained in this document. in no event will seller be liable to buyer or to any other party for loss of profits, loss of savings, or punitive, exemplary, incidental, consequential or special damages, even if seller has knowledge of the possibility of such potential loss or damage and even if caused by sellers negligence. ? 1997 pmc-sierra, inc. pmc-960529 (r4) issue date: december 1997.

▲Up To Search▲

Price & Availability of PM7375

	To Download PM7375 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .