Design Tradeoffs in a Flash Translation Layer(2010,drona.csa.iisc.ernet.in(~gopi)

期刊issn

IEEE TRANSACTIONS ON FUZZY SYSTEMS1063-6706

International Journal of Neural Systems0129-0657

IEEE TRANSACTIONS ON PATTERN ANALYSIS AND MACHINE INTELLIGENCE0162-8828

IEEE TRANSACTIONS ON EVOLUTIONARY COMPUTATION1089-778X

INTEGRATED COMPUTER-AIDED ENGINEERING1069-2509

IEEE Transactions on Cybernetics2168-2267

IEEE Transactions on Neural Networks and Learning Systems2162-237X

MEDICAL IMAGE ANALYSIS1361-8415

Information Fusion1566-2535

INTERNATIONAL JOURNAL OF COMPUTER VISION0920-5691

IEEE TRANSACTIONS ON IMAGE PROCESSING1057-7149

IEEE Computational Intelligence Magazine1556-603X

EVOLUTIONARY COMPUTATION1063-6560

IEEE INTELLIGENT SYSTEMS1541-1672

PATTERN RECOGNITION0031-3203

ARTIFICIAL INTELLIGENCE0004-3702

KNOWLEDGE-BASED SYSTEMS0950-7051

NEURAL NETWORKS0893-6080

EXPERT SYSTEMS WITH APPLICATIONS0957-4174

Swarm and Evolutionary Computation2210-6502

Arria II Device Architecture

■Diagnostic features

■Serial loopback from the transmitter serializer to the receiver CDR for

transceiver physical coding sublayer (PCS) and PMA diagnostics

■Parallel loopback from the transmitter PCS to the receiver PCS with built-in self

test (BIST) pattern generator and verifier

■Reverse serial loopback pre- and post-CDR to transmitter buffer for physical

link diagnostics

■Loopback master and slave capability in PCIe hard IP blocks

■Support for protocol features such as MSB-to-LSB transmission in a

SONET/SDH configuration and spread-spectrum clocking in a PCIe

configuration

Table1–5 lists common protocols and the ArriaII dedicated circuitry and features for

implementing these protocols.

1For other protocols supported by ArriaII devices, such as SONET/SDH, SDI, SATA

and SRIO, refer to the Transceiver Architecture in Arria II Devices chapter.Table1–5.Sample of Supported Protocols and Feature Descriptions for Arria II DevicesSupported ProtocolsFeature Descriptions

MIPI Alliance FAQs

Copyright © 2006 MIPI Alliance, Inc. All rights reserved. MIPI Alliance Member Confidential.

1 1

Frequently Asked Questions: 2 MIPI Alliance Standard for D-PHY v0.65 3

Version 0.65 – 26 July 2006 4 5 Copyright © 2006 MIPI Alliance, Inc. All rights reserved. 6 7 The material contained herein is not a license, either expressly or impliedly, to any IPR owned or controlled 8 by any of the authors or developers of this material or MIPI. The material contained herein is provided on 9 an “AS IS” basis and to the maximum extent permitted by applicable law, this material is provided AS IS 10 AND WITH ALL FAULTS, and the authors and developers of this material and MIPI hereby disclaim all 11 other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if 12 any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of 13 accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of 14 negligence. 15 16 ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET 17 POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD 18 TO THIS MATERIAL. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL 19 OR MIPI BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE 20 GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, 21 CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER 22 CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR 23 ANY OTHER AGREEMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY 24 HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. 25 26 Questions pertaining to this document, or the terms or conditions of its provision, should be addressed to: 27 28 MIPI Alliance, Inc. 29 c/o IEEE-ISTO 30 445 Hoes Lane 31 Piscataway, NJ 08854 32 Attn: Board Secretary 33 MIPI Alliance FAQs

移植SDT工程为ADS工程

Chinakang翻译 2004.4

声明：文档有些地方翻译可能不是很到位，不当之处请批评指正。此外，为了大家

理解的方便，很多地方中文翻译之后用圆括号紧跟原文相应表述。

本文档讲述将已有的SDT(ARM Software Development Toolkit)生成的工程转换

为ADS(the ARM Developer Suite)工程涉及到的方面，同时给出一些转换过程中可

能遇到的诊断信息以及解决方案。

本文当为(ADS Getting Started Guide, section 2, “Differences”(ADS开始指导文档

第二部分“区别”)的互补材料，强烈建议用户首先阅读其整章内容。

工程文件转换(仅对windows)

我们知道ARM Project Manager (APM)管理SDT工程文件，CodeWarrior IDE管理

ADS工程文件，不幸的是现存的APM工程对CodeWarrior来说是不可用的，且没

有转换APM.apj工程文件为CodeWarrior .mcp工程文件的自动方法。

建议的方法如下：

1．配置APM选择“echo all command lines verbosely”(点击Tools菜单的APM子

菜单,在echo all command lines verbosely前打勾)。

2．重新编译工程，在编译日志窗口显示各个工具对每一源文件、目标文件等的处

理情况。

3．拷贝/粘贴汇编、编译、连接命令行到一个零时文本文件，例如：

[armcc -O1 -echo -W -g+ -MD -DMSC_CLOCK -Ic:\ARM250\INCLUDE]

注意：不建议拷贝工具配置窗口之外的内容，因为在选项树的某一级打开窗口看到的内容与在

树的更深一层打开窗口看到的内容可能不一致。

4．去掉方括号[]和任何APM的特定标志如-echo以及-MD。