ICC-Docdex Rules-Pub 811

ICC使用小结（1）ICC的输入文件MilkyWay（physical library），TLUPlus文件（interconnect文件），lib文件（logical library），netlist，constraints（sdc），floorplan文件（.fp或.def）由于ICC会使用MilkyWay数据格式，因此有必要先熟悉MilkyWay格式的产生。

（2）ICC的步骤流程ICC的流程如下：（1）import design(netlist/sdc/database)——（2）create_floorplan 或adjust floorplan——（3）placement ——（4）cts——（5）route——（6）final signoff （3）具体每一步过程及注意点（操作点）（4）Import design具体操作：set_link_library xxxset_target_library xxxcreate_mu_lib design_library –technology xxx.tf –mw_reference_library ref_library open set_tlu_plus_file –max_tluplus max_file –min_tluplus min_file –tech2itf_map map_fileread_verilog xxx.vcurrent_design xxxlinkread_def xxx.defderive_pg_connection –power_net xxx_power_net –power_pin xxx_power_pin –ground_net xxx_ground_net –ground_pin xxx_ground_pinderive_pg_connection –power_net xxx_power_net –power_pin xxx_power_pin –ground_net xxx_ground_net –ground_pin xxx_ground_pin -tieread_floorplan xxx.fp或新创建一个floorplan接下来的任务了。

#interface Ethernet0/0/6#interface Ethernet0/0/7#interface GigabitEthernet0/0/0ip address 192.168.1.1 255.255.255.0#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0 nat outbound 2000#wlan#interface Wlan-Radio0/0/0#interface Cellular0/0/0link-protocol ppp#interface Cellular0/0/1link-protocol ppp#interface NULL0#ip route-static 0.0.0.0 0.0.0.0 218.24.164.1 #user-interface con 0user-interface vty 0 4user-interface vty 16 20#return[Huawei-GigabitEthernet0/0/1]nat ser pro tcp glo 218.24.164.213 www in 192.168.1 .200 8080Error: The address conflicts with interface or ARP IP.[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0nat outbound 2000#return[Huawei-GigabitEthernet0/0/1]undo nat ou 2000[Huawei-GigabitEthernet0/0/1]nat ser pro tcp glo 218.24.164.213 www in 192.168.1 .200 8080Error: The address conflicts with interface or ARP IP.[Huawei-GigabitEthernet0/0/1][Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0#return[Huawei-GigabitEthernet0/0/1]nat ou 2000 ?address-group IP address-group of NATinterface Specify the interface<cr> Please press ENTER to execute command[Huawei-GigabitEthernet0/0/1]nat ou 2000 ad[Huawei-GigabitEthernet0/0/1]nat ou 2000 address-group 1Error: The address conflicts with interface or ARP IP. [Huawei-GigabitEthernet0/0/1]di cu[V200R001C01]#snmp-agent local-engineid 800007DB034C1FCC45D3A6 snmp-agent#voice#http server enable#drop illegal-mac alarm#dhcp enable#set transceiver-monitoring disable#acl number 2000rule 0 permit source 192.168.1.0 0.0.0.255rule 1 deny#aaaauthentication-scheme defaultauthorization-scheme defaultaccounting-scheme defaultdomain default[Huawei-GigabitEthernet0/0/1][Huawei-GigabitEthernet0/0/1][Huawei-GigabitEthernet0/0/1][Huawei-GigabitEthernet0/0/1]qu[Huawei]acl 2000[Huawei-acl-basic-2000]di th[V200R001C01]#acl number 2000rule 0 permit source 192.168.1.0 0.0.0.255rule 1 deny#return[Huawei-acl-basic-2000]undo rule 0[Huawei-acl-basic-2000]undo rule 1[Huawei-acl-basic-2000]rule permi ?fragment Check fragment packetnone-first-fragment Check the subsequence fragment packet source Specify source addresstime-range Specify a special timevpn-instance Specify a VPN-Instance<cr> Please press ENTER to execute command [Huawei-acl-basic-2000]rule permi[Huawei-acl-basic-2000]qu[Huawei]int g0/0/1[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0#return[Huawei-GigabitEthernet0/0/1]nat ou[Huawei-GigabitEthernet0/0/1]nat outbound 2000 add 1Error: The address conflicts with interface or ARP IP.[Huawei-GigabitEthernet0/0/1]qu[Huawei]acl 2000[Huawei-acl-basic-2000]di th[V200R001C01]#acl number 2000rule 5 permit#return[Huawei-acl-basic-2000]undo rule 5[Huawei-acl-basic-2000]rule 0 per so[Huawei-acl-basic-2000]rule 0 per source ?IP_ADDR<X.X.X.X> Address of sourceany Any source[Huawei-acl-basic-2000]rule 0 per source 192.168.1.0 0.0.0.255 [Huawei-acl-basic-2000]rule 1 de^Error:Ambiguous command found at '^' position.[Huawei-acl-basic-2000]di th[V200R001C01]#acl number 2000rule 0 permit source 192.168.1.0 0.0.0.255#return[Huawei-acl-basic-2000]rule 1 deny ?fragment Check fragment packetnone-first-fragment Check the subsequence fragment packetsource Specify source addresstime-range Specify a special timevpn-instance Specify a VPN-Instance<cr> Please press ENTER to execute command [Huawei-acl-basic-2000]rule 1 deny[Huawei-acl-basic-2000]di th[V200R001C01]#acl number 2000rule 0 permit source 192.168.1.0 0.0.0.255rule 1 deny#return[Huawei-acl-basic-2000]qu[Huawei]int g0/0/1[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0#return[Huawei-GigabitEthernet0/0/1]nat ou[Huawei-GigabitEthernet0/0/1]nat outbound 2000 ?address-group IP address-group of NATinterface Specify the interface<cr> Please press ENTER to execute command [Huawei-GigabitEthernet0/0/1]nat outbound 2000 ad 1Error: The address conflicts with interface or ARP IP.[Huawei-GigabitEthernet0/0/1]nat outbound 2000[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0nat outbound 2000#return[Huawei-GigabitEthernet0/0/1]dis nat ad[Huawei-GigabitEthernet0/0/1]qu[Huawei]dis nat ad 1NAT Address-Group Information:--------------------------------------Index Start-address End-address--------------------------------------1 218.24.164.213 218.24.164.213--------------------------------------Total : 1[Huawei]di cu[V200R001C01]#snmp-agent local-engineid 800007DB034C1FCC45D3A6 snmp-agent#voice#http server enable#drop illegal-mac alarm#dhcp enable#set transceiver-monitoring disable#acl number 2000rule 0 permit source 192.168.1.0 0.0.0.255rule 1 deny#aaaauthentication-scheme defaultauthorization-scheme defaultaccounting-scheme defaultdomain defaultdomain default_adminlocal-user admin password simple adminlocal-user admin service-type http#firewall zone trust#nat address-group 1 218.24.164.213 218.24.164.213 #interface Ethernet0/0/0#interface Ethernet0/0/1#interface Ethernet0/0/2#interface Ethernet0/0/3#interface Ethernet0/0/4#interface Ethernet0/0/5#interface Ethernet0/0/6#interface Ethernet0/0/7#interface GigabitEthernet0/0/0ip address 192.168.1.1 255.255.255.0#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0 nat outbound 2000#wlan#interface Wlan-Radio0/0/0#interface Cellular0/0/0link-protocol ppp#interface Cellular0/0/1link-protocol ppp#interface NULL0#ip route-static 0.0.0.0 0.0.0.0 218.24.164.1 #user-interface con 0user-interface vty 0 4user-interface vty 16 20#return[Huawei][Huawei]int g0/0/1[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0nat outbound 2000#return[Huawei-GigabitEthernet0/0/1]nat pro ?^Error: Unrecognized command found at '^' position.[Huawei-GigabitEthernet0/0/1]qu[Huawei]nat ?address-group IP address-group of NATalg Application level gatewaydns-map DNS mappingfilter-mode NAT filter modelink-down Link down reset session functionmapping-mode NAT mapping modeoverlap-address Overlap address pool to temp address pool map static Specify static NAT[Huawei]dis cu[V200R001C01]#snmp-agent local-engineid 800007DB034C1FCC45D3A6snmp-agent#voice#http server enable#drop illegal-mac alarm#dhcp enable#set transceiver-monitoring disable#acl number 2000rule 0 permit source 192.168.1.0 0.0.0.255rule 1 deny#aaaauthentication-scheme defaultauthorization-scheme defaultaccounting-scheme defaultdomain defaultdomain default_adminlocal-user admin password simple adminlocal-user admin service-type http#firewall zone trust#nat address-group 1 218.24.164.213 218.24.164.213 #interface Ethernet0/0/0#interface Ethernet0/0/1#interface Ethernet0/0/2#interface Ethernet0/0/3#interface Ethernet0/0/4#interface Ethernet0/0/5#interface Ethernet0/0/6#interface Ethernet0/0/7#interface GigabitEthernet0/0/0ip address 192.168.1.1 255.255.255.0#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0 nat outbound 2000#wlan#interface Wlan-Radio0/0/0#interface Cellular0/0/0link-protocol ppp#interface Cellular0/0/1link-protocol ppp#interface NULL0#ip route-static 0.0.0.0 0.0.0.0 218.24.164.1#user-interface con 0user-interface vty 0 4user-interface vty 16 20#return[Huawei]dis cu[V200R001C01]#snmp-agent local-engineid 800007DB034C1FCC45D3A6 snmp-agent#voice#http server enable#drop illegal-mac alarm#dhcp enable#set transceiver-monitoring disable#acl number 2000rule 0 permit source 192.168.1.0 0.0.0.255rule 1 denyaaaauthentication-scheme defaultauthorization-scheme defaultaccounting-scheme defaultdomain defaultdomain default_adminlocal-user admin password simple adminlocal-user admin service-type http#firewall zone trust#nat address-group 1 218.24.164.213 218.24.164.213 #interface Ethernet0/0/0#interface Ethernet0/0/1#interface Ethernet0/0/2#interface Ethernet0/0/3#interface Ethernet0/0/4#interface Ethernet0/0/5#interface Ethernet0/0/6#interface Ethernet0/0/7#[Huawei][Huawei]undo nat add 1[Huawei]nat ?address-group IP address-group of NATalg Application level gatewaydns-map DNS mappingfilter-mode NAT filter modelink-down Link down reset session functionmapping-mode NAT mapping modeoverlap-address Overlap address pool to temp address pool mapstatic Specify static NAT[Huawei]int g0/0/1[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0nat outbound 2000#return[Huawei-GigabitEthernet0/0/1]nat ser pro tcp glo 218.24.164.213 7008 ins 192.168 .1.200 7008Error: The address conflicts with interface or ARP IP.[Huawei-GigabitEthernet0/0/1]di veHuawei Versatile Routing Platform SoftwareVRP (R) software, Version 5.90 (AR1200 V200R001C01)Copyright (C) 2011 HUAWEI TECH CO., LTDHuawei AR1220 Router uptime is 0 week, 0 day, 3 hours, 14 minutesBKP 0 version information:1. PCB Version : AR01BAK1A VER.A2. If Supporting PoE : Yes3. Board Type : AR12204. MPU Slot Quantity : 15. LPU Slot Quantity : 2MPU 0(Master) : uptime is 0 week, 0 day, 3 hours, 14 minutes SDRAM Memory Size : 512 M bytesFlash Memory Size : 256 M bytesNVRAM Memory Size : 512 K bytesMPU version information :1. PCB Version : AR01SRU1A VER.C2. MAB Version : 03. Board Type : AR1220W-S4. CPLD1 Version : 1045. BootROM Version : 225[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1ip address 218.24.164.213 255.255.255.0nat outbound 2000#return[Huawei-GigabitEthernet0/0/1]undo ip add ?IP_ADDR<X.X.X.X> IP addressbootp Bootp clientbootp-alloc Bootp client allocdhcp Dynamic host configure protocoldhcp-alloc IP address allocunnumbered Share an address with another interface<cr> Please press ENTER to execute command[Huawei-GigabitEthernet0/0/1]undo ip add[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1nat outbound 2000#return[Huawei-GigabitEthernet0/0/1]nat ser pro tcp glo ?X.X.X.X Global IP address of NATcurrent-interface Address of current interfaceinterface Specify the interface[Huawei-GigabitEthernet0/0/1]nat ser pro tcp glo 218.24.164.213 7008 ?inside Specify inside information of NAT[Huawei-GigabitEthernet0/0/1]nat ser pro tcp glo 218.24.164.213 7008 inside 192. 168.1.200 7008[Huawei-GigabitEthernet0/0/1]di th[V200R001C01]#interface GigabitEthernet0/0/1nat server protocol tcp global 218.24.164.213 7008 inside 192.168.1.200 7008nat outbound 2000#return[Huawei-GigabitEthernet0/0/1]Please check whether system data has been changed, and save data in timeConfiguration console time out, please press any key to log on<Huawei><Huawei><Huawei><Huawei>saThe current configuration will be written to the device.Are you sure to continue? (y/n)[n]:yIt will take several minutes to save configuration file, please wait.......... ...Configuration file had been saved successfullyNote: The configuration file will take effect after being activated<Huawei>。

icc2 upf编写方法ICC2 UPF编写方法ICC2（Integrated Circuit Compiler 2）是一种常用的集成电路设计工具，用于优化和布局设计。

UPF（Unified Power Format）是一种用于电源管理的统一标准。

在使用ICC2进行电路设计时，编写正确的UPF文件非常重要，以确保设计的功耗和电源管理符合要求。

编写UPF文件的方法有很多，下面将介绍一种常用的方法。

1. 确定设计需求：在开始编写UPF文件之前，首先要明确设计的功耗和电源管理需求。

例如，确定芯片的工作模式，电源供应方式，以及各个模块的功耗要求等。

2. 创建UPF文件：使用任何文本编辑器创建一个新的UPF文件。

UPF文件通常以.upf为后缀名。

3. 定义供电域（power domain）：根据设计需求，使用UPF语法定义供电域。

供电域是电源管理的基本单元，用于划分芯片中的不同部分。

可以使用关键字create_power_domain来创建供电域，并使用关键字add_power_domain_port定义供电域的输入输出端口。

4. 定义电源网络（power net）：使用关键字create_power_net定义电源网络。

电源网络是供电域之间的连接，用于传递电源信号和电流。

可以使用关键字connect_power_net连接不同的供电域。

5. 定义电源规则（power domain rule）：使用关键字create_power_domain_rule定义电源规则。

电源规则用于指定不同供电域的电源行为，例如供电时序、电源模式以及电源切换等。

可以使用关键字set_power_domain_rule设置电源规则的各种属性。

6. 定义功耗约束（power constraint）：使用关键字create_power_constraint定义功耗约束。

功耗约束用于指定每个供电域的功耗限制。

可以使用关键字set_power_constraint设置功耗约束的值。

