データシートサーチシステム
  Japanese  ▼
ALLDATASHEET.JP

X  

NHIXP435AD データシート(PDF) 12 Page - Intel Corporation

部品番号 NHIXP435AD
部品情報  Intel IXP43X Product Line of Network Processors
PDF  24 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
メーカー  INTEL [Intel Corporation]
ホームページ  http://www.intel.com
Logo INTEL - Intel Corporation

NHIXP435AD データシート(HTML) 12 Page - Intel Corporation

Back Button NHIXP435AD Datasheet HTML 8Page - Intel Corporation NHIXP435AD Datasheet HTML 9Page - Intel Corporation NHIXP435AD Datasheet HTML 10Page - Intel Corporation NHIXP435AD Datasheet HTML 11Page - Intel Corporation NHIXP435AD Datasheet HTML 12Page - Intel Corporation NHIXP435AD Datasheet HTML 13Page - Intel Corporation NHIXP435AD Datasheet HTML 14Page - Intel Corporation NHIXP435AD Datasheet HTML 15Page - Intel Corporation NHIXP435AD Datasheet HTML 16Page - Intel Corporation Next Button
Zoom Inzoom in Zoom Outzoom out
 12 / 24 page
background image
4.0 Non-Intel XScale® Technology Errata Descriptions
Intel® IXP43X Product Line of Network Processors
Specification Update
December 2008
12
Order Number: 316847; Revision: 005US
5.
Intel XScale® Processor Non-Branch Instruction in Vector Table
Problem:
If an exception occurs in thumb mode and a non-branch instruction is executed at the
corresponding exception vector, that instruction may execute twice. Instructions
located at exception vectors must be branch instructions that go to the appropriate
handler, but the ARM architecture allows the FIQ handler to be placed directly at the
FIQ vector (0x0000001c/0xffff001c) without requiring a branch. Because of this
condition, the first instruction of such an FIQ handler may be executed twice if it is not
a branch instruction.
Implication: Instructions may be executed twice if an exception occurs in thumb mode and if it is a
non-branch instruction.
Workaround: If a no-op is placed at the beginning of the FIQ handler, the no-op will execute twice
and there will not be any incorrect behavior. If a branch instruction is placed at the
beginning of the handler, it will not be executed twice.
Status:
No Fix.
6.
EX_IOWAIT_N Timing
Problem:
There are two problems with the functionality of the expansion bus IOWAIT protocol. If
both T2 and T3 are programmed to be 0 (normal timing), the expansion bus controller
will not extend the T3 data state as described in Section 12.4.1.5 “Using I/O Wait” on
page 572, of the Intel® IXP43X Product Line of Network Processors Developer’s Manual
- Rev. 001 (April 2007). This occurs because there is a synchronizer on the
EX_IOWAIT_N signal that causes the expansion bus controller to transition to the T4
state before the EX_IOWAIT_N is detected.
Additionally, the Intel® IXP43X Product Line of Network Processors Developer’s Manual
states that the expansion bus controller will transition to the T4 state upon the de-
assertion of EX_IOWAIT_N. The expansion bus controller does not do this — instead it
waits for the T3 count to expire before proceeding to T4.
Implication: The expansion bus will not extend the T3 data state as shown in Figure 141 of the
Intel® IXP43X Product Line of Network Processors Developer’s Manual - Rev. 001 (April
2007).
Workaround: To avoid unexpected timing issues, T2 or T3 must be programmed to non-zero values
and assurances made that EX_IOWAIT_N is asserted at least three cycles before the
deasserting edge of EX_RD_N. Additionally, the extended wait states will not be
changed after the deassertion of EX_IOWAIT_N.
Status:
No Fix.
7.
Ethernet Coprocessors — Ethernet Pad Enable Overrides Append FCS
Problem:
The Intel® IXP43X Product Line of Network Processors has an Ethernet coprocessor
that is configured by the Intel® IXP400 Software. The coprocessor can be programmed
via the Ethernet Transmit Control Registers to either append or not append the FCS on
the transmitted Ethernet frames. When the frame payload size is less than 60 bytes,
the Pad Enable control bit has priority over the Append FCS control bit on whether or
not the FCS is appended on a frame.
Implication: When the frame payload size is less than 60 bytes, the FCS will be appended to the
Transmit frames even though the Append FCS control bit is not set because the Pad
Enable control bit overrides the Append FCS control bit.
Workaround: None.
Status:
No Fix.
8.
Ethernet Coprocessors — Length Errors on Received Frames
Workaround: The Intel® IXP43X Product Line of Network Processors has an Ethernet coprocessor
that is configured by the Intel® IXP400 Software. The Ethernet coprocessor can
indicate length error on received frames only when stripping of pad bytes from the
received frame is enabled.
Implication: Length errors on received frames when pad stripping (Receive Control 1 Register,
bit-1) is disabled will not be indicated to the NPE software when it reads the Receive
status. When pad stripping is enabled, length error indicates that the packet length is



Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24


データシート ダウンロード

Go To PDF Page


リンク URL



ALLDATASHEETはお客様のビジネスに役立ちますか?  [ DONATE ] 

Alldatasheetは   |   広告   |   お問い合わせ   |   プライバシーポリシー   |   データシートへのリンク    |   リンク交換   |   メーカーリスト
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com