pc.arch.and.interface.notes.v2
presto windowns编译
presto windowns编译Presto是Hadoop生态系统中一个快速交互式分析引擎，旨在提供高速的数据查询和处理能力。
虽然Presto的主要用例是在Linux环境下运行，但它也可以在Windows操作系统上进行编译和部署。
本文将一步一步地介绍如何在Windows上编译Presto。
第一步：准备编译环境首先，确保你的Windows系统中安装了JDK（Java Development Kit）。
Presto需要Java 8或更高版本进行编译和运行。
你可以通过运行`java -version`命令来检查JDK的版本。
如果没有安装JDK，你可以从Oracle 官方网站（接下来，你需要安装Git以及编译和构建工具Maven。
Git用于从源代码库中获取Presto的最新版本，而Maven用于管理项目的依赖关系和构建过程。
你可以从Git官方网站（Maven官方网站（第二步：获取Presto源代码打开一个命令行窗口，并导航到你希望保存Presto源代码的目录。
执行下面的命令来克隆Presto的Git仓库：git clone这将创建一个名为“presto”的目录，并将Presto的源代码下载到该目录中。
第三步：编译Presto进入“presto”目录，并执行下面的命令来编译Presto：mvn clean install -DskipTests这个过程可能需要一些时间来下载和编译Presto的依赖库。
完成编译后，你将在“presto”目录的“presto-server/target”子目录中找到编译好的Presto服务器文件。
第四步：配置Presto在Windows上运行Presto之前，你需要进行一些配置。
进入“presto-server/target”子目录，并在其中创建一个名为“etc”的目录。
在“etc”目录中，创建名为“node.properties”的文件，并写入以下内容：node.environment=productionnode.id=your-unique-node-idnode.data-dir=c:/presto/data请注意，你需要将“your-unique-node-id”替换为一个唯一的节点标识符，并将“c:/presto/data”替换为一个你希望将Presto数据存储的目录。
接口工作室 WinISP编程软件 使用指南
WinISP使用指南 接口工作室（Interface Studio）推出的PDIUSBD12 USB开发板采用的MCU是Philips 公司的P89C51RD2，该款单片机除了兼容标准8051系列之外还有许多增强特性，其中的ISP 功能可以使用户能够抛弃笨重而且昂贵的编程器，不必插拔芯片就可轻松地在电路中对单片机编程，节约了用户的成本，极大地方便了程序调试过程。
WinISP是Philips公司为其具有ISP功能的单片机而设计的编程软件。
下面以WinISP2.26版，Windows2000操作系统为例，介绍该软件的安装和使用方法。
一．安装步骤1． WinISP的安装文件很小，约2.13M，假定放在如图1所示的目录。
图1 WinISP安装文件图标2．双击，进入安装画面如图2所示。
图2 安装过程13．之后出现如图3所示的欢迎界面，单击Next按钮。
图3 安装过程24．接着出现安装路径选择对话框，如果用户想改变默认安装路径，单击Browse按钮，如图4所示，在Choose Directory对话框中选择想要安装的目录，然后单击OK，再单击Next按钮。
图4 安装过程35．选择程序文件夹名，该名称就是桌面开始菜单中添加的软件名称，如图5所示，一般没有必要更改此项，直接单击Next。
图5 安装过程46．短暂的文件拷贝完后，出现图6所示的安装完成对话框，单击Finish完成安装。
图6 安装过程5二． WinISP的使用安装完成后，如图7所示，单击WinISP应用程序，启动WinISP。
WinISP启动后的画面如图8所示。
图8 启动WinISP可以看到左边一列按钮是灰的。
在Chip下拉组合框中选中USB开发板所使用的芯片P89C51RD2，这个时候左边的一列按钮已经有效了，但是还要在Port下拉组合框中选择你的串口电缆连接的计算机的串口号COM1(或COM2),在Osc(MHz)中输入18.432。
如图9所示。
NuMicro N9H30系列开发板用户手册说明书
NuMicro®FamilyArm® ARM926EJ-S BasedNuMaker-HMI-N9H30User ManualEvaluation Board for NuMicro® N9H30 SeriesNUMAKER-HMI-N9H30 USER MANUALThe information described in this document is the exclusive intellectual property ofNuvoton Technology Corporation and shall not be reproduced without permission from Nuvoton.Nuvoton is providing this document only for reference purposes of NuMicro microcontroller andmicroprocessor based system design. Nuvoton assumes no responsibility for errors or omissions.All data and specifications are subject to change without notice.For additional information or questions, please contact: Nuvoton Technology Corporation.Table of Contents1OVERVIEW (5)1.1Features (7)1.1.1NuMaker-N9H30 Main Board Features (7)1.1.2NuDesign-TFT-LCD7 Extension Board Features (7)1.2Supporting Resources (8)2NUMAKER-HMI-N9H30 HARDWARE CONFIGURATION (9)2.1NuMaker-N9H30 Board － Front View (9)2.2NuMaker-N9H30 Board － Rear View (14)2.3NuDesign-TFT-LCD7 － Front View (20)2.4NuDesign-TFT-LCD7 － Rear View (21)2.5NuMaker-N9H30 and NuDesign-TFT-LCD7 PCB Placement (22)3NUMAKER-N9H30 AND NUDESIGN-TFT-LCD7 SCHEMATICS (24)3.1NuMaker-N9H30 － GPIO List Circuit (24)3.2NuMaker-N9H30 － System Block Circuit (25)3.3NuMaker-N9H30 － Power Circuit (26)3.4NuMaker-N9H30 － N9H30F61IEC Circuit (27)3.5NuMaker-N9H30 － Setting, ICE, RS-232_0, Key Circuit (28)NUMAKER-HMI-N9H30 USER MANUAL3.6NuMaker-N9H30 － Memory Circuit (29)3.7NuMaker-N9H30 － I2S, I2C_0, RS-485_6 Circuit (30)3.8NuMaker-N9H30 － RS-232_2 Circuit (31)3.9NuMaker-N9H30 － LCD Circuit (32)3.10NuMaker-N9H30 － CMOS Sensor, I2C_1, CAN_0 Circuit (33)3.11NuMaker-N9H30 － RMII_0_PF Circuit (34)3.12NuMaker-N9H30 － RMII_1_PE Circuit (35)3.13NuMaker-N9H30 － USB Circuit (36)3.14NuDesign-TFT-LCD7 － TFT-LCD7 Circuit (37)4REVISION HISTORY (38)List of FiguresFigure 1-1 Front View of NuMaker-HMI-N9H30 Evaluation Board (5)Figure 1-2 Rear View of NuMaker-HMI-N9H30 Evaluation Board (6)Figure 2-1 Front View of NuMaker-N9H30 Board (9)Figure 2-2 Rear View of NuMaker-N9H30 Board (14)Figure 2-3 Front View of NuDesign-TFT-LCD7 Board (20)Figure 2-4 Rear View of NuDesign-TFT-LCD7 Board (21)Figure 2-5 Front View of NuMaker-N9H30 PCB Placement (22)Figure 2-6 Rear View of NuMaker-N9H30 PCB Placement (22)Figure 2-7 Front View of NuDesign-TFT-LCD7 PCB Placement (23)Figure 2-8 Rear View of NuDesign-TFT-LCD7 PCB Placement (23)Figure 3-1 GPIO List Circuit (24)Figure 3-2 System Block Circuit (25)Figure 3-3 Power Circuit (26)Figure 3-4 N9H30F61IEC Circuit (27)Figure 3-5 Setting, ICE, RS-232_0, Key Circuit (28)Figure 3-6 Memory Circuit (29)Figure 3-7 I2S, I2C_0, RS-486_6 Circuit (30)Figure 3-8 RS-232_2 Circuit (31)Figure 3-9 LCD Circuit (32)NUMAKER-HMI-N9H30 USER MANUAL Figure 3-10 CMOS Sensor, I2C_1, CAN_0 Circuit (33)Figure 3-11 RMII_0_PF Circuit (34)Figure 3-12 RMII_1_PE Circuit (35)Figure 3-13 USB Circuit (36)Figure 3-14 TFT-LCD7 Circuit (37)List of TablesTable 2-1 LCD Panel Combination Connector (CON8) Pin Function (11)Table 2-2 Three Sets of Indication LED Functions (12)Table 2-3 Six Sets of User SW, Key Matrix Functions (12)Table 2-4 CMOS Sensor Connector (CON10) Function (13)Table 2-5 JTAG ICE Interface (J2) Function (14)Table 2-6 Expand Port (CON7) Function (16)Table 2-7 UART0 (J3) Function (16)Table 2-8 UART2 (J6) Function (16)Table 2-9 RS-485_6 (SW6~8) Function (17)Table 2-10 Power on Setting (SW4) Function (17)Table 2-11 Power on Setting (S2) Function (17)Table 2-12 Power on Setting (S3) Function (17)Table 2-13 Power on Setting (S4) Function (17)Table 2-14 Power on Setting (S5) Function (17)Table 2-15 Power on Setting (S7/S6) Function (18)Table 2-16 Power on Setting (S9/S8) Function (18)Table 2-17 CMOS Sensor Connector (CON9) Function (19)Table 2-18 CAN_0 (SW9~10) Function (19)NUMAKER-HMI-N9H30 USER MANUAL1 OVERVIEWThe NuMaker-HMI-N9H30 is an evaluation board for GUI application development. The NuMaker-HMI-N9H30 consists of two parts: a NuMaker-N9H30 main board and a NuDesign-TFT-LCD7 extensionboard. The NuMaker-HMI-N9H30 is designed for project evaluation, prototype development andvalidation with HMI (Human Machine Interface) function.The NuMaker-HMI-N9H30 integrates touchscreen display, voice input/output, rich serial port serviceand I/O interface, providing multiple external storage methods.The NuDesign-TFT-LCD7 can be plugged into the main board via the DIN_32x2 extension connector.The NuDesign-TFT-LCD7 includes one 7” LCD which the resolution is 800x480 with RGB-24bits andembedded the 4-wires resistive type touch panel.Figure 1-1 Front View of NuMaker-HMI-N9H30 Evaluation BoardNUMAKER-HMI-N9H30 USER MANUAL Figure 1-2 Rear View of NuMaker-HMI-N9H30 Evaluation Board1.1 Features1.1.1 NuMaker-N9H30 Main Board Features●N9H30F61IEC chip: LQFP216 pin MCP package with DDR (64 MB)●SPI Flash using W25Q256JVEQ (32 MB) booting with quad mode or storage memory●NAND Flash using W29N01HVSINA (128 MB) booting or storage memory●One Micro-SD/TF card slot served either as a SD memory card for data storage or SDIO(Wi-Fi) device●Two sets of COM ports:–One DB9 RS-232 port with UART_0 used 75C3232E transceiver chip can be servedfor function debug and system development.–One DB9 RS-232 port with UART_2 used 75C3232E transceiver chip for userapplication●22 GPIO expansion ports, including seven sets of UART functions●JTAG interface provided for software development●Microphone input and Earphone/Speaker output with 24-bit stereo audio codec(NAU88C22) for I2S interfaces●Six sets of user-configurable push button keys●Three sets of LEDs for status indication●Provides SN65HVD230 transceiver chip for CAN bus communication●Provides MAX3485 transceiver chip for RS-485 device connection●One buzzer device for program applicationNUMAKER-HMI-N9H30 USER MANUAL●Two sets of RJ45 ports with Ethernet 10/100 Mbps MAC used IP101GR PHY chip●USB_0 that can be used as Device/HOST and USB_1 that can be used as HOSTsupports pen drives, keyboards, mouse and printers●Provides over-voltage and over current protection used APL3211A chip●Retain RTC battery socket for CR2032 type and ADC0 detect battery voltage●System power could be supplied by DC-5V adaptor or USB VBUS1.1.2 NuDesign-TFT-LCD7 Extension Board Features●7” resolution 800x480 4-wire resistive touch panel for 24-bits RGB888 interface●DIN_32x2 extension connector1.2 Supporting ResourcesFor sample codes and introduction about NuMaker-N9H30, please refer to N9H30 BSP:https:///products/gui-solution/gui-platform/numaker-hmi-n9h30/?group=Software&tab=2Visit NuForum for further discussion about the NuMaker-HMI-N9H30:/viewforum.php?f=31 NUMAKER-HMI-N9H30 USER MANUALNUMAKER-HMI-N9H30 USER MANUAL2 NUMAKER-HMI-N9H30 HARDWARE CONFIGURATION2.1 NuMaker-N9H30 Board － Front View Combination Connector (CON8)6 set User SWs (K1~6)3set Indication LEDs (LED1~3)Power Supply Switch (SW_POWER1)Audio Codec(U10)Microphone(M1)NAND Flash(U9)RS-232 Transceiver(U6, U12)RS-485 Transceiver(U11)CAN Transceiver (U13)Figure 2-1 Front View of NuMaker-N9H30 BoardFigure 2-1 shows the main components and connectors from the front side of NuMaker-N9H30 board. The following lists components and connectors from the front view:NuMaker-N9H30 board and NuDesign-TFT-LCD7 board combination connector (CON8). This panel connector supports 4-/5-wire resistive touch or capacitance touch panel for 24-bits RGB888 interface.Connector GPIO pin of N9H30 FunctionCON8.1 - Power 3.3VCON8.2 - Power 3.3VCON8.3 GPD7 LCD_CSCON8.4 GPH3 LCD_BLENCON8.5 GPG9 LCD_DENCON8.7 GPG7 LCD_HSYNCCON8.8 GPG6 LCD_CLKCON8.9 GPD15 LCD_D23(R7)CON8.10 GPD14 LCD_D22(R6)CON8.11 GPD13 LCD_D21(R5)CON8.12 GPD12 LCD_D20(R4)CON8.13 GPD11 LCD_D19(R3)CON8.14 GPD10 LCD_D18(R2)CON8.15 GPD9 LCD_D17(R1)CON8.16 GPD8 LCD_D16(R0)CON8.17 GPA15 LCD_D15(G7)CON8.18 GPA14 LCD_D14(G6)CON8.19 GPA13 LCD_D13(G5)CON8.20 GPA12 LCD_D12(G4)CON8.21 GPA11 LCD_D11(G3)CON8.22 GPA10 LCD_D10(G2)CON8.23 GPA9 LCD_D9(G1) NUMAKER-HMI-N9H30 USER MANUALCON8.24 GPA8 LCD_D8(G0)CON8.25 GPA7 LCD_D7(B7)CON8.26 GPA6 LCD_D6(B6)CON8.27 GPA5 LCD_D5(B5)CON8.28 GPA4 LCD_D4(B4)CON8.29 GPA3 LCD_D3(B3)CON8.30 GPA2 LCD_D2(B2)CON8.31 GPA1 LCD_D1(B1)CON8.32 GPA0 LCD_D0(B0)CON8.33 - -CON8.34 - -CON8.35 - -CON8.36 - -CON8.37 GPB2 LCD_PWMCON8.39 - VSSCON8.40 - VSSCON8.41 ADC7 XPCON8.42 ADC3 VsenCON8.43 ADC6 XMCON8.44 ADC4 YMCON8.45 - -CON8.46 ADC5 YPCON8.47 - VSSCON8.48 - VSSCON8.49 GPG0 I2C0_CCON8.50 GPG1 I2C0_DCON8.51 GPG5 TOUCH_INTCON8.52 - -CON8.53 - -CON8.54 - -CON8.55 - -NUMAKER-HMI-N9H30 USER MANUAL CON8.56 - -CON8.57 - -CON8.58 - -CON8.59 - VSSCON8.60 - VSSCON8.61 - -CON8.62 - -CON8.63 - Power 5VCON8.64 - Power 5VTable 2-1 LCD Panel Combination Connector (CON8) Pin Function●Power supply switch (SW_POWER1): System will be powered on if the SW_POWER1button is pressed●Three sets of indication LEDs:LED Color DescriptionsLED1 Red The system power will beterminated and LED1 lightingwhen the input voltage exceeds5.7V or the current exceeds 2A.LED2 Green Power normal state.LED3 Green Controlled by GPH2 pin Table 2-2 Three Sets of Indication LED Functions●Six sets of user SW, Key Matrix for user definitionKey GPIO pin of N9H30 FunctionK1 GPF10 Row0 GPB4 Col0K2 GPF10 Row0 GPB5 Col1K3 GPE15 Row1 GPB4 Col0K4 GPE15 Row1 GPB5 Col1K5 GPE14 Row2 GPB4 Col0K6GPE14 Row2GPB5 Col1 Table 2-3 Six Sets of User SW, Key Matrix Functions●NAND Flash (128 MB) with Winbond W29N01HVS1NA (U9)●Microphone (M1): Through Nuvoton NAU88C22 chip sound input●Audio CODEC chip (U10): Nuvoton NAU88C22 chip connected to N9H30 using I2Sinterface–SW6/SW7/SW8: 1-2 short for RS-485_6 function and connected to 2P terminal (CON5and J5)–SW6/SW7/SW8: 2-3 short for I2S function and connected to NAU88C22 (U10).●CMOS Sensor connector (CON10, SW9~10)–SW9~10: 1-2 short for CAN_0 function and connected to 2P terminal (CON11)–SW9~10: 2-3 short for CMOS sensor function and connected to CMOS sensorconnector (CON10)Connector GPIO pin of N9H30 FunctionCON10.1 - VSSCON10.2 - VSSNUMAKER-HMI-N9H30 USER MANUALCON10.3 - Power 3.3VCON10.4 - Power 3.3VCON10.5 - -CON10.6 - -CON10.7 GPI4 S_PCLKCON10.8 GPI3 S_CLKCON10.9 GPI8 S_D0CON10.10 GPI9 S_D1CON10.11 GPI10 S_D2CON10.12 GPI11 S_D3CON10.13 GPI12 S_D4CON10.14 GPI13 S_D5CON10.15 GPI14 S_D6CON10.16 GPI15 S_D7CON10.17 GPI6 S_VSYNCCON10.18 GPI5 S_HSYNCCON10.19 GPI0 S_PWDNNUMAKER-HMI-N9H30 USER MANUAL CON10.20 GPI7 S_nRSTCON10.21 GPG2 I2C1_CCON10.22 GPG3 I2C1_DCON10.23 - VSSCON10.24 - VSSTable 2-4 CMOS Sensor Connector (CON10) FunctionNUMAKER-HMI-N9H30 USER MANUAL2.2NuMaker-N9H30 Board － Rear View5V In (CON1)RS-232 DB9 (CON2,CON6)Expand Port (CON7)Speaker Output (J4)Earphone Output (CON4)Buzzer (BZ1)System ResetSW (SW5)SPI Flash (U7,U8)JTAG ICE (J2)Power ProtectionIC (U1)N9H30F61IEC (U5)Micro SD Slot (CON3)RJ45 (CON12, CON13)USB1 HOST (CON15)USB0 Device/Host (CON14)CAN_0 Terminal (CON11)CMOS Sensor Connector (CON9)Power On Setting(SW4, S2~S9)RS-485_6 Terminal (CON5)RTC Battery(BT1)RMII PHY (U14,U16)Figure 2-2 Rear View of NuMaker-N9H30 BoardFigure 2-2 shows the main components and connectors from the rear side of NuMaker-N9H30 board. The following lists components and connectors from the rear view:● +5V In (CON1): Power adaptor 5V input ●JTAG ICE interface (J2) ConnectorGPIO pin of N9H30Function J2.1 - Power 3.3V J2.2 GPJ4 nTRST J2.3 GPJ2 TDI J2.4 GPJ1 TMS J2.5 GPJ0 TCK J2.6 - VSS J2.7 GPJ3 TD0 J2.8-RESETTable 2-5 JTAG ICE Interface (J2) Function●SPI Flash (32 MB) with Winbond W25Q256JVEQ (U7); only one (U7 or U8) SPI Flashcan be used●System Reset (SW5): System will be reset if the SW5 button is pressed●Buzzer (BZ1): Control by GPB3 pin of N9H30●Speaker output (J4): Through the NAU88C22 chip sound output●Earphone output (CON4): Through the NAU88C22 chip sound output●Expand port for user use (CON7):Connector GPIO pin of N9H30 FunctionCON7.1 - Power 3.3VCON7.2 - Power 3.3VCON7.3 GPE12 UART3_TXDCON7.4 GPH4 UART1_TXDCON7.5 GPE13 UART3_RXDCON7.6 GPH5 UART1_RXDCON7.7 GPB0 UART5_TXDCON7.8 GPH6 UART1_RTSCON7.9 GPB1 UART5_RXDCON7.10 GPH7 UART1_CTSCON7.11 GPI1 UART7_TXDNUMAKER-HMI-N9H30 USER MANUAL CON7.12 GPH8 UART4_TXDCON7.13 GPI2 UART7_RXDCON7.14 GPH9 UART4_RXDCON7.15 - -CON7.16 GPH10 UART4_RTSCON7.17 - -CON7.18 GPH11 UART4_CTSCON7.19 - VSSCON7.20 - VSSCON7.21 GPB12 UART10_TXDCON7.22 GPH12 UART8_TXDCON7.23 GPB13 UART10_RXDCON7.24 GPH13 UART8_RXDCON7.25 GPB14 UART10_RTSCON7.26 GPH14 UART8_RTSCON7.27 GPB15 UART10_CTSCON7.28 GPH15 UART8_CTSCON7.29 - Power 5VCON7.30 - Power 5VTable 2-6 Expand Port (CON7) Function●UART0 selection (CON2, J3):–RS-232_0 function and connected to DB9 female (CON2) for debug message output.–GPE0/GPE1 connected to 2P terminal (J3).Connector GPIO pin of N9H30 Function J3.1 GPE1 UART0_RXDJ3.2 GPE0 UART0_TXDTable 2-7 UART0 (J3) Function●UART2 selection (CON6, J6):–RS-232_2 function and connected to DB9 female (CON6) for debug message output –GPF11~14 connected to 4P terminal (J6)Connector GPIO pin of N9H30 Function J6.1 GPF11 UART2_TXDJ6.2 GPF12 UART2_RXDJ6.3 GPF13 UART2_RTSJ6.4 GPF14 UART2_CTSTable 2-8 UART2 (J6) Function●RS-485_6 selection (CON5, J5, SW6~8):–SW6~8: 1-2 short for RS-485_6 function and connected to 2P terminal (CON5 and J5) –SW6~8: 2-3 short for I2S function and connected to NAU88C22 (U10)Connector GPIO pin of N9H30 FunctionSW6:1-2 shortGPG11 RS-485_6_DISW6:2-3 short I2S_DOSW7:1-2 shortGPG12 RS-485_6_ROSW7:2-3 short I2S_DISW8:1-2 shortGPG13 RS-485_6_ENBSW8:2-3 short I2S_BCLKNUMAKER-HMI-N9H30 USER MANUALTable 2-9 RS-485_6 (SW6~8) FunctionPower on setting (SW4, S2~9).SW State FunctionSW4.2/SW4.1 ON/ON Boot from USB SW4.2/SW4.1 ON/OFF Boot from eMMC SW4.2/SW4.1 OFF/ON Boot from NAND Flash SW4.2/SW4.1 OFF/OFF Boot from SPI Flash Table 2-10 Power on Setting (SW4) FunctionSW State FunctionS2 Short System clock from 12MHzcrystalS2 Open System clock from UPLL output Table 2-11 Power on Setting (S2) FunctionSW State FunctionS3 Short Watchdog Timer OFFS3 Open Watchdog Timer ON Table 2-12 Power on Setting (S3) FunctionSW State FunctionS4 Short GPJ[4:0] used as GPIO pinS4Open GPJ[4:0] used as JTAG ICEinterfaceTable 2-13 Power on Setting (S4) FunctionSW State FunctionS5 Short UART0 debug message ONS5 Open UART0 debug message OFFTable 2-14 Power on Setting (S5) FunctionSW State FunctionS7/S6 Short/Short NAND Flash page size 2KBS7/S6 Short/Open NAND Flash page size 4KBS7/S6 Open/Short NAND Flash page size 8KBNUMAKER-HMI-N9H30 USER MANUALS7/S6 Open/Open IgnoreTable 2-15 Power on Setting (S7/S6) FunctionSW State FunctionS9/S8 Short/Short NAND Flash ECC type BCH T12S9/S8 Short/Open NAND Flash ECC type BCH T15S9/S8 Open/Short NAND Flash ECC type BCH T24S9/S8 Open/Open IgnoreTable 2-16 Power on Setting (S9/S8) FunctionCMOS Sensor connector (CON9, SW9~10)–SW9~10: 1-2 short for CAN_0 function and connected to 2P terminal (CON11).–SW9~10: 2-3 short for CMOS sensor function and connected to CMOS sensorconnector (CON9).Connector GPIO pin of N9H30 FunctionCON9.1 - VSSCON9.2 - VSSCON9.3 - Power 3.3VCON9.4 - Power 3.3V NUMAKER-HMI-N9H30 USER MANUALCON9.5 - -CON9.6 - -CON9.7 GPI4 S_PCLKCON9.8 GPI3 S_CLKCON9.9 GPI8 S_D0CON9.10 GPI9 S_D1CON9.11 GPI10 S_D2CON9.12 GPI11 S_D3CON9.13 GPI12 S_D4CON9.14 GPI13 S_D5CON9.15 GPI14 S_D6CON9.16 GPI15 S_D7CON9.17 GPI6 S_VSYNCCON9.18 GPI5 S_HSYNCCON9.19 GPI0 S_PWDNCON9.20 GPI7 S_nRSTCON9.21 GPG2 I2C1_CCON9.22 GPG3 I2C1_DCON9.23 - VSSCON9.24 - VSSTable 2-17 CMOS Sensor Connector (CON9) Function●CAN_0 Selection (CON11, SW9~10):–SW9~10: 1-2 short for CAN_0 function and connected to 2P terminal (CON11) –SW9~10: 2-3 short for CMOS sensor function and connected to CMOS sensor connector (CON9, CON10)SW GPIO pin of N9H30 FunctionSW9:1-2 shortGPI3 CAN_0_RXDSW9:2-3 short S_CLKSW10:1-2 shortGPI4 CAN_0_TXDSW10:2-3 short S_PCLKTable 2-18 CAN_0 (SW9~10) Function●USB0 Device/HOST Micro-AB connector (CON14), where CON14 pin4 ID=1 is Device,ID=0 is HOST●USB1 for USB HOST with Type-A connector (CON15)●RJ45_0 connector with LED indicator (CON12), RMII PHY with IP101GR (U14)●RJ45_1 connector with LED indicator (CON13), RMII PHY with IP101GR (U16)●Micro-SD/TF card slot (CON3)●SOC CPU: Nuvoton N9H30F61IEC (U5)●Battery power for RTC 3.3V powered (BT1, J1), can detect voltage by ADC0●RTC power has 3 sources:–Share with 3.3V I/O power–Battery socket for CR2032 (BT1)–External connector (J1)●Board version 2.1NUMAKER-HMI-N9H30 USER MANUAL2.3 NuDesign-TFT-LCD7 －Front ViewFigure 2-3 Front View of NuDesign-TFT-LCD7 BoardFigure 2-3 shows the main components and connectors from the Front side of NuDesign-TFT-LCD7board.7” resolution 800x480 4-W resistive touch panel for 24-bits RGB888 interface2.4 NuDesign-TFT-LCD7 －Rear ViewFigure 2-4 Rear View of NuDesign-TFT-LCD7 BoardFigure 2-4 shows the main components and connectors from the rear side of NuDesign-TFT-LCD7board.NuMaker-N9H30 and NuDesign-TFT-LCD7 combination connector (CON1).NUMAKER-HMI-N9H30 USER MANUAL 2.5 NuMaker-N9H30 and NuDesign-TFT-LCD7 PCB PlacementFigure 2-5 Front View of NuMaker-N9H30 PCB PlacementFigure 2-6 Rear View of NuMaker-N9H30 PCB PlacementNUMAKER-HMI-N9H30 USER MANUALFigure 2-7 Front View of NuDesign-TFT-LCD7 PCB PlacementFigure 2-8 Rear View of NuDesign-TFT-LCD7 PCB Placement3 NUMAKER-N9H30 AND NUDESIGN-TFT-LCD7 SCHEMATICS3.1 NuMaker-N9H30 － GPIO List CircuitFigure 3-1 shows the N9H30F61IEC GPIO list circuit.Figure 3-1 GPIO List Circuit NUMAKER-HMI-N9H30 USER MANUAL3.2 NuMaker-N9H30 － System Block CircuitFigure 3-2 shows the System Block Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-2 System Block Circuit3.3 NuMaker-N9H30 － Power CircuitFigure 3-3 shows the Power Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-3 Power Circuit3.4 NuMaker-N9H30 － N9H30F61IEC CircuitFigure 3-4 shows the N9H30F61IEC Circuit.Figure 3-4 N9H30F61IEC CircuitNUMAKER-HMI-N9H30 USER MANUAL3.5 NuMaker-N9H30 － Setting, ICE, RS-232_0, Key CircuitFigure 3-5 shows the Setting, ICE, RS-232_0, Key Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-5 Setting, ICE, RS-232_0, Key Circuit3.6 NuMaker-N9H30 － Memory CircuitFigure 3-6 shows the Memory Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-6 Memory Circuit3.7 NuMaker-N9H30 － I2S, I2C_0, RS-485_6 CircuitFigure 3-7 shows the I2S, I2C_0, RS-486_6 Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-7 I2S, I2C_0, RS-486_6 Circuit3.8 NuMaker-N9H30 － RS-232_2 CircuitFigure 3-8 shows the RS-232_2 Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-8 RS-232_2 Circuit3.9 NuMaker-N9H30 － LCD CircuitFigure 3-9 shows the LCD Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-9 LCD Circuit3.10 NuMaker-N9H30 － CMOS Sensor, I2C_1, CAN_0 CircuitFigure 3-10 shows the CMOS Sensor,I2C_1, CAN_0 Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-10 CMOS Sensor, I2C_1, CAN_0 Circuit3.11 NuMaker-N9H30 － RMII_0_PF CircuitFigure 3-11 shows the RMII_0_RF Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-11 RMII_0_PF Circuit3.12 NuMaker-N9H30 － RMII_1_PE CircuitFigure 3-12 shows the RMII_1_PE Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-12 RMII_1_PE Circuit3.13 NuMaker-N9H30 － USB CircuitFigure 3-13 shows the USB Circuit.NUMAKER-HMI-N9H30 USER MANUALFigure 3-13 USB Circuit3.14 NuDesign-TFT-LCD7 － TFT-LCD7 CircuitFigure 3-14 shows the TFT-LCD7 Circuit.Figure 3-14 TFT-LCD7 CircuitNUMAKER-HMI-N9H30 USER MANUAL4 REVISION HISTORYDate Revision Description2022.03.24 1.00 Initial version NUMAKER-HMI-N9H30 USER MANUALNUMAKER-HMI-N9H30 USER MANUALImportant NoticeNuvoton Products are neither intended nor warranted for usage in systems or equipment, anymalfunction or failure of which may cause loss of human life, bodily injury or severe propertydamage. Such applications are deemed, “Insecure Usage”.Insecure usage includes, but is not limited to: equipment for surgical implementation, atomicenergy control instruments, airplane or spaceship instruments, the control or operation ofdynamic, brake or safety systems designed for vehicular use, traffic signal instruments, all typesof safety devices, and other applications intended to support or sustain life.All Insecure Usage shall be made at customer’s risk, and in the event that third parties lay claimsto Nuvoton as a result of customer’s Insecure Usage, custome r shall indemnify the damagesand liabilities thus incurred by Nuvoton.。
simplicity studio编译工程示例-概述说明以及解释
simplicity studio编译工程示例-概述说明以及解释1.引言1.1 概述Simplicity Studio是一种集成开发环境(IDE)，专门用于开发和调试Silicon Labs公司的嵌入式设备。
它为开发人员提供了一种便捷的工具，使他们可以通过一个用户友好的界面来编写、编译和调试应用程序。
Simplicity Studio具有一系列功能和特点，使它成为一个强大而又灵活的开发平台。
首先，它支持多种不同型号的Silicon Labs芯片，包括各种系列的32位ARM Cortex-M微控制器，蓝牙低能耗芯片以及无线射频设备。
这使得开发人员可以在同一个平台上开发各种类型的项目，而无需切换开发工具。
其次，Simplicity Studio提供了丰富的软件组件和例程库，用于简化开发流程。
这些组件和库覆盖了多个应用领域，包括物联网(IoT)、智能家居、工业自动化和医疗等。
开发人员可以利用这些现成的模块，快速构建出高质量的应用程序。
此外，Simplicity Studio还提供了一整套调试工具，方便开发人员进行代码调试和性能优化。
它支持多种调试接口，包括J-Link、USB DebugAdapter和CMSIS-DAP等。
开发人员可以通过这些接口实现源代码级别的调试，以及对系统资源的监视和分析。
总之，Simplicity Studio是一款功能丰富、易于使用的开发环境，旨在提高开发人员的工作效率和应用程序的质量。
它将硬件和软件开发工具紧密结合在一起，使开发人员能够快速构建出稳定可靠的嵌入式应用。
在下面的文章中，我们将以编译工程示例为例，介绍Simplicity Studio的具体用法和开发流程。
1.2文章结构1.2 文章结构本文将按照以下结构进行详细介绍Simplicity Studio的编译工程示例：2.1 简介Simplicity Studio2.1.1 功能和特点2.1.2 使用场景2.2 编译工程示例2.2.1 创建工程2.2.2 编译和调试3.结论3.1 总结3.2 使用建议在第一个部分中，我们将简要介绍Simplicity Studio的概述，并阐述本文的目的。
ESP Alchemist Version 5.2.1 SCC Client Interface 安
ESP Alchemist Version 5.2.1SCC Client InterfaceInstallation InstructionsInstalling Alchemist SCC InterfaceHardware and Software Requirements•ESP Alchemist 5.2.1•SCC-compliant IDE•Windows 98 and laterNote: ESP Alchemist SCC Interface was tested with Windows Visual Studio and IBM VisualAge for Java. Because IDEs may integrate SCC implementations differently, other SCC-compliant IDEs may not behave as documented.Installing the software from a CD-ROM4.Insert the ESP Alchemist CD into a CD drive.5.Follow the instructions in the installation wizard. See the ESP Alchemist SCCInterface Installation Parameters table below for installation details.Installing the software from the Cybermation web site1.Connect to your company’s portal on the Cybermation web site and navigate to theAlchemist installation location.2.Double-click on the setup.exe icon.3.Follow the instructions in the installation wizard. See the ESP Alchemist SCCInterface Installation Parameters table below for installation details. Uninstalling the software1.From the Start menu, select Settings > Control Panel > Add/Remove Programs.2.Select ESP Alchemist SCC Interface and click Change/Remove.3.Click OK to confirm that you want to uninstall the software, and follow theinstructions in the uninstallation wizard..ESP Alchemist SCC Interface Installation ParametersParameter DescriptionUserid The Alchemist user ID. It must have access toAlchemist libraries. It is not case sensitive.Zone Name The name of the Alchemist zone where you want tostore the source code.Alchemist IP Address or Domain Name The ESP Alchemist server IP address. The server IP address may be either in hostname or numeric format. It is defined in the Alchemist server.RMS Port The Request Manager Server port number. It isdefined in the Alchemist server.CXS Port The Component Export Server port number. It isdefined in the Alchemist server.Department Name The primary security group for the Alchemist userID. May be optional depending on your Alchemistserver configuration.Multiple Source-Code Control ProvidersIt is possible to have more than one SCC-compliant provider installed on your computer. When you install ESP Alchemist SCC, you can specify whether you want ESP Alchemistto be your default SCC provider. To change the default SCC, you must edit the Windows Registry file:1.In the Start menu, select Run...2.In the Open field, type regedit.3.Navigate to theHKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders key.4.This key lists string values for every SCC provider. Review to ensure that the ESPAlchemist entry is Software\Cybermation\Alchemist.5.Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProviderkey.6.The ProviderRegKey entry specifies the default SCC provider.•If you want Alchemist to be the default SCC provider, enterSoftware\Cybermation\Alchemist as the value of ProviderRegKey.•If you want to change the default SCC provider, enter the value of one of the other providers listed in the InstalledSCCProviders sub-key.7.In the Registry menu, select Exit to exit the Registry Editor.Additional DocumentationWhen you install ESP Alchemist SCC Interface, the ESP Alchemist SCC User’s Guide in Adobe Portable Document Format (PDF) is automatically installed. For additional Alchemist documentation, including ESP Alchemist Messages and Codes, you should install the ESP Alchemist 5.2.1 Online Documentation package, either from the ESP Alchemist Documentation CD or from your Cybermation customer portal web site.Trademark NoticesCybermation is a registered trademark of Cybermation Inc.Microsoft, Windows and Visual C++ are registered trademarks of Microsoft Corporation.IBM and VisualAge are registered trademarks of International Business Machines Corporation.Java is a trademark of Sun Microsystems, Inc.All other brand and product names are trademarks or registered trademarks of their respective companies.。
Autodesk Softimage 2011 Service Pack 1 (SP1) 说明书
The latest service pack for Autodesk® Softimage® 2011 software includes 130 fixes.Crosswalk 5.1Softimage 2011 SP1 ships with Crosswalk v.5.1.CoexistenceSoftimage 2011 SP1 is a full build and can co-exist with Softimage 2011. Softimage 2011 is not required to be uninstalled first. LicensingSoftimage 2011 SP1 uses the same license as Softimage 2011. When installing Softimage 2011 SP1:•Enter the product key 590C1 and your Softimage 2011 serial number, and then click Next.•If you have a Network license, click Configure to switch to the Network licensing method.DocumentationSoftimage 2011 SP1 includes full English and Japanese documentationThe full list of fixes is as follows:ModelingUDEV00255606 Crash while transforming boolean elementsUDEV00256310 Regression in Boolean behaviorUDEV00246940 Cannot see painted vertex colors after vertex color property modified by another toolUDEV00247045 ClusterProperties do not resize properly on topo change if a CustomOperator are set to the texture projection UDEV00257973 extreme lag when moving pivot using alt key in scale modeUDEV00257773 Boolean operation crashes SoftimageData managementUDEV00257530 Cache Manager - Adding a cache to an object that has an Audio Clip returns an errorUDEV00257308 Cache Manager - Write - Branch select is not considered in Multiple selectionUDEV00257307 Cache Manager - Write - When Attribute list is empty selected attributes stay identicalUDEV00256625 Cache Manager - Write - "Attributes" list doesn't clearly display which attributes is stored for each object UDEV00256623 Cache Manager - Spaced out the numbers preceding the object names in the object listsUDEV00257172 Cache Manager - *.cacheslist should not be default file extension for the read cache browserUDEV00257169 Caching Save Cache to Mixer button create an unused imageclipUDEV00255923 ReadAnimationCache - Can add badly formed path sequenceUDEV00256620 Cache Manager - Write - been able to select a group or hierarchy (in branch) and add the contents to the list UDEV00257539 [CER] Refmodels - Crash with Scene explorer OpenUDEV00257564 [CER] Crash when testing the Displacement Ocean shader node.UDEV00257278 Put a PointCloud on a RefModel, do some color modifs. then update the RefModel -> Simulation is wrong UDEV00257310 CRASH when undoing delete model ( specific )UDEV00257231 Refmodel we cannot export a ref model’s delta in the current project.UDEV00257346 The "Models to Reconnect To" parameter of RefModel not working with multiple models targetsUDEV00257362 Crash when adding CustomPSet to offloaded RefModelUDEV00257180 New Layer or Partition configuration is not persisted with Reference Model objectsUDEV00257688 Texture Layers ports are disconnected when loading an older scene in Softimage 2011CrosswalkUDEV00257368 FBX - imported file from previous version of the format has mesh facetedUDEV00257166 XSI Crosswalk FBX export hard/soft edge problemUDEV00257951 FBX - Linux - Crash importing using HardEdges EnableUDEV00257726 FBX - Crash importing Shape AnimationUDEV00257715 Crosswalk needs to increment to version 5.1Face RobotUDEV00256437 FaceRobot > Assemble doesn't work on Korean LocaleUDEV00257200 FR Script Error pop when doing Clear Fast Playback CacheCompositingUDEV00257358 Fx : plug-in operators are missingUIUDEV00257149 Hang with scene searchUDEV00257519 Crash when editing new LayoutUDEV00257483 Regression - unable to dolly when looking through a spot light without an interest constraintUDEV00257217 Regression from 2010 | items missing in the Modify texture menuUDEV00257374 Softimage does not display proper texture in VM when user changes texture imageclip in an override property. UDEV00255873 memo cam causes XSI to crash ( scene specific )UDEV00257651 Default character models' Keyable Params and Key Sets are not correctRenderingUDEV00257657 Shader preset manager mixes up shaders and class IDs when you have SPDL custom shaders in a workgroup UDEV00258079 Custom realtime shaders does not load in SP1UDEV00257908 Crash | ICE cache files with Motion Blur CrashUDEV00257618 Regression - ICE volume rendering - Particle_Gradient_FCurve is not workingUDEV00257208 Enable to load a volume shader in Mental RayUDEV00257507 Crash when rendering an ICE TreeUDEV00257677 Changes to pass shader parameters force the renderer cache to emptyUDEV00257621 invert flag in texture layer editor does not get set in 2011 from 2010 resulting in different rendered result UDEV00257499 Regression: Crash when using Render Region with "Toon Paint and Host"UDEV00257315 Crash when selecting a clip if the rendertree is activeUDEV00257216 Setting frost samples to 1 produces artifactsUDEV00256792 RTS | Ultimap_Preview node logs SiWarning upon creationUDEV00246516 Exporting Shader Compounds Loses Japanese StringsUDEV00257573 CgFx Shader - Crash Loading specific ShaderUDEV00257207 DirectX Viewport freeze after Screen saver when "On resume, display logon screen" is enableUDEV00257610 Crash when setting Photometric cd/m^2 Factor to zeroUDEV00257606 Display problem with the Projection Lookup NodeUDEV00257425 There is no "SimpleShader_CGFX.scn"UDEV00257271 python stops working correctly when I use xsibatchUDEV00257114 Fast Light Effects - Projected texture flips as you move/animate the light interestUDEV00257254 Editable option in the ShaderCompound properties doesn't anymoreUDEV00257292 multiple camera groups aren't picked up inside modelsUDEV00257677 Changes to pass shader parameters force the renderer cache to emptyUDEV00257571 [CER ] 36427081 | race condition on render cleanup/restart which can lead to a crashUDEV00257572 [CER] Crash when viewing lightmap previewUDEV00257825 32-bit Softimage does not load shaders from "nt-x86" folder of workgroup addonsUDEV00257319 Crash when switching from mib_photmetric with profile to mia_photometricUDEV00255527 Shaders disappear after changing workgroupUDEV00257882 Rendering | Pointcloud is not reading attributes being used by the clipUDEV00257204 Crash when rendering standins and scrubbing the time lineUDEV00257418 Crash: Render region with standins and GIUDEV00257734 Crash when Rendering StandinUDEV00255524 Problems when loading shaders from Plugin ManagerUDEV00254446 Material overrides only works with the first layerUDEV00257781 Camera Lens Shader Items are duplicated each time you undo a camera movementUDEV00257874 Crash changing flow texture color with render region openUDEV00257807 Rendering | Black renders when 2 shaders classes uses the same DLL/shaderUDEV00257743 Softimage hangs indefinitely loading a scene containing shaders which are not installed.UDEV00257771 CER | 37267480 | Crash when changing hair strands with preview render window openUDEV00257236 Satellite rendering is not properly opening up a connection with SoftimageSDK/ScriptingUDEV00257972 SDK ICE: CIndexSet iterator not initializing properlyUDEV00257954 SDK ICE: ICENode.ExposedPorts[0] drills down through all compounds (SDK)UDEV00257953 SDK ICE: ICE Port Dirty States Not Working with Multiphase/Element Generator NodeUDEV00258113 ICEAttribute::IsDefined() always returns trueUDEV00257533 SDK ICE: Few problems with ICE nodesUDEV00256186 XSIApplication.ActiveToolName doesn't return the precise BrushTool mode when using PaintVertexColorTool UDEV00257626 XSI::ClusterProperty::GetValues() crashes Softimage when querying an EnvelopeWeight property for values UDEV00256436 Folded Lines of code not displayed in script editorUDEV00256968 RefGuide: ClusterProperty.Elements.1.vbs Example - for loop index variable is wrong, and script doesn't work. UDEV00257745 SDK Command: XSI.Application cannot access XSI commands not created by the FrameworkSimulationUDEV00258051 RBD | Freeze loading a specific sceneUDEV00257925 RBD | 2010 Client Scene Crash on load in Softimage 2011UDEV00258112 ICE-RBD | Wrong default values for static, dynamic and elasticity coefficientsUDEV00257701 ICE | Crash renaming Set Data nodeUDEV00257506 ICE | crash duplicating bone with ICE tree that sets length (branch connection)UDEV00257642 ICE | Kinematics workgroup : fixed compounds and new sample sceneUDEV00256992 ICE |connecting to texture_projection_def brokenUDEV00257613 Regression - unable to write to a custom param from ICE treeUDEV00257598 ICE-RBD | Angular velocity is clamped at ± PI rad/sUDEV00257432 ICE particles - alpha blended point sprites not depth sorted properlyUDEV00257403 ICE | Crash! Create an ICE graph then put one of the object in a ModelUDEV00257369 ICE | GetData chaining invalidation issuesUDEV00257417 ICE | Graph is not updated when CopyPaste ICE TreeUDEV00257153 selecting the weightmap name rather than the .weights in 'Filter by Weightmap' ICE compound causes crash UDEV00256913 cannot create symmetry mapping templates if deformer's kine is ice drivenUDEV00256099 ICE-Kine | Crash when relocating ICE operator in stack.UDEV00256432 ICE | Sometimes the graph is invalidated when dragging some nodes on it.UDEV00255965 ICE | Tree does not reconnect after save and reloadUDEV00257279 ICE | kinematics : compound needs updateUDEV00257132 ICE | Crash when deleting Scalar ICE node under certain conditionsUDEV00257496 Cannot set implicit bone's length attribute using this.lengthUDEV00257946 ICE | Crash when deleting Compound after exporting privateUDEV00257864 ICE AngularVelocity rotation is inversedUDEV00257751 ICE Cache crash when loading point locator attributesUDEV00257752 ICE Cache | Unable to cache persistable attributesUDEV00257833 XSI can crash while connecting ICE nodesUDEV00257404 ICE | Tree not evaluated correctly after writing to custom parameterUDEV00257753 ICE | Negative zeros can be displayedUDEV00258260 Multi-phase Ice Node Fails to ExecuteLinuxUDEV00256388 I can't run 2011on FC12UDEV00257201 LINUX | No Icons visible on the Essential Skills videos pageUDEV00257094 LINUX | Audio defects when scrubbing or playing frame by frameUDEV00257094 Linux : Now using OpenAL for Audio (resolves issue when scrubbing or playing frame-by-frame)Tools /SetupUDEV00257631 JA localization: Japanese character truncated for Help > About Autodesk Softimage > Build Version (UI) UDEV00257240 XSI crashes when starting from command line with a scene parameterUDEV00257965 Essential movies don't open from NetviewUDEV00257964 Windows7 | 64-Bit | Scripting engine would fail to initialize on certain W7 systems causing a crash on startup UDEV00257775 CER call stacks for 64-bit systems are often corrupt or incorrectDocumentationUDEV00254555 RefGuide: SITransformation.AddLocalRotation > in_bIncrementEulerAngles arg info is missing in the SDK Guide UDEV00254399 RefGuide: The example for AddVertexColor is badly indentedUDEV00249925 SDK Doc: ArrayParameter not shown in Parameter pageUDEV00245887 missing HW shaders exampleUDEV00257126 Japanese Softimage Guide : translation incorrect in "Working with OpenEXR HDR Images in the Fx Tree"。
Intel Ethernet Fabric Suite软件发布说明（版本11.0.0.0 Rev.
Intel® Ethernet Fabric Suite SoftwareRelease Notes for 11.0.0.0Rev. 1.0March 2021Doc. No.: 637962, Rev.: 1.0You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein.No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.All product plans and roadmaps are subject to change without notice.The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.Intel technologies may require enabled hardware, software or service activation.No product or component can be absolutely secure.Your costs and results may vary.Intel, the Intel logo, and other Intel marks are trademarks of Intel Corporation or its subsidiaries. Other names and brands may be claimed as the property of others.Copyright © 2021, Intel Corporation. All rights reserved.Intel® Ethernet Fabric Suite SoftwareRelease Notes for 11.0.0.0March 2021 2Doc. No.: 637962, Rev.: 1.0Contents1.0 Overview of the Release (5)1.1 Audience...............................................................................................................51.2 Software License Agreement....................................................................................51.3 If You Need Help....................................................................................................51.4 Release Packages...................................................................................................51.5 Intel Hardware.......................................................................................................61.6 Operating Systems.................................................................................................61.7 Kernel Modules for Rendezvous Driver.......................................................................71.8 Network File Systems..............................................................................................71.9 MPI Libraries. (8)1.9.1 Supported MPI Libraries...............................................................................81.9.2 Compiler Versions and Distributions.. (9)1.10 Document Versions...............................................................................................91.11 Installation Requirements.. (9)1.11.1 Best Practices...........................................................................................91.11.2 Software and Firmware Requirements..........................................................91.11.3 OS RPMs Installation Prerequisites.............................................................101.11.4 Installation Instructions (11)2.0 Issues (13)2.1 Open Issues (13)2.1.1 Third Party Open Issues (15)3.0 Related Information (16)3.1 Intel ® Ethernet Fabric Suite Documentation Library (16)3.1.1 How to Search the Intel ® Ethernet Fabric Suite Documentation Set (16)Contents—Intel ® Ethernet FabricIntel ® Ethernet Fabric Suite SoftwareMarch 2021Release Notes for 11.0.0.0Doc. No.: 637962, Rev.: 1.03Tables1Supported Hardware..................................................................................................62Supported Operating Systems.....................................................................................63Supported OS by CPU................................................................................................74Kernel Modules for Rendezvous Driver..........................................................................75Supported MPI Libraries.............................................................................................86Compiler Versions and Distributions.............................................................................97Supported Document Versions....................................................................................98RHEL* 7.x, 8.x Distribution RPMs...............................................................................109SLES* 15.x Distribution RPMs...................................................................................1110Open Issues (1311)Third Party Open Issues (15)Intel ® Ethernet Fabric—TablesIntel ® Ethernet Fabric Suite Software Release Notes for 11.0.0.0March 20214Doc. No.: 637962, Rev.: 1.01.0 Overview of the ReleaseThis document provides a brief overview of the changes introduced into the Intel ®Ethernet Fabric Suite Software by this release. References to more detailedinformation are provided where necessary. The information contained in this document is intended as supplemental information only; it should be used in conjunction with the documentation provided for each component.These Release Notes list the features supported in this software release, open issues,and issues that were resolved during release development.AudienceThe information provided in this document is intended for installers, software support engineers, service personnel, and system administrators.Software License AgreementThis software is provided under license agreements and may contain third-partysoftware under separate third-party licensing. Please refer to the license files provided with the software for specific details.If You Need HelpTechnical support for Intel ® Ethernet Fabric Suite products is available 24 hours a day,365 days a year . Please contact Intel Customer Support or your Intel representative.Release PackagesThere are two Intel ® Ethernet Fabric Software packages:•Basic for compute, service, and login nodes•Intel Ethernet Fabric Suite (IEFS) for management nodesThe Basic package includes:•Software that installs the following packages :—kernel rendezvous module for scalable optimized large message transfers with PSM3.—PSM3 OFI (libfabric) provider: libpsm3-fi—Open MPI. See MPI Libraries on page 8 for details.—Intel Ethernet basic administration tools for use on all cluster nodes. Also required for full FastFabric functionality administering the node.The IEFS package includes the Basic package plus:1.1 1.2 1.3 1.4Overview of the Release—Intel ® Ethernet FabricIntel ® Ethernet Fabric Suite SoftwareMarch 2021Release Notes for 11.0.0.0Doc. No.: 637962, Rev.: 1.05•FastFabric Toolset, which enables rapid, consistent installation and configuration of Intel ® EFS host software and management software tools, as well as simplified installation, configuration, validation, and optimization of HPC fabrics.Intel HardwareThe following table lists the Intel hardware supported in this release. The table does not include OEM-specific hardware, such as custom adapters and switches.NOTEThe Intel ® PSM3 implementation has a limit of 32 NICs per node.Table 1.Supported HardwareHardwareDescriptionIntel ® Xeon ® Scalable ProcessorsSkylake CPU-based servers 2nd Generation Intel ® Xeon ® Scalable Processors Cascade Lake CPU-based servers 3nd Generation Intel ® Xeon ® Scalable Processors Ice Lake CPU-based servers Intel ® Ethernet 800 Series PCIe Adapter100 GbE PCIe adapterOperating SystemsThis release of the Intel ® Ethernet Fabric Suite Software supports the operating systems listed in the following table.Table 2.Supported Operating SystemsOperating SystemUpdate/SP Base Kernel Version Red Hat* Enterprise Linux* (RHEL*) 7.9 X86_64Update 93.10.0-1160.el7.x86_64Red Hat* Enterprise Linux* (RHEL*) 8.1 X86_64Update 14.18.0-147.el8.x86_64Red Hat* Enterprise Linux* (RHEL*) 8.2 X86_64Update 2 4.18.0-193.el8.x86_64Red Hat* Enterprise Linux* (RHEL*) 8.3 X86_64Update 3 4.18.0-240.el8.x86_64CentOS*-7 (2009) X86_64 (corresponds to RHEL* 7.9)(2009) 3.10.0-1160.el7.x86_64CentOS*-8 (1911) X86_64 (corresponds to RHEL* 8.1)(1911) 4.18.0-147.el8.x86_64CentOS*-8 (2004) X86_64 (corresponds to RHEL* 8.2)(2004) 4.18.0-193.el8.x86_64CentOS*-8 (2011) X86_64 (corresponds to RHEL* 8.3)(2011) 4.18.0-240.el8.x86_64SUSE* Linux* Enterprise Server (SLES*) 15.1 X86_64Service Pack 1 4.12.14-195_default SUSE* Linux* Enterprise Server (SLES*) 15.2 X86_64Service Pack 25.3.18-22-default1.5 1.6 Intel ® Ethernet Fabric—Overview of the ReleaseIntel ® Ethernet Fabric Suite Software Release Notes for 11.0.0.0March 20216Doc. No.: 637962, Rev.: 1.0Table 3.Supported OS by CPUCPU TypeRHEL *SLES *7.98.18.28.315.115.2Intel ® Xeon ® Scalable Processors (Skylake CPU-based servers)●●●●●●2nd Generation Intel ® Xeon ® Scalable Processors (codename Cascade Lake)●●●●●●3nd Generation Intel ® Xeon ® Scalable Processors (codename Ice Lake)●●CPU TypeCentO S*72009819118200482011Intel ® Xeon ® Scalable Processors (Skylake CPU-based servers)●●●●2nd Generation Intel ® Xeon ® Scalable Processors (codename Cascade Lake)●●●●3nd Generation Intel ® Xeon ® Scalable Processors (codename Ice Lake)●Kernel Modules for Rendezvous DriverThis release of the Intel ® Ethernet Fabric Suite Software contains the rendezvous driver kernel modules listed in the following table.NOTEThe version number is shown in bold.Table 4.Kernel Modules for Rendezvous DriverOSRPM VersionRHEL* 7.9kmod-iefs-kernel-updates-3.10.0_1160.el8.x86_64-6091.x86_64.rpm RHEL* 8.1kmod-iefs-kernel-updates-4.18.0_147.el8.x86_64-6091.x86_64.rpm RHEL* 8.2kmod-iefs-kernel-updates-4.18.0_193.el8.x86_64-6091.x86_64.rpm RHEL* 8.3kmod-iefs-kernel-updates-4.18.0_240.el8.x86_64-6091.x86_64.rpm SLES* 15.1iefs-kernel-updates-kmp-default-4.12.14_195_default_k4.12.14_195-6091.x86_64.rpmSLES* 15.2iefs-kernel-updates-kmp-default-5.3.18_22_default_k5.3.18_22- 6091.x86_64.rpmNetwork File SystemsThis section reports the network file systems that have been tested with this release of the Intel ® Ethernet Fabric Suite Software. Note that not all combinations of OS, file system, and Intel ® EFS software are tested.The following parallel file systems have been validated:1.7 1.8 Overview of the Release—Intel ® Ethernet FabricIntel ® Ethernet Fabric Suite SoftwareMarch 2021Release Notes for 11.0.0.0Doc. No.: 637962, Rev.: 1.07•IBM* Spectrum Scale 1:—Version 5.0.5.0 on RHEL* 8.1, SLES* 15.1, and SLES* 15.2•BeeGFS 7.1Additionally, in-distro NFS capability for the supported distros has also been validated.MPI LibrariesNOTEThe binary and sources for Open MPI are included in the software package. Thebinaries are built using the GCC compiler . FastFabric provides a simple tool to rebuild this MPI library using either the GCC compiler or the Intel ® Compiler (not included in the software package). Refer to Intel ® Ethernet Fabric Suite FastFabric User Guide ,Rebuilding MPI Library and Tools.NOTEIntel recommends that you run the Intel ® MPI mpivars.sh script when using Intel ®MPI with Intel ® EFS and OFI (libfabric).If you are not using Intel ® MPI with Intel ® EFS and OFI, do not run this script.NOTEThis release of IEFS has only been validated against the in-distro versions of libfabric and the version of libfabric included with Intel MPI Library 2019, Update 10..Supported MPI LibrariesThe table below lists the different MPI libraries supported by Intel ® Ethernet Fabric Software with the corresponding version, fabric support, and compiler used. Note that the second column indicates if the MPI library is included in the Intel ® Ethernet Fabric Suite Software package.Table 5.Supported MPI LibrariesMPI ImplementationIncluded in BasicPackage?Runs Over Compiled With Open MPI 4.0.5YesPSM3 (via OFI)GCC orIntel ® Compiler Intel ®MPI Library 2019, Update 10No PSM3 (via OFI)Intel ® CompilerIntel ® MPI Library 2019, Update 10 is recommended to be used with IEFS. It can be obtained via the following URL (with proper credentials): https:///akdlm/irc_nas/17534/l_mpi_2019.10.317.tgz1.9 1.9.1 1Formerly known as General Parallel File System (GPFS)Intel ® Ethernet Fabric—Overview of the ReleaseIntel ® Ethernet Fabric Suite Software Release Notes for 11.0.0.0March 20218Doc. No.: 637962, Rev.: 1.0Compiler Versions and DistributionsThe Open MPI libraries that are included in the release, and built with OFI/PSM3support, were built with the following compiler versions:Table piler Versions and DistributionsCompiler OS DistributionCompiler Version(GNU) gcc RHEL* 7.9gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)(GNU) gcc RHEL* 8.1gcc version 8.3.1 20190507 (Red Hat* 8.3.1-4)(GNU) gcc RHEL* 8.2gcc version 8.3.1 20191121 (Red Hat* 8.3.1-5)(GNU) gcc RHEL* 8.3gcc version 8.3.1 20191121 (Red Hat* 8.3.1-5)(GNU) gcc SLES* 15 SP1gcc version 7.4.1 20190424 [gcc-7-branch revision 270538] (SUSE*Linux*)(GNU) gccSLES* 15 SP2gcc version 7.5.0 (SUSE Linux)Document VersionsThe following table lists the end user document versions supported by this release.Table 7.Supported Document VersionsTitleDoc. NumberRevisionIntel ® Ethernet Fabric Suite Software Installation Guide 632484 1.0Intel ® Ethernet Fabric Suite Host Software User Guide 632489 1.0Intel ® Ethernet Fabric Suite FastFabric User Guide 632487 1.0Intel ® Ethernet Fabric Performance Tuning Guide 632488 1.0Intel ® Ethernet Fabric Suite Software Release Notes6350911.0Related LinksIntel Ethernet Fabric Suite Documentation Library on page 16Installation RequirementsThis section provides installation requirements for this release.Best Practices•Intel recommends that users update to the latest versions of Intel ® Ethernet Fabric Suite software to obtain the most recent functional and security updates.•To improve security, the administrator should log out users and disable multi-user logins prior to performing provisioning and similar tasks.Software and Firmware RequirementsTable 2 on page 6 lists the operating systems supported by this release. For the required packages, refer to OS RPMs Installation Prerequisites .1.9.2 1.101.11 1.11.1 1.11.2 Overview of the Release—Intel ® Ethernet FabricIntel ® Ethernet Fabric Suite SoftwareMarch 2021Release Notes for 11.0.0.0Doc. No.: 637962, Rev.: 1.09OS RPMs Installation PrerequisitesEnsure that the following requirements are met prior to installing the software.•In addition to normal OS installation options, OS RPMs must be installed before you can install the Intel ® Ethernet Fabric Suite software.•Refer to the applicable section below to verify that all required RPMs are installed for the specific version of your OS distribution.•Depending on the packages you choose, there may be additional prerequisites. For additional information, refer to the Release Notes for your specific release and installation type.Red Hat* Enterprise Linux* OS RPMsThe tables below list the RPMs for each supported RHEL* release.NOTESome RHEL* rpms are available in a Server-Optional repository. Please install the RHEL* Server-Optional version from Red Hat* which contains additional, required development packages.Table 8.RHEL* 7.x, 8.x Distribution RPMsEthernet CentricSystem CentricOther/GenerallyInstalledBuild Requirements libibverbs atlas libstdc++-devel bash autoconf librdmacm bc ncurses-compat-libskernelautomake rdma-core coreutils ncurses-libs kernel-modules-extra bisonrdma-core-devel createrepo numactl-libs kmod elfutils-libelf-devel libfabric (1.8 or higher)expat openssl libgcc expat-devel E810 drivers (ice andirdma)expect openssl-devel perlflexgcc-gfortranopenssl-libs perl-Getopt-Long gcc-c++.x86_64glibc pciutils perl-Socket kernel-abi-whitelists kernel-devel redhat-rpm-configpkgconf kernel-rpm-macros libatomic rpm-build python2libfabric-devel (1.8 or higher)libgfortran sysfsutilssystemdlibnl3-devel libgomp tcl libpfm libquadmath tcsh libtool libstdc++zliblibuuid-devel ncurses-devel numactl-developenssl-devel (1.1.1 or higher)tcl-devel1.11.3 Intel ® Ethernet Fabric—Overview of the ReleaseIntel ® Ethernet Fabric Suite Software Release Notes for 11.0.0.0March 202110Doc. No.: 637962, Rev.: 1.0SUSE* Linux* Enterprise Server OS RPMsThe tables below list the RPMs for each supported SLES* release.NOTESome SLES* rpms are available in SLES* Software Development Kit (SDK). Please install the SLES* SDK iso from SUSE* which contains additional, required development packages.Table 9.SLES* 15.x Distribution RPMsEthernet CentricSystem Centric Other/GenerallyInstalledBuild Requirementslibverbs1bc libnuma1bash bison librdmacm1coreutils libopenssl1_1glibc flex rdma-core createrepo_clibopenssl-devel grep kernel-devel rdma-core-devel expect libosmcomp3irqbalance libexpat-devel libfabric (1.8 or higher)gcc-fortranlibquadmath0kmod libnuma-devel E810 drivers (ice andirdma)kernel-devel libudev-devellibedit0libopenssl-devel (1.0.1or higher)kernel-syms libz1libgcc_s1libuuid-devel libatomic1openssl libstdc++6ncurses-devel libexpat1rpm-buildperl tcl-devel libgfortran4tcl perl-base valgrind-devel libgomp1tcshpkg-config libfabric-devel (1.8 orhigher)libncurses6python-base systemd udevExampleThe example below shows how to install a group of OS RPMs on a RHEL* OS server .Not all required OS RPMs are included in this example and some OS RPMs in this example might not be needed.# yum install qperf perftest rdma expat libstdc++-devel gcc-gfortran atlas tcl expect tcsh sysfsutils pciutils bc libibverbs-devel librdmacm-devel ibacm-devel openssl-devel libuuid-devel expatdevel valgrind-devel libgnome libibverbs*ncurses-devel hwloc hwloc-guiIntel recommends that you build your own list of OS RPMs for installation.Installation InstructionsThere are two Intel ® Ethernet Fabric Software packages:•IntelEth-FS.<distro >-x86_64.<version >.tgz for the management node.1.11.4 Overview of the Release—Intel ® Ethernet Fabric•IntelEth-Basic.<distro >-x86_64.<version >.tgz for compute, service,and login nodes.The packages in the tgz file are RPMs. Installing individual RPMs is not supported in this release.Refer to the Intel ® Ethernet Fabric Suite Software Installation Guide for related software requirements and complete installation procedures.Intel ® Ethernet Fabric—Overview of the Release2.0 IssuesThis section lists the resolved and open issues in the Intel ® Ethernet Fabric Suite Software.Open IssuesThe following table lists the open issues for this release.Table 10.Open Issues2.1Issues—Intel ® Ethernet FabricIntel® Ethernet Fabric—IssuesID Description WorkaroundHED-1482When running ethfabricinfo directly or viaethfastfabric the "Summary of FabricComponents" fails, ethfabricinfo reports itcannot find the configuration file /etc/eth-tools/mgt_config.conf.Copy /etc/eth-tools/mgt_config.xml to /etc/eth-tools/mgt_config.conf and maintain both files so they are identical.HED-1484On some systems, when running Perform Single Host Verification via ethfastfabric, The hostverify toolreports a timeout.When prompted, select a timeout of 2 minutes or more.HED-1485Various fastfabric operations may fail. Most obvious is when running Perform Single Host Verification viaethfastfabric, The hostverify tool reports snmpget isnot found.On RHEL and Centos systems, install net-snmp-utilson all nodes which will run fastfabric.Third Party Open IssuesThe following table lists the third party open issues for this release. Table 11.Third Party Open IssuesID Description WorkaroundHED-87 Whamcloud LU-13976Lustre is not supported on Intel® Ethernet 800 SeriesPCIe AdapterNo workaround at this time.HED-1286In upstream and other distributions of OpenMPIMPI_Ssend and MPI_Issend do not work properly.As a result, additional 0-length messages may bepresented to the MPI application.The OpenMPI distributed in IEFS includes the fix for this. If using other versions of OpenMPI, ensure the upstream patch(18baa5e291623169b5c85e3df7e35906a559bb4e) is present.2.1.1Issues—Intel® Ethernet Fabric3.0Related InformationIntel ® Ethernet Fabric Suite Documentation LibraryIntel ® Ethernet Fabric Suite publications are available at the following URL:https:///content/www/us/en/design/products-and-solutions/networking-and-io/high-performance-networking/technical-library.htmlUse the tasks listed in this table to find the corresponding Intel ® Ethernet Fabric Suite document.TaskDocument TitleDescriptionInstalling host softwareInstalling NIC firmwareIntel ® Ethernet Fabric Suite Software Installation GuideDescribes using a Text-based User Interface (TUI) to guide you through the installation process. You have the option of using command line interface (CLI) commands to perform the installation or install using the Linux* distribution software.Managing a fabric using FastFabricIntel ®Ethernet Fabric Suite FastFabric User GuideProvides instructions for using the set of fabric management tools designed to simplify and optimize common fabricmanagement tasks. The management tools consist of Text-based User Interface (TUI) menus and command line interface (CLI) commands.Running MPI applications on Intel ® EFSRunning middleware that uses Intel ® EFSIntel ® Ethernet Fabric Suite Host Software User GuideDescribes how to set up and administer the Network Interface Card (NIC) after the software has been installed and provides a reference for users working with Intel ® PSM3. Performance Scaled Messaging 3 (PSM3) is an Open Fabrics Interface (OFI,aka libfabric) provider which implements an optimized user-level communications protocol. The audience for thisdocument includes cluster administrators and those running or implementing Message-Passing Interface (MPI) programs.Optimizing system performance Intel ® Ethernet Fabric Performance Tuning GuideDescribes BIOS settings and parameters that have been shown to ensure best performance, or make performance more consistent, on Intel ® Ethernet Fabric Suite Software. If you are interested in benchmarking the performance of your system, these tips may help you obtain better performance.Learning about new release features,open issues, and resolved issues for a particular releaseIntel ® Ethernet Fabric Suite Software Release NotesHow to Search the Intel ® Ethernet Fabric Suite Documentation SetMany PDF readers, such as Adobe* Reader and Foxit* Reader , allow you to search across multiple PDFs in a folder .Follow these steps:1.Download and unzip all the Intel ® Ethernet Fabric Suite PDFs into a single folder .3.13.1.1Intel ® Ethernet Fabric—Related Information2.Open your PDF reader and use CTRL-SHIFT-F to open the Advanced Search window.3.Select All PDF documents in...4.Select Browse for Location in the dropdown menu and navigate to the folder containing the PDFs.5.Enter the string you are looking for and click Search .Use advanced features to further refine your search criteria. Refer to your PDF reader Help for details.Related Information—Intel ® Ethernet Fabric。
Program Protection Manual for the C-64 Volume II说明
arsenic to
make n-channel transistors in p-type substrates.
N-channel ICs have channels which are composed of negatively
charged carriers. CMOS or Complementary MOS ICs utilize both p-channel
P-suesTIIATE
IPf'OIII CELL
IIpMlM Cl!LL
PPMII READ ONLY MEMORY PAGE 255
...
"~r;.'000'"
I, .~I
L"'':"C~ES II
I I I
I
I I I
I
I
I
I
I
'EJ
I DATA
f < J .~F.O.
N-SUBSTRATE
PMOS P-CHANNEL OEVICE GATE
GATE . 'O,~, ¢q ,~,
. "-'.,L M'.d-k ~ P . A'"''
__""'+~
I
....' P.. . I '---'------' . I I ""m )
I I ::"u,"", CMOS
and n-channel devices on a common substrate. Either p-or n-type substrates can be used, but areas of the opposite substrate (wells) must be present to create the complementary transistor type.
V2426 Windows Embedded Standard 7用户手册（第一版）2013年12月
V2426 Windows Embedded Standard 7User’s ManualFirst Edition, December 2013/product© 2013 Moxa Inc. All rights reserved.V2426 Windows Embedded Standard 7User’s ManualThe software described in this manual is furnished under a license agreement and may be used only in accordance withthe terms of that agreement.Copyright Notice© 2013 Moxa Inc. All rights reserved.TrademarksThe MOXA logo is a registered trademark of Moxa Inc.All other trademarks or registered marks in this manual belong to their respective manufacturers.DisclaimerInformation in this document is subject to change without notice and does not represent a commitment on the part of Moxa.Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time.Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use.This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication.Technical Support Contact Information/supportMoxa AmericasToll-free: 1-888-669-2872 Tel: +1-714-528-6777 Fax: +1-714-528-6778Moxa China (Shanghai office) Toll-free: 800-820-5036Tel: +86-21-5258-9955 Fax: +86-21-5258-5505Moxa EuropeTel: +49-89-3 70 03 99-0 Fax: +49-89-3 70 03 99-99Moxa Asia-PacificTel: +886-2-8919-1230 Fax: +886-2-8919-1231Moxa IndiaTel: +91-80-4172-9088 Fax: +91-80-4132-1045Table of Contents1.Introduction ...................................................................................................................................... 1-1Software Components ......................................................................................................................... 1-2 2.System Initialization ......................................................................................................................... 2-1Overview ........................................................................................................................................... 2-2 Initializing User Settings .............................................................................................................. 2-2 3.Enabling Embedded Filters ................................................................................................................ 3-1Enhanced Write Filter .......................................................................................................................... 3-2 Overview .................................................................................................................................... 3-2Enabling Enhanced Write Filter ...................................................................................................... 3-3 File-Based Write Filter ......................................................................................................................... 3-6 Overview .................................................................................................................................... 3-6Configure File-Based Write Filter ................................................................................................... 3-6 4.Examples ........................................................................................................................................... 4-1Watchdog .......................................................................................................................................... 4-2 Enabling Watchdog Function ......................................................................................................... 4-2 5.System Recovery ............................................................................................................................... 5-1Overview: Setting Up the Recovery Environment .................................................................................... 5-2 Step 1: Prepare the USB drive .............................................................................................................. 5-2 Step 2: Setting the BIOS to Boot via USB .............................................................................................. 5-4 Step 3 (opt.): Create a Custom System Image ....................................................................................... 5-5 Step 4: Reset BIOS to Original State ..................................................................................................... 5-8 Step 5: Perform a Test Restoration ....................................................................................................... 5-91Introduction Thank you for buying Moxa’s V2426 train computer. It comes with the Windows 7 Embedded software platform,providing a simple and familiar development environment for on-board train applications.Software ComponentsSoftware ComponentsRefer to the following content for the software components of the Windows Embedded Standard 7 pre-installed on the V2426 computers.Core OS:• 32-bit support• Remote Client• Remote Procedure CallApplications and Services Development:• .Net Framework 3.5• Remote Desktop Protocol 7.1• COM OLE Application Support• COM+ Application Support• MSMQInternet Services:• Internet Explorer 8.0• IIS 7.0File Systems and Data Store:• Windows Data Access Components• Windows Backup and RestoreDiagnostics:• Common Diagnostic Tools• Problem Reports and SolutionsFonts: Chinese (Trad. and Simp.), Japanese, Korean, Western, Middle Eastern, South East Asian, and South Asian FontsGraphics and Multimedia:• MPEG DTV-DVD Audio Decoder (MPEG-2, AAC)• MPEG Layer-3 Audio Codecs(MP3)• MPEG4 Decoders• Windows Media Video VC-1 (WMV) Codecs• DirectX and Windows Device Experience• Windows Media Player 12International:• IME Simplified Chinese Support• IME Traditional Chinese SupportManagement:• Group Policy Management• Windows Management Instrument (WMI)• Windows UpdateNetworking:• Extensible Authentication Protocol (EAP)• Internet Authentication Service• Telnet Server• Bluetooth• Domain Services• Network Access Protection• Network and Sharing Center• Quality of Service• Remote Access Service (RAS)• Telephony API Client• Windows Firewall• Wireless NetworkingSecurity:• Credential Roaming Service• Credentials and Certificate Management• Windows Authorization Manager (AZMAN)• Windows Security Center• Active Directory Rights Management• Security Base• Encrypted File System (EFS)Embedded Features:• Enhanced Write Filter (EWF)• File-Based Write Filter (FBWF)• Message Box Default Reply• Registry Filter• WSDAPI for .NETEmbedded Self-Health Diagnostic Software: SNMP-based remote scripting layer for monitoring, reporting, and control2System Initialization This chapter describes how to initialize the system settings on V2426 computer when you boot up the computerat first time.The following topics are covered in this chapter:❒OverviewInitializing User SettingsOverviewLike most laptop computer, you need to type a user name to create your user account to enable the embedded computer to work, follow the steps below:Initializing User Settings1.When you boot the embedded computer for the first time, you need to enter a user name for thiscomputer.2.Type the password, retype the password. In addition, you may also type a password hint in case youforget your password. If you do not want to set the password, leave it blank and click Next.3.Select the windows update option.4.Select the time zone and daylight saving time option and click Next.5.Select computer’s current location. Windows will automatically apply the correct network settings basedo the network’s location.6.Now you can start to use V2426 embedded computer.3Enabling Embedded FiltersThis chapter describes how to operate the embedded enabling features on the V2426 computer.The following topics are covered in this chapter:❒Enhanced Writer Filter❒File-Based Write FilterEnhanced Write FilterOverviewEnhanced Write Filter (EWF) provides a means for protecting a volume from writes. This allows the operating system (OS) to boot from write-protected hard disks. All writes to an EWF-protected volume. (The Hard Disk in Figure 1) are redirected to an overlay(EWF Volume in Figure 1). Because EWF does not write data to hard disk directly, so it can protect the hard disk from sudden power loose. These writes are cached in the overlay and made available as part of the volume. This gives the appearance that the volume is writeable. The overlay is an independent storage location which exists in random access memory (RAM). If desired, the data stored in the overlay may be committed to the protected volume. Refer to the following figure for the overview of the EWF structure.Enabling Enhanced Write FilterFollow these steps to enable the Enhanced Write Filter1.First open right-click the lock icon in the left side.2.Select volume in Volume Information and then select Configure.3.Select Enable in Pending command.4.Reboot the system.5.Check if the icon has been changed to locked status.6.Select Configure.7.Select volume and select the Pending command for your need.File-Based Write FilterOverviewAccording to Microsoft:File-Based Write Filter (FBWF) allows the Windows Embedded platform to maintain theappearance of read and write access on write-sensitive or read-only storage. FBWFmakes read and write access transparent to applications.Writing to storage media may be undesirable or impossible in embedded devices. FBWFredirects all writes targeted for protected volumes to a RAM cache called an overlay. Usedin this context, an overlay is similar to a transparency overlay on an overhead projector.Any change made to the overlay affects the picture as seen in the aggregate, but if theoverlay is removed, the underlying picture remains unchanged.FBWF provides the advanced feature than EWF to let user specify the directory to write the data to disk drive directly, in our default setting, the default directory is under c:\temp, which means you can read/write the data into disk without commit action.Configure File-Based Write FilterTo enable file-based write filtering, do the following:1.Right-click the lock icon on the right side2. Select Configure .3. In the configuration tab, check Filter state enabled and Cache pre-allocation enabled .And then select C:, and then select Protect and Apply.4. Reboot the system.5.Right-click the icon.6.Click Configure.7.Change to Exclusion List and select browse button.8.Select the file to exclude the protection.9.Click + button.10.Check if the file path has been added.V2426-W7E Series Moxa Software Package11.Change to Cache Content tab.12.Select the file to you want to save to physical disk and select commit13. Reboot system to take effect4ExamplesThis chapter describes how to use various examples on the V2426 computers for different functions.The following topics are covered in this chapter:❒WatchdogEnabling Watchdog FunctionV2426-W7E Series ExamplesWatchdogThe V2426 computers provide example for users to enable the watchdog function. The Watchdog example is under <Software DVD>\examples\project\WatchDog\ and the executable file Watchdog.exe is under <Software DVD>\examples\TC6000Release.You can follow the steps below to test the watchdog function with executable file.Enabling Watchdog Function1.Create c:\programs\example folder and copy the Watchdog.exe into the folder.2.Execute Watchdog.exe.3.You will see the *pdwPortVal = 0x80 which means the watchdog function is enabled, and then you needto press Enter in every 10 seconds or the system will reboot.4.To stop the watchdog function, press q to exit the program, and you will see the *pdwPortVal = 0xc0which means the watchdog function is disabled.5System Recovery The V2426 ready-to-run embedded computers are a Windows Embedded Standard 7 platform. This chapterdescribes the recovery process in the event of system instability.The following topics are covered in this chapter:❒Overview: Setting Up the Recovery Environment❒Step 1: Prepare the USB drive❒Step 2: Setting the BIOS to Boot via USB❒Step 3 (opt.): Create a Custom System Image❒Step 4: Reset BIOS to Original State❒Step 5: Perform a Test RestorationOverview: Setting Up the Recovery EnvironmentA V2426 computer, a 4 GB (min.) USB drive, and a copy of the recovery suite are all required to set up theV2426’s system recovery environment.The recovery procedure itself requires only a V2426 computer and a bootable USB drive.The following procedure describes the basic process of setting up the system recovery environment.1.First, the recovery programs and system image file will be copied over to the USB drive, and the drive willbe set up to provide a system boot process by copying an ISO image of the boot environment to the USB.2.The system will be re-booted, and BIOS will be manually configured to boot the system from the USB port.3.An image of the current software system will be created on the USB drive, for the recovery environment touse when restoring the system.4.The system will be re-booted again, and the BIOS returned to its original state.Step 1: Prepare the USB drive1.Load the software DVD that came with your V2426 computer and execute tuxboot-windows-23.exefrom the software DVD\recovery\V2426W7E folder, select Pre-Downloaded, and click the buttonmarked with an ellipsis (…) to browse the file system and find the location of the boot environment’s ISOimage.2.Navigate to\recovery\on the software DVD and select the boot environment’s ISO image.3.Set the device Type (lower left-hand corner) as USB Drive, then set the Drive dialog to the letter underwhich the USB is currently mounted.4.Click OK, and the boot environment t and bootloader will be copied to your USB drive.5.Because of the file system naming conventions used, for any given computer only a single recovery imagemay be used on any given USB drive. Consequently, at this point, users need to make a decision about which sort of system recovery is preferred:A. a basic recovery of the root OS, orB. a recovery image of the fully configured OS, with all user-installed software applications andscripts.a.To configure the recovery environment to boot into a fully configured system, users should clickReboot Now to close the installation environment and restart the computer. They should then proceed to the next section, Step 2: Setting the BIOS to Boot via USB and continue the installation of the recovery environment by continuing to Step 3 (opt.): Creating a Custom System Image.b.To configure the recovery environment to boot into a clean OS image with no applications, users shouldinstead click Exit here to complete the installation and return to the OS. From within the desktopenvironment, the user should then manually copy the directory containing the base OS from thesoftware DVD over to the USB drive. To do this, copy #:\<SoftwareDVD>\recovery\os_image over to the partition image directory, F:\home\partimag\. At this point, Step 1 has been completed, and you should proceed to Step 2: Setting the BIOS to Boot via USB.Step 2: Setting the BIOS to Boot via USB At this stage, users will reset the BIOS so that the system boots directly from the USB. This must be donebefore the rest of the system recovery environment may be configured1.Turn on the computer and, during the POST process, press F2 until you hear a long beep. You should thenenter the BIOS setup menu.e the arrow keys to navigate to the Boot tab, and then press Enter.3.Select Boot Type Order to open the dialog that will allow you to set the boot priority for the system drives.e the arrow keys to highlight USB and then press the plus key (+) to move it to the first position, orselect the other options above it and use the dash key(–) to move them down.5.Press F10 and then press Enter to save and exit the BIOS configuration interface. This should initiate thenext reboot, during which your system should now boot from the USB drive.Step 3 (opt.): Create a Custom System ImageThe instructions which follow are only to be used if you decided in Step 1of this process to create a full copy of an already-configured system. If you have not yet installed any software on your system, then return to section 5b of Step 1: Preparing the USB Drive and follow the instructions to create a clean OS image.Using this procedure, you will save to the USB drive a copy of the entire system as it is currently configured to be used as a full system recovery image should the system crash. All files under F:\home\partimag\ will be overwritten. Additionally, you should have already changed the BIOS settings to make the USB drivethe first boot priority. If you have not yet reset the boot priority, first return to Step 2: Setting the BIOS to Boot via USB, just above, and follow the directions there.1.Once the system has launched and the V2426 has booted the recovery environment from the USB drive,navigate to the entry ClonezillaLive Save Disk, and select it by pressing Enter. This will take you into the recovery image creation environment, allowing you to copy your full system setup to the USB drive.2.The V2426 will now boot into the image creation environment. Wait for the boot process to finish.3.Once the image creation environment has completed booting up, you will be given a warning and asked ifyou wish to continue. Please keep in mind that if you create the recovery image, then any residual files currently copied to the /home/partimag directory will be deleted. If there are any files remaining in the USB partition image directory and you wish to save them, you must exit the recovery environment and copy these files to another disk. If you wish to continue with the image creation, press Y (case insensitive) to continue.4. At this point, the recovery environment will copy of the entire hard drive to your USB drive. This will likelytake several minutes, and perhaps as long as half an hour. Do not remove the USB drive during this time; wait patiently for the process to finish. Depending on the speed of your USB drive, this may be a good time to get a cup of coffee, or take a nap.5.At this point you may choose to power down the computer (press 0), reboot (press 1), enter a consoleterminal (access a console TTY -- press 2), or re-initiate the entire procedure (press 3). Do not removethe USB drive until you have rebooted or powered down the system.6.Once you have powered down the system and removed the USB drive, you have finished configuring therecovery environment. The USB drive should be clearly labeled and stored in a safe place. You may nowcontinue to the next section, where you will return the BIOS to its original state (Step 4) and test therecovery procedure for successful configuration (Step 5).Step 4: Reset BIOS to Original StateNow you will need to return the boot priority to its original configuration so that the system will boot from the original disk. This is done for two reasons; the first is security, so that the machine may not be rebooted from unauthorized USB drives The second, however, is functional: currently, if the V2426 is set to boot from the USB drive, then the V2426 will hang any time a USB data drive (i.e.: non-bootable image) is inserted in the machine at boot time. The V2426 does not currently have the capacity to distinguish between simple USB data drives and boot-capable OS drives.1.Reboot the system, and press F2 to enter the BIOS setup menu.2.Select Hard Disk and shift it to the top boot priority by using the + key, then press Enter. Make sure thehard disk has first boot priority.3.Press F10 and then press Enter to save and exit the BIOS settings dialog.Step 5: Perform a Test RestorationConnect the USB drive to any of the V2426’s USB ports and then reboot the computer. The system will boot from the USB into the Clonezilla boot loader.1.Select ClonezillaLive Restore Disk to boot into the system restoration environment.2.Wait for the boot process to finish.3.At this point, the system will remind you that you are about to overwrite your entire operating system witha new drive image, and ask you if you want to continue. When prompted, enter Y (case insensitive) fromthe keyboard to start the system restoration process. Any other letter or Ctrl-C will cancel it and exitClonezilla.on the partition listed (sda1, in the example below). If you wish to continue, enter Y (case insensitive).5.Wait for the process to finish.6.At this point, complete the restoration by selecting (0) Power off. This will shut down the computer;however, if the Power Switch remains inserted in the front panel of the computer and is left in the ON position, then the system fail to shutdown and will immediately initiate a soft reboot, instead. To avoid this, users may use the switch to cut power to the computer immediately following the shutdown, or may simply remove the power switch from the front panel and then use the console to shut down the computer by pressing 0.7.After the computer has powered down, remove the USB drive and store it in a safe place.。
西门子技术问题总汇
文档标题
如何设置模拟量输入模板 SM 431-7KF00的温度补偿？ 如何解决 SIMATIC BATCH 的 IL43基本设备上 hotfix 安装的问题？ 如果通过 PCS7 V6.1 SP1 DVD 单独安装 SIMATIC BATCH Report 需要注意哪些设置？ 为什么冗余模拟量输出模块的每个通道只有一半电流输出？ 使用WinCC/Web Navigator V6.1 SP1需要什么样的操作系统和软件？ 是否 COM PROFIBUS 可以使用所有版本的 GSD 文件？ 如何在 WinCC flexible 中组态与S7 控制器的 Profinet 连接? 如何在操作面板上设定定时器时间， 同时如何输出定时器的剩余时间？ 数据块初始值与实际值的含义 如何通过窗口对象滚动条步进调节过程值参数？ 使用 SINAUT ST7 向电子邮箱接受方发送文本信息 SMS 需要做何设置？ 可以使用CPU317-2PN/DP替代在iMap中组态的CPU315-2PN/DP吗? 什么情况下插入C-PLUG卡或者C-PLUG有什么作用? 通过一台PC，可以使用哪种方式访问与IWLAN/PB link PNIO或IE/PB link PNIO连接的PROFIBUS设备? 当在SINAUT网络中使用4线变压器应该注意哪些设置？ 在 SINAUT 网络中，使用MD3拨号调制解调器作为专线调制解调器时，要进行哪些设置？ 如何安装 DCF77 天线, 当选择 DCF77 天线时需要注意什么？ 使用SINAUT ST7向传真机发送文本信息时，需要进行哪些设置？ 在 SINAUT 项目中发送短消息必须进行哪些特殊服务的设置? 如何在S7-300 PN CPU和CP343-1之间建立一个open TCP 通讯连接，以及如何进行数据交换？ 如何在两个S7-300 PN CPU之间建立一个open TCP 通讯连接，以及如何进行数据交换？ 哪些控制系统可以成功与SINAUT ST7一起使用? 使用“零－Modem”电缆连接 TIM 模块应该注意什么？ 当用 SINAUT 诊断工具的ST1协议进行诊断时，为什么TIM的状态不能显示？ TIM 3V-IE 和 TIM 3V-IE Advanced 模块在以太网上通信时使用哪个端口号？ 如何对没有接入网络的S7-200CPU编程？ 掉电后，LOGO！的程序会丢失吗？ 从 PCS7 V6.1 起，为什么没有分配任何 hierarchy (PH) 的 测量点(变量)通过编译不能在OS中自动创建相应的变量？ 在SFC中，如何实现从一个 Sequencer 跳出后回到另一个 Sequencer 的某个固定位置并继续执行？ 如何实现过程变量的平均值归档？ 存储文件的目标路径和备份可选路径有何作用？ WinCC变量归档中如何实现采集周期小于500ms的变量归档？ 为什么在 OS 上会显示如下信息“时间跳变通知－永久切换为从站模式”? 在西门子A&D产品支持网站是否可以下载关于ET200M的手册？ 在S7-400上怎样安装冗余电源？ UDT改变后怎样更新使用UDT产生的数据块。 为什么在FB块中使用OUT变量赋值被调用FB块的IN变量时出现错误信息34：4469？ 如何查看4-mation导入-导出错误 不能正确引导8212-1QU IBM/Lenovo M52 ThinkCentre 实时趋势更新缓慢的原因 如何保存变量名字典CSV文件的格式
纹理物体缺陷的视觉检测算法研究--优秀毕业论文
摘 要
在竞争激烈的工业自动化生产过程中，机器视觉对产品质量的把关起着举足 轻重的作用，机器视觉在缺陷检测技术方面的应用也逐渐普遍起来。与常规的检 测技术相比，自动化的视觉检测系统更加经济、快捷、高效与 安全。纹理物体在 工业生产中广泛存在，像用于半导体装配和封装底板和发光二极管，现代 化电子 系统中的印制电路板，以及纺织行业中的布匹和织物等都可认为是含有纹理特征 的物体。本论文主要致力于纹理物体的缺陷检测技术研究，为纹理物体的自动化 检测提供高效而可靠的检测算法。 纹理是描述图像内容的重要特征，纹理分析也已经被成功的应用与纹理分割 和纹理分类当中。本研究提出了一种基于纹理分析技术和参考比较方式的缺陷检 测算法。这种算法能容忍物体变形引起的图像配准误差，对纹理的影响也具有鲁 棒性。本算法旨在为检测出的缺陷区域提供丰富而重要的物理意义，如缺陷区域 的大小、形状、亮度对比度及空间分布等。同时，在参考图像可行的情况下，本 算法可用于同质纹理物体和非同质纹理物体的检测，对非纹理物体 的检测也可取 得不错的效果。 在整个检测过程中，我们采用了可调控金字塔的纹理分析和重构技术。与传 统的小波纹理分析技术不同，我们在小波域中加入处理物体变形和纹理影响的容 忍度控制算法，来实现容忍物体变形和对纹理影响鲁棒的目的。最后可调控金字 塔的重构保证了缺陷区域物理意义恢复的准确性。实验阶段，我们检测了一系列 具有实际应用价值的图像。实验结果表明 本文提出的纹理物体缺陷检测算法具有 高效性和易于实现性。 关键字: 缺陷检测；纹理；物体变形；可调控金字塔；重构
Keywords: defect detection, texture, object distortion, steerable pyramid, reconstruction
II
NVIDIA FX Composer 2 商品说明书
NVIDIA FX Composer 2
The World’s Most Advanced Shader Authoring Environment
All-New Extensible Plug-In Architecture User-Friendly Shader Authoring Shader Performance Analysis Deep Content Pipeline Integration
Vertex Attribute Packing
Advanced Scripting Support
Full Python scripting Access every aspect of FX Composer in scripts Automate any process Console for writing and running scripts Run scripts from the Windows command line (i.e., “FXComposer2.exe myscript.py” Customizable, scriptable toolbars
View data in tables or graphs
See shader throughput, register usage, instruction counts, and branching performance
Deep Content Pipeline Integration
Semantic and Annotation remapping
COLLADA format support and extras
Material Instance Scene Binding Material Instance Vertex Binding Skinning Support for rendering COMMON Profiles Vertex Stream Remapper Full-Scene Effects
V2416快速安装指南说明书
P/N: 1802024160011V2416 Quick Installation GuideSecond Edition, April 2014OverviewThe V2416 Series embedded computers are based on the Intel Atom N270 x86 processor and feature 4 RS-232/422/485 serial ports, dual LAN ports, and 3 USB 2.0 hosts. In addition, the V2416 computers provide VGA and DVI-I outputs and are EN 50155 certified to confirm their robustness for railway and industrialapplications. 2 hot-swappable and removable storage trays are also provided for convenient, fast and easy storage expansion. The V2416 also features user-defined programmable LEDs and an associated API for storage management, supporting storageplug/unplug functionality, automatic storage removal, and storage status display. An API Library is included for easy development and storage capacity notification.Package ChecklistBefore installing, verify that the package contains the following items:• V2416 embedded computer. • Wall mounting kit• PS2 to KB/MS Y-type cable• Documentation and Software CD or DVD • Quick installation guide (printed)• Product Warranty Statement (printed)NOTE: Please notify your sales representative if any of the above items are missing or damaged.V2416 Panel LayoutV2416 Front & Rear ViewsLED IndicatorsThe following table describes the LED indicators located on the front and rear panels of the V2416. LED Name LED Color LED FunctionPower Green Power is on and functioning normally OffPower is off, or power error exists Storage Yellow CF/HDD card is detectedOff CF/HDD card is not detected LAN (1, 2)Green 100 Mbps Ethernet mode Yellow1000 Mbps Ethernet mode Off 10 Mbps or no activityTx (P1-P4)Green Serial ports P1-P4 transmitting data Off Serial ports P1-P4 not transmitting dataRx (P1-P4) Yellow Serial ports P1-P4 receiving data Off Serial ports P1-P4 not receiving data X2 (Disk 1, Disk 2)Yellow User-programmable OffUser-programmableInstalling the V2416The V2416 can be DIN-rail mounted, wall mounted, and VESA mounted. Some mounting kits may need to be purchased separately. Refer to the Hardware User’s Manual for detailed installation instructions.Connector DescriptionPower ConnectorConnect the 12 to 48 VDC power line with M12 connectors to the V2416 computer. If the power is supplied properly, the Power LED will light up. The OS is ready when the Ready LED glows a solid green.Grounding the V2416Grounding and wire routing help limit the effects of noise due to electromagnetic interference (EMI). Run the ground connection from the ground screw to the grounding surface prior to connecting the power.V2416SG: The Shielded Ground (sometimes called Protected Ground) contact is the central pin of the power input connector. Connect the SG wire to an appropriate grounded metal surface.VGA and DVI OutputsThe V2416 comes with a D-Sub 15-pin female connector for a VGA monitor; it also comes with a DVI-I connector for the DVI display. These output interfaces are all located on the front panel. Use the proper cable to connect. PS/2 PortThe V2416 embedded computer comes with a PS/2 mini-DINconnector to connect to a PS/2 keyboard and PS/2 mouse. Use the Y-type cable to convert the mini-DIN connector into two 6-pin mini-DIN connectors to connect both a PS/2 keyboard and PS/2 mouse at the same time. You may also use the USB ports to connect your USB-based keyboard and mouse. Please note that without a Y-type cable, the PS/2 connector on the V2416 can only work with a PS/2 keyboard. A PS/2 mouse will not function when directly connected to the PS/2 connector on the V2416 embedded computer.CompactFlash SlotThe V2416 has a CompactFlash slot located on the front panel for storage expansion. It supports CF Type-I/II with DMA mode. To install a CompactFlash card, remove the outer cover, and then insert the CF card in the socket. When finished, push the cover into the socket and fasten the screws. USB HostsThe V2416 has one USB port with a M12 connector on the front panel, and two USB ports with type A connectors on the rear panel. These USB ports can be used to connect flash disks for storing large amounts of data. Ethernet PortsTwo 10/100/1000 Mbps Ethernet ports using M12 connectors are located on the front panel. See the following pin assignments./supportThe Americas: +1-714-528-6777 (toll-free: 1-888-669-2872)Europe: +49-89-3 70 03 99-0 Asia-Pacific: +886-2-8919-1230China: +86-21-5258-9955 (toll-free: 800-820-5036)2014 Moxa Inc., All Rights Reserved10/100 Mbps1000 MBps 1 -- TRD3+ 2 -- TRD4+ 3 -- TRD4- 4 ERx- TRD1- 5 ETx+ TRD2+ 6 ERx+ TRD1+ 7 -- TRD3- 8 ETx-TRD2-Serial PortsThe serial ports use DB9 connectors. Each port can be configured by software for RS-232, RS-422, or RS-485. The pin assignments for the ports are shown in the following table: Pin RS-232 RS-422 RS-485 (4-wire) RS-485 (2-wire) 1 DCD TxDA(-) TxDA(-) --- 2RxD TxDB(+) TxDB(+) ---3 TxD RxDB(+) RxDB(+) DataB(+)4 DTR RxDA(-) RxDA(-) DataA(-)5 GND GND GND GND6 DSR --- --- ---7 RTS --- --- --- 8CTS---------Audio InterfaceThe V2416 comes with an audio input and an audio output, allowing users to connect a speaker or an earphone. DI/DOThe V2416 comes with a 6-ch digital input and 2-ch digital output in the terminal block connectors.Hot-swappable and removable Storage TraysThe V2416 computers come with 2 removable slots for inserting additional storage media; it also supports hot swapping forconvenient, fast, and easy storage expansion. The user-defined programmable LEDs and the associated API for storagemanagement support storage plug/unplug functionality, automatic storage removal, and storage status display. Refer to the Hardware User's Manual for detailed storage installation. Reset ButtonPress the “Reset Button” on the rear panel of the V2416 to reboot the system automatically. The Ready LED will blink on and off for the first 5 seconds, and then maintain a steady glow once the system has rebooted.Real-time ClockThe V2416’s real-time clock is powered by a lithium battery. We strongly recommend that you do not replace the lithium battery without help from a qualified Moxa support engineer. If you need to change the battery, contact the Moxa RMA service team.Powering on the V2416To power on the V2416, connect the power cable to the V2416’s M12 power connector (located at the rear panel). Press the power button to turn on the computer. Note that the Shielded Ground wire should be connected to the central pin of the connector. It takes about 30 seconds for the system to boot up. Once the system is ready, the Power LED will light up.Configuring the Ethernet InterfacePower on the V2416 computer after connecting a monitor,keyboard, and mouse, and verifying that the power source is ready. Once the operating system boots up, the first step is to configure the Ethernet interface. The factory default settings for the V2416 LANs are show below. (Please note that the XPE and W7E models use DHCP settings.)Default IP Address NetmaskLAN1 192.168.3.127 255.255.255.0 LAN2 192.168.4.127255.255.255.0Linux users should follow these steps:If you are using the console cable for first-time configuration of the network settings, enter the following commands to edit the interfaces file:#ifdown –a//Disable LAN1/LAN2 interface first, before youreconfigure the LAN settings. LAN 1 = eth0, LAN 2= eth1,#vi /etc/network/interfaces//check the LAN interface first// After the boot settings of the LAN interface have been modified, use the following command to activate the LAN settings immediately:#sync; ifup –aXPE users should follow these steps:1. Go to Start Network Connections .2. Right-click Network Connections , click Properties . Next,select Internet Protocol (TCP/IP), and then click Properties .3. Click OK after inputting the proper IP address and netmask.W7E users should follow these steps:1. Go to Start -> Control Panel-> Network and Internet ->View network status and tasks -> Change adapter setting .2. In the screen of Local Area Connection Properties, clickInternet Protocol (TCP/IP) and then select Properties . Select Internet Protocol Version 4, and then click Properties .3. Click OK after inputting the proper IP address and netmask. NOTE: Refer to the User’s Manual for other configuration information.。
windows craft 编译代码
"Windows Craft" 似乎不是一个已知的编程工具或环境。
如果你是指 "Windows" 操作系统和 "Craft" 文本编辑器（如 Sublime Text，Visual Studio Code 等）进行代码编译，这是可以做到的。
以下是在 Windows 操作系统上使用不同的文本编辑器编译代码的一般步骤：1. 安装编程环境：首先，你需要在你的 Windows 计算机上安装一个编程环境。
这可能是 Python，Java，C++，JavaScript 等。
2. 安装文本编辑器：然后，你需要安装一个文本编辑器，如Sublime Text，Visual Studio Code 等。
3. 打开代码文件：在文本编辑器中打开你想要编译的代码文件。
4. 保存文件：确保你已经保存了你的代码文件。
5. 编译代码：根据你的编程环境和代码文件类型，你可能需要打开命令提示符或终端，然后导航到你的代码文件所在的目录。
然后，你可能需要输入一条命令来编译你的代码。
例如，如果你在使用Python，你可能会输入 `python your_file.py`。
如果你在使用Java，你可能会输入 `javac your_file.java`。
6. 运行代码：一旦你的代码已经被编译，你可以通过在命令提示符或终端中输入一个运行命令来执行它。
例如，在 Python 中，你可能会输入 `python your_file.py`。
在 Java 中，你可能会输入`java your_file`。
这只是一个一般性的指南，具体步骤可能会因你的特定环境、编程语言和工具而异。
如果你能提供更多的信息，我可能能提供更具体的指导。
华盛顿HP OpenView Omniback II 4.1平台与集成支持矩阵说明书
HP OpenView Omniback II 4.1Platform & Integration support matrixVersion: 1.7 Date: October 24, 2003NOTE: For the following Omniback II components, only those “Omniback component-Operating System” combinations are supported for which the corresponding Operating System version is supported by the respective vendors.omniback II componentsupported operating systemsCell Manager• Windows NT 4.0 • Windows 2000 • Windows XP PRO• HP-UX 10.20, 11.03, 11.113, 11.203,5 Graphical User Interface• Windows 98 1• Windows ME 1 • Windows NT 4.0 • Windows 2000 • Windows XP HE • Windows XP PRO• HP-UX 10.20, 11.03, 11.113, 11.203,5 Managers-of-Managers (MoM)• Windows NT 4.0 • Windows 2000 • Windows XP PRO• HP-UX 10.20, 11.03, 11.113, 11.203,5 Backup Device Server (media agent), including robotic control• Windows NT 4.0 • Windows 2000 • Windows XP PRO• Novell NetWare 6 4.11, 4.2, 5.0, 5.1, 6.07• HP-UX 10.20, 11.03, 11.113, 11.203,5, 11.223 &5• Sun Solaris 42.6, 7 , 8•For Windows NT PCs, the following SCSI interface cards are supported: AMD, Adaptec, Symbios• MPE/iX 66.0, 6.5 • Linux Red Hat 6.x,7.x,8.x • Linux SuSe 6.x, 7.x, 8.x Backup Device Server (media agent), without robotic controlThe above list plus the following: • IBM AIX 4.3.x, AIX 5.1, 5.28• SNI Sinix 5.4.3, 5.4.4•SCO OpenServer 5.0.5 (Compaq)1The following limitations apply:• Browsing the Microsoft Windows Network is disabled. • Only US English version of GUI is supported.• Only local installation direct from installation CD-ROM is supported.2The following limitation applies: The Backup Agent on Unixware 7.1.1 can only be installed locally and not via push installation. 3 NIS+ is not supported.4 For Solaris – SunOS version compatibility, please refer to the Sun OS support matrix. 5HP-UX 11.11 is pHP-UX 11i version 1.0. HP-UX 11.20 is HP-UX 11i version 1.5. HP-UX 11.22 is HP-UX 11i version 1.66 Push installation not possible, need to be installed locally7For Netware 6.0 support, the patch OMNIBACK_00059 needs to be installed. DA & MA do not take advantage of the new features introduced by NSS 3.0 8 To utilize this feature, the patch PHSS_28584 is required 9 To utilize this feature, the patch PHSS_28232 is required 10To utilize this feature, the patch PHSS_28336 is requiredoperating systemsupported processor platformHP-UX PA-RISC or IA-642Windows XPIntel, IA-32, or AMDBackup Agents (disk agents)• Windows NT 4.0 • Windows XP HE 6 • Windows 956 • Windows 986 • Windows ME 6 • Windows 2000 • Windows XP PRO• Novell NetWare 64.11, 4.2,5.0, 5.1,6.07• HP-UX 10.20, 11.03, 11.113, 11.203,5, 11.223&5 • HP MPE/iX 6, 6.0, 6.5 • Sun Solaris 4 2.6, 7, 8• IBM AIX 4.3.x, 5.1, 5.28• SGI IRIX 6.4, 6.5• SNI Sinix 5.4.3, 5.4.4• SCO OpenServer 5.0.5, SCO Unixware 7.x 2 • Digital UNIX/Tru64 Unix 4.0x • Tru64 UNIX version 5.0, 5.1x • MP-RAS NCR V4_3.0• DYNIX Sequent Intel 4.4.26• Linux – Red Hat Distribution 6.x, 7.x, 8.x 9• Linux – SuSE 6.x, 7.x, 8.x 10• Caldera OpenLinux 2.4x, 3.1.1 • Debian Linux v2.2.r3, 3.0• Additional UNIX platforms via NFS •Additional platforms via shared disksWindows NT 1Intel, IA-32, or AMDWindows 2000 Intel, IA-32, or AMDLinux – Red Hat Distribution Intel, IA-32, or AMDLinux – SuSE Intel, IA-32, or AMDLinux --- Debian Intel, IA-32Sun Solaris SPARC1The Windows NT 4.0 Backup Agent (disk agent) is also supported on Alpha Systems.2 Supported in Emulation modeNOTE: For the following integration matrices, only those combinations of applications and operating systems that are supported by the respective vendors are supported by HP OpenView Omniback II.application agents supported databases / integrationsOracle (32-bit) (including Oracle Parallel Server and RAC) • Oracle 7.3.4/EBU 2.2 : HP-UX 10.20(32-bit), 11.0 (32 & 64-bit)Windows NT 4.0Solaris 2.6 (32-bit)AIX 4.3.x• Oracle 8.0.x/Recovery Manager : HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit)Windows NT 4.0Solaris 2.6 (32-bit), 7 (32 & 64-bit)AIX 4.3.x• Oracle 8.1.x/Recovery Manager : HP-UX 11.0 (32 & 64-bit), 11.11(32 & 64-bit) Solaris 7, 8 (32 & 64-bit)AIX 4.3.x, AIX 5.16, 5.26, 8Windows NT 4.0, Windows 2000Linux - Red Hat Distribution 6.x , 7.xLinux – Suse 7.x• Oracle 9i/Recovery Manager9 : Solaris 7 & 8 (32-bit)Linux – Red Hat 7.x, 8.x6SuSE 7.x, 8.x6Windows NT 4.0, Windows 2000Oracle (64-bit) (including Oracle Parallel Server and RAC)• Oracle 8.0.x/Recovery Manager : HP-UX 11.0 (64-bit)• Oracle 8.1.x/Recovery Manager: HP-UX 11.0 (64-bit), 11.11(64-bit) Solaris 7 & 8 (64-bit)AIX 4.3.3 (64-bit)10AIX 5.1 (64-bit)6, 5.2 (64-bit)6, 8Tru64 5.x (64-bit)10• Oracle 9i/Recovery Manager9 : HP-UX 11.0 (64-bit), 11.11 (64-bit)Solaris 7 & 8 (64-bit)AIX 4.3.3 (64-bit)10AIX 5.1 (64-bit)6, 5.2 (64-bit)6, 8Tru64 5.x (64-bit)10Informix (32-bit) • Informix 7.24 : HP-UX 10.20, 11.0 (32-bit)Sinix 5.4.3Solaris 7 (32-bit)• Informix 7.3x : HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit), 11.11 (32 & 64 bit)Sun Solaris 2.6 (32-bit), 7 & 8 (32 & 64-bit)AIX 4.3.xWindows NT 4.0• Informix XPS 8.2x : HP-UX 11.0 (32 & 64-bit)• Informix XPS 8.3x : HP-UX 11.0 (32 & 64-bit), 11.11 (32 & 64-bit)• Informix IDS 9.2x : HP-UX 11.0 (32 & 64-bit), 11.11 (32 & 64-bit)Solaris 7, 8 (32 & 64-bit)Windows 2000• Informix IDS 9.3x : HPUX 11.0 & 11.11 (32 & 64-bit)Solaris 2.6 (32-bit), Solaris 7 & 8 (32 & 64-bit)AIX 4.3.3 (32 & 64-bit)Windows 20005Informix (64-bit) • Informix 7.31 : HP-UX 11.0 (64-bit)Solaris 7 & 8 (64-bit)AIX 4.3.x (64-bit)• Informix XPS 8.2x : HP-UX 11.0 (64-bit)• Informix XPS 8.3x : HP-UX 11.0 (64-bit), 11.11 (64-bit)• Informix IDS 9.2(0,1)1 : HP-UX 11.0 (64-bit), 11.11 (64-bit)Solaris 7 & 8 (64-bit)• Informix IDS 9.3x : HPUX 11.0 (64-bit), 11.11(64-bit)Solaris 7 & 8 (64-bit)AIX 4.3.3 (64-bit)Sybase (32-bit) • Sybase SQL Server 11.1 : HP-UX 10.20• Sybase Adaptive Server 11.5: HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit)Solaris 2.6 (32-bit), 7 (32 & 64-bit)• Sybase Adaptive Server 11.9.2 : HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit)• Sybase Adaptive Server 11.9.2 : Windows NT 4.0—requires 11.9.2.1 ESD #1maintenance release or later; contact Sybase support for details• Sybase Adaptive Server 12.0 : HP-UX 11.0, 11.11 (32 & 64-bit)Solaris 7 & 8 (32 & 64-bit)Windows 2000Windows NT 4.0• Sybase Adaptive Server 12.5 : HP-UX 11.0 , 11.11 (32 & 64-bit)Solaris 7 & 8 (32 & 64-bit)Windows NT 4.0, Windows 2000Sybase (64-bit) • Sybase Adaptive Server 11.9.3 : HP-UX 11.0 (64-bit), 11.11 (64-bit)Solaris 7, 8 (64-bit)• Sybase Adaptive Server 12.0 : HP-UX 11.0 (64-bit), 11.11 (64-bit)Solaris 7 & Solaris 8 (64-bit)• Sybase Adaptive Server 12.5 : HP-UX 11.0 (64-bit), 11.11 (64-bit)Solaris 7 & 8 (64-bit)Microsoft SQL Server • Microsoft SQL Server 7.0 : Windows NT 4.0• Microsoft SQL Server 7.0 : Windows 2000• Microsoft SQL Server 2000 : Windows 2000Microsoft Exchange Server • Microsoft Exchange Server 5.0 : Windows NT 4.0• Microsoft Exchange Server 5.5 : Windows NT 4.0• Microsoft Exchange Server 5.5 : Windows 2000• Microsoft Exchange Server 2000 : Windows 2000• Microsoft Exchange Server 5.5 – Single mailbox restore - Windows NT 4.0Windows 2000• Microsoft Exchange Server 2000 – Single mailbox restore : Windows 2000 SAP 2 & 4 (32-bit) • SAP R/3 3.1x : HP-UX 10.20, 11.0 (32-bit)AIX 4.3.x (32-bit)Windows NT 4.0• SAP R/3 4.0 : HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit)AIX 4.3.xWindows NT 4.0• SAP R/3 4.5, using RMAN mode : HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit)Windows NT 4.0, Windows 2000• SAP R/3 4.5, using backint mode : HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit)AIX 4.3.xSolaris 2.6 (32-bit), 7, 8 (32 & 64-bit)Windows NT 4.0, Windows2000• SAP R/3 4.6x, using RMAN mode : HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit)HP-UX 11.11 (32 & 64-bit)Windows NT 4.0, Windows 2000Solaris 7 & 8 (32 & 64-bit)• SAP R/3 4.6x, using backint mode: HP-UX 10.20 (32-bit), 11.0 (32 & 64-bit)HP-UX 11.11 (32 & 64-bit)Linux Suse 7.xAIX 4.3.xSolaris 7, 8(32 & 64-bit)Windows NT 4.0Windows 2000• SAP R/3 Enterprise 4.7x, using backint & RMAN mode: Windows 2000Linux SuSe 8.x• SAP Brtools 6.10, using backint & RMAN mode: : Windows NT4.0Windows2000Linux Suse 7.x• SAP Brtools 6.20, using backint & RMAN mode: :Windows2000Linux Suse 8.xSAP 2 & 4 (64-bit) • SAP R/3 4.0 : HP-UX 11.0 (64-bit)• SAP R/3 4.5, using backint and RMAN mode : HP-UX 11.0 (64-bit)• SAP R/3 4.6x, using backint mode : HP-UX 11.0 (64-bit), 11.11(64-bit)• SAP R/3 4.6x, using RMAN mode: HP-UX 11.0 (64-bit), 11.11(64-bit)Solaris 7 & 8 (64-bit)AIX 4.3.3 (64-bit)11, 5.1 (64-bit), 5.2 (64-bit)10• SAP R/3 Enterprise 4.7x : HP-UX 11.0 (64-bit), 11.11(64-bit)(using backint & RMAN mode) Solaris 9 (64-bit)Tru64 5.xx (64-bit)11AIX 5.1 (64-bit), 5.2 (64-bit)10• SAP Brtools 6.10 : HP-UX 11.0 (64-bit), 11.11(64-bit)(using backint & RMAN mode Solaris 7 & 8 (64-bit)AIX 4.3.3 (64-bit)11AIX 5.1 (64-bit), 5.2 (64-bit)10Tru64 5.xx (64-bit)11• SAP Brtools 6.20 : HP-UX 11.0 (64-bit), 11.11(64-bit)(using backint & RMAN mode) Solaris 9 (64-bit)Tru64 5.xx (64-bit)11AIX 5.1 (64-bit), 5.2 (64-bit)10Baan IV 3• Baan IV on Oracle, Informix, and Microsoft SQL Server (see versions above) Lotus Notes, Lotus Domino • Lotus Domino/Notes R5 : HP-UX 11.0 (32 & 64-bit), HPUX 11.11 (32 & 64-bit)(Online Integration) AIX 4.3.xWindows NT 4.0, Windows 20001Chain restore is not working for Informix ODS 9.20.FC1 (64-bit) and earlier versions.2Omniback II uses the official SAP backup/restore API (BRTOOLS), which is available only in conjunction with the Oracle database. Therefore, Omniback II support is only dependent on the SAP brtools version (as supported by SAP in combination with various SAP Kernels) but is independent of the Oracle version.3 Baan users with Oracle, Informix, or Sybase databases can back up their application data byfollowing the instructions for the integration of Omniback II and their database in the HPOpenView Omniback II Integration Guide.4 If you have SAP & Oracle 9i combination, following patches are required for it to besupported:OMNIBACK_00097 – For Windows Installation ServerPHSS_28723 – For HP-UX Installation Server5 To utilize this feature the patch OMNIBACK_00094 is required6 To utilize this feature the patch PHSS_28582 is required7The whitepaper is located on the CD-ROM “HP OpenView Omniback II for WindowsNT/2000” in the folder:\Product_Information\Whitepapers & Service Deployment.8 To utilize this feature, the patch PHSS_28584 is required9 Oracle 9i includes all released versions of Oracle 9.x.x.x10 To utilize this feature, the patch PHSS_28584 is required11To enable this feature the Patch(es) PHSS_26888/PHSS_26887 is required. application supported versionsHP OpenView VantagePoint Operations • VPO Management Server:VPO 6.0 : HP-UX 10.20, 11.0Service Navigator : HP-UX 10.20, 11.0• VPO Managed Node (Omniback Cell Server)VPO Agent 6.05 : HP-UX 10.20, 11.0, 11.11VPO Agent 6.03 : Windows NT 4.0, Windows 2000VP Performance Agent C.03.20 : HP-UX 10.20, 11.0, 11.11VP Performance Agent C.03.00 : Windows NT 4.0, Windows 2000HP OpenView ManageX HP OpenView ManageX 3.5, 4.0, 4.2 : Windows 4.0, Windows 2000 HP OpenView OmniStorage • HP OpenView OmniStorage 3.0 : HP-UX 10.20• HP OpenView OmniStorage 3.11: HP-UX 10.20, 11.0• HP Openview Omnistorage 3.12 : HP-UX 10.20, 11.0HP Openview Network Node Manager1 • HP Openview Network Node Manager 6.2 : HPUX 10.20, 11.0Windows NT 4.0, Windows 20001Omniback II integrates with the Solid database in Network Node Manager for an online backup of the database.array type supportedHP SureStore XP 1• HP SureStore Business Copy XP/Continuous Access XPEMC 2• EMC TimeFinder/SRDFHP SureStore Virtual array3• HP SureStore Business Copy VA1Please refer to the “HP OpenView Omniback II 4.1 Zero Downtime (Split-mirror) backup & Instant Recovery Support Matrix for HP Storageworks XP Disk Array” for further details on the integration.2Please refer to the “HP OpenView Omniback II 4.1 EMC split-mirror backup integration Support Matrix” for further details on the integration.3 Please refer to the “HP OpenView Omniback II 4.1 Zero Downtime Backup & Instant RecoverySupport Matrix for HP Storageworks Virtual Array 7100 & 7400” for further details on the integration.NAS applicationSupported versionsNDMP• NetApp Filer ONTAP version 5.3.x, 6.x, NDMP v2 : HP-UX 11.0 Solaris 7 & 8 Windows NT 4.0 Windows 2000 • EMC Celerra(Symmetrix Network File Storage,Version: T2.2.49 or higher)1 : HP-UX 11.0 Solaris 7 & 8 Windows NT 4.0 Windows 2000 HP NAS 80002• NAS 8000 Linux 2.4.17HP NAS B3000/e70002• Windows 20001 Documentation available only in the HP OpenView Omniback II 4.1 release notes.2For supported devices, please refer to the device support matrices of the respective NASvendors. Only those devices that are supported by the respective NAS vendors and are also listed in HP OpenView Omniback II 4.1 Device Support Matrix as supported, are supported.application agentssupported databases / integrationsHP OpenView Omniback II Open File Manager•HP OpenView Omniback IIOpen File Manager 7.x : Windows NT 4.0Windows 2000 Novell NetWare 4.x, 5.x •HP OpenView Omniback II Open File Manager 8.x : Windows NT 4.0 Windows 2000 Novell NetWare 4.x, 5.x Novell Netware 6.011 To utilize this feature, Omniback patch OMNIBACK_00093 is requiredoperating systemfile systemsWindows NT• NTFS • FAT •CIFScluster softwaresupported cluster software versionHP MC/ServiceGuard• HP MC/ServiceGuard 10.xx : HP-UX 10.20 • HP MC/ServiceGuard 11.xx : HP-UX 11.0 •HP MC/ServiceGuard 11.xx : HP-UX 11.11 Microsoft Cluster Server •Microsoft Cluster Server : Windows NT 4.0Windows 2000Windows 2000/XP• NTFS 5.0 (including Image Backup)• FAT16, FAT32• CIFSWindows 98 • FAT• VFAT• FAT32Windows 95 • FAT• VFAT• FAT32Novell NetWare • NetWare FSsupported namespaces: MAC, NFS, NSS1, OS/2(long namespace), DOSHP-UX • HFS (including Raw disk)• NFS (including NFS3 on HP-UX 10.30 and higher)• LOFS (Loopback FS)• Cache FS• VxFS (10.x, 11.x) (including Raw disk)• DCE DFS (10.20 only)Solaris3 • UFS• PC FS (MSOS compatible FS)• HSFS• VxFS4• Tmp FS• LOFS (Loopback FS)Linux (Red Hat, SuSe, Debian & Caldera)3 • ext2, ext, minix, xiafs, ReiserFS, ext32IBM AIX3 • AIX physical FS “oaix”• JFS (Journaling FS)SGI IRIX3 • EFS (Extent File System)• XFS (IRIX Journaling FS)SNI Sinix3 • HSFS (High Sierra FS)• UFS (UNIX File System)• VxFSSCO OpenServer3 • HTFS (High Throughput FS)• DTFS• S51K• S52KSCO Unixware3 • memfs• s5• sfs (Note: ACLs are not backed up and restored.)• ufs• bfs• vxfs (Note: ACLs are not backed up and restored.) Digital UNIX Alpha Systems/Tru64 UNIX3 • UFS (UNIX FS)• AdvFS (Advanced File System)MP-RAS NCR Intel • BFS (Boot File System)• Cache FS• S5 FS• UFS (UNIX File System)• VxFS• LOFS (Loopback FS)DYNIX Sequent • UFS (UNIX File System)• VxFS1Novell NetWare NSS is supported, with the following limitations:• The new NSS volumes on NetWare 5.0 allow creation of deep directory structures (deeper than 100). Omniback II can back up only to a depth of 100.• NetWare 5.0 NSS volumes allow 8 TB file size, but the maximum file size that Omniback II backs up is 4 GB.NetWare 5.0 has an NSS_ADMIN volume on every system with NSS volumes present. This isa special read-only volume that contains information about NSS volume configuration.NSS_ADMIN is not backed up.2 To utilize ext3 support, the patches PHSS_25965/PHSS_25964 must be installed.3 Raw Disk Backup is supported. In case of Tru64, it is not supported if LSM is installed4 VxFS attributes backup is only supported for Solaris 2.6operating system file system number of ACL entries(basic/extended)Windows NT NTFS < 2 GBWindows NT FAT < 2 GBWindows 2000 NTFS 5.0 < 2 GBWindows XP Pro NTFS 5.0 < 2 GB512Novell NetWare NetWare FS (MAC, NFS, OS/2,DOS) 1Novell Netware NSS UnlimitedHP-UX HFS 3/16HP-UX VxFS (10.x, 11.x) 4/17 (JFS 3.3 & 4)HP-UX DCE DFS (10.20 only) 3/8188IBM AIX AIX (Physical FS “oaix”) 1024 (4096 bytes)1Limited with Omniback II record size and SMS API.。
windows craft 编译代码
Windows Craft 编译代码1. 介绍Windows Craft 是一个用于编译代码的工具，它提供了一套简单易用的界面和功能，帮助开发者在 Windows 操作系统上进行代码编译。
本文将详细介绍 WindowsCraft 的使用方法以及一些常用的功能。
2. 安装Windows Craft 的安装非常简单，只需按照以下步骤进行操作：1.下载 Windows Craft 的安装包。
2.双击运行安装包，按照提示完成安装过程。
3.安装完成后，可以在开始菜单中找到 Windows Craft 的快捷方式。
3. 编译代码Windows Craft 提供了多种编译代码的方式，包括命令行和图形界面两种方式。
下面将分别介绍这两种方式的使用方法。
3.1 命令行编译在命令行中使用 Windows Craft 进行代码编译非常方便。
只需打开命令行窗口，输入相应的命令即可。
以下是一些常用的命令：# 编译 C++ 代码craft compile --language=c++ --source=source.cpp --output=output.exe# 编译 Java 代码craft compile --language=java --source=source.java --output=output.jar# 编译 C# 代码craft compile --language=c# --source=source.cs --output=output.exe以上命令中，--language参数指定了编译的语言，--source参数指定了源代码文件，--output参数指定了编译后的输出文件。
3.2 图形界面编译Windows Craft 的图形界面提供了更直观、易用的编译方式。
只需打开 Windows Craft 的界面，按照以下步骤进行操作：1.打开 Windows Craft。
2.在界面上选择要编译的代码文件。
Polycom RPX HD 400和200系列版本2.7.1发布说明书
Release NotesPolycom® RPX™ HD 400 and 200 SeriesVersion 2.7.1Polycom announces the general availability release of its Polycom RealPresence Experience™ (RPX) HD, version 2.7.1. This document provides the latest information about this release.TopicsIntroducing the Polycom RPX HD 2.7.1 Release (2)What’s New in RPX HD Version 2.7.1? (2)Software and Firmware Used in Version 2.7.1 (2)Upgrading the Software to Version 2.7.1 (3)Configuring the Content Monitors in Your RPX Suite (4)Issues Fixed in This Release (6)Known Issues and Limitations (7)For Users (7)For Administrators (9)Where to Get the Latest Product Information (10)Copyright Information© 2011 Polycom, Inc. All rights reserved.3725-25796-012/B (January 2011)Polycom, Inc.4750 Willow RoadPleasanton, CA 94588-2708USATrademark InformationPOLYCOM®, the Polycom "Triangles" logo and the names and marks associated with Polycom's products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom.Introducing the Polycom RPX HD 2.7.1 ReleasePolycom is pleased to announce the release of the Polycom RPX HD 400 and 200 Series, version 2.7.1.The Polycom RealPresence Experience High Definition offers unprecedented high-definition video ina cinematic view, extraordinary StereoSurround™ audio, and high resolution content. This trulyimmersive meeting environment provides the ultimate meeting experience for executives in anyorganization, linking sites across the globe.What’s New in RPX HD Version 2.7.1?RPX HD version 2.7.1 is a maintenance release for RPX HD version 2.7, which provides the following functionality:∙Optimize bandwidth with H.264 High Profile, a standards-based video compression technology that delivers full HD quality while lowering your bandwidth requirements by up to 50 percent.H.264 High Profile is supported only on RPX HD systems with HDX 8000 series codecs.∙Simply and easily view a list of scheduled meetings and join those meetings using the Polycom Conferencing for Microsoft® Outlook® feature.∙Support for the new Delta VW7028 projector, which replaces the Delta VW7008 projector beginning in the first quarter of 2011.Information on the configuration of these and other RPX features is provided in the PolycomImmersive Telepresence (ITP) Administrator’s Guide.Software and Firmware Used in Version 2.7.1RPX HD version 2.7.1 uses the following software and firmware:∙Polycom Telepresence Tool version: 2.7.1.1 (TelepresenceTool_2.7.1.1.msi)∙Crestron software version: 2.7.1-1 (RPX_2.7.1-1.zip)∙Crestron AV2/PRO2 firmware version: 4.001.1012 (Feb 17 2009)(pro2_av2_cp2_cp2e_rack2_pac2_4.001.1012.zip)∙Crestron Touch Panel firmware version: 3.001.0015 (tps-3000_tps-3000l_tps-3100_tps-4000_tps- 4000l_3.001.0015.zip)∙HDX software version: polycom-hdx-hf-2.6.1.3_00_itp271-5267.pup∙HDX software version without encryption: polycom-hdx-hf-2.6.1.3_00_itp271_ne-5267.pup∙Delta projector firmware version for VW7008 projectors: FD31+SD30. The full file names are FD31-VW7008-20090907 and SD30-VW7008-2008090.∙Delta projector firmware version for VW7028 projectors: FP04+SP04. The full file names are FP04-VW7028BBCP-20101203 and SP04-VW7028BBCP-20100913.For information on versions of other Polycom products, such as RMX™ and CMA™, that are compatible with this release, refer to the Polycom Immersive Telepresence (ITP) Deployment Guide.Upgrading the Software to Version 2.7.1If the software at the RPX HD site is being upgraded to version 2.7.1 from an earlier version, theinstaller must follow these configuration procedures:1.Upgrade the Delta projector firmware if necessary.NOTE If you are upgrading the software to version 2.7.1 and your systemhas Delta projectors, you must ensure that the Delta projectorfirmware is at the correct version listed in the previous section. Thismay require you to upgrade the projector firmware. The firmwareupgrade must be performed onsite by a trained installer.2.Upgrade the HDX software.3.Configure the control system.4.Install and use the Telepresence Tool.5.Configure the Immersive Telepresence features.6.Align and calibrate the projectors (if you upgraded the projector firmware).7.Configure, align, and match the cameras (if you upgraded the projector firmware).The steps above are described in the Polycom RealPresence Experience (RPX) HD 400 Series Installation Guide, Version 2.7.1 or the Polycom RealPresence Experience (RPX) HD 200 Series Installation Guide,Version 2.7.1 as well as the Polycom Immersive Telepresence (ITP) Administrator’s Guide.Important Note: If your RPX HD system was installed after April 30, 2010 and you wish to upgrade from version 2.6 to version 2.7.1 software, you may need to obtain a new 1080p software license (part number 5150-26946-001) from Polycom. Please contact Polycom Customer Support at for more information.Configuring the Content Monitors in Your RPX Suite1.On the laptop, start the Polycom Telepresence Tool.2.The first time you use the Polycom Telepresence Tool with the RPX, the Select TelepresenceModel dialog box will appear and you must do the following:a.In the Select Model field, select the RPX system model.b.In the Select Main Display field, select the video format for the main displays installed inthe room.c.In the Select Content Display field, select Standard – VGA 1024x768.You must select Standard – VGA 1024x768 whether you have standard or widescreencontent monitors.d.Click OK.3.Press the Enter button on the content monitor to display the Configuration screen.4.Press the Right Arrow button on the screen to select Image Properties.5.Click OK.6.Press the Right Arrow button on the screen to select Scaling.7.Click OK.8.Select Full Screen.9.Click OK.10.If needed, press the Auto Sync button to make the content fill the screen.11.Repeat steps 3 through 10 for the remaining content monitors.Issues Fixed in This ReleaseRPX version 2.7.1 incorporates both HDX software version 2.6.1.3 and HDX hotfix version 2.6.1.3-HF5. HDX software version 2.6.1.3 provides a correction for an issue recently observed at the factory in which Polycom HDX systems restarted intermittently while in a call. HDX hotfix version 2.6.1.3-HF5 provides a correction to an intermittent lip sync issue.The following table lists the other issues fixed in RPX HD Version 2.7.1.Feature DescriptionAudio/Video Calls On rare occasions when placing a video or audio call with the Enhanced UI, the system may have automatically dialed the number before you pressed the Connect button.When viewing an RPX system in a 1080p multipoint call with an RMX 2000 or RMX 4000 with MPMx, you will no longer see a thin black vertical line between cells of the RPX system. For more information, refer to the Polycom® ImmersiveTelepresence (ITP) Deployment Guide.Touch Panel/ User Interface When joining a Polycom Conferencing for Microsoft Outlook (PCO) conference from the Touch Panel, you were not prompted for a conference password, even if a password was required for the meeting.With PCO, private meeting details were displayed on the Touch Panel, even if the Primary HDX system was not configured to Show Private Meeting Details.Known Issues and LimitationsFor UsersThe following table lists the known issues relevant to RPX HD end users.Feature DescriptionAudio/Video Calls The RPX will not accept any incoming audio calls when it is already in a video call.To avoid this issue, place outgoing audio calls instead of receiving incoming audio calls when you are already in a video call.When DTMF tones are heard during the process of dialing an audio call, the near-end and far-end audio is muted for a brief moment.If you hang up an incoming audio call and then immediately place an outgoing audio call, the RPX may not hang up the initial incoming audio call.To avoid this issue, wait five seconds between consecutive audio calls.If the RPX is in a single endpoint video call (such as with a VSX or HDX video conferencing system) and the Do Not Disturb feature on the RPX is disabled, an incoming call from a two-codec or three-codec system will cause the center camera on the RPX to momentarily move to the side before returning to its correct position.If the projectors are in sleep mode when an incoming video call is automatically accepted by the RPX, it may take up to 70 seconds for the projectors to automatically power up. During the 70 seconds that it takes for the projectors to warm up and show far-end video, the RPX meeting participants may not notice that the call has been established.To avoid this issue, verify that the projectors are powered up before placing or receiving any video calls.If the projectors are in sleep mode when a video call comes in, any codecs that are not being used will briefly show near-end video. This only occurs when the number of near-end codecs is more than the number of far-end codecs, such as when a RPX 400 on the near end receives an incoming call from an RPX 200 on the far end, or when either an RPX 400 or 200 receives an incoming call from a single endpoint (VSX or HDX).If you place a point-to-point call to an RMX Virtual Meeting Room (VMR) and then add a site to the call from the Conference List on the Meeting Composer screen (with the Enhanced UI only), the point-to-point call will be dropped and a multipoint call will be created with the VMR as a participant in that multipoint call.To avoid this, hang up the VMR call and then make a new call with the participants that you want in that call.If you are using Meeting Composer and you dial two audio sites concurrently, the Touch Panel may show that you are connected to the second audio number dialed when you are actually connected to the first number dialed.To avoid this issue, when want to connect to multiple audio sites or to both audio and video sites when using Meeting Composer, connect to the video sites first (if any), and then add the audio sites one at a time.When you place a call to an RMX VMR using the following syntax, the call will not go through: IP##MeetingRoomID.To avoid this issue, place the call using this syntax: MeetingRoomID@IP (for example,*************.130.21).Feature DescriptionAudio/Video Calls If you dial an incomplete IP address for a video call (for example, 172.16.254.), you may hear a ringing sound for approximately 90 seconds. Until the ringing ceases, you will be unable to place another call.Content If you share content using a laptop, for best results, set its input resolution to 1024x768 and its refresh rate to 75 Hz. This will ensure that the content image renders correctly.Document Cameras The Eye-10 document camera used in some custom solutions does not support the Freeze function that is available for other document camera models.Touch Panel/ User Interface If you press the Content button on the Touch Panel when no content source (such as a laptop) is connected to the RPX with the VGA cable, the Primary HDX codec will generate a hidden message on the Primary wall screen. The message states "PC input resolution and/or refresh rate not supported.” This message will not be visible onscreen because the RPX is programmed to picture mute all wall screens when the system is not in a call. If you establish a video call while the message is activated, the call will take longer than usual to connect. To avoid this issue, wait three seconds (during which time the message will time out) before placing a video call from the Touch Panel.In an audio call from an RPX to a cellular phone or analog phone, if the remote user disconnects the call first, the Touch Panel continues to show the audio call as in progress. To avoid this issue, manually press the Hang Up button after each audio call is completed. The RPX will not accept incoming audio or video calls when the Hang Up button is off hook.When searching for a site in the global directory with the Enhanced UI, up to nine characters can typically be displayed on the screen. However, depending on the width of the letters in the name, more or less of the site name may be truncated.With Meeting Composer, when dialing a phone number with more than 10 digits, or dialing anyotherlongstringsuchasextension@IP_address(ex:*************.130.201),the string will likely be truncated when displayed in the right-hand pane of the Touch Panel.If you place a point-to-point call to an RMX Virtual Meeting Room (VMR) and then add an audio-only site to the call, the two columns on the left side of the Meeting Composer screen in the Enhanced UI will go blank and the icons at the top of the columns will become grayed-out.When Polycom Conferencing for Microsoft Outlook (PCO) is used to schedule multiple meetings and you select one of the meetings on the Touch Panel, the details for that meeting display on the left side of the Touch Panel screen. If that meeting is cancelled, it is removed from the meeting list; however, the details of the cancelled meeting are still displayed on the left side of the Touch Panel screen.To fix this issue, simply select a different meeting from the meeting list.For AdministratorsThe following table lists the known issues relevant to RPX HD administrators.Feature DescriptionAudio/Video Calls When the primary codec answers an incoming video call, any HDX codecs that are not being used will automatically accept any other incoming video calls if the following conditions exist:1. The RPX 200 Series or RPX 400 Series is in a single endpoint video call with aVSX or HDX video conferencing system (video ad-hoc dialing).2. The RPX 400 is in a video call with an RPX 200 Series, a TPX™ 306M, or a TPX204M.To prevent unused codecs from accepting any incoming calls, use the Do Not Disturb timer. To change the amount of time before Do Not Disturb is activated, access the DoNotDisturbTimer field in the System_Config.ini file. In this field, you can enter a value between 10 and 300, or leave the value at 0 if you want to keep the feature disabled: DoNotDisturbTimer=x where x is the value (in seconds) of the desired timeoutperiod.For example, DoNotDisturbTimer=120 sets the parameter to 120 seconds.If you use the web UI to place a call that is not at the default call speed, the codecs will not automatically adjust to the same call speed. The Primary codec will connect at the call speed specified in the HDX web UI Call Quality field, but the remaining codecs will connect at the default call speed.To avoid this issue when placing a call using the web UI, connect to each codec individually at the desired call speed (if the desired call speed is different from the default).Avoid using the suffixes ‘1’, ‘2’, ‘3’, and ‘4’ for your audio speed dial name entries. Using these suffixes may cause the system to incorrectly interpret them as an ITP suite, instead of distinct audio speed dial entries.Avoid creating directory entries that have an “&” symbol in the name. If you do so, the entry will appear on the site list with the word “amp” in the name rather than the “&” symbol.When the RPX is in a call, sending Telnet commands to change the video format may not work properly.To avoid this issue, do not use Telnet commands to change the video format when the RPX is in a call.If you use the web UI to place a call that is not at the default call speed, the codecs will not automatically adjust to the same call speed. The Primary codec will connect at the call speed specified in the HDX web UI Call Quality field, but the remaining codecs will connect at the default call speed.To avoid this issue when placing a call using the web UI, connect to each codec individually at the desired call speed (if the desired call speed is different from the default).When an RPX calls another RPX in a point-to-point call, the codecs begin to connect one at a time. If network resources become limited, not all of the codecs may connect, which may make it appear that one of the projectors is not working properly. If a projector does not work correctly in a call, you should check if the codec connected. If it did not connect, reducing the call bandwidth may solve the issue.If your ITP environment is configured to use both the LDAP directory and H.323 Gatekeeper functions, and your speed dial entries are not IP addresses, video calls may take longer to connect due to the additional communication involved between the various components in the solution.Feature DescriptionControl System When you connect to the codecs through Telnet or through the Crestron Toolbox and use the command prompt, you may see “overflow buffer” and other error messages when you usethe Touch Panel. These errors also appear on the Crestron log. This issue does not affectsystem performance or functionality.Directory If you add a site from the CMA directory to the speed dial list and then later change the name of that site in the CMA, the speed dial entry name that is displayed on the Touch Panel maynot be updated.To fix this issue, reboot the codecs and the AV2 System Controller. Alternatively, from theHDX web UI, delete and re-add the renamed CMA site to the Speed Dial list.Microphones If you disconnect the Polycom Ceiling Microphone Arrays and then connect any microphones other than Ceiling Microphone Arrays, the proper stereo settings may be lost.If this occurs, launch the Polycom Telepresence Tool, make sure that all the HDX codecs areconnected, and then click Configure HDXs to set the microphones to their correct settings.Touch Panel/ User Interface If any of the HDX codecs are rebooted without rebooting the AV2 System Controller as well, the HDX UI remains onscreen.To avoid this issue, reboot the AV2 System Controller whenever any of the HDX codecs are rebooted. The VNOC, Service, and Site Administration teams are advised to reboot (power up) the AV2 System Controller after the HDX reboots (powers up) as part of the reset process or when recovering from a power failure. Placing a call without rebooting the AV2 System Controller will cause the Touch Panel to freeze.If you reboot the Primary HDX codec while the RPX is in an audio call (with the Help Desk, for example), the Hang Up button on the Touch Panel will freeze.To avoid this issue, reboot the AV2 System Controller when the Hang Up button enters that frozen state.Occasionally, the incorrect video format will be displayed on the Touch Panel Admin screen. To determine the correct video format:1. From the web UI, go to Admin Settings > Cameras.2. Check the Video Quality field for the camera being used. If VideoQuality=Sharpness, the video format is 1080p30; if Video Quality=Motion, thevideo format is 720p60.Alternatively, you can check the Video Format on the web UI Place a Call page.When initially loading the Crestron Touch Panel and then loading the AV2 System Controller, a Toolbox Results dialog box may appear at the end of the installation process. Although this dialog box displays an error message, the installation completed successfully.If users report that the Touch Panel seems to take an unusually long time to return directory information, check if there are LDAP entries in the directory that are no longer valid. If there are such entries, correct them.Where to Get the Latest Product InformationTo view the latest Polycom product documentation, visit the Support section of the Polycom website at .。
Synopsys DesignWare IP for HPC SoCs 2说明书
DesignWare IP for Cloud Computing SoCs2High-Performance ComputingToday’s high-performance computing (HPC) solutions provide detailed insights into the world around us and improve our quality of life. HPC solutions deliver the data processing power for massive workloads required for genome sequencing, weather modeling, video rendering, engineering modeling and simulation, medical research, big data analytics, and many other applications. Whether deployed in the cloud or on-premise, these solutions require high performance and low-latency compute, networking, and storage resources, as well as leading edge artificial intelligence capabilities. Synopsys provides a comprehensive portfolio of high-quality, silicon-proven IP that enables designers to develop HPC SoCs for AI accelerators, networking, and storage systems.Benefits of Synopsys DesignWare IP for HPC• Industry’s widest selection of high-performance interface IP , including DDR, PCI Express, CXL, CCIX, Ethernet, and HBM, offers high bandwidth and low latency to meet HPC requirements• Highly integrated, standards-based security IP solutions enable the most efficient silicon design and highest levels of data protection• Low latency embedded memories with standard and ultra-low leakage libraries, optimized for a range of cloud processors, provide a power- and performance-efficient foundation for SoCsIP for HPC SoCs in Cloud ComputingOverviewHyperscale cloud data centers continue to evolve due to tremendous Internet traffic growth from online collaboration, smartphones and other IoT devices, video streaming, augmented and virtual reality (AR/VR) applications, and connected AI devices. This is driving the need for new architectures for compute, storage, and networking such as AI accelerators, Software Defined Networks (SDNs), communications network processors, and solid state drives (SSDs) to improve cloud data center efficiency and performance. Re-architecting the cloud data center for these latest applications is driving the next generation of semiconductor SoCs to support new high-speed protocols to optimize data processing, networking, and storage in the cloud. Designers building system-on-chips (SoCs) for cloud and high performance computing (HPC) applications need a combination of high-performance and low-latency IP solutions to help deliver total system throughput. Synopsys provides a comprehensive portfolio of high-quality, silicon-proven IP that enables designers to develop SoCs for high-end cloud computing, including AI accelerators, edge computing, visual computing, compute/application servers, networking, and storage applications. Synopsys’ DesignWare ® Foundation IP , Interface IP , Security IP , and Processor IP are optimized for high performance, low latency, and low power, while supporting advanced process technologies from 16-nm to 5-nm FinFET and future process nodes.3Benefits of Synopsys DesignWare IP for AI Accelerators• Industry’s widest selection of high-performance interface IP , including DDR, USB, PCI Express (PCIe), CXL, CCIX, Ethernet, and HBM, offers high bandwidth and low latency to meet the high-performance requirements of AI servers• Highly integrated, standards-based security IP solutions enable the most efficient silicon design and highest levels of data protection• Low latency embedded memories with standard and ultra-low leakage libraries, optimized for a range of cloud processors, provide a power- and performance-efficient foundation for SoCsArtificial Intelligence (AI) AcceleratorsAI accelerators process tremendous amounts of data for deep learning workloads including training and inference which require large memory capacity, high bandwidth, and cache coherency within the overall system. AI accelerator SoC designs have myriad requirements, including high performance, low power, cache coherency, integrated high bandwidth interfaces that are scalable to many cores,heterogeneous processing hardware accelerators, Reliability-Availability-Serviceability (RAS), and massively parallel deep learning neural network processing. Synopsys offers a portfolio of DesignWare IP in advanced FinFET processes that address the specialized processing, acceleration, and memory performance requirements of AI accelerators.IP for Core AI AcceleratorBenefits of Synopsys DesignWare IP for Edge Computing• Industry’s widest selection of high-performanceinterface IP , including DDR, USB, PCI Express, CXL, CCIX, Ethernet, and HBM, offers high bandwidth and low latency to meet the high-performance requirements of edge computing servers• Highly integrated, standards-based security IP solutions enable the most efficient silicon design and highest levels of data protection• Low latency embedded memories with standard and ultra-low leakage libraries, optimized for a range of edge systems, provide a power- and performance-efficient foundation for SoCsIP for Edge Server SoCEdge ComputingThe convergence of cloud and edge is bringing cloud services closer to the end-user for richer, higher performance, and lower latency experiences. At the same time, it is creating new business opportunities for cloud service providers and telecom providers alike as they deliver localized, highly responsive services that enable new online applications.These applications include information security, traffic and materials flow management, autonomous vehicle control, augmented and virtual reality, and many others that depend on rapid response. For control systems in particular, data must be delivered reliably and with little time for change between data collection and issuing of commands based on that data.To minimize application latency, service providers are moving the data collection, storage, and processing infrastructure closer to the point of use—that is, to the network edge. To create the edge computing infrastructure, cloud service providers are partnering with telecommunications companies to deliver cloud services on power- and performance-optimized infrastructure at the network edge.ServersThe growth of cloud data is driving an increase in compute density within both centrally located hyperscale data centers and remote facilities at the network edge. The increase in compute density is leading to demand for more energy-efficient CPUs to enable increased compute capability within the power and thermal budget of existing data center facilities. The demand for more energy-efficient CPUs has led to a new generation of server CPUs optimized for performance/watt.This same increase in data volume is also driving demand for faster server interfaces to move data within and between servers. Movement of data within the server can be a major bottleneck and source of latency. Minimizing data movement as much as possible and providing high-bandwidth, low-latency interfaces for moving data when required are key to maximizing performance and minimizing both latency and power consumption for cloud and HPC applications. To improve performance, all internal server interfaces are getting upgrades:• DDR5 interfaces are moving to 6400 MBps• Doubling the bandwidth of PCIe interfaces as they move from PCIe 4.0 at 16GT/s to PCIe 5.0 at 32GT/s and PCIe 6.0 at 64GT/s • Compute Express Link (CXL) provides a cache coherent interface that runs over the PCIe electrical interface and reduces the amount of data movement required in a system by allowing multiple processors/accelerators to share data and memory efficiently• New high-speed SerDes technology at 56Gbps and 112Gbps using PAM4 encoding and supporting protocols enable faster interfaces between devices including die, chips, accelerators, and backplanesCloud server block diagram Benefits of Synopsys DesignWare IP for Cloud Compute Servers• Silicon-proven PCIe 5.0 IP is used by 90% of leadingsemiconductor companies• CXL IP is built on silicon-proven DesignWare PCIExpress 5.0 IP for reduced integration risk and supports storage class memory (also referred to as persistentmemory) for speed approaching that of DRAM withSSD-like capacity and cost• 112Gbps XSR/USR SerDes supports a wide range ofdata rates (2.5 to 112 Gbps) with area-optimized RXVisual ComputingAs cloud applications evolve to include more visual content, support for visual computing has emerged as an additional function of cloud infrastructure. Applications for visual computing include streaming video for business applications, online collaboration, on-demand movies, online gaming, and image analysis for ADAS, security, and other systems that require real-time image recognition. The proliferation of visual computing as a cloud service has led to the integration of high-performance GPUs into cloud servers, connected to the host CPU infrastructure via high-speed accelerator interfaces.Server-based graphics accelerator block diagram45NetworkingTraditional data centers use a tiered network topology consisting of switched Ethernet with VLAN tagging. This topology only defines one path to the network, which has traditionally handled north-south data traffic. The transition to a flat, two-tier leaf-spine hyperscale data center network using up to 800G Ethernet links enables virtualized servers to distribute workflows among many virtual machines, creating a faster, more scalable cloud data center environment.Smart network interface cards (NICs) combine hardware, programmable AI acceleration, and security resources to offload server processors, freeing the processors to run applications. Integrated security, including a root of trust, protects coefficient and biometric data as it moves to and from local memories. Smart NICs accelerate embedded virtual switch, transport offloads, and protocol overlay encapsulation/decapsulation such as NVGRE, VXLAN and MPLS. By offering dedicated hardware offloads including NVMe-over-Fabric (NVMEoF) protocols, Smart NICs free the server CPU to focus compute cycles on cloud application software and enable efficient data sharing across nodes for HPC workloads.Network switch SoCs enable cloud data center top-of-rack and end-of-row switches and routers to scale port densities and speeds to quickly adapt to changing cloud application workloads. By scaling port speeds from 10Gb Ethernet to 400/800G Ethernet and extending port densities from dozens to hundreds of ports, the latest generation Ethernet switch SoCs must scale to provide lowest latency and highest throughput flow control and traffic management. Synopsys’ DesignWare Interface IP portfolio supports high-performanceprotocols such as Ethernet, PCI Express, CXL, CCIX, USB, DDR, and HBM. DesignWare Interface IP is optimized to help designers meet the high-throughput, low-latency connectivity needs of cloud computing networking applications. Synopsys’ Foundation IP offers configurable embedded memories for performance, power, and area, as well as high-speed logic libraries for all processor munication service providers are turning towards server virtualization to increase efficiency, flexibility, and agility tooptimize network packet processing. The latest communications architecture uses Open vSwitch Offloads (OVS), OVS over Data Plane Development Kits (DPDK), network overlay virtualization, SR-IOV, and RDMA to enable software defined data center and Network Function Virtualization (NFV), acceleratingcommunications infrastructure. To achieve higher performance, communications network processors can accelerate OVS offloads for efficiency and security. Synopsys provides a portfolio of high-speed interface IP including DDR, HBM, Ethernet for up to 800G links, CXL for cache coherency, and PCI Express for up to 64GT/s data rates. DesignWare Security IP enables the highest levels of security encryption, and embedded ARC processors offer fast, energy-efficient solutions to meet throughput and QoS requirements. Synopsys’ Foundation IP delivers low-latency embedded memories with standard and ultra-low leakage libraries for a range of cloud processors.IP for Smart NIC in cloud computing networkIP for cloud computing network switchIP for communication network processorsStorageNVMe-based Solid-State Drives (SSDs) can utilize a PCIe interface to directly connect to the server CPU and function as a cache accelerator allowing frequently accessed data, or “hot” data, to be cached extremely fast. High-performance PCIe-based NVMe SSDs with extremely efficient input/ output operation and low-read latency improve server efficiency and avoid having to access the data through an external storage device. NVMe SSD server acceleration is ideal for high transaction applications such as AI acceleration or database queries queries, as well as HPC workloads that require high-performance, low-latency access to large data sets. PCIe-based NVMe SSDs not only reduce power and cost but also minimize area compared to hard disk drives (HDDs). Synopsys’ portfolio of DesignWare Interface IP for advanced foundry processes, supporting high-speed protocols such as PCI Express, USB, and DDR, are optimized to help designers meet their high-throughput, low-power, and low-latency connectivity for cloud computing storage applications. Synopsys’ Foundation IP offers configurable embedded memories for performance, power, and area, as well as high-speed logic libraries for all processor cores. Synopsys also provides processor IP ideally suited for flash SSDs.Storage• High-performance, low-latency PCI Express controllersand PHYs supporting data rates up to 64GT/s enableNVMe-based SSDs• High-performance, low-power ARC processors supportfast read/write speeds for NVMe-based SSDs• Portfolio of interface IP including Ethernet, USB,PCI Express, and DDR provides low latency andfast read/write operationsFigure 6: IP for cloud computing storage6©2021 Synopsys, Inc. All rights reserved. Synopsys is a trademark of Synopsys, Inc. in the United States and other countries. A list of Synopsys trademarks is available at /copyright.html . All other names mentioned herein are trademarks or registered trademarks of their respective owners.05/04/21.CS610890866-SG Bro-Cloud Computing Brochure.。
光立方开发板程序下载方法及调试过程
光立方开发板程序下载方法及调试过程光立方开发板是一款基于FPGA的硬件开发平台，可执行数字信号处理、数字信号生成、图像和视频处理等任务。
本文将重点介绍在Windows系统下如何下载光立方开发板程序并进行调试。
一、准备工作在开始下载程序之前，我们需要先进行一些准备工作：1.安装Xilinx ISE软件，它是运行并下载FPGA程序的关键软件。
2.下载并安装光立方驱动，并将光立方开发板连接到电脑。
3.下载并安装JTAG烧录器，以便通过JTAG接口向开发板烧录程序。
4.准备好FPGA程序文件。
二、下载程序1.打开Xilinx ISE软件，创建新的工程。
选择FPGA型号并设置工程路径和名称。
2.添加UCF约束文件和FPGA程序文件。
在工程目录下，新建一个.ucf文件，并在ISE工具栏中选择Process-> Generate Programming File。
3.选择工程路径，将程序文件转换成比特流的数据文件。
这个文件后面将用于烧录到开发板上。
4.打开JTAG烧录器软件，然后设置好开发板的连接端口和IP地址。
5.将光立方开发板与电脑连接，并插上电源。
6.在ISE软件中，选择Tools-> iMPACT打开JTAG烧录器。
7.在打开的iMPACT窗口中，选择new project并命名。
8.选择Cable Setup-> Add Cable，将连接端口和IP地址配置给烧录器。
9.在iMPACT软件中选择File-> Open..打开比特流数据文件。
10.右键单击Xilinx硬件设备图标，选择Program，然后程序将开始下载。
下载完成后，iMPACT软件将提示“Successful”.三、调试程序下载完程序后，我们可以开始调试程序。
1.在ISE中打开ISE design suite command prompt，运行openJTAG，连接开发板。
2.连接到开发板后，运行xmd命令，进入调试模式。
NVIDIA Hopper Architecture 兼容性指南说明书
i
ii
Hopper Compatibility Guide, Release 12.0
Hopper Compatibility Guide for CUDA Applications The guide to building CUDA applications for Hopper GPUs
Contents
4.2 Building Applications Using CUDA Toolkit 11.8 . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Independent Thread Scheduling Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1. Applications Built Using CUDA Toolkit 11.7 or Earlier
1
Hopper Compatibility Guide, Release 12.0
2
Contents
Chapter 1. About this Document
This application note, Hopper Architecture Compatibility Guide for CUDA Applications, is intended to help developers ensure that their NVIDIA® CUDA® applications will run on the NVIDIA® Hopper architecture based GPUs. This document provides guidance to developers who are familiar with programming in CUDA C++ and want to make sure that their software applications are compatible with Hopper architecture.
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
PC接口概要虚拟化工作组2010-7-261.概述PC机普遍采用三级总线结构，即HOST/PCI/ISA，目前已演变成HUB2.PCI总线从物理上看，PCI总线即一组信号线加上一个总线仲裁机构，各个设备（包括桥）挂接在PCI总线上并保证遵循PCI总线规范。
PCI总线是基于事务的，一般在一个主设备和一个从设备之间进行（特殊周期除外，它是一种广播事务）。
一个事务包括一个地址相（对于64位总线，包括2个地址相）和若干数据相，因此PCI天然地支持猝发传送，即启动一次总线可以传送一批数据。
PCI总线是一种多级树型总线，各级PCI总线间通过PCI/PCI桥相连。
为什么要使用PCI/PCI桥？跨总线的普通读写事务需要PCI/PCI桥的中转吗？2.1. PCI总线信号定义PCI总线信号可分为2类，一类是必须的信号，另一类是可选的信号。
必须的信号如AD[31..0]、C/BE[3..0]#、FRAME#等，可选的信号如REQ#/GNT#，从设备可以没有这2个信号，再如INTA#/INTB#/INTC#/INTD#，不产生中断的设备可以没有这4个信号。
当然，PCI扩展槽必须包含全部的信号，因为无法预计插在扩展槽上的设备会使用哪些信号。
2.2.PCI总线命令类型在事务的地址相，C/BE[3..0]#信号线给出总线周期的命令类型。
PCI共支持12种总线周期命令，分别是中断响应（0000）、特殊周期（0001）、I/O读（0010）、I/O写（0011）、存储器读（0110）、存储器写（0111）、配置周期读（1010）、配置周期写（1011）、存储器多行读（1100）、双地址周期（1101）、存储器行读（1110）、存储器写和使无效（1111）。
2.3.PCI地址空间及寻址PCI总线已成为PC系统的中心，HOST/PCI桥和PCI/ISA桥共同决定了PC系统的地址布局。
在使用PCI总线的PC系统中，存在3类独立的物理地址空间，分别是：存储器空间、I/O空间和配置空间。
存储器空间和I/O空间是统一编址的。
主存、PCI或ISA总线上的设备的存储器共同使用同一内存地址空间，内存地址空间的大小随处理器而异，对于i386平台可能是4GB（32位）、64GB（36位）或更高。
PCI或ISA总线上的设备的寄存器共同使用64KB的I/O地址空间。
配置空间是独立编址的，每个PCI设备的每个功能具有独立的一块配置空间，因此在访问设备的配置空间时，需在IDSEL#信号线上给出片选信号。
主设备在访问PCI存储器空间时，给出的地址必须是4字节对齐的，AD[1..0]用于给出猝发传送序，可以是线性增量模式或高速缓存行环绕模式。
主设备仅能在地址相中给出要访问的存储器区域的起始地址，以后AD[31..0]将用于传送数据，因此在每个数据相后，从设备应能按主设备要求的猝发传送序自动对地址进行修正。
主设备在访问PCI的I/O空间时，地址可以采用任意对齐方式。
主设备在访问PCI配置空间时，给出的地址必须是4字节的对齐的，AD[1..0]应为00或01，其中00表示要寻址的PCI设备位于本级PCI总线上，01表示要寻址的PCI设备位于某条下级PCI总线上。
2.4.主设备启动的PCI事务的终止当主设备完成它预定的任务时，事务可以正常终止。
为了防止一个主设备长时间地占用总线，每个主设备内部还设置了一个定时器LT（Latency Timer），当LT超时且GNT#为否定时，说明主设备已经占用了一定时间的总线且此时总线仲裁器批准了其他主设备的总线使用申请，则该主设备暂时终止当前事务，以后再继续当前事务。
当一个主设备启动一个总线事务，当5个时钟周期后，仍没有从设备肯定DEVSEL#信号来认领该事务，则主设备强行终止当前事务，称为主设备夭折（Master Abort）。
多数情况下，可能是主设备给出了一个PCI总线上不存在的地址。
2.5.从设备启动的PCI事务的终止从设备使用STOP#、TRDY#和DEVSEL#信号的组合来表达不同的从设备启动的PCI事务终止。
主设备启动了一个事务后，从设备认领了该事务，但从设备由于比较忙（初始数据相超过16个时钟周期，即从肯定FRAME#信号到初始数据相发生之间为16个周期）或从设备资源被锁定等原因，可能无法立即响应该事务，则从设备启动重试（Retry）来结束该事务，这是一种正常的事务终止。
主设备启动了一个事务后，从设备认领了该事务且完成了初始数据相，但不能完成时间期限内（8个时钟周期）完成后续的数据相，则从设备可以启动切断（Disconnect）来终止当前事务，这也是一种正常的事务终止。
当从设备认领了一个事务后，当它检测到一个致命错误或者它认为无能力完成该事务，就可以目标夭折（Target Abort）方式来终止该事务。
这是一种非正常的事务终止，主设备不应再重复发起这个事务。
2.6.设备选择及减译码当主设备启动一个事务后，总线上的各个设备应该对该事务地址相中给出的地址进行译码，译码选中的设备应肯定DEVSEL#信号，表明它正在响应该事务。
这种正常的译码方法称为“正译码”。
若设备能在地址相后的第1个时钟周期给出DEVSEL#信号，则称该设备为快速译码设备，若能在地址相后的第2个或第3个时钟周期给出DEVSEL#信号，则称该设备为中速译码设备或慢速译码设备。
若在地址相后的第3个时钟周期仍没有设备给出DEVSEL#信号，则采用“减译码”的设备应认领该事务。
通常采用“减译码”的设备是PCI/ISA桥，PCI/ISA桥同时也“正译码”对其内部某些寄存器的访问。
2.7.背靠背事务一般而言，在两个PCI总线事务之间需要插入一个IDLE周期用于总线周转。
为提高总线利用率，PCI支持背靠背的总线事务，即某些情况下，同一主设备可在总线上执行两个连续的总线事务，前一事务完成后，无需插入IDLE周期就可以立即启动后一事务。
有两类背靠背事务，一类是当主设备发起的前一个事务是写事务，且后一个事务的从设备与前一个事务的从设备相同时，无需任何条件就可以启动背靠背事务，因为前一事务的数据相和后一事务的地址相都由同一主设备驱动，前后两个事务的FRAME#、IRDY#也都由同一主设备驱动，而前后两个事务的DEVSEL#和TRDY#都由同一从设备驱动。
另一类背靠背事务是指：当主设备发起的前一个事务是写事务，但后一事务与前一事务不是寻址同一个从设备。
这种情况下，AD[31..0]、FRAME#、IRDY#信号线也无冲突，此时能否执行背靠背事务取决于从设备是否能满足以下两个要求：一是从设备能够识别没有IDLE周期开始的事务，并能捕获地址相中的信息；二是从设备以非FAST译码速度来使DEVSEL#有效。
从设备是否能够支持第二类背靠背事务反映在其配置空间的状态寄存器中，若该寄存器的Fast Back-to-Back Capable位为1，则从设备支持第二类背靠背事务，否则不支持。
主设备如何得知是否能够发起背靠背事务呢？在系统配置阶段，若BIOS检测到总线上的所有从设备均支持背靠背事务，则主设备将其配置空间的命令寄存器的Fast Back-to-Back Enable位置1。
两类背靠背事务都要求前一个事务是写事务，原因是明显的，如果前一个事务是读事务，则该事务结束时AD[31..0]是由从设备驱动，后一事务开始时必须插入IDLE周期，主设备才能向AD[31..0]上打入地址相。
2.8.特殊周期特殊周期（Special Cycle）用于在PCI总线上广播消息，这些消息可以通告处理器的状态，也可以用于在PCI设备间传递消息。
一个特殊周期同样具有一个地址相和若干数据相，在地址相阶段C/BE[3..0]为0001，但AD[31..0]上没有明确的地址信息，因而也没有从设备会发出DEVSEL#信号，感兴趣的从设备在IRDY#有效的第一个时钟锁存数据。
启动特殊周期的主设备在发出数据后，至少还要持续4个时钟周期才能结束该事务，以便各潜在的从设备有足够的时间去接受和处理这些消息。
特使周期事务是以一个Master-Abort方式来终止的，这对于特殊周期来说是一个正常的终止，配置空间状态寄存器中的Master-Abort位不会被置位。
特殊周期传递的典型的消息有SHUTDOWN（表示处理器正在进入停机模式）、HALT（表示处理器正执行一个Halt指令）等。
2.9.中断及中断响应周期PCI总线上有INTA~INTD共4根中断请求线。
并非所有的设备都能产生中断请求，如果设备PCI配置空间的“中断引脚”字段值为0，就表示设备不能产生中断。
如果设备能够产生中断，则设备PCI配置空间的“中断引脚”字段值为1、2、3或4，表示设备的中断请求引脚连接在了总线的哪根中断请求线上，这是由硬件决定的，因此“中断引脚”字段是个只读字段。
以上只是问题的一个方面，另外的问题是PCI总线的4根中断请求线最终连接到中断控制器8259的哪个引脚上，这是通过对南桥芯片中的PIR（PCI Interrupt Router）编程来控制的，具体来说就是设置南桥芯片的PIRQRC（PIRQ Route Control）寄存器，这是由软件决定的，决定的结果会写在设备PCI配置空间的“中断线”字段中。
注意，多个PCI总线中断引脚可能映射到同一个8259引脚。
不同种类的CPU有不同的中断机制，有不同的取得中断向量的方法。
以x86为例，当CPU响应中断后，会在HOST总线上发起中断响应周期，并由HOST/PCI 桥转换成PCI中断响应周期。
x86平台的中断控制器是在PCI/ISA桥中实现的，因此PCI/ISA桥会减译码中断响应周期，并在内部将PCI中断响应周期转换为两个8259能够识别的双脉冲，而后由8259提供中断相连，并经过PCI/ISA桥放到PCI总线上。
总体来说，PCI中断响应周期类似于一个PCI读周期。
2.10.配置周期每个PCI设备都有独立的配置空间，若设备是多功能设备，则每个功能具有独立的配置空间。
配置空间最大为256字节，其中的信息用于反映设备对PCI 总线操作及有关硬件的支持和状态。
配置空间使用配置空间读/写事务来访问。
通过对配置空间的访问，操作系统可以枚举出PCI总线上的所有设备。
生成PCI配置空间访问的根源在于处理器，处理器以某种特定的操作表达配置空间访问的请求，由Host/PCI桥生成PCI总线上的配置读/写周期。
配置周期可以跨PCI/PCI桥，由PCI/PCI桥把上一条PCI总线上的配置周期转化成下一条PCI总线上的配置周期。
PCI总线是一种分级总线，每级总线上可以有多个设备，每个设备可以有多个功能，而每个功能具有一个配置空间。
为访问到配置空间中的信息，处理器必须给出总线号、设备号、功能号和配置空间内地址偏移，为此处理器给出的地址如下图所示。