Micro Focus Security ArcSight ConnectorsSmartConnector for Microsoft DNS Trace Log Multiple Server FileConfiguration GuideSeptember 17, 2020Configuration GuideSmartConnector for Microsoft DNS Trace Log Multiple Server FileSeptember 17, 2020Copyright © 2014 – 2020 Micro Focus or one of its affiliates.Legal NoticesMicro FocusThe Lawn22-30 Old Bath RoadNewbury, Berkshire RG14 1QNUKhttps://.Confidential computer software. Valid license from Micro Focus required for possession, use or copying. The information contained herein is subject to change without notice.The only warranties for Micro Focus products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein.No portion of this product's documentation may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser's internal use, without the express written permission of Micro Focus.Notwithstanding anything to the contrary in your license agreement for Micro Focus ArcSight software, you may reverse engineer and modify certain open source components of the software in accordance with the license terms for those particular components. See below for the applicable terms.U.S. Governmental Rights. For purposes of your license to Micro Focus ArcSight software, “commercial computer software” is defined at FAR 2.101. If acquired by or on behalf of a civilian agency, the U.S. Government acquires this commercial computer software and/or commercial computer software documentation and other technical data subject to the terms of the Agreement as specified in 48 C.F.R. 12.212 (Computer Software) and 12.211 (Technical Data) of the Federal Acquisition Regulation (“FAR”) and its successors. If acquired by or on behalf of any agency within the Department of Defense (“DOD”), the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of the Agreement as specified in 48 C.F.R. 227.7202- 3 of the DOD FAR Supplement (“DFARS”) and its successors. This U.S. Government Rights Section 18.11 is in lieu of, and supersedes, any other FAR, DFARS, or other clause or provision that addresses government rights in computer software or technical data.Trademark NoticesAdobe™ is a trademark of Adobe Systems Incorporated.Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.UNIX® is a registered trademark of The Open Group.Documentation UpdatesThe title page of this document contains the following identifying information:* Software Version number* Document Release Date, which changes each time the document is updated* Software Release Date, which indicates the release date of this version of the softwareTo check for recent updates or to verify that you are using the most recent edition of a document, go to: https:///t5/ArcSight-Product-Documentation/ct-p/productdocsRevision HistoryDate Description09/17/2020 The Rcode value is appended to DECID, for events which have Device Event Category as "PACKET".08/21/2019 Updated Microsoft DNS Trace Log Multiple Server File mappings06/19/2019 Added support for Microsoft Windows Server 2019 for Microsoft DNS Trace Log Multiple Server File.04/16/2018 Added support Microsoft Windows 2016 for Microsoft DNS Trace Log Multiple Server File.10/17/2017 Added encryption parameters to Global Parameters.07/15/2017 Removed platform support for Windows 2003.11/30/2016 Updated installation procedure for setting preferred IP address mode.09/30/2014 First edition of this Configuration Guide.SmartConnector for Microsoft DNS Trace Log Multiple Server FileSmartConnector for Microsoft DNS Trace Log Multiple Server File This guide provides information for installing the SmartConnector for Microsoft DNS Trace Log Multiple Server File and configuring the device for event collection. Microsoft's Domain Name Service (DNS) included with Microsoft Windows 2008, Microsoft Windows 2012, MicrosoftWindows 2012 R2, Microsoft Windows 2016, and Microsoft Windows 2019 are supported. Product OverviewThe Domain Name System (DNS) is a hierarchical distributed database and an associated set of protocols that define a:⏹Mechanism for querying and updating the database⏹Mechanism for replicating the information in the database among servers⏹Schema of the databaseWith DNS, the host names reside in a database that can be distributed among multiple servers, decreasing the load on any one server and providing the ability to administer this naming system on a per-partition basis. DNS supports hierarchical names and allows registration of various data types in addition to host name to IP address mapping used in HOSTS files.This ArcSight SmartConnector lets you import events generated by the Microsoft DNS Trace Log Multiple Server File device into the ArcSight System. See the section "Device Event Mapping to ArcSight Data Fields" later in this document for the specific events mapped to fields in theArcSight database.ConfigurationDetailed information regarding DNS Monitoring can be found at: /en-us/library/cc783975(WS.10).aspx.The primary tool used to manage DNS servers is the DNS console, which can be found in the Administrative Tools folder in the Start menu's Programs folder.DNS server event messages are separated and kept in their own system event log, the DNS server log. The DNS server log contains events logged by the DNS server service. Most critical DNS server service events are logged here, such as when the server starts but cannot locate initializing data.You can change the event types logged by DNS servers using the DNS console. You also can use the DNS console to selectively enable additional debug logging options for temporary tracelogging to a text-based file of DNS server activity.Configuration Guide Using Server Debug Logging OptionsBy default, all debug logging options are disabled. When selectively enabled, the DNS Serverservice can perform additional trace-level logging of selected types of events or messages for general troubleshooting and debugging of the server. Dns.log contains debug logging activity.By default, it is located in the windir\System32\Dns folder.The following DNS debug logging options are available:Packet DirectionOutgoingPackets sent by the DNS server are logged in the DNS server log file.IncomingPackets received by the DNS server are logged in the log file.Packet ContentQueries/TransfersSpecifies that packets containing standard queries (per RFC 1034) are logged in the DNSserver log file.UpdatesSpecifies that packets containing dynamic updates (per RFC 2136) are logged in the DNSserver log file.NotificationsSpecifies that packets containing notifications (per RFC 1996) are logged in the DNSserver log file.Transport ProtocolUDPSpecifies that packets sent and received over UDP are logged in the DNS server log file.TCPSpecifies that packets sent and received over TCP are logged in the DNS server log file.Packet TypeRequestSpecifies that request packets are logged in the DNS server log file (a request packet ischaracterized by a QR bit set to 0 in the DNS message header).ResponseSpecifies that response packets are logged in the DNS server log file (a response packetis characterized by a QR bit set to 1 in the DNS message header).Other OptionsSmartConnector for Microsoft DNS Trace Log Multiple Server FileFilter packets by IP addressProvides additional filtering of packets logged in the DNS server log file.DetailsSpecifies that all event details be logged in the DNS server log file.Log FileFile path and name lets you specify the name and location of the DNS server log file. Log file maximum size limit lets you set the maximum file size for the DNS server log file.To select and enable debug logging options on the DNS server:1Open DNS. (Click Start -> Control Panel -> Administrative Tools. Double-click DNS.)2In the console tree, right-click the applicable DNS server, then click Properties.3Click the Debug Logging tab.4To set the debug logging options, first select Log packets for debugging. To ensure collecting the appropriate information for processing by ArcSight, select the options shown in the following figure.In addition to selecting events for the DNS debug log file, select the default values or specify the file name, location, and maximum file size for the file.Configuration Guide Install the SmartConnectorThe following sections provide instructions for installing and configuring your selectedSmartConnector.Connector Appliance/ArcSight Management Center supports mounting forNetwork File System (NFS) and CIFS (Windows) shares. When you installthis connector on one of these devices, establish a CIFS mount on thedevice before adding the connector. Provide this share name duringconnector configuration. For more information, see Remote File Systemsin the Connector Appliance or ArcSight Management CenterAdministrator's Guide.Prepare to Install ConnectorBefore you install any SmartConnectors, make sure that the ArcSight products with which the connectors will communicate have already been installed correctly (such as ArcSight ESM orArcSight Logger).For complete product information, read the Administrator's Guide as well as the Installation and Configuration guide for your ArcSight product before installing a new SmartConnector. If you are adding a connector to the ArcSight Management Center, see the ArcSight Management Center Administrator's Guide for instructions, and start the installation procedure at "Set GlobalParameters (optional)" or "Select Connector and Add Parameter Information."Before installing the SmartConnector, be sure the following are available:⏹Local access to the machine where the SmartConnector is to be installed⏹Administrator passwordsInstall Core SoftwareUnless specified otherwise at the beginning of this guide, this SmartConnector can be installed on all ArcSight supported platforms; for the complete list, see the SmartConnector Product andPlatform Support document, available from the Micro Focus SSO and Protect 724 sites.1Download the SmartConnector executable for your operating system from the Micro Focus SSO site.2Start the SmartConnector installation and configuration wizard by running the executable.Follow the wizard through the following folder selection tasks and installation of the coreconnector software:IntroductionChoose Install FolderSmartConnector for Microsoft DNS Trace Log Multiple Server FileChoose Shortcut FolderPre-Installation SummaryInstalling...3When the installation of SmartConnector core component software is finished, the following window is displayed:Set Global Parameters (optional)If you choose to perform any of the operations shown in the following table, do so before adding your connector. You can set the following parameters:Parameter SettingFIPS mode Select 'Enabled' to enable FIPS compliant mode. To enable FIPS Suite B Mode, see theSmartConnector User Guide under "Modifying Connector Parameters" for instructions. Initially, thisvalue is set to 'Disabled'.Remote Management Select 'Enabled' to enable remote management from ArcSight Management Center. When queriedby the remote management device, the values you specify here for enabling remote managementand the port number will be used. Initially, this value is set to 'Disabled'.Remote Management Listener Port The remote management device will listen to the port specified in this field. The default port number is 9001.Preferred IP Version When both IPv4 and IPv6 IP addresses are available for the local host (the machine on which theconnector is installed), you can choose which version is preferred. Otherwise, you will see only oneselection. The initial setting is IPv4.The following parameters should be configured only if you are using Micro Focus SecureData solutions to provide encryption. See the Micro Focus SecureData Architecture Guide for more information.Configuration Guide Parameter SettingFormat Preserving Encryption Data leaving the connector machine to a specified destination can be encrypted by selecting ‘Enabled’ to encrypt the fields identified in ‘Event Fields to Encrypt' before forwarding events. If encryption is enabled, it cannot be disabled. Changing any of the encryption parameters again will require a fresh installation of the connector.Format PreservingPolicy URLEnter the URL where the Micro Focus SecureData Server is installed.Proxy Server (https) Enter the proxy host for https connection if any proxy is enabled for this machine. Proxy Port Enter the proxy port for https connection if any proxy is enabled for this machine.Format Preserving Identity The Micro Focus SecureData client software allows client applications to protect and access data based on key names. This key name is referred to as the identity. Enter the user identity configured for Micro Focus SecureData.Format PreservingSecretEnter the secret configured for Micro Focus SecureData to use for encryption.Event Fields to Encrypt Recommended fields for encryption are listed; delete any fields you do not want encrypted and add anystring or numeric fields you want encrypted. Encrypting more fields can affect performance, with 20 fieldsbeing the maximum recommended. Also, because encryption changes the value, rules or categorizationcould also be affected. Once encryption is enabled, the list of event fields cannot be edited.After making your selections, click Next. A summary screen is displayed. Review the summary of your selections and click Next. Click Continue to return to proceed with "Add a Connector"window. Continue the installation procedure with "Select Connector and Add ParameterInformation."Select Connector and Add Parameter Information1Select Add a Connector and click Next. If applicable, you can enable FIPS mode and enable remote management later in the wizard after SmartConnector configuration.2Select Microsoft DNS Trace Log Multiple Server File and click Next.3Enter the required SmartConnector parameters to configure the SmartConnector, then click Next.SmartConnector for Microsoft DNS Trace Log Multiple Server FileParameter DescriptionFolder The absolute path to the location of the log files.- For Windows platform, use: 'c:\Program Files\DNS_Multi_File\logs\'- For Linux platform, use: '/var/log/dnsmultifile/'For multiple servers, click Add and enter information about the additionalserver.- For Windows platform, use: \\<servername>\folder\folder.Wildcard The log file name ('*.log') has two parts:- Part 1: ('*') is the file name- Part 2: ('.log') is the file type- For example: 'dnsmulti.log'Log File Type Accept the default "tracelog".Select a Destination1The next window asks for the destination type; select a destination and click Next. For information about the destinations listed, see the ArcSight SmartConnector User Guide.2Enter values for the destination. For the ArcSight Manager destination, the values you enter for User and Password should be the same ArcSight user name and password you createdduring the ArcSight Manager installation. Click Next.Configuration Guide 3Enter a name for the SmartConnector and provide other information identifying the connector's use in your environment. Click Next. The connector starts the registrationprocess.4If you have selected ArcSight Manager as the destination, the certificate import window for the ArcSight Manager is displayed. Select Import the certificate to the connector fromdestination and click Next. (If you select Do not import the certificate to connector fromdestination, the connector installation will end.) The certificate is imported and the Addconnector Summary window is displayed.Complete Installation and Configuration1Review the Add Connector Summary and click Next. If the summary is incorrect, click Previous to make changes.2The wizard now prompts you to choose whether you want to run the SmartConnector as a stand-alone process or as a service. If you choose to run the connector as a stand-aloneprocess, select Leave as a standalone application, click Next, and continue with step 5.3If you chose to run the connector as a service, with Install as a service selected, click Next.The wizard prompts you to define service parameters. Enter values for Service InternalName and Service Display Name and select Yes or No for Start the service automatically.The Install Service Summary window is displayed when you click Next.4Click Next on the summary window.5To complete the installation, choose Exit and Click Next.For instructions about upgrading the connector or modifying parameters, see the SmartConnector User Guide.Run the SmartConnectorSmartConnectors can be installed and run in stand-alone mode, on Windows platforms as aWindows service, or on UNIX platforms as a UNIX daemon, depending upon the platformsupported. On Windows platforms, SmartConnectors also can be run using shortcuts and optional Start menu entries.If the connector is installed in stand-alone mode, it must be started manually and is notautomatically active when a host is restarted. If installed as a service or daemon, the connector runs automatically when the host is restarted. For information about connectors running asservices or daemons, see the ArcSight SmartConnector User Guide.To run all SmartConnectors installed in stand-alone mode on a particular host, open a command window, go to $ARCSIGHT_HOME\current\bin and run: arcsight connectorsSmartConnector for Microsoft DNS Trace Log Multiple Server FileTo view the SmartConnector log, read the file$ARCSIGHT_HOME\current\logs\agent.log; to stop all SmartConnectors, enter Ctrl+C in the command window.Device Event Mapping to ArcSight FieldsThe following section lists the mappings of ArcSight data fields to the device's specific event definitions. See the ArcSight Console User's Guide for more information about the ArcSight data fields.Microsoft DNS Trace Log Multiple Server File Mappings to ArcSight ESM Fields ArcSight ESM Field Device-Specific FieldAgent (Connector) Severity High = 2, 3, 5, 16, SERVFAIL, NXDOMAIN, REFUSED, BADVERS, BADSIG; Medium = 1, 4, 6-10, 17-22, Error, Warning, FORMERR, NOTIMP, YXDOMAIN, YXRRSET, NXRRSET, NOTAUTH, NOTZONE,BADKEY, BADTIME, BADMODE, BADNAME, BADALG, BADTRUNC; Low = 0, 11-15, 23-65535,Information, Success, NOERROR (based on Rcode values at:/enp/protocol/dns.htm#Rcode, Return code) Application Protocol application protocolBytes In Size, incoming bytesDestination Address destination addressDestination DNS Domain destination DNS domainDestination Host Name destination host nameDestination NT Domain destination NT domainDevice Action Action taken by the deviceDevice Custom IPv6 Address 2 Source IPv6 addressDevice Custom Number 2 TTLDevice Custom String 1 Thread IdDevice Custom String 2 OpCodeDevice Custom String 3 Flags (character codes)Device Custom String 4 Reason or error codeDevice Direction Snd=Outbound, Rcv=InboundDevice Event Category ContextDevice Event Class ID Event Name (For events which have Device Event Category as "PACKET" the DECID has beenappended OPCODE with Rcode value.)Device Product 'DNS Trace Log'Device Receipt Time DateTimeDevice Severity One of (Information, Warning, Error, Success, NOERROR)Device Vendor 'Microsoft'File Name file nameFile Path file pathMessage Rcode description (based on Rcode descriptions at:/enp/protocol/dns.htm#Rcode, Return code Name Rcode name (based on Rcode name at:/enp/protocol/dns.htm#Rcode, Return code Request URL Question NameSource Address Source network addressConfiguration GuideArcSight ESM Field Device-Specific FieldSource DNS Domain sourceDNSDomainSource Host Name Source host nameSource Port Source portSource Service Name sourceServiceNameStart Time startTimeTransport Protocol transport protocol (UDP)。

Type 289RC Exhaust BoosterIntroductionScope of the ManualThis manual describes the principles of operation and provides installation instructions and a parts list for the Type 289RC exhaust booster.Product DescriptionThe Type 289RC high-capacity exhaust booster provides “release control (RC)” control pressure to actuators, other pneumatic devices, and related systems that require rapid response, such as surgevalves or recycle valves on compressors. This exhaust booster is normally used on control valve actuators to speed up the proportional operation of a control valve in response to sudden pressure changes from pneumatic output devices, such as solenoid valves or pneumatic instruments. By carefully matching the instrument and actuator performance with the bypass valve adjustment, the Type 289RC reduces overshoot and related problems while allowing very fast positioning response to system requirements (i.e., compressor surge control). The one-way throttling action offers superior control with exceptional stability and the specially designed boosting system provides high flow rates with minimum buildup.Figure 1.Type 289RC Exhaust BoosterInstruction Manual D102588X012January 2018Type 289RCSpecificationsSpecifications for the Type 289RC exhaust booster are listed on page 2. Specifications for a given exhaust booster as it originally comes from the factory are stamped on the nameplate.Body Size(1)1 NPTInlet and Outlet ConnectionsInlet: Connect to the outlet via a bypass valve, adjustable from 0 to 0.3 C v. (Piping is normally configured by the customer.) See Figure 3.Signal: 1/8 NPT (standard)Outlet: 1 NPTMaximum Pressure(1)100 psig / 6.9 barInput to Output Pressure RatioFixed at 1 to 1Dead Band0.5 psid / 0.034 bar d pressure across thebypass valveMaximum Exhaust Flow CapacityC v = 22. System capacity limited by thesmallest restriction between the exhaust valve and pressure source (actuator). Temperature Capabilities(1)-20 to 180°F / -29 to 82°CApproximate Weight4 lbs / 2 kg1. The pressure/temperature limits in this Instruction Manual and any applicable standard or code limitation should not be exceeded.Principle of OperationThe Type 289RC 1 NPT outlet port is connected directly to a spring return actuator and the 1/8 NPT inlet connection on the spring case is connected tothe controlling instrument (I/P transducer, controller, positioner, etc.). The assembly of the Type 289RC to a control valve requires the inlet and outlet chambers be connected via a bypass valve. The bypass valve should be installed between the two 1/8 NPT connections on the Type 289RC or any other convenient location per the customer’s preference. The Type 289RC exhaust booster has a factory set opening threshold of 0.5 psid / 0.03 bar d. The adjustment screw in the booster body is not field adjustable. The bypass valve is adjustedon the control valve system to account for differences in various instrument and actuator performance characteristics. Once adjusted, the control valve action is as described in the following paragraph.As the output pressure of the instrument increases the actuator moves the valve normally since the exhaust booster cannot be actuated with an increasing signal. When the output pressure of the instrument decreases the actuator will move the valve until the rate of change of the output pressure develops 0.5 psid /0.034 bar d across the bypass valve. When this occurs, the pressure differential in the Type 289RC causes the exhaust booster valve to begin opening and begin reducing the pressure in the actuator. The greater the differential pressure develops across the bypass valve, the further the exhaust booster will open. The booster exhaust valve closes as the pressure difference between the instrument and actuator decreases.InstallationThe schematic on page 3 (Figure 2) shows the typical Type 289RC installation. Connect the instrument supply to the 1/8 NPT spring case inlet and the actuator to the 1 NPT side port outlet. The inlet and outlet must be connected via an adjustable bypass valve. Flow through the exhaust valve must be in the same direction as the flow arrow on the body.NoteMounting is recommended with theoutlet exhaust connection pointingdown. If it is necessary to pipe thisoutlet away from the area, remove theoutlet screen.Protect the outlet exhaust connectionagainst the entrance of rain, snow,insects or any other foreign materialthat may block the outlet or affect theopening and closing of the valve.2Type 289RCFigure 2. Typical Type 289RC Exhaust Booster and Control Valve InstallationA720845 TO 125 psig /3.1 TO 8.6 bar3Type 289RCOperating InformationNever operate this system with thebypass valve closed.NoteThe Type 289RC requires no adjustment.The adjusting screw (key 6) is factory setand must not be changed.In the operating configuration (Figure 2) the bypass valve may require adjustment for optimum actuator response. Always begin with the bypass valve open. If opened enough, the instrument signal will drive the actuator and the system will respond as if the exhaust booster was not installed. As the bypass valve is closed the actuator response will be faster only inthe exhaust mode. Response in the filling direction will remain unchanged. If the control valve tends to overshoot the desired position, the bypass valve has been closed too far.CalibrationThe exhaust booster’s calibration is factory set. This unit should not require calibration unless the adjusting screw has been loosened or the spring has been changed. Use the following procedure to calibrate a Type 289RC exhaust booster:1. C onnect the assembled Type 289RC to twoindependent pressure sources (P1 and P L) withpressure gauges as shown in Figure 3.2. Place a plug in the 1/8 NPT body connection.3. Set P1 and P L at 6 psig / 0.41 bar.4. Screw the adjusting screw in all the way.5. Adjust P L to 5.3 psig / 0.37 bar.6. Turn the unit upside down and put just enoughwater into the exhaust port to cover the sealingsurface. Turn the adjusting screw out until the first bubble appears at the exhaust port.7. Lock adjusting screw in place.MaintenanceType 289RC exhaust boosters are subject to normal wear and should be inspected periodically. The inspection frequency and replacement of partsdepends on the severity of the service conditions.Maintenance requires taking theexhaust booster out of service. To avoidpersonal injury or equipment damage,release or bypass any pressure inthe exhaust booster before beginningrequired maintenance.Elastomer ReplacementKey numbers refer to Figure 5.1. Loosen the adjusting screw (key 6) and removethe eight machine screws (key 8) from the spring case (key 2).2. Remove the spring case (key 2).3. Remove the spring (key 7) and upper springseat (key 4).4. Remove the spacer ring (key 42). The diaphragmsmay stick to the spacer.5. Remove the two machine screws (key 29) andlift out the diaphragm/valve assembly. Lift up thevalve assembly for more screwdriver clearance. 6. Use a 7/16 in. / 11 mm wrench to remove the hexnut (key 24). Then remove the parts in order: spring guide (key 17), first diaphragm head (key 43) withcurved side facing the diaphragm, diaphragm(key 5), second diaphragm head (key 43) withcurved side facing the diaphragm, spacer (key 41), third diaphragm head (key 43) with curved sidefacing the diaphragm, second diaphragm (key 5),stem guide (key 31), spacer (key 23), O-ring(key 30), O-ring holder (key 21), O-ring (key 20),O-ring holder (key 22) and O-ring (key 30).7. Remove and discard all non-metallic parts.8. Position the stem (key 18) to accept all parts.Replace all non-metallic parts with new parts.Then place parts on the stem (key 18) in reverseorder of step 6. Make sure to:a. L ubricate all O-rings with a light coating ofsilicone grease.4Type 289RCFigure 3. Type 289RC Exhaust Booster Calibration ConnectionPRESSuRE SOuRCE WITh GAuGEPRESSuRE SOuRCE WITh GAuGEPLuG FOR TESTMEASuREMENTA7219b. A ssemble both diaphragms so the springsides (marked on diaphragm) face toward the spring. c. A ssemble the valve seat holder and O-ring assembly (keys 20, 21 and 22) by hand prior to placing it on the stem. d. Do not tighten the hex nut (24) until step 11.9. Place the machine screws (key 29) in the stem guide assembly (key 31), position the diaphragm/valve assembly in the valve body (key 1), and tighten screws (key 29) to 15 to 20 in-lbs / 1.7 to 2.3 N•m.10. P osition the spacer ring (key 42) between thediaphragms and align all holes with at least three machine screws (key 8) turned partially into the body.11. W hile holding the stem (key 18) through theexhaust port in the bottom of the body, tighten the hex nut (key 24) to 30 to 35 in-lbs / 3.4 to 3.9 N •m. Hold the diaphragm head (key 43) while tightening the hex nut to be sure it does not turn or move.12. Remove the aligning machine screws (key 8).13. P lace the spring (key 7) firmly around the lowerspring guide (key 17) and install the upper spring seat (key 4).14. Orient the spring case (key 2) as required whilecarefully positioning over the spring and seat.15. Insert and tighten the machine screws (key 8)to 40 to 45 in-lbs / 4.5 to 5.1 N•m using a cross tightening process.16. Recalibrate unit using Calibration procedure onpage 4.5Type 289RCParts OrderingWhen corresponding with your local Sales Office about this equipment, always reference the equipment serial number stamped on the spring case (key 2). When ordering replacement parts, specify the complete11-character part number of each required part as found in the following parts list.Key Description Part Number 17 Lower Spring Guide, Zinc-plated carbon steel 1D666625072 18 Pitot Tube or Stem, Aluminum 17B3186X012 20* O-ring, Nitrile (NBR)1F269206992 21 O-ring Holder, Aluminum 1F826409012 22 O-ring Washer, Aluminum 1F826509012 23 Spacer17B7490X012 24 Hex Nut 1A499724122 28 Pipe PlugT13718T0012 29Machine Screw (2 required) 1H526928982 30 O-ring, Nitrile (NBR) (2 required) 1D687506992 31 Stem Guide Assembly, Zinc/Brass 18B0253X012 41 Spacer, Aluminum 17B3185X012 42 Spacer Ring, Aluminum 27B3187X012 43 Diaphragm Head, Zinc-plated Carbon steel (2 required) 1P901425062 44* Screw Seal 1V205699012 45Washer1F826709012 46* Gasket1F826804022Parts ListKey Description Part Number 1 Valve Body, Aluminum 14B9956X012 2 Spring Case, Aluminum2P901508012 3 Diaphragm Head, Zinc-plated carbon steel 1D666428982 4 Spring Seat, Zinc-plated carbon steel1D667125072 5* Diaphragm, Nitrile (NBR) on nylon (2 required) 24B5622X012 6 Adjusting Screw1D995448702 7 Spring, 302 Stainless steel 17B9737X012 8 Machine Screw (8 required) 1C856228992 9 Screen 1E564843122 11 Hex Nut 1D667728982 13 Snap Ring 13A9938X012 15* Gasket, Nitrile (NBR)13A9929X012 16Nameplate- - - - - - - - - - -*Recommended spare part.Figure 4. Typical Response Curve for Type 657 Size 45 Actuator with Type 289RC Exhaust Booster(Using a Type 546 I/P Transducer with 4 to 20 mA input signal, 6 to 30 psig / 0.41 to 2.1 bar output and 35 psig /2.4 bar supply pressure; a Type 657 or 645 Valve Actuator with 10 to 26 psig / 0.69 to 1.8 bar setting and 0 to 1.5 in. / 0 to 38 mm of travel; and a Type 289RC Exhaust Booster with a bypass valve.)A7218P E R C E N T O F C u R R E N T (4 T O 20 m A = 100)P E R C E N T O F A C T u A T O R T R A v E L (1.5 I N . / 38 m m = 100)TIME IN SECONDS-0.1-100.10.20.30.40.51020304050607080901001100.080 SECONDS OF DEAD TIME0.320 SECONDS, 85% FuLL STROKEINPuT SIGNALACTuATOR TRAvEL6Type 289RCType 289RCPART NOT ShOWNMAChINE SCREW (KEy 29)ByPASS vALvE, TuBING, AND FITTINGSNOT SuPPLIED WITh ThE TyPE 289RC ExhAuST BOOSTERFigure 5. Type 289RC Exhaust Booster7Type 289RC/EmersonAutomationSolutions/company/emerson-automation-solutions /emr_automation*******************************D102588X012 © 1998, 2018 Emerson Process Management Regulator Technologies, Inc. All rights reserved. 01/18.The Emerson logo is a trademark and service mark of EmersonElectric Co. All other marks are the property of their prospective owners. Fisher™ is a mark owned by Fisher Controls International LLC, a business of Emerson Automation Solutions.The contents of this publication are presented for information purposes only, and while effort has been made to ensure their accuracy, they are not to be construed as warranties or guarantees, express or implied, regarding the products or services described herein or their use or applicability. All sales are governed by our terms and conditions, which are available on request. We reserve the right to modify or improve the designs or specifications of our products at any time without notice.Emerson Process Management Regulator Technologies, Inc. does not assume responsibility for the selection, use or maintenance of anyproduct. Responsibility for proper selection, use and maintenance of any Emerson Process Management Regulator Technologies, Inc. product remains solely with the purchaser.Emerson Automation Solutions AmericasMcKinney, Texas 75070 USA T +180****5853+1 972 548 3574EuropeBologna 40013, Italy T +39 051 419 0611Asia PacificSingapore 128461, Singapore T +65 6770 8337Middle East and Africa Dubai, United Arab Emirates T +971 4 811 8100。

ICC编译软件使用入门AVR单片机的开发环境主要指程序的编译、调试和下载，这都需要运用软件的支持。

AVR的开发软件众多，常用的主要有以下几个：A VR Studio：ATMEL的专业AVR单片机集成开发环境,完全免费。

ATMEL AVR Studio集成开发环境(IDE),包括了AVR Assembler编译器、AVR Studio调试器、支持芯片下载编程功能。

AVR Studio支持以下开发工具：AVRISP mkII，JTAGICE mkII，A VR Dragon，JTAGICE，A VRISP，STK500/501/502/503/504/505/520等。

IAR A VR：在所有第三方提供的C编译器中 IAR AVR的功能、代码效率、稳定性都是最好的，但使用该软件需要支付较高的费用。

ICC A VR：ICC AVR C编译器是AVR初学者的首选 C编译器，不仅操作简单，界面友好，而且ICC AVR的自助生成代码向导功能非常好用，对初学者来说降低了门槛。

ICC AVR Demo版本为45天完全版，45天后转为2K限制版。

GCC A VR：GCC AVR 的编译器是完全免费的开源ATMEL AVR开发工具，对初学者来说，入门较难。

GCC AVR包含以下组件：C/C++ 编译器，汇编编译器，模拟仿真，编程器，硬件调试器。

本文将以ICC编译器作为开发平台，以下以一个实例的方式简单介绍它的基本使用方法，更详细详细的介绍请参考ICC用户手册。

1、启动ICC编译软件，如下图所示。

2、选择菜单Project--->New，打开Save New Project as 对话框，在对话框中选择保存路径和项目名称，单击保存确定。

3、选择菜单File--->New，新建一个源程序文件，如下图所示。

4、在新建的文件上输入源程序，如下图为简单示例，用于点亮端口A的LED灯。

5、单片机内部器件的初始化代码可用代码生成器获得。

ICC Useful CommandsSelect routing between two pins:change_selection [gui_get_routes_between_objects {phy/u_SE2DIFF/CKI phy/u_XE36MSC3/XC10}] Write flat verilog netlist:change_names -hierarchy -rules verilogungroup -all -flattenwrite_verilog -no_core_filler_cells OUT/${mw_topLevel}_flat.vConnect signal through hierarchies:connect_pin -from fromPin -to listOfDestinationPinsICC bug: Vias not visible in lower level:Workaround:Use the following cmd to change the view of a module to CEL view:change_macro_view -reference phy_core -view CELKeep value "Default" in Settings -> View -> Child View NameSet port properties:set_attribute [get_port -all VDD] port_type Powerset_attribute [get_port -all VDD] direction InoutPurge cells:redirect /dev/null "remove_mw_cell -version_kept 0 place_opt_icc" --> SolvNet Article Keeps last version of cell "place_opt_icc".Get placement utilization of a certain area:report_placement_utilization -coordinates {X1 Y1 X2 Y2}Cell sizing:Via menue: ECO -> size cellor on the cmd line:get_alternate_lib_cells phy_dig/clk_gating/icc_place792size_cell phy_dig/clk_gating/icc_place792 TSMC_CLN90G_SC9NTHVT_SLOW_M40_0P9/BUFX3H1T10N Report wire length:report_net_statistics {net1 net2}Skip route on nets:set_net_routing_rule -rule default -reroute freeze [get_nets {list_of_nets}] --> SolvNet ArticleCheck logic vs. physical library:check_library -logic lib/LM/phy_core_SLOW_125_0P9.db -mw_library_name phy_core -cellsphy_coreCaution:FRAM view of the physical cell needs to exist, otherwise the check willfail!!!Open the GUI of a certain command:gui_show_form place_optGet default values of a command:get_command_option_values -default -command clock_optReport layout statistics:report_design -physicaleco-by-netlist-change command:update_mw_design_eco -change_verilog OUT/verilog_netlist.v phy_core -top_module phy_core Run eco route:route_eco -auto -search_repair_loop 5 -utilize_dangling_wires -reroutemodified_nets_first_then_othersAdd padding to cells:set_keepout_margin -outer {5 5 5 5} -macro_masters AVT20 -type hard --> SolvNet Article Snapshot of graphical window:gui_set_setting -window [gui_get_current_window -types Layout -mru] -setting viewshot -value xxx.pngList all loaded procedures:info procWrite verilog file:write_verilog -no_pg_nets verilog_file.vWrite verilog file with power pins and power signals:write_verilog -pg_ports -output_net_name_for_pg verilog_file.vUsing a file as input for a command:route_group -nets [read [open nets_file.txt r]]。

Lithium Ion Battery and ChargerThe MX-880’s lithium ion battery can be used without rules.rechargeable batteries and can be kept charging for any when the MX-880 needs the client simply plugs in the charger and con-500 Mamaroneck Avenue,Harrison,NY 10528 Phone:(914) 835-4484 Fax:(914) 835-4532Automatic BacklightingThe integral motion sensor detects any movement of the remote control and automatically backlights or one can press the Light button.An MX-880 in every RoomSpecify a customized MX-880 for every room in a e the included set of preprinted room labels to fit in the coined area at the base of the control to iden-tify which remote is cus-tomized for each room.Customize with Icons and BackgroundsLike the MX-3000,the MX-880 displays any of the acclaimed factory themes.etary graphics can add their own themes,backgrounds by simply placing their custom work in the right folder .dard 418MHz version or the MX-880i 433MHz The RFX-250 is included with both the MRF-350Routing Base Station and the MSC-400 Master System Controller (specify “i” series for 433 MHz RFX-250 for MX-880RFX-250i for MX-880iNarrow Band RF Transmission.MX-880 is compatible with the MSC-400 Master System ControllerImport MX-900 Devices,Complete With Macros or simply Open MX-900 FilesInstead of reprogramming a similar system,installers can freely import codes and macros from MX-900 files via Device Import,or simply open an MX-900 file in MX-880 Editor and make modifications to it.MX-880 Editor’s unique Device Assign window enables macro steps tobe imported as well as IR commands.Powerful Macro Programming Via Nesting,Multiple Page Jumps and Programmable VariablesMacro programming inMX-880 Editor enables theinstaller to freely create sophisticated status screens in macros,since there is nolimit to the number of page jumps inside a macro.With the ability to nest a macro inside anothermacro,an installer can cre-ate a complex routine,labelit descriptively and simply alias to it in one step.Variables can be used to track power status,users,rooms,or to create options that change in all macros based on one button press by the user.Fast,Structured Programming via the Program MenuWhen starting from scratch,MX-880’s open architecture enables the installer to start a new project with any template.By following the steps of the Program Menu,the installer quickly creates a finished working setup.Once tested and refined,the installer can freely experiment with any of the Color Graphic themes without affecting the setup.Additionally,companies with their own cus-tom graphics can add them to the visible themes in the Editor by sim-ply creating matching and correctly sized artwork in a new folder in the Graphics directory of MX-880 Editor.Label Buttons Freely via the Drag and Drop IR Database NavigatorIn addition to the tradi-tional Save All,which instantly creates a device,installers can customize the LCD but-ton with new text labels via the IR Database Navigator,now improved with textreplacement on any but-ton the installer drags to.In seconds,a program-mer can completely revise the layout of a device.Simply replace the text and the IR command.Instantly Navigate Existing FilesLike all OpenArchitecture MX Editors,the installer can open an existing file and instantly access any part of the file by clicking in T ree View.By expanding the plus signs in tree view,programmers can accelerate macro programming by making all the devices with macro codes on them accessible with one click of the mouse.At a Glance,Identify or T est any Button’s ProgrammingIn Simulator View any button with programming is FLAGGED,giving the installer an instant glimpse into the functionality of each page.An MSC-400 T rigger Command A Macro Punch ThroughPre Programmed IR Database Command Learned IR CommandBy simply navigating through the pages of a customer’s file the installer can easily identify a missing command.More importantly,by select-ing a button the installer can view any command in the button’s action list and test it individually.Quickly Drag and Drop Codes & T riggersAs with all OpenArchitecture MX Editors,the installer can import codes from work done on other remote controls using the Universal Browser.When programming MSC-400 triggers,a quick drag from the browser to either the selected button or the macro window is all that it takes to harness the sophistication of the MSC-400.Speed Programming with Color Graphics!PT M L T。

ArcSight SmartConnectors Software Version:8.4.3Configuration Guide for the F-Secure Anti-Virus File SmartConnectorDocument Release Date:October2023Software Release Date:October2023Legal NoticesOpen Text Corporation275Frank Tompa Drive,Waterloo,Ontario,Canada,N2L0A1Copyright NoticeCopyright2022-2023Open Text.The only warranties for products and services of Open Text and its affiliates and licensors(“Open Text”)are as may be set forth in the express warranty statements accompanying such products and services.Nothing herein should be construed as constituting an additional warranty.Open Text shall not be liable for technical or editorial errors or omissions contained herein.The information contained herein is subject to change without notice. Trademark Notices“OpenText”and other Open Text trademarks and service marks are the property of Open Text or its affiliates.All other trademarks or service marks are the property of their respective owners.Documentation UpdatesThe title page of this document contains the following identifying information:l Software Version numberl Document Release Date,which changes each time the document is updatedl Software Release Date,which indicates the release date of this version of the softwareTo check for recent updates or to verify that you are using the most recent edition of a document,go to:https:///support-and-services/documentationContentsConfiguration Guide for the F-Secure Anti-Virus File SmartConnector4Product Overview5 Configuration6Installing the SmartConnector7 Preparing to Install the SmartConnector7 Installing the SmartConnector7Device Event Mapping to ArcSight Fields9 F-Secure Mappings to ArcSight ESM Fields9 Send Documentation Feedback10Configuration Guide for the F-Secure Anti-Virus File SmartConnector Configuration Guide for the F-Secure Anti-Virus File SmartConnectorThis guide provides information for installing the SmartConnector for F-Secure Anti-Virus File and configuring the device for event collection.Intended AudienceThis guide provides information for IT administrators who are responsible for managing the ArcSight software and its environment.Additional DocumentationThe ArcSight SmartConnector documentation library includes the following resources: l Technical Requirements Guide for SmartConnector,which provides information about operating system,appliance,browser,and other support details for SmartConnector.l Installation and User Guide for SmartConnectors,which provides detailed information about installing SmartConnectors.l Configuration Guides for ArcSight SmartConnectors,which provides informationabout configuring SmartConnectors to collect events from different sources.l Configuration Guide for SmartConnector Load Balancer,which provides detailedinformation about installing Load Balancer.For the most recent version of this guide and other ArcSight SmartConnectordocumentation resources,visit the documentation site for ArcSight SmartConnectors8.4.Contact InformationWe want to hear your comments and suggestions about this book and the otherdocumentation included with this product.You can use the comment on this topic link at the bottom of each page of the online documentation,or send an email to MFI-***********************************.For specific product issues,contact Open Text Support for Micro Focus products.Product OverviewProduct OverviewF-Secure Policy Manager offers an easy and scalable way to deploy security applications, define and deploy security policies,and monitor security to ensure compliance with corporate security policies.Policy Manager provides a centralized management console for the security of the managed hosts in the network.ConfigurationConfigurationF-Secure Policy Manager Console logs messages in the Message pane about different eventsin Information,Warnings,and Error categories.Each Message pane tab can contain messages of all three severity.You can delete a category in the displayed context menu.Right-click an individualmessage to cut,copy,and delete operations.By default,messages are logged into UTF-8files in the message subdirectory of the local F-Secure Policy Manager Console installation directory.A separate log file is created for each message category.You can use the Preferences-Locations page to specify the directory for the log file and to switch logging on and off.Installing the SmartConnectorThe following sections provide instructions for installing and configuring your selected SmartConnector.Connector Appliance/ArcSight Management Center supports mounting for Network FileSystem(NFS)and CIFS(Windows)shares.When you install this connector on one of thesedevices,establish a CIFS mount on the device before adding the connector.Provide thisshare name during connector configuration.For more information,see Remote FileSystems in the Connector Appliance or ArcSight Management Center Administrator'sGuide.Preparing to Install the SmartConnectorBefore you install any SmartConnectors,make sure that the OpenText ArcSight products with which the connectors will communicate have already been installed correctly(such as ArcSight ESM or ArcSight Logger).For complete product information,refer to the Administrator's Guide to ArcSight Platform,available on ArcSight Documentation.If you are adding a connector to the ArcSight Management Center,see the ArcSight Management Center Administrator's Guide available on ArcSight Documentation for instructions.Before installing the SmartConnector,make sure that the following are available:l Local access to the machine where the SmartConnector is to be installedl Administrator passwordsInstalling the SmartConnector1.Start the installation wizard.2.Follow the instructions in the wizard to install the core software.3.Specify the relevant Global Parameters,when prompted.4.Select F-Secure Anti-Virus File from the Type drop-down,then click Next.5.For Trap Files Base Folder,specify the absolute path to the directory in which the logfiles are located,then click Next.Note:Mapped network drives must not be used in a Windows environment.WhenWindows executes a process as a service,an entirely new"virtual"environment iscreated.As a result,any drives you have mapped as a user must be re-mapped to berecognized by the SmartConnector.6.Select a destination and configure parameters.7.Specify a name for the connector.8.(Conditional)If you have selected ArcSight Manager as the destination,thecertificate import window for the ArcSight Manager is displayed.Select Import the certificate to the connector from destination,and then click Next.The certificate is imported and the Add connector Summary window is displayed.Note:If you select Do not import the certificate to connector from destination,theconnector installation will end.9.Select whether you want to install the connector as a service or in the standalonemode.plete the installation.11.Run the SmartConnector.For instructions about upgrading the connector or modifying parameters,seeInstallation and User Guide for SmartConnector.Device Event Mapping to ArcSight FieldsDevice Event Mapping to ArcSight Fields The following section lists the mappings of ArcSight data fields to the device's specific event definitions.See the ArcSight Console User's Guide for more information about the ArcSight data fields.F-Secure Mappings to ArcSight ESM FieldsSend Documentation FeedbackIf you have comments about this document,you can contact the documentation team by email.If an email client is configured on this computer,click the link above and an email window opens with the following information in the subject line:Feedback on Configuration Guide for the F-Secure Anti-Virus File SmartConnector (SmartConnectors8.4.3)Just add your feedback to the email and click send.If no email client is available,copy the information above to a new message in a web mail client,and send your feedback to***************************************.We appreciate your feedback!。

uDigital communicator with phone line monitor (loop or ground start)uMultiple telephone numbers, primary and duplicate paths with main and alternate destinations uAll reports within each of four route groups are programmableuOptional dual phone line switcher monitors two phone linesuOptional network interface module for two-way communication over Ethernet networksThe D7412G Control Panel provides an integrated solution for Access Control, Security, and Fire Alarm system applications. The control panel is capable of monitoring alarm points for intruder or fire alarms while operating user command centers and other outputs. The control panel includes a communicator that reports events to selected PSTN or IP network destinations through four programmable route groups.Programming and accessory modules offer flexibility and beneficial features rarely found in other security control systems.The D7412G Control Panel provides eight on-board points, up to 67 off-board points, 64 relays, and two access control doors. Grant access from a Wiegand style card reader connected to: a D9210B Access Control Module, a request-to-enter or request-to-exit input, or a keypad.FunctionsProgrammable Outputs• 2 A alarm power at 12 VDC• 1.4 A auxiliary power at 12 VDC •Four alarm output patterns •Automatic bell test•Programmable bell shut-off timerThe D7412G Control Panel provides up to 75individually identified points. Each pointaccommodates normally open (NO) and or normally closed (NC) devices with end-of-line (EOL) resistor supervision. Each point is programmable for fire, fire supervisory, or burglary applications.System Response•31 custom point indexes, including fire supervisory •Selectable point response time •Cross point compatibility •Fire alarm verification •Fire inspector’s local test •Watch mode•Scheduled events (skeds) arm, disarm, bypass and unbypass points, control relays, control authority levels, and control door accessUser Interface•Supervises up to eight command centers or keypads (up to 32 non-supervised command centers or keypads can be used)•Custom command center text•Full function command menu including custom functions•Each user has authority by area and 16-character name•14 custom authority levels control user’s authority to change, add, delete passcodes or access control tokens/cards, disarm, bypass points, and initiate system tests•Adjustable brightness or volume for keypad display orsounderNoticeAt least one keypad per system is recommended.Area ConfigurationsArea programming offers a wide selection of different system configurations. Each area is assigned anaccount number to define annunciation, control, and reporting functions. Multiple areas can be linked to a shared area which is automatically controlled (hallway or lobby). Area arming can be conditional on other areas (master or associate).User PasscodesUser passcodes contain three to six digits. Each user is assigned one of 14 customized authority levels in each area. Passcodes can be restricted to operate onlyduring certain times. User names can contain up to 16characters. The user name can be viewed, printed,reported to a central station in Modem IIIa 2Communications format or retrieved with Remote Programming (RPS) software.Security and Fire DetectionThe D7412G Control Panel provides eight on-board points, and up to 67 additional off-board points (depending on model and expansion interfaces).Program individual points to monitor all types of burglar alarm, fire alarm, and supervision municationsThe D7412G has four route groups. It can sort reports by priority and transmit reports to four route groups each of which has a programmable primary and backup destination.The D7412G is compatible with the D6600 NetCom Communications System using a DX4020 NetworkInterface Module. It has programmable anti-replay anti-substitution when using a DX4020.The Modem IIIa 2 Communications Format, available with Bosch receivers, adds reporting capabilities such as:•Individual point numbers and text•Opening or closing reports by area number, user number, and user text•Remote programming attempts •Diagnostic reportsEvent Log Storage, Viewing and PrintingAll local and transmitted events (up to 1,000 total events) are stored in a log. The event log includes time, date and event, with area, point and user number. You can view the event log from selectkeypads or remotely retrieve event information using RPS. With the printer interface module installed, the D7412G Control Panel allows the use of one on-siteparallel printers. The Event Log and a local printer provide a record of openings and closings without extra communications costs. RPS operators can retrieve events periodically using one phone call,rather than receiving several calls each day. When the control panel’s event log reaches the storage limit, it can send a report to a receiver.Access events that you can store, view or print include:•Access granted •No entry•Request-to-enter •Request-to-exitAccess Control•Custom door strike, point shunt and auto disarming response by area•Logging options for: Access Granted, No Entry,Request-to-exit, and Request-to-enter•14 panel-wide access levels with both manual and scheduled controlScheduled Events (Skeds)The D7412G Control Panel's internal clock and calendar helps to operate individually scheduledevents (skeds). Skeds perform a specific function such as arm/disarm, relay control, or point bypassing. The D7412G Control Panel offers:•40 scheduled events with up to 26 different functions •16 open or closing windows •Eight user windows•Day-of-week, date-of-year, or holiday only schedules •Four holiday schedules of 366 days each (leap year)Fire TestWhen a user activates Fire Test Mode, the controlpanel suppresses all reports to the central station. Use a passcode at the keypad to activate Fire Test Mode.The keypad and annunciator show all testing data. An automatic sensor reset feature saves time; you do not need to reset the sensors manually. At the end of test,the keypad shows the number of untested points.Programming, Diagnostics and ControlsUsers can program all system functions on-site with a D5200 Programmer, or remotely through RPS. A programmable system passcode prevents unauthorized remote programming.The control panel accommodates up to four separate telephone numbers for primary, alternate and backup receivers for automatic test reports.When resetting alarms, arming or disarming a combination fire/burglary and/or access control system, the user is identified by name and number.Installation/configuration notesCompatible ProductsKeypads D1260 Series Keypads (D1260, D1260W,D1260R, D1260BLK, D1260B)D720 Series Keypads (D720, D720W, D720R,D720B)D1255 Series Keypads (D1255, D1255W,D1255R, D1255B, D1255RB)D1256 and D1256RB Fire KeypadsD1257 and D1257RB Remote Fire AlarmAnnunciatorsD279A Independent Zone ControlDetectors OD850 Series Outdoor TriTech DetectorsMX250 Series Smoke DetectorsMX775i Addressable PIR DetectorMX794i Long Range Multiplex PIR DetectorMX934i Addressable PIR DetectorMX938i Addressable PIR DetectorZX776Z PIR DetectorZX794Z Long Range PIR DetectorZX835 TriTech Microwave/PIR DetectorZX935Z PIR DetectorZX938Z PIR DetectorZX970 PIR/Microwave DetectorBosch conventional detectors include Blue Line,seismic, PIR, TriTech PIR Microwave, photoelectric,and heat, and smoke.Enclosures D8103 Universal EnclosureD8108A Attack-Resistant EnclosureD8109 Fire EnclosureMagneticContactsAll Bosch magnetic contacts, including recessed,terminal connection, miniature, overhead door, andsurface mount.Bells D440 Bell 12 V, 15 cm (6 in.)D441 Bell 24 V, 15 cm (6 in.)MB-G10-12-R Bell 12 V, 25.4 cm (10 in.)MB-G10-24-R Bell 24 V, 25.4 cm (10 in.) Modules C900V2 Dialer Capture ModuleD125B Dual Class B Initiating ModuleD127 Reversing Relay ModuleD129 Class A Initiating ModuleD130 Auxiliary Relay ModuleD136 Plug-in RelayD185 Reverse Polarity Signaling ModuleD192C Notification Appliance Circuit ModuleD192G Notification Appliance Circuit ModuleD8121A Derived Channel S.T.U. Five Zone (Non-UL)D8122 Derived Channel S.T.U. Five Zone (UL)D8125MUX Multiplex Bus InterfaceD8125 POPEX Point ExpanderD8128D OctoPOPIT Eight Point ExpanderD8129 Octo-relay ModuleD9127 Series POPIT ModulesD9131A Printer and Parallel Interface ModuleD9210BLC Access Control Interface ModuleDS7432 Eight-input Remote ModuleDS7457i Series Single Zone Multiplex InputModulesDS7460i Two-input ModuleDS7461i Single-input Multiplex ModuleDS7465i Input and Output ModuleDX4010i RS-232 Serial Interface ModuleDX4020 Network Interface Module PeripheralHardwarervm4c Remote Video ModuleProgramming D5200 Series ProgrammersRPS or RPS-Lite Remote Programming Software Readers ARD-R10 iCLASS Mullion ReaderARD-R40 iCLASS Switchplate ReaderARD-RK40-09 iCLASS PIN ReaderARD-VSMART iCLASS ReaderD8201/W Series Low-profile ReadersD8203/W Series Mullion Proximity ReadersD8223 Prox Pro ReaderD8224 Mullion ReaderD8224-SP Switch Plate ReaderD8225 Mini Mullion ReaderD8227 Insert Card ReaderD8301/W Series Low-profile Proximity ReadersD8302 Vandal-resistant ReaderD8303/W Series Mullion Proximity ReadersD8304/W Series Extended Range ProximityReadersWP644 Series Waterproof Pass-through Readers SAFECOM RadioCommunicatorsSC2104 Series Slave CommunicatorsSC3100 Series Data Transfer RadioCommunicatorsSC4000 Series Full Data Transfer RadioCommunicatorWirelessProductsD8125INV Wireless InterfaceFA113 Keychain Remote ControlFA116 Executive ProgrammerFA202 Wireless Smoke Detector and TransmitterFA203S Necklace Pendant Transmitter (Single-button)FA203D Necklace Pendant Transmitter (Double-button)FA204 Necklace Pendant TransmitterFA205S Belt Clip/Loop Transmitter (Single-button)FA205D Belt Clip/Loop Transmitter (Double-button)FA206DS PIR TransmitterFA206i PIR TransmitterFA209 Billtrap TransmitterFA210 Universal Transmitter (Off-white)FA210-BN Universal Transmitter (Brown)FA210W Universal Wide Gap Transmitter (Off-white)FA210W-BN Universal Wide Gap Transmitter(Brown)FA216L Low Temperature TransmitterFA216H High Temperature TransmitterFA223S Water-resistant Pendant (White Single-button)FA223D Water-resistant Pendant (Black Double-button)FA250 High-power Universal TransmitterFA400 Remote ReceiverFA404R Transmitter ReceiverFA416R Transmitter ReceiverFA570 High Power Indoor RepeaterFA575 High Power Indoor/Outdoor RepeaterTechnical specificationsCommunicationsEnvironmental ConsiderationsNumber of…Power RequirementsOrdering informationD7412G Control PanelIncludes one printed circuit board (PCB).Order number D7412GD7412G Attack-Resistant KitIncludes one PCB, one D8108A Attack-Resistant Enclosure, and one D1640 Transformer.Order number D7412G-AD7412G Fire and Burglar KitIncludes one PCB, one D8109 Fire Enclosure, one D928 Dual Phone Line Switcher, and two D161 Dual Modular Phone Cords.Order number D7412G-BD7412G Commercial Burglar KitIncludes one PCB, one D8103 Enclosure, and oneD1640 Transformer.Order number D7412G-C D7412G Commercial Burglar KitIncludes one PCB, one D6103 Enclosure, and oneD1640 Transformer.Order number D7412G-DAccessoriesICP‑EZTS Dual Tamper SwitchCombination tamper switch with a wire loop for additional tamper outputs.Order number ICP-EZTSD101 Lock and Key SetShort-body lock set with one key supplied. Uses the D102 (#1358) replacement key.Order number D101D122 Dual Battery HarnessHarness with circuit breaker. Connects two batteries to a compatible control panel.Order number D122D122L Dual Battery Harness with Long LeadsColor-coded harness with circuit breaker and leads measuring 89 cm (35 in.). Connects 12 V batteries to compatible control panels.Order number D122LD126 Standby Battery (12 V, 7 Ah)A rechargeable sealed lead‑acid power supply used as a secondary power supply or in auxiliary or ancillary functions.Order number D126D137 Mounting BracketUsed to mount accessory modules in D8103, D8108A, and D8109 enclosures.Order number D137D138 Mounting Bracket, Right AngleUsed to mount accessory modules in D8103, D8108A, and D8109 enclosures.Order number D138D1218 Battery (12 V, 18 Ah)A 12 V sealed lead‑acid battery for standby and auxiliary power with two bolt‑fastened terminals. Includes hardware for attaching battery leads or spade connectorsOrder number D1218D1224 Battery (12 V, 26‑28 Ah)A 12 V sealed lead‑acid battery for standby and auxiliary power with two bolt‑fastened terminals. Includes hardware for attaching battery leads or spade connectors.Order number D1224D1238 Battery (12 V, 38 Ah)A 12 V sealed lead-acid battery for standby and auxiliary power with two bolt‑fastened terminals. Includes hardware for attaching battery leads or spade connectors.Order number D1238D1640 TransformerSystem transformer rated at 16.5 VAC, 40 VA.Order number D1640D8103 EnclosureGrey steel enclosure measuring 41 cm x 41 cm x 9 cm (16 in. x 16 in. x 3.5 in.).Order number D8103D8108A Attack Resistant EnclosureGrey steel enclosure measuring 41 cm x 41 cm x 9 cm (16 in. x 16 in. x 3.5 in.). UL Listed. Includes lock and key set. Requires the D2402 Mounting Plate.Order number D8108A D8109 Fire EnclosureRed steel enclosure measuring 40.6 cm x 40.6 cm x 8.9 cm (16 in. x 16 in. x 3.5 in). UL Listed. Includes a lock and key set.Order number D8109D9002‑5 Mounting SkirtMounts inside D8103, D8108A, and D8109 enclosures. Can accept up to six standard 7.62 cm x 12.7 cm (3 in. x 5 in.) cards.Order number D9002-5D136 Plug‑In RelayMaximum rating is 1 A at 24 VDC or 2 A at 12 VDC. Available individually (D136) or in a package of 25(D136‑25).Order number D136D928 Dual Phone Line SwitcherAllows the control panel to operate over and supervise two separate phone lines. Only one D162 phone cord is supplied. Two additional D161 or D162 phone cords are required.Order number D928Software OptionsRPS Kit (LPT)Account management and control panel-programming software with LPT connection.Order number D5500C-LPTRPS Kit (USB)Account management and control panel programming software with USB security key (dongle).Order number D5500C-USBRepresented by:Americas:Europe, Middle East, Africa:Asia-Pacific:China:America Latina:Bosch Security Systems, Inc. 130 Perinton Parkway Fairport, New York, 14450, USA Phone: +1 800 289 0096 Fax: +1 585 223 9180***********************.com Bosch Security Systems B.V.P.O. Box 800025617 BA Eindhoven, The NetherlandsPhone: + 31 40 2577 284Fax: +31 40 2577 330******************************Robert Bosch (SEA) Pte Ltd, SecuritySystems11 Bishan Street 21Singapore 573943Phone: +65 6571 2808Fax: +65 6571 2699*****************************Bosch (Shanghai) Security Systems Ltd.201 Building, No. 333 Fuquan RoadNorth IBPChangning District, Shanghai200335 ChinaPhone +86 21 22181111Fax: +86 21 22182398Robert Bosch Ltda Security Systems DivisionVia Anhanguera, Km 98CEP 13065-900Campinas, Sao Paulo, BrazilPhone: +55 19 2103 2860Fax: +55 19 2103 2862*****************************© Bosch Security Systems 2013 | Data subject to change without notice 2496214539 | en, V1, 01. Oct 2013。

C U S T O M E R ED U C A T I O N SE R V I C E S IC Compiler 1WorkshopStudent Guide20-I-071-SSG-011 2010.12Synopsys Customer Education Services700 East Middlefield RoadMountain View, California 94043Workshop Registration: 1-800-793-3448Copyright Notice and Proprietary Information Copyright © 2011 Synopsys, Inc. All rights reserved. This software and documentation contain confidential and proprietary information that is the property of Synopsys, Inc. The software and documentation are furnished under a license agreement and may be used or copied only in accordance with the terms of the license agreement. No part of the software and documentation may be reproduced, transmitted, or translated, in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without prior written permission of Synopsys, Inc., or as expressly provided by the license agreement.Destination Control StatementAll technical data contained in this publication is subject to the export control laws of the United States of America. Disclosure to nationals of other countries contrary to United States law is prohibited. It is the reader’s responsibility to determine the applicable regulations and to comply with them.DisclaimerSYNOPSYS, INC., AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.Registered Trademarks (®)Synopsys, AMPS, Cadabra, CATS, CRITIC, CSim, Design Compiler, DesignPower, DesignWare, EPIC, Formality, HSIM, HSPICE, iN-Phase, in-Sync, Leda, MAST, ModelTools, NanoSim, OpenVera, PathMill, Photolynx, Physical Compiler, PrimeTime, SiVL, SNUG, SolvNet, System Compiler, TetraMAX, VCS, Vera, and YIELDirector are registered trademarks of Synopsys, Inc.Trademarks (™)AFGen, Apollo, Astro, Astro-Rail, Astro-Xtalk, Aurora, AvanWaves, Columbia,Columbia-CE, Cosmos, CosmosEnterprise, CosmosLE, CosmosScope, CosmosSE, DC Expert, DC Professional, DC Ultra, Design Analyzer, Design Vision, DesignerHDL, Direct Silicon Access, Discovery, Encore, Galaxy, HANEX, HDL Compiler, Hercules, Hierarchical Optimization Technology, HSIMplus, HSPICE-Link, iN-Tandem, i-Virtual Stepper, Jupiter, Jupiter-DP, JupiterXT, JupiterXT-ASIC, Liberty, Libra-Passport,Library Compiler, Magellan, Mars, Mars-Rail, Milkyway, ModelSource, Module Compiler, Planet, Planet-PL, Polaris, Power Compiler, Raphael, Raphael-NES,Saturn, Scirocco, Scirocco-i, StarRC, Star-SimXT, Taurus, TSUPREM-4, VCS Express, VCSi, VHDL Compiler, VirSim, and VMC are trademarks of Synopsys, Inc. Service Marks (SM)MAP-in, SVP Café, and TAP-in are service marks of Synopsys, Inc.SystemC is a trademark of the Open SystemC Initiative and is used under license. ARM and AMBA are registered trademarks of ARM Limited. Saber is a registered trademark of SabreMark Limited Partnership and is used under license. All other product or company names may be trademarks of their respective owners.Document Order Number: 20-I-071-SSG-011IC Compiler 1 Student GuideUnit i: Introduction & OverviewFacilities ............................................................................................................................ i-2 Workshop Goal ................................................................................................................. i-3 Workshop Target Audience .............................................................................................. i-4 Workshop Prerequisite Knowledge .................................................................................. i-5 Introductions ..................................................................................................................... i-6 Curriculum Flow ............................................................................................................... i-7 Agenda .............................................................................................................................. i-8 Agenda .............................................................................................................................. i-9 Agenda ............................................................................................................................ i-10 High-Level IC Compiler Flow ........................................................................................ i-11 Lab 0: IC Compiler GUI – MainWindow ....................................................................... i-12 Lab 0: IC Compiler GUI – LayoutWindow .................................................................... i-13 Lab 0A: IC Compiler GUI .............................................................................................. i-14 Unit 1: Data Setup & Basic FlowUnit Objectives ................................................................................................................ 1-2 A Word of Caution About Scripts and Flows .................................................................. 1-3 General IC Compiler Flow ............................................................................................... 1-4 Data Setup ........................................................................................................................ 1-5 Logical Libraries .............................................................................................................. 1-6 Physical Reference Libraries ........................................................................................... 1-7 Milkyway Structure of Physical Libraries ....................................................................... 1-8 1. Specify the Logical Libraries ....................................................................................... 1-9 IC Compiler Initialization Files ..................................................................................... 1-10 2. Create a “Container”: The Design Library ................................................................ 1-11 Initial Structure of a Milkyway Design Library ............................................................ 1-12 3a. Read the Netlist and Create a Design CEL .............................................................. 1-13 What Does uniquify Do? ............................................................................................... 1-14 Milkyway Design Library with Design Cell .................................................................. 1-15 3b. Shortcut: Import the Netlist ..................................................................................... 1-16 The Technology File (.tf file) ......................................................................................... 1-17 Example of a Technology File ...................................................................................... 1-18 4. Specify TLU+ Parasitic RC Model Files ................................................................... 1-19 Timing is Based on Cell and Net Delays ....................................................................... 1-20 TLU+ Models ................................................................................................................ 1-21 Mapping file ................................................................................................................... 1-22 5a. Check the Libraries .................................................................................................. 1-23 5b. Verify Logical Libraries Are Loaded ...................................................................... 1-246. Define Logical Power/Ground Connections .............................................................. 1-257. Apply and Check Timing Constraints........................................................................ 1-26 Timing Constraints......................................................................................................... 1-278. Ensure Proper Modeling of Clock Tree ..................................................................... 1-289. Apply Timing and Optimization Controls ................................................................. 1-29 Available Timing and Optimization Controls ................................................................ 1-30 Timing and Optimization Setup Example ...................................................................... 1-3110. Perform a ‘Timing Sanity Check’ ............................................................................ 1-3211. Remove Unwanted “Ideal Net/Networks” ............................................................... 1-3312. Save the Design........................................................................................................ 1-34 UNIX Manipulation of a Milkyway Database ............................................................... 1-35 Loading an Existing Cell After Exiting ICC .................................................................. 1-36 Data Setup Summary ..................................................................................................... 1-37 Example .synopsys_dc.setup ......................................................................................... 1-38 Example Timing & Optimization Control ..................................................................... 1-39 Example Data Setup Run Script (1 of 2) ....................................................................... 1-40 Data Setup Run Script cont’d (2 of 2) ........................................................................... 1-41 Test for Understanding (1 of 2) ..................................................................................... 1-42 Test for Understanding (2 of 2) ..................................................................................... 1-43 General IC Compiler Flow ............................................................................................. 1-44 Design Planning ............................................................................................................. 1-45 Load an Existing Floorplan ............................................................................................ 1-46 Placement and Related Optimizations ........................................................................... 1-47 Clock Tree Synthesis ..................................................................................................... 1-48 Routing ........................................................................................................................... 1-49 Chip Finishing ................................................................................................................ 1-50 Analyzing the Results (1/2) ........................................................................................... 1-51 Analyzing the Results (2/2) ........................................................................................... 1-52 Example “run” Script ..................................................................................................... 1-53 Basic Flow Summary ..................................................................................................... 1-54 Lab 1: Design Setup and Basic Flow ............................................................................. 1-55 Appendix A .................................................................................................................... 1-56 Enable Multiple Clocks per Register ............................................................................. 1-57 Enable Constant Propagation ......................................................................................... 1-58 Enable Multiple Port Net Buffering ............................................................................... 1-59 Enable Constant Net Buffering, if Needed .................................................................... 1-60 Define “Don’t Use” or “Preferred” Cells ....................................................................... 1-61 Keep Spare or Unloaded Cells ....................................................................................... 1-62 Prevent Buffering of Clock-as-Data Networks .............................................................. 1-63 Modify Optimization Priority if Needed........................................................................ 1-64 Enable Recovery and Removal Timing Arcs ................................................................. 1-65 Apply Area Constraint for Area Recovery .................................................................... 1-66 Apply a Power and Area Critical Range ........................................................................ 1-67 Unit 2: Design PlanningUnit Objectives ................................................................................................................ 2-2 General IC Compiler Flow ............................................................................................... 2-3Terminology ..................................................................................................................... 2-4 ICC Design Planning and Re-Synthesis Flow ................................................................. 2-5 Create the Starting Floorplan ........................................................................................... 2-6 Select the Design Planning Task GUI ............................................................................. 2-7 Create Physical-only Pad Cells ........................................................................................ 2-8 Specify Pad Cell Locations .............................................................................................. 2-9 Initialize the Floorplan ................................................................................................... 2-10 Core Area Parameters .................................................................................................... 2-11 Floorplan After Initialization ......................................................................................... 2-12 Insert Pad Filler Cells..................................................................................................... 2-13 Create P/G Pad Rings..................................................................................................... 2-14 Prior to Virtual Flat Placement ...................................................................................... 2-15 Ignore Extra Routing Layers .......................................................................................... 2-16 Constraining Macros ...................................................................................................... 2-17 Manual Macro Placement .............................................................................................. 2-18 Congestion Potential Around Macro Cells .................................................................... 2-19 Apply Global Placement Blockages .............................................................................. 2-20 Apply Specific Placement Blockages ............................................................................ 2-21 Summary: Create the Starting Floorplan ....................................................................... 2-22 Test For Understanding.................................................................................................. 2-23 Perform Virtual Flat Placement ..................................................................................... 2-24 Set Placement Strategy Parameters ................................................................................ 2-25 VF Placement with Virtual IPO (VIPO) ........................................................................ 2-26 Perform Virtual Flat Placement ..................................................................................... 2-27 Hierarchy Aware Placement or Gravity ......................................................................... 2-28 Summary: Virtual Flat Placement .................................................................................. 2-29 Reduce Congestion ........................................................................................................ 2-30 Is the Design Congested? ............................................................................................... 2-31 Understanding the Congestion Calculation ................................................................... 2-32 Congestion Guidelines ................................................................................................... 2-33 Can Analyze Congestion Layer-by-Layer ..................................................................... 2-34 Modify Macro Placement Constraints ........................................................................... 2-35 Apply Standard Cell Placement Constraints .................................................................. 2-36 Is High Cell Density Causing Congestion? ................................................................... 2-37 Reducing Cell Density Hotspots .................................................................................... 2-38 Coordinate-based Placement Blockages ........................................................................ 2-39 Modify “FP Placement Strategy” Options ..................................................................... 2-40 Placement Strategy Options and Defaults ...................................................................... 2-41 Macro Placement Strategy Examples ............................................................................ 2-42 Perform Congestion-driven Placement .......................................................................... 2-43 Invoke the High Effort Congestion Strategy ................................................................. 2-44 Modify the Floorplan ..................................................................................................... 2-45 “Fix” All Macro Cell Placement .................................................................................... 2-46 Summary: Reduce Congestion ....................................................................................... 2-47 Test For Understanding (1 of 2)..................................................................................... 2-48 Test For Understanding (2 of 2)..................................................................................... 2-49Synthesize the Power Network (PNS) ........................................................................... 2-50 Power Network Synthesis (PNS) ................................................................................... 2-51 Define Logical Power/Ground Connections .................................................................. 2-52 P/G Rings Around Groups of Macros ............................................................................ 2-53 Create P/G Rings Around Groups of Macros ................................................................ 2-54 Ready for PNS ............................................................................................................... 2-55 Apply Power Network Constraints ................................................................................ 2-56 Synthesize and Analyze the Power Network ................................................................. 2-57 Modify Constraints and Re-synthesize .......................................................................... 2-58 Create Virtual Power/Ground Pads if Needed ............................................................... 2-59 Create New Floorplan with Added P/G Pads ................................................................ 2-60 Commit the Power Network .......................................................................................... 2-61 Connect P/G Pins and Create Power Rails .................................................................... 2-62 Analyze the Power Network .......................................................................................... 2-63 Apply Power Net Placement Blockages ........................................................................ 2-64 Perform Placement Legalization .................................................................................... 2-65 Summary: Synthesize the Power Network .................................................................... 2-66 Reduce Delay ................................................................................................................. 2-67 Global Route and Analyze Congestion .......................................................................... 2-68 Modify Power Net Placement Blockages ...................................................................... 2-69 Return to “Reduce Congestion”, if Needed ................................................................... 2-70 Analyze Timing ............................................................................................................. 2-71 Perform In-Place Optimization ...................................................................................... 2-72 Modify Floorplan or Re-Synthesize, if Needed ............................................................. 2-73 Summary: Reduce Delay ............................................................................................... 2-74 Write Out the DEF File .................................................................................................. 2-75 Floorplan Settings Not Saved in DEF ............................................................................ 2-76 Write out DEF File......................................................................................................... 2-77 Re-Synthesize Before Placement ................................................................................... 2-78 Re-Synthesize Before Placement ................................................................................... 2-79 Test For Understanding (1 of 2)..................................................................................... 2-80 Test For Understanding (2 of 2)..................................................................................... 2-81 Summary ....................................................................................................................... 2-82 Lab 2: Design Planning .................................................................................................. 2-83 Appendix A .................................................................................................................... 2-84 Macro Constraints: Arrays ............................................................................................. 2-85 Macro Constraints: Legal Orientation Option .............................................................. 2-86 Macro Constraints: Anchor Bound Option ................................................................... 2-87 Macro Constraints: Side Channel Option ..................................................................... 2-88 Macro Constraints: Relative Location ........................................................................... 2-89 Appendix B .................................................................................................................... 2-90 Floorplan Exploration and Re-Synthesis Flow .............................................................. 2-91 Floorplan Exploration Objectives .................................................................................. 2-92 Overview: Floorplan Exploration .................................................................................. 2-93 Load the Floorplan Definition (DEF) File ..................................................................... 2-94 Pre-exploration Settings and Checks ............................................................................. 2-95Check Placement Readiness .......................................................................................... 2-96 Perform Low-effort Placement Optimization ................................................................ 2-97 Check and Fix Congestion ............................................................................................. 2-98 Modify the Floorplan ..................................................................................................... 2-99 Analyze and Fix Timing .............................................................................................. 2-100 Write Out the Floorplan DEF File ........................................................................... 2-101 Summary: Floorplan Exploration ................................................................................ 2-102 Summary: 3rd Party Design Planning Flow ................................................................ 2-103 Unit 3: PlacementUnit Objectives ................................................................................................................ 3-2 General IC Compiler Flow ............................................................................................... 3-3 Design Status Prior to Placement ..................................................................................... 3-4 IC Compiler Placement Flow ........................................................................................... 3-5 Placement Setup and Checks ........................................................................................... 3-6 “Fix” all Macro Cell Placements ..................................................................................... 3-7 Verify Layer and Placement Constraints ......................................................................... 3-8 Non-Default Clock Routing ............................................................................................. 3-9 Specify Non-Default Routing Rules .............................................................................. 3-10 Check Placement Readiness .......................................................................................... 3-11 Summary: Placement Setup and Checks ........................................................................ 3-12 Design-for-Test (DFT) Setup ......................................................................................... 3-13 Pre-Existing Scan Chains ............................................................................................... 3-14 The Issue with Existing Scan Chains ............................................................................. 3-15 SCANDEF-Based Chain Reordering ............................................................................. 3-16 Re-ordering Chains within Same “Partition” ................................................................. 3-17 Example SCANDEF from Synthesis with DFT ............................................................ 3-18 Example: Placement with Existing Ordering ................................................................. 3-19 Example: Reordering Within Scan-Chains .................................................................... 3-20 Example: Reordering Within Partitions ......................................................................... 3-21 Placement-Based Scan Chain Re-Ordering ................................................................... 3-22 Summary: DFT Setup .................................................................................................... 3-23 Power Setup ................................................................................................................... 3-24 Where Does Power Dissipation Occur? ......................................................................... 3-25 Leakage Power Optimization ......................................................................................... 3-26 Report Multi-Vth Cells .................................................................................................. 3-27 Reducing Dynamic Power Dissipation .......................................................................... 3-28 Switching Activity Terminology ................................................................................... 3-29 SAIF File Provides Switching Activity ......................................................................... 3-30 What if SAIF is Not Available? ..................................................................................... 3-31 Dynamic Power Optimization: LPP ............................................................................... 3-32 Dynamic Power Optimization: GLPO ........................................................................... 3-33 Summary: Power Optimization Flow ............................................................................ 3-34 Test For Understanding.................................................................................................. 3-35。

10
POTENZA 200Hz POWER
36
CARICA BORDO EDGE LOADING
11
PREFUS.COLLA QMS-C GLUE FEED PUMP QMS-C
37
CARICA BORDO EDGE LOADING
12
INCOLLATORE GLUING UNIT
38
INTESTATORE YU/SP750 CUT-OFF UNIT YU/SP750
DATA DATE
DISEGNATO DRAWN
DATA DATE
CONTROLLATO CHECKED
DATA DATE
APPROVATO APPROVED
15
ALIMENTAZIONE GENERALE POWER SUPPLY MAIN
41
REFILATORE 1 TRIMMING UNIT 1
Corrente di
23.Set.2008 15.Dic.2007
23.Set.2008
limitazione Current of limitation (kA)
FUSIBILI FUSES
2
17 17 17 17 17 17
NH32A gG NH32A gG NH40A gG NH40A gG NH63A gG NH63A gG
INGRESSI INPUTS
SINGAPORE
FORMATO FORMAT SCALA SCALE FOGLIO SHEET
24
AUSILIARI AUXILIARES
50
INGRESSI INPUTS
A4 1:1 1
2977100314C

（转贴）下面的更详细点ICCAVR中文使用说明（1）ImageCraft ICCAVR 的中文使用说明ICCAVR 介绍1 ImageCraft 的ICCAVR 介绍ImageCraft 的ICCAVR 是一种使用符合ANSI 标准的C 语言来开发微控制器MCU程序的一个工具它有以下几个主要特点ICCAVR 是一个综合了编辑器和工程管理器的集成工作环境IDE 其可在WINDOWS9X/NT 下工作源文件全部被组织到工程之中文件的编辑和工程的构筑也在这个环境中完成编译错误显示在状态窗口中并且当你用鼠标单击编译错误时光标会自动跳转到编辑窗口中引起错误的那一行这个工程管理器还能直接产生您希望得到的可以直接使用的INTEL HEX 格式文件INTEL HEX 格式文件可被大多数的编程器所支持用于下载程序到芯片中去ICCAVR 是一个32 位的程序支持长文件名出于篇幅考虑本说明书并不介绍通用的C 语言语法知识仅介绍使用ICC AVR 所必须具备的知识因此要求读者在阅读本说明书之前应对C 语言有了一定程度的理解2 ICCAVR 中的文件类型及其扩展名文件类型是由它们的扩展名决定的IDE 和编译器可以使用以下几种类型的文件输入文件.c 扩展名----表示是C 语言源文件.s 扩展名----表示是汇编语言源文件.h 扩展名----表示是C 语言的头文件.prj 扩展名----表示是工程文件这个文件保存由IDE 所创建和修改的一个工程的有关信息.a 扩展名----库文件它可以由几个库封装在一起libcavr.a 是一个包含了标准C 的库和AVR 特殊程序调用的基本库如果库被引用链接器会将其链接到您的模块或文件中您也可以创建或修改一个符合你需要的库输出文件.s 对应每个C 语言源文件由编译器在编译时产生的汇编输出文件.o 由汇编文件汇编产生的目标文件多个目标文件可以链接成一个可执行文件.hex INTEL HEX 格式文件其中包含了程序的机器代码.eep INTEL HEX 格式文件包含了EEPROM 的初始化数据.cof COFF 格式输出文件用于在ATMEL 的AvrStudio 环境下进行程序调试.lst 列表文件在这个文件中列举出了目标代码对应的最终地址.mp 内存映象文件它包含了您程序中有关符号及其所占内存大小的信息.cmd NoICE 2.xx 调试命令文件.noi NoICE 3.xx 调试命令文件.dbg ImageCraft 调试命令文件3 附注和扩充#pragma 编译附注这个编译器接受以下附注#pragma interrupt_handler <func1>:<vector number> <func2>:<vector> ...这个附注必须在函数之前定义它说明函数func1 func2 是中断操作函数所以编译器在中断操作函数中生成中断返回指令reti 来代替普通返回指令ret 并且保存和恢复函数所使用的全部寄存器同样编译器根据中断向量号vector number 生成中断向量地址#pragma ctask <func1> <func2>...这个附注指定了函数不生成挥发寄存器来保存和恢复代码它的典型应用是在RTOS实时操作系统中让RTOS 核直接管理寄存器#pragma text:<name>改变代码段名称使其与命令行选项相适应#pragma data:<data>改变数据段名称使其与命令行选项相适应这个附注在分配全局变量至EEPROM中时必须被使用读者可参考访问EEPROM 的例子#pragma abs_address:<address>函数与全局数据不使用浮动定位重定位而是从<address>开始分配绝对地址这在访问中断向量和其它硬件项目时特别有用#pragma end_abs_address结束绝对定位使目标程序使用正常浮动定位C++ 注释如果你选择了编译扩充(Project->Options->Compiler) 你可以在你的源代码中使用C ++ 的// 类型的注释二进制常数如果你选择了编译扩充(Project->Options->Compiler) 你可以使用0b<1|0>* 来指定二进制常数例如0b10101 等于十进制数21在线汇编你可以使用asm("string")函数来指定在线汇编代码读者可参考在线汇编4 代码转换IAR 或其它ANSI C 编译系统的代码转换IAR C 编译器作为应用于AVR 的第一个C 编译器它有十分丰富的源代码当你从IAR编译系统转换到ImageCraft 编译系统时绝大多数符合ANSI C标准的程序代码不需要转换IAR C 中IO 寄存器的定义与ICCAVR 也是相同的中断操作描述ICCAVR 使用pragma 附注描述中断操作函数而IAR 引入了语法扩充interrupt 关键字下面是一个对照在ICCAVR 中#pragma interrupt_handler func:4 // 4 是这个中断的向量号func 为中断处理函数名称ICCAVR 可以使多个中断向量共用一个中断处理函数在IAR 中interrupt [vector_name] func() // vector_name 是某一个中断向量的名称IAR C 的中断向量地址使用中断名称来代替以增加程序的可读性扩充关键字IAR 引入flash 关键字将项目分配进入程序存贮空间FLASH 存贮器ICCAVR 使用const 关键字来达到相同的目的过程调用转换在两个编译系统之间函数参数传递使用的寄存器是不同的这仅影响手工写的汇编函数在线汇编宏等IAR 不支持在线汇编符号而ICCAVR 支持在线汇编ICCAVR中文使用说明（2）1 起步自你启动IDE 后首先从Project 菜单系统选择Open 命令进入\icc\examples.avr 目录并且选择并打开led 工程工程管理器显示在这个工程中只有一个文件led.c 然后从Project 菜单中选择Options 命令打开工程编译选项在"T arget"标号下选择目标处理器然后从Project 菜单中选择Make Project 命令IDE 将调用编译器编译这个工程文件并且在状态窗口中显示所有的信息如果没有错误在与源文件同一个目录在这个例子中是\icc\examples.avr 中输出一个文件led.hex 这个文件是INTEL HEX 格式大多数能支持AVR MCU 的编程器和模拟器都支持这种格式并且能下载这个程序进入你的目标系统这样就完成了一个程序的构筑如果你希望用支持COFF 调试信息的工具来测试你的程序比如AVR Studio 那么你需要从Project 菜单中选择Options 命令在编译标签下选择COFF 输出文件格式对一些常用的功能你也可使用工具条或鼠标右键弹出菜单例如你可以在工程窗口单击鼠标右键选择编译选项在工程窗口中双击文件名IDE 将使用编辑器打开这个文件按这个方法打开led.c作为试验可设置一些错误例如从一行中删除分号现在从Project 菜单中选择Make Project 命令IDE 首先自动保存已经改变的文件并且开始编译这个文件这时在状态窗口中会显示错误信息单击状态窗口中错误信息行或单击其左边的错误符号光标将移到编辑器中错误行的下面一行上基本上所有C 编译器都是这样开始一个新的工程从Project 菜单中选择New 命令并且浏览至你希望输出工程文件的目录输出文件的名称取决于你的工程文件名称例如如果你创建一个名称为foo.prj 的工程那么输出文件名称为foo.hex 或foo.cof 等自从创建你自己的工程后你可以开始写你的源代码(C 或汇编格式) 并且将这个文件加入到工程文件排列中单击工具栏中Build 图标可以很容易地构筑这个工程IDE 输出与ATMEL 的AVR Studio 完全兼容的COFF 文件你可以使用ATMEL 的AVR Studio 来调试你的代码为更容易地使用这个开发工具你可以使用应用程序向导来生成一些使用有关硬件的初始化代码2 C 程序的剖析一个C 程序必须定义一个main 调用函数编译器会将你的程序与启动代码和库函数链接成一个可执行文件因此你也可以在你的目标系统中执行它启动代码的用途在启动文件中很详细地被描述了一个C 程序需要设定目标环境启动代码初始化这个目标使其满足所有的要求通常你的main 例程完成一些初始化后然后是无限循环地运行作为例子让我们看\icc\examples 目录中的文件led.c#include <io8515.h>/* 为使能够看清LED 的变化图案延时程序需要有足够的延时时间*/void Delay(){unsigned char a, b;for (a = 1; a; a++)for (b = 1; b; b++);}void LED_On(int i){PORTB = ~BIT(i); /* 低电平输出使LED 点亮*/Delay();}void main()4{int i;DDRB = 0xFF; /*定义B口输出*/PORTB = 0xFF; /* B 口全部为高电平对应LED 熄灭*/while (1){/*LED 向前步进*/for (i = 0; i < 8; i++)LED_On(i);/* LED 向后步进*/for (i = 8; i > 0; i--)LED_On(i);/* LED 跳跃*/for (i = 0; i < 8; i += 2)LED_On(i);for (i = 7; i > 0; i -= 2)LED_On(i);}}这个main 例程是很简单的在初始化一些IO 寄存器后之后它运行在一个无限循环中并且在这个循环中改变LED 的步进图案LED 是在LED_On 例程中被改变的在LED_On 例程中直接写正确的数值到IO 端口因为CPU 运行很快为能够看见图案变化LED_On 例程调用了延时例程因为延时的实际延时值不能被确定这一对嵌套循环只能给出延时的近似延时时间如果这个实际定时时间是重要的那么这个例程应该使用硬件定时器来完成延时其它的例子8515intr.c 程序很简单但同样清楚地显示了如何用C 写一个中断处理过程这两个例子可以作为你的程序的起点四ICCAVR 的IDE 环境1 编译一个单独的文件正常建立一个输出文件的次序是你首先应该建立一个工程文件并且定义属于这个工程的所有文件然而我们有时也需要将一个文件单独地编译为目标文件或最终的输出文件这时可以这样操作从IDE 菜单File 中选择Compile File... 命令来执行to Object 和to Output 中的任意一个当你调用这个命令时文件应该是打开的并且在编辑窗口中可以编辑的编译一个文件为目标文件to Object 对检查语法错误和编译一个新的启动文件是很有用的编译一个文件为输出文件to Output 对较小的并且是一个文件的程序较为有用注意这里使用默认的编译选项2 创建一个新的工程为创建一个新的工程从菜单Project 中选择New 命令IDE 会弹出一个对话框在对话框中你可以指定工程的名称这也是你的输出文件的名称如果你使用一些已经建立的源文件你可在菜单Project 中选择AddFile(s) 命令另外你可以在菜单File 中选择New 命令来建立一个新的源文件来输入你的代码你可以在菜单File 中选择Save 或Save As 命令来保存文件然后你可以象上面所述调用AddFile(s) 命令将文件加入到工程中也可在当前编辑窗口中单击鼠标右键选择Add to Project 将文件加入已打开的工程列表中通常你输出源文件在工程同一个目录中但也可不作这样要求工程的编译选项使用菜单中Project 中的Options 命令3 工程管理工程管理允许你将多个文件组织进同一个工程而且定义它们的编译选项这个特性允许你将工程分解成许多小的模块当你处理工程构筑时只有一个文件被修改和重新编译如果一个头文件作了修改当你编译包含这个头文件的源文件时IDE 会自动重新编译已经改变的头文件一个源文件可以写成C 或汇编格式的任意一种C 文件必须使用.c 扩展名汇编文件必须使用.s 扩展名你可以将任意文件放在工程列表中例如你可以将一个工程文档文件放在工程管理窗口中工程管理器在构筑工程时对源文件以外的文件不予理睬对目标器件不同的工程可以在编译选项中设置有关参数当你新建一个工程时使用默认的编译选项你可以将现有编译选项设置成默认选项也可将默认编译选项装入现有工程中默认编译选项保存在default.prj 文件中为避免你的工程目录混乱你可以指定输出文件和中间文件到一个指定的目录通常这个目录是你的工程目录的一个子目录4 编辑窗口编辑窗口是你与IDE 交流信息的主要区域在这个窗口中你可以修改相应的文件当编译存在错误时用鼠标单击有关错误信息时编辑器会自动将光标定位在错误行的位置注意对C 源文件中缺少分号的错误编辑器定位于其下面一行5 应用构筑向导应用构筑向导是用于创建外围设备初始化代码的一个图形界面你可以单击工具条中的Wizard 按钮或菜单Tools 中的ApplicationBuilder 命令来调用它应用构筑向导使用编译选项中指定的目标MCU来产生相应的选项和代码应用构筑向导显示目标MCU 的每一个外围设备子系统它的使用是很显而易见的在这里你可以设置MCU 的所具有的中断内存定时器IO 端口UART SPI 和模拟量比较器等外围设备并产生相应的代码如果你需要的话还可产生main( )函数6 状态窗口状态窗口显示IDE 的状态信息7 终端仿真IDE 有一个内置的终端仿真器注意它不包含任意一个ISP 在系统编程功能但它可以作为一个简单的终端或许可以显示你的目标装置的调试信息也可下载一个ASC 码文件从6.20 版本开始IDE 加入了对ISP 的支持五菜单解释1 弹出菜单在ICCAVR 环境中单击右键那么ICCAVR 会根据实际情况弹出相应的工具菜单2 File Menu 文件菜单New 新建一个文件你可在编辑窗口是输入文字或代码Reopen 重新打开历史文件有关历史文件显示的右边的子菜单中Open 打开一个已以经存在的文件用于编辑文件用浏览窗口选择Reload … form Disk 放弃全部的修改从磁盘中重新装载当前文件Reload ….from Back UP 从最后一次的备份文件中装载当前文件Save 保存当前文件如果环境设置中设置了保存备份文件则将原文件以<file>.~<ext>形式保存Save as 将当前文件用另外一个名称来保存Close 关闭当前文件如果文件有过修改系统会进行提示Compile File … to Object 编译当前文件成目标文件注意目标文件不可以直接用于对芯片编程或用于调试其主要用于语法检查为创建新的启动文件或库产生目标文件Compile File ... to Output 编译当前文件成输出文件其产生的输出文件可用于编程器和调试器Save All 保存所有打开的文件Closs All 关闭当前打开的所有文件同样它会提示你保存已经修改的文件Print 打印当前文件Exit 退出ICCAVR 的IDE 环境3 Edit Menu 编辑菜单Undo 撤消最后一次的修改Redo 撤消最后一次的UndoCut 剪切选择的内容到剪帖板Copy 拷贝选择的内容到剪帖板Paste 将剪帖板内容粘帖在当前光标的位置Delete 删除选择的内容Select All 选择全部内容Block Indent 对选择的整块内容右移Block Outdent 对选择的整块内容左移4 Search menu 寻找菜单Find … 在编辑窗口中寻找一个文本它有以下选项Match Case –区分大小写Whole Word –全字匹配Up/Down –往上或往下Find in Files... –在当前打开的文件中或在当前工程的所有文件中或当前目录中的文件中寻找一段文本它有以下选项Case Sensitive –大小写敏感Whole Word - 全字匹配Regular Expression –寻找规则的表达式Replace... –在编辑器中替换文本Find Again –寻找下一个Goto Line Number –转到指定行号Add Bookmark –添加书签Delete Bookmark –删除书签Next Bookmark –跳转到下一个签Goto Bookmark –跳转到指定的书签5 View Menu 视图菜单Status Window –如果选中显示状态窗口Project Makefile –以只读方式打开makefile 文件Output Listing File –以只读方式打开列表文件6 Project Menu 工程菜单New... –创建一个新的工程文件Open –打开一个已经存在的工程文件Open All Files... –打开工程的全部源文件Close All Files –关闭全部打开的文件Reopen... –重新打开一个最近打开过的工程文件Make Project –解释和编译已经修改的文件为输出文件Rebuild All –重新构筑全部文件注意在版本升级后对原有工程最好全部重新构筑Add File(s) –添加一个文件到工程中这个文件可以是非源文件Remove Selected Files –从工程中删除选择的文件Option... –打开工程编译选项对话框Close –关闭工程Save As... –将工程换一个名称存盘7 Tools Menu 工具菜单Environment Options –打开环境和终端仿真器选项对话框Editor and Print Options –打开编辑和打印选项对话框AVR Calc –打开AVR 计算器可以计算UART 的波特率定时器的定时常数Application Builder –打开应用向导程序生成硬件的初始化代码Configure Tools –允许你添加自己的内容到工具菜单Run –以命令行方式运行一个程序8 Compiler Options 编译选项编译选项总共有三个页面Paths Compiler 和T arget在Paths 页面中有Include Path(s) –你可以指定包含文件的路径Assembler Include Path(s) –指定汇编包含文件的路径Library Path –链接器所使用的库文件的路径Output Directory –输出文件的目录Compiler 页面有Strict ANSI C Checking –严格的ANSI C 语法检查Accept Extensions –接受C++类型语法扩充Macro Define(s) –定义宏宏之间用空格或分号分开宏定义形式如下name[:value] 或name[=value]例如DEBUG:1;PRINT=printf等价于#define DEBUG 1#define PRINT printfMacro Undefine(s) –同上但意义相反Output File Format –输出文件格式COFF/HEX Intel HEX 或COFFOptimizations –代码优化Default –基本优化象寄存器分配共用相同的子例程等Maximize Code Size Reduction –只有专业版才可使用它调用了代码压缩优化去除了无用的碎片代码T arget 页面有Device Configuration –选择目标MCUMemory Sizes –要选择"Custom" 时指定内存大小包括ROM SRAM 和EEPROMText Address –通常代码地址开始于中断向量区域后面Data Address –指定数据起始地址通常为0x60Use Long JMP/CALL –指定MCU 是否支持长跳转和长调用Enhanced Core –指定硬件支持增强核指令IO Registers Offset Internal SRAM –指定内部SRAM 的偏移量例如, 8515 的SRAM起始于0x60, 在IO 寄存器空间后面延伸了512 字节而Mega603 , IO 寄存器覆盖在SRAM 空间中因此SRAM 也是从0 开始的Internal 对External SRAM –指定你的目标系统的数据SRAM 类型PRINTF Version –选择PRINTF 的版本Small 或Basic: 只有%c, %d, %x, %X, %u, and %s 格式支持Long: 支持%ld, %lu, %lx, %lXFloating point: %f 支持注意这个选项需要很大的内存AVR Studio Simulator IO –如果选中AVR Studio 的终端模拟仿真被支持Additional Libraries –使用标准库以外的附加库Strings in FLASH –字符串只保存在FLASH存贮器中Return Stack Size –指定编译器使用的硬件堆栈的大小编译器使用的软件堆栈的大小不需地指定Non Default Startup –允许你指定一个启动文件的位置系统默认的启动文件在Paths 页中指定这样IDE 可以使用多个启动文件Unused ROM Fill Pattern –用一串十六进制数填充空余的ROM 空间ICCAVR中文使用说明（3）C 库函数与启动文件1 启动文件这个链接器会自动将启动文件连接到您的程序之前并将标准库libcavr.a 与你的程序相连接启动文件根据目标MCU 的不同在crtavr.o 和crtatmega.o 中间任意选择一个启动文件定义了一个全局符号__start 它也是您的程序的起点启动文件的功能有1 初始化硬件和软件堆栈指针2 从idata 区拷贝初始化数据到直接寻址数据区data 区3 将bss 区全部初始化为零4 调用用户主例程main 函数5 定义一个退出点如果你的主函数main( )一旦退出它将进入这个退出点进行无限循环启动文件也定义了复位向量你不需要修改启动文件来使用别的中断具体可参考中断操作部分为修改和使用新的启动文件cd \icc\libsrc.avr ; 进入你安装的编译器路径<edit crtavr.s> ; 编辑修改crtavr.s 文件<open crtavr.s using the IDE> ; 用IDE 打开crtavr.s 文件<Choose "Compile File To->Object"> ;选择编译到目标文件创建一个新的crtavr.o copy crtavr.o ..\lib ; 拷贝到库目录如果您使用的目标MCU 是Mega 你应该用"crtatmega" 代替"crtavr" 注意Mega 的每个中断入口地址使用两个字word 而非Mega 芯片每一个中断入口地址使用一个字word .你也可以有多个启动文件你可以在工程选项对话框中很方便地直接指定一个启动文件加入您的工程中注意您必须指定启动文件的绝对路径或启动文件必须位于工程选项库路径所指定的目录中2 常用库介绍1 库源代码这个库源代码缺省路径为c:\icc\libsrc.avr\libsrc.zip 是一个密码保护的ZIP 压缩文件你可以从互连网上任意下载一个UNZIP 程序进行解压缩当本软件被开锁后密码显示在"About"对话框中例如unzip -s libsrc.zip; unzip 提示输入密码2 AVR 特殊函数----- ICCAVR 有许多访问UART EEPROM 和SPI 的函数堆栈检查函数对检测堆栈是否溢出很有用另外我们的互连网上有一个页专门存放用户写的源代码3 io*.h (io2313.h, io8515.h, iom603.h, ... 等.)这些文件中是从ATMEL 官方公开的定义IO 寄存器的源文件经过修改得到的应该用这些文件来代替老的avr.h 文件PORTB = 1;uc = PORTA;4 macros.h这个文件包含了许多有用的宏和定义5 其它头文件下列标准的C 头文件是被支持的如果你的程序使用了头文件所列出的函数那么包含头文件是一个好习惯在使用浮点数和长整型数的程序中必须用#include 预编译指令包含这些包含了这些函数原形的头文件读者可参考返回非整型值的函数assert.h - assert(), 声明宏ctype.h –字符类型函数float.h –浮点数原形limits.h –数据类型的大小和范围math.h –浮点运算函数stdarg.h –变量参数表.stddef.h –标准定义stdio.h –标准输入输出IO 函数stdlib.h –包含内存分配函数的标准库string.h –字符串处理函数3 字符类型库下列函数按照输入的ACS II 字符集字符分类使用这些函数之前应当用"#include <ctype.h>"包含int isalnum(int c)如果c 是数字或字母返回非零数值否则返回零int isalpha(int c)如果c 是字母返回非零数值否则返回零int iscntrl(int c)如果c 是控制字符如FF, BELL, LF ..等返回非零数值否则返回零int isdigit(int c)如果c 是数字返回非零数值否则返回零int isgraph(int c)如果c 是一个可打印字符而非空格返回非零数值否则返回零int islower(int c)如果c 是小写字母返回非零数值否则返回零int isprint(int c)如果c 是一个可打印字符返回非零数值否则返回零int ispunct(int c)如果c 是一个可打印字符而不是空格数字或字母返回非零数值否则返回零int isspace(int c)如果c 是一个空格字符返回非零数值包括空格CR, FF, HT, NL, 和VT 否则返回零int isupper(int c)如果c 是大写字母返回非零数值否则返回零int isxdigit(int c)如果c 是十六进制数字返回非零数值否则返回零int tolower(int c)如果c 是大写字母则返回c 对应的小写字母其它类型仍然返回cint toupper(int c)如果c 是小写字母则返回c 对应的大写字母其它类型仍然返回c4 浮点运算库下列函数支持浮点数运算使用这些函数之前必须用#include <math.h> 包含float asin(float x)以弧度形式返回x 的反正弦值float acos(float x)以弧度形式返回x 的反余弦值float atan(float x)以弧度形式返回x 的反正切值float atan2(float x, float y)返回y/x 的反正切其范围在- ~+ 之间float ceil(float x)返回对应x 的一个整型数小数部分四舍五入float cos(float x)返回以弧度形式表示的x 的余弦值float cosh(float x)返回x 的双曲余弦函数值float exp(float x)返回以e 为底的x 的幂即exfloat exp10(float x)返回以10 为底的幂即10xfloat fabs(float x)返回x 的绝对值float floor(float x)返回不大于x 的最大整数float fmod(float x, float y)返回x/y 的余数float frexp(float x, int *pexp)把浮点数x 分解成数字部分y 尾数和以2 为底的指数n 两个部分即x=y 2 n y的范围为0.5 y 1 y 值被函数返回而n 值存放到pexp 指向的变量中float fround(float x)返回最接近x 的整型数float ldexp(float x, int exp)返回x 2 e x pfloat log(float x)返回x 的自然对数float log10(float x)返回以10 为底的x 的对数float modf(float x, float *pint)把浮点数分解成整数部分和小数部分整数部分存放到pint 指向的变量小数部分应当大于或等于0 而小于1 并且作为函数返回值返回float pow(float x, float y)返回x y 值float sqrt(float x)返回x 的平方根float sin(float x)返回以弧度形式表示的x 的正弦值float sinh(float x)返回x 的双曲正弦函数值float tan(float x)返回以弧度形式表示的x 的正切值float tanh(float x)返回x 的双曲正切函数值5 标准输入输出库标准的文件输入输出是不能真正植入微控制器MCU 的标准stdio.h 的许多内容不可以使用不过有一些IO 函数是被支持的同样使用之前应用"#include <stdio.h>"预处理并且需要初始化输出端口最低层的IO 程序是单字符的输入(getchar)和输出(putchar)程序如果你针对不同的装置使用高层的IO 函数例如用printf 输出LCD 你需要全部重新定义最底层的函数为在ATMEL 的AVR Studio 模拟器终端IO 窗口使用标准IO 函数应当在编译选项中选中相应的单选钮注意作为缺省单字符输出函数putchar 是输出到UART 装置没有修改无论如何为使输出能如期望的那样出现在程序终端窗口中'' 字符必须被映射为成对的回车和换行CR/LFint getchar()使用查寻方式从UART 返回一个字符int printf(char *fmt, ..)按照格式说明符输出格式化文本frm 字符串格式说明符是标准格式的一个子集%d--输出有符号十进制整数%o --输出无符号八进制整数%x - 输出无符号十六进制整数%X –除了大写字母使用'A'-'F'外同%x%u - 输出无符号十进制整数%s –输出一个以C 中空字符NULL 结束的字符串%c –以ASCII 字符形式输出只输出一个字符%f –以小数形式输出浮点数%S –输出在FLASH存贮器中的字符串常量printf 支持三个版本取决于你的特别需要和代码的大小越高的要求代码越大基本形: 只有%c, %d, %x, %u, 和%s 格式说明符是承认的长整形: 针对长整形数的修改%ld, %lu, %lx 被支持, 以适用于精度要求较高的领域浮点形: 全部格式包括%f 被支持你使用编译选项对话框来选择版本代码大小的增加是值得关注的int putchar(int c)输出单个字符这个库程序使用了UART 以查寻方式输出单个字符注意输出’’字符至程序终端窗口int puts(char *s)输出以NL 结尾的字符串int sprintf(char *buf, char *fmt)按照格式说明符输出格式化文本frm 字符串到一个缓冲区格式说明符同printf( ) "const char *" 支持功能cprintf 和csprintf 是将FLASH中的格式字符串分别以prinf 和sprinf 形式输出6 标准库和内存分配函数标准库头文件<stdlib.h>定义了宏NULL 和RAND_MAX 和新定义的类型size_t 并且描述了下列函数注意在你调用任意内存分配程序比如.. calloc malloc 和realloc)之前必须调用_NewHeap 来初始化堆heapint abs(int i)返回i 的绝对值int atoi(char *s)转换字符串s 为整型数并返回它字符串s 起始必须是整型数形式字符否则返回0。

Feature目录Directed-broadcast（定向广播） (1)DHCP (4)IP Accounting（记账） (18)NetFlow (23)WCCP (30)DRP （Director Response Protocol） (32)IP Event Dampening(IP事件惩罚) (33)Core dump（核心崩溃） (36)GLBP （Gateway Load Balancing Protocol ） (38)SLA （Service Level Agreements） (52)NTP（网络时间协议） (66)Summer-time夏令时 (70)Syslog and local logging (72)FTP&TFTP (75)HTTP&HTTPS (76)SNMP (79)RMON（远程监视） (84)Embedded Event Manager (EEM) (86)SCP（安全复制协议） (110)Directed-broadcast（定向广播）概述在默认情况下，Cisco路由器在收到任何广播数据的时候，默认都是丢弃而不转发，在某些时候，有些广播是必须的，比如我们通常使用的NetBios Name Server协议，DNS协议，还有DHCP协议。

就像DHCP协议，当主机在没有地址的情况下，向服务器请求IP地址，正因为自己没有IP地址，却又不知道服务器在哪，所以需要使用广播来查找，这时，如果服务器在远程网络，而路由器又拒绝转发广播，那么将给我们的DHCP带来麻烦。

要如何才能在这种情况下让网络正常工作呢，那就是让路由器帮我们把广播转发到我们需要到达的目标网络，这样需要到达远程网络的广播，我们称为定向广播，比如我们本地网络是10.1.1.0/24的网段，我们需要将广播发到192.168.1.0/24的网段，那么只想让广播在192.168.1.0/24网段发送，广播地址为192.168.1.255，但如果直接这样发，是到达不了192.168.1.0/24网段的，所以需要得到路由器的允许。

Package‘ROpenFIGI’October12,2022Type PackageTitle R Interface to OpenFIGIVersion0.2.8Author Ruokun Huang<**********************>Maintainer Ruokun Huang<**********************>Description Provide a simple interface to Bloomberg's OpenFIGI API.Pleasesee<https://>for API details and registration.You may beeligible to have an API key to accelerate your loading process.License GPL(>=3)LazyData TRUEURL https:///HuangRicky/ROpenFIGIImports httr,jsonliteSuggests testthat,dplyrRoxygenNote5.0.1NeedsCompilation noRepository CRANDate/Publication2016-06-0408:38:44R topics documented:OpenFIGI (2)OpenFIGI_assignadditionalcols (2)OpenFIGI_MappingCreator (3)ROpenFIGI (4)sampleOpenFIGIdf (4)showFIGIIDType (5)Index612OpenFIGI_assignadditionalcols OpenFIGI OpenFIGI main functionDescriptionOpenFIGI main functionUsageOpenFIGI(input,apikey=NULL,openfigiurl="https:///v1/mapping",preferdf=F) Argumentsinput input data.frame or json,and others that can be feed into toJSONapikey your API keyopenfigiurl Bloomberg’s OpenFIGI URL,please see https://openfi/apipreferdf if only supply1input,do you prefer to see the data.frame directlyDetailsyou may need to setInternet2()or set up proxy if neededValuea list of data.frame,of a data.frame if preferdf=T and only1requestExamples##Not run:setInternet2()figirst=OpenFIGI(sampleOpenFIGIdf())##End(Not run)OpenFIGI_assignadditionalcolsAssign addition colsDescriptionAssign addition colsUsageOpenFIGI_assignadditionalcols(rst1,additioncols)OpenFIGI_MappingCreator3Argumentsrst1a result listadditioncols additional columns you would like to include in the data.frameDetailsinternal functionValuea data.frame with new columnsOpenFIGI_MappingCreatorCreate mapping table out of OpenFIGIDescriptionCreate mapping table out of OpenFIGIUsageOpenFIGI_MappingCreator(input,apikey=NULL,openfigiurl="https:///v1/mapping",additioncols=c("ID_ISIN","ID_BB_UNIQUE","ID_SEDOL","ID_COMMON","ID_WERTPAPIER","ID_CUSIP","ID_BB","ID_ITALY","ID_EXCH_SYMBOL","ID_FULL_EXCHANGE_SYMBOL","COMPOSITE_ID_BB_GLOBAL","ID_BB_GLOBAL_SHARE_CLASS_LEVEL","ID_BB_SEC_NUM_DES","ID_BB_GLOBAL","TICKER","ID_CUSIP_8_CHR","OCC_SYMBOL","UNIQUE_ID_FUT_OPT","OPRA_SYMBOL", "TRADING_SYSTEM_IDENTIFIER"))Argumentsinput input data.frame or json,and others that can be feed into toJSONapikey your API keyopenfigiurl Bloomberg’s OpenFIGI URL,please see https://openfi/apiadditioncols additional columns you would like to include in the data.frameDetailsassiging ISIN,CUSIP and other columns needed.Requires dplyr package to bind rows.Valuea data.frame4sampleOpenFIGIdf Examples##Not run:setInternet2()figirst=OpenFIGI_MappingCreator(sampleOpenFIGIdf())##End(Not run)ROpenFIGI ROpenFIGIDescriptionROpenFIGIDetailsProvide a simple interface to OpenFIGI by Bloomberg.parse data into data.frameAuthor(s)Ruokun Huang<**********************>Maintainer:Ruokun Huang<**********************>sampleOpenFIGIdf Generate a Sample data.frame for FIGI requestDescriptionGenerate a Sample data.frame for FIGI requestUsagesampleOpenFIGIdf()Valuea data.frame of sample requestshowFIGIIDType5 showFIGIIDType Generate FIGI Supported IdentifiersDescriptionGenerate FIGI Supported IdentifiersUsageshowFIGIIDType()Valuea char vectorIndexOpenFIGI,2OpenFIGI_assignadditionalcols,2OpenFIGI_MappingCreator,3ROpenFIGI,4ROpenFIGI-package(ROpenFIGI),4 sampleOpenFIGIdf,4showFIGIIDType,56。

UNIX系统后门的安放和日志的擦除-电脑资料这里请看一下这一篇文章：Linux下的后门和日志工具/Article/200604/8442.html当我们通过某种手段控制一个主机时，为了使自己能再次光顾这台计算机，我们通常在这个机器上留下后门，以便我们再次访问．一个做得好的后门，即使在入侵被管理员发现后，仍然能让你再次访问到主机．本文的意旨是让你学会如何在完全控制系统后保留自己的根用户权限，下面介绍一下我常用的制作后门的手法，不会也不可能覆盖到所有可能的方法，请原谅．1.Rhosts + + 后门在连网的Unix机器中,象Rsh和Rlogin这样的服务是基于rhosts 文件里的主机名使用简单的认证方法. 用户可以轻易的改变设置而不需口令就能进入. 入侵者只要向可以访问的某用户的rhosts文件中输入"+ +", 就可以允许任何人从任何地方无须口令便能进入这个帐号. 特别当home目录通过NFS向外共享时, 入侵者更热中于此. 这些帐号也成了入侵者再次侵入的后门. 许多人更喜欢使用Rsh, 因为它通常缺少日志能力. 许多管理员经常检查"+ +", 所以入侵者实际上多设置来自网上的另一个帐号的主机名和用户名,从而不易被发现.例如：# echo + + > /usr/bin/.rhosts# cat /usr/bin/.rhosts+ +# rlogin -l bin localhost将不用输入密码直接用bin帐号rlogin登陆进你的机器．2.Login后门在Unix里,login程序通常用来对telnet来的用户进行口令验证. 入侵者获取login.c的原代码并修改使它在比较输入口令与存储口令时先检查后门口令. 如果用户敲入后门口令,它将忽视管理员设置的口令让你长驱直入. 这将允许入侵者进入任何帐号,甚至是root.由于后门口令是在用户真实登录并被日志记录到utmp和wtmp前产生一个访问的, 所以入侵者可以登录获取shell却不会暴露该帐号. 管理员注意到这种后门后, 便用"strings"命令搜索login程序以寻找文本信息. 许多情况下后门口令会原形毕露. 入侵者就开始加密或者更好的隐藏口令, 使strings命令失效. 所以更多的管理员是用MD5校验和检测这种后门的.一般的rootkit包里都有login后门程序．3.服务进程后门inetd 进程负责监听各个TCP和UDP端口的连接请求，并根据连接请求启动相应的服务器进程，。

五菜单解释 iccavr使用手册P71 弹出菜单在 ICCAVR 环境中单击右键那么ICCAVR 会根据实际情况弹出相应的工具菜单2 File Menu 文件菜单New 新建一个文件你可在编辑窗口是输入文字或代码Reopen 重新打开历史文件有关历史文件显示的右边的子菜单中Open 打开一个已以经存在的文件用于编辑文件用浏览窗口选择Reload … form Disk 放弃全部的修改从磁盘中重新装载当前文件Reload ….from Back UP 从最后一次的备份文件中装载当前文件Save 保存当前文件如果环境设置中设置了保存备份文件则将原文件以<file>.~<ext>形式保存Save as 将当前文件用另外一个名称来保存Close 关闭当前文件如果文件有过修改系统会进行提示Compile File … to Object 编译当前文件成目标文件注意目标文件不可以直接用于对芯片编程或用于调试其主要用于语法检查为创建新的启动文件或库产生目标文件Compile File ... to Output 编译当前文件成输出文件其产生的输出文件可用于编程器和调试器Save All 保存所有打开的文件Closs All 关闭当前打开的所有文件同样它会提示你保存已经修改的文件Print 打印当前文件Exit 退出ICCAVR 的IDE 环境3 Edit Menu 编辑菜单Undo 撤消最后一次的修改Redo 撤消最后一次的UndoCut 剪切选择的内容到剪帖板Copy 拷贝选择的内容到剪帖板Paste 将剪帖板内容粘帖在当前光标的位置Delete 删除选择的内容Select All 选择全部内容Block Indent 对选择的整块内容右移Block Outdent 对选择的整块内容左移4 Search menu 寻找菜单Find …在编辑窗口中寻找一个文本它有以下选项Match Case –区分大小写Whole Word –全字匹配Up/Down –往上或往下Find in Files... –在当前打开的文件中或在当前工程的所有文件中或当前目录中的文件中寻找一段文本它有以下选项Case Sensitive –大小写敏感Whole Word - 全字匹配Regular Expression –寻找规则的表达式Replace... –在编辑器中替换文本Find Again –寻找下一个Goto Line Number –转到指定行号Add Bookmark –添加书签Delete Bookmark –删除书签Next Bookmark –跳转到下一个签Goto Bookmark –跳转到指定的书签5 View Menu 视图菜单Status Window –如果选中显示状态窗口Project Makefile –以只读方式打开 makefile 文件Output Listing File –以只读方式打开列表文件6 Project Menu 工程菜单New... –创建一个新的工程文件Open –打开一个已经存在的工程文件Open All Files... –打开工程的全部源文件Close All Files –关闭全部打开的文件Reopen... –重新打开一个最近打开过的工程文件Make Project –解释和编译已经修改的文件为输出文件Rebuild All –重新构筑全部文件注意在版本升级后对原有工程最好全部重新构筑Add File(s) –添加一个文件到工程中这个文件可以是非源文件Remove Selected Files –从工程中删除选择的文件Option... –打开工程编译选项对话框Close –关闭工程Save As... –将工程换一个名称存盘7 Tools Menu 工具菜单Environment Options –打开环境和终端仿真器选项对话框Editor and Print Options –打开编辑和打印选项对话框AVR Calc –打开 AVR 计算器可以计算UART 的波特率定时器的定时常数Application Builder –打开应用向导程序生成硬件的初始化代码Configure Tools –允许你添加自己的内容到工具菜单Run –以命令行方式运行一个程序8 Compiler Options 编译选项编译选项总共有三个页面 Paths Compiler 和Target在 Paths 页面中有Include Path(s) –你可以指定包含文件的路径Assembler Include Path(s) –指定汇编包含文件的路径Library Path –链接器所使用的库文件的路径Output Directory –输出文件的目录Compiler 页面有Strict ANSI C Checking –严格的 ANSI C 语法检查Accept Extensions –接受 C++类型语法扩充Macro Define(s) –定义宏宏之间用空格或分号分开宏定义形式如下name[:value] 或 name[=value]例如DEBUG:1;PRINT=printf等价于#define DEBUG 1#define PRINT printfMacro Undefine(s) –同上但意义相反Output File Format –输出文件格式 COFF/HEX Intel HEX 或COFFOptimizations –代码优化Default –基本优化象寄存器分配共用相同的子例程等Maximize Code Size Reduction –只有专业版才可使用它调用了代码压缩优化去除了无用的碎片代码Target 页面有Device Configuration –选择目标 MCUMemory Sizes –要选择"Custom" 时指定内存大小包括ROM SRAM 和EEPROMText Address –通常代码地址开始于中断向量区域后面Data Address –指定数据起始地址通常为0x60Use Long JMP/CALL –指定 MCU 是否支持长跳转和长调用Enhanced Core –指定硬件支持增强核指令IO Registers Offset Internal SRAM –指定内部 SRAM 的偏移量例如, 8515 的SRAM起始于0x60, 在IO 寄存器空间后面延伸了512 字节而 Mega603 , IO 寄存器覆盖在SRAM 空间中因此SRAM 也是从0 开始的Internal 对External SRAM –指定你的目标系统的数据 SRAM 类型PRINTF Version –选择 PRINTF 的版本Small 或 Basic: 只有 %c, %d, %x, %X, %u, and %s 格式支持Long: 支持 %ld, %lu, %lx, %lXFloating point: %f 支持注意这个选项需要很大的内存AVR Studio Simulator IO –如果选中 AVR Studio 的终端模拟仿真被支持Additional Libraries –使用标准库以外的附加库Strings in FLASH –字符串只保存在 FLASH存贮器中Return Stack Size –指定编译器使用的硬件堆栈的大小编译器使用的软件堆栈的大小不需地指定Non Default Startup –允许你指定一个启动文件的位置系统默认的启动文件在Paths 页中指定这样IDE 可以使用多个启动文件Unused ROM Fill Pattern –用一串十六进制数填充空余的 ROM 空间。