ISM6222_S11_04_AppLayer_Ch2

Content1CANopen 2 1.1EDS Files 2 1.2Support 2 1.3Features 2 1.3.1Basic information 2 1.3.2Basics based on CiA DS-301, V4.2.0 2 1.3.3Basics based on CiA DSP-406, V3.2 3 1.3.4Basics SDO communication 3 1.3.5Basics PDO communication based on CiA 301, V4.2.0 3 1.4Object Library 4 1.4.1Communication Profile Area based on DS 301 V4.2.0 4 1.4.2Device Profile Area 6 1.4.3Manufacturer specific Area 8 1.5Explanations to Object Library 9 1.5.1Object 0x6300 Encoder Cams 9 1.5.2Cam state registers 9 1.5.3Object 0x6400 Work Area 9 1.5.3.1Work Area Supervision 9 1.5.3.2Work Area State 9 1.6LSS / Layer Setting Service 9 1.6.1Configuration of Node-ID 10 1.6.2Configuration of Bit Rate 10 1.6.3Store Configuration Data 11 1.7SDO Services 11 1.7.1SDO Download 11 1.7.2SDO Upload 12 1.7.3SDO Abort 12 1.8Process Data PDO 12 1.8.1PDO Default Setting 12 1.8.2PDO Parameter Setting 12 1.9Error Handling 14 1.9.1Emergency Messages 14 1.10Error Objects 15 1.10.1Manufacturer-specific Status 15 1.11Non-Volatile Storage and Data Restoration 16 1.12Abbreviations 17 1.13Document Changes 171 CANopenThis document reflects the Novotechnik sensor protocol implementation of the standard CANopen protocol.A basic knowledge of the CAN Bus is required for a proper understanding of this document.Most of the definitions made are according to the following CiA Standard specifications.For making use of all the features that these specifications offer, a knowledge about them is absolutely necessary. The sensor supports the CANopen Communication profile DS-301, V4.2.0, Encoder profile DSP-406, V3.2 and Layer Setting Services (LSS) DSP-305, V1.1.2.1.1 EDS FilesFor integration in a common CANopen projecting tool, electronic data sheet (*.eds) files are provided.These files can be downloaded from the Novotechnik Web Site, see Downloads/Operating manualswhere also this document can be found.Electric data sheet see file Product series_CANopen.1.2 SupportIfyouhaveanyquestions,******************************************************.Electronic data sheets or user manuals for previous software versions are available on request.1.3 Features1.3.1 Basic informationVendor ID: 386 = 0x0182 (Novotechnik)Product code: TP1: 04035 = 0x0FC3, TH1: 04042 = 0x0FCA, TM1: 04228 = 0x1084, TF1: 04052 = 0x0FD4 Rev.-No.: f.e 196613 = 0x30005Serial No.: see product label, “YYMMxxxx”1.3.2 Basics based on CiA DS-301, V4.2.01.3.3 Basics based on CiA DSP-406, V3.21.3.4 Basics SDO communication1.3.5 Basics PDO communication based on CiA 301, V4.2.01.4 Object Library1.4.1 Communication Profile Area based on DS 301 V4.2.01) for 1 position marker2) for 2 position markers1.4.2 Device Profile Area* for 1 position marker: default value 0x01** for 1 position marker and product series TM1 / TF1: not available 1.4.3 Manufacturer specific Area1.5 Explanations to Object Library1.5.1 Object 0x6300 Encoder CamsEncoder cams are used to indicate if a position falls below or exceeds a defined value.1.5.2 Cam state registersCam active: the current position value is between the higher and lower cam-limitCam inactive: the current position value is not between the higher and lower cam-limit.The values for low limit (0x631x) and high limit (0x632x) regard the values for preset (0x6010) and measuring steps (0x6005). The value of hysteresis (0x633x) is added in direction of motion.Note: the cam high limit value can have a lower value than the cam low limitA change in cam state causes an EMCY message.The cam state objects (0x6300) are able to be mapped to the TPDOs.1.5.3 Object 0x6400 Work AreaIt is possible for encoders to define a so-called user defined working area.The main purpose for a work area is to get a high-priority information (via EMCY message) when the transducer’s p o-sition leaves its predefined working area.The actual work area information with work area low limit and work area high limit may be stored in object 0x6401 and 0x6402. This way, the area state object (0x6400) may also be used as software limit switches.1.5.3.1 Work Area SupervisionEach work area channel is fixedly linked to a position channel:1.5.3.2 Work Area StateThe values for low limit (0x6401) and high limit (0x6402) regard the values for preset (0x6010) and scaling (0x6501, 0x6502).A change in work area state causes an EMCY message.The work area state objects (0x6400) are able to be mapped to the TPDOs.1.6 LSS / Layer Setting ServiceTo configure the encoder via the LSS(according CiA DS 305) the encoder is handled as a slave, thePLC must have a LSS master functionality.A LSS-message is composed as follows:This applies to the COB-ID:• LSS-Master ⇒ LSS-Slave: 2021 (0x7E5)• LSS-Slave ⇒ LSS-Master: 2020 (0x7E4)LSS can only be used when the encoder is in the stopped status or pre-operational status.The NMT command for setting the encoder in stopped status is:To program via LSS the sensor has to be switched to LSS configuration state.There are two possible ways to do so:• Switch Mode Selective:only the addressed CANopen device is switched to the LSS configuration stateLSS requires data content in the following objects:Example:Vendor-ID (see index 1018/1) 0x0182 LSS-Command 0x40 Product code (see index 1018/2) 0x0BE0 LSS-Command 0x41 Rev.No. (see index 1018/3) 0x10003 LSS-Command 0x42 Serial-No. (see index 1018/4) 0x12345678 LSS-Command 0x43 After receiving the identification objects, the encoder answers with LSS-Command 0x44.• Switch Mode Global: all CANopen devices supporting LSS are switched to the LSS configuration stateWhen the CAN devices are in configuration state the Node-ID and/or the bit rate can be changed. 1.6.1 Configuration of Node-IDThe Node-ID can be programmed with the LSS-Command 0x11N ID: new Node-ID in the range of 1 (127)Err Code: 0: protocol successfully completed / 1: Node-ID out of rangeChange of Node-ID will cause:•Automatic alteration of COB-ID’s for SDO1, EMCY and Heartbeat and TPDOs.•Non-volatile Node-ID storage through …Store Configuration“ in the LSS mode configur ation.1.6.2 Configuration of Bit RateThe Bit Rate can be programmed with LSS-Command 0x13Table Index: 0x07: 20 kBaud0x06: 50 kBaud0x04: 125 kBaud0x03: 250 kBaud0x02: 500 kBaud0x01: 800 kBaud0x00: 1000 kBaudErr Code: 0: protocol successfully completed 1: Bit timing not supportedChange of Bit rate will cause:•The bit rate gets active•Non-volatile CAN bit rate storage through …Store Configuration“ in the LSS mode configuration1.6.3 Store Configuration DataThe LSS configuration data (Node-ID and Bit Rate) are stored to the non-volatile memory of the sen-sor using LSS-Command 0x17Err Code: 0: protocol successfully completed 2: storage media access error1.7 SDO ServicesService Data Objects SDO (according to CiA DS 301) manage the parameter data exchange, e.g. thenon-cyclical execution of the preset function.Parameters of device object library (object index/subindex see chapter 1.4 Object Library) can beread, written or stored by means of SDO.1.7.1 SDO DownloadThe SDO download service is used to configure the parameters.Command 0x2_: 0x22 write command, parameter to encoder0x23 write command, 4 Byte parameter to encoder0x27 write command, 3 Byte parameter to encoder0x2B write command, 2 Byte parameter to encoder0x2F write command, 1 Byte parameter to encoderCommand 0x60: confirmation: parameter receivedNODE-IDUsing writing to object 0x2000, non-volatile storage has to be done by w riting the“save”- signature (0x65766173) on object 0x1010/1 (TP1/TH1) or 0x1010/4 (TF1). These changes will become effective after a communication restart or a power up.Changing the Node-ID will affect all COB-IDs according to the “predefined co nnection s et”.Example: COB-ID TPDO1 = 0x180 + (Node-ID)BIT-RATEUsing writing to object 0x2001; non-volatile storage has to be done by writing the“save”- signature (0x65766173) on ob-ject 0x1010/1 (TP1/TH1) or 0x1010/4 (TF1). These changes will become effective after a communication restart or a power up.1.7.2 SDO UploadThe SDO upload service is used to read the parameters.Command 0x40: read command, parameters from encoderCommand 0x4_: 0x42 read command, parameter to encoder0x43 read command, 4 Byte parameter to encoder0x47 read command, 3 Byte parameter to encoder0x4B read command, 2 Byte parameter to encoder0x4F read command, 1 Byte parameter to encoder1.7.3 SDO AbortIf the SDO download or SDO upload service fails for any reason, the sensor responds with a SDO abort protocol. Abort Code: 0x06090011 subindex does not exist0x06090030 value exceeded0x06020000 object does not exist0x06010001 object is write only0x06010002 object is read only0x06060000 access error0x08000020 data transport error0x08000000 general error0x08000022 wrong state1.8 Process Data PDOProcess Data Objects (according CiA DS 301)manage the process data exchange, f.e the cyclical transmission of the position value. The process data exchange with the CANopen PDOs is a very slim process without protocol overhead.1.8.1 PDO Default Setting2 Transmit PDOs (TPDO) with each max. 8 bytes are provided:0x1800 TPDO1: default: Event-driven with event timer switched off (changeable to synchronous)0x1801 TPDO2: default: synchronous1.8.2 PDO Parameter SettingThe contents of the encoder-specific TPDOs can be configured by variable mapping according to cus-tomer´s requirements. This mapping has to be performed for the encoder as well as for the receiver.The PDO is limited to a maximum size of 8 bytes and 5 mappings per each PDO.Step 1: For changing of mapping, the sensor must be in properational mode and the MSB of PDOCOB-ID has to be set to 1 to deactivate it.Step 2: Clearing entries in mapping table of PDO1 (PDO2) => subindex 0x0 of object 1A00 (1A01)has to be set to 0x00.Step 3: Mapping of objects into PDOExample:A PDO shall be mapped in a way that the "current position", the "current speed" and the "current chiptemperature" are transmitted in one PDO .Mapping #1 “current position”:Mapping #2 “current speed”:Mapping #3: “current chip temperature”.Step 4: Setting entries in mapping table => subindex 0x0 of object 1A00 has to be set to the numbers of mapping en-tries (e.g. 0x03)Step 5: For re-activating the PDO, the MSB of PDO COB-ID has to be set to 0.Note:TPDO1 value for Event Timer must always be higher than the value for Inhibit Time (except for value 0).Failed sending of TPDOs can occur if:•more TPDOs shall be sent than the CANbus may accept due to insufficient CAN bit rate compared to TPDO/Event Timer •excessive bus load or unfavourable setting of COB-ID in the CANopen network prevents TPDOsending•Object 0x1800/5- event timer- is set to 0.1.9 Error HandlingDepending on the type of error occured, the sensor will react accordingly:* according to DS-301, see chapter 1.7 SDO Services** details see chapter 1.9.1 Emergency Messages1.9.1 Emergency MessagesCOB-ID EMCY in object 0x1014.Error-Register in object 0x1001.0x50xx Device Hardware 0x60xx Device Software 0x80xx Monitoring 0x90xx External Error1.10 Error Objects1.10.1 Manufacturer-specific StatusThe object 0x1002 shows the sensor status bit code and is used for internal process control purposes. For servicing this information can be requested via SDO (see chapter 1.7 SDO Services).Bit Definition (if bit value = 1)2 CAN Bus-Off Timer started0-1 NMT Condition of Sensor%11 stopped%10 operational%01 pro-operational%00 initialisation1.11 Non-Volatile Storage and Data RestorationDefault values for all data objects are stored in the non-volatile program memory.Data encryption to the non-volatile memory is only admitted in the pre-operational status.• Storage via LSS:Data must be stored through the LSS Service Configuration/Store while in LSS Configuration Mode (see chapter 1.6 LSS / Layer Setting Service)• Storage via SDO:Object 0x1010:Data is stored in the non-volatile memory during encryption of object 0x1010 with …save“ signature (0x65766173).Object 0x1011:Encryption of object 0x1011 with the sig nature …load“ (0x64616F6C) will upload data from the non-volatile memory. Default settings are being restored (see chapter 1.7 SDO Services).CAUTION: In case of custom programmed parameters like node-ID, averaging, bit rate etc. these will be reset to default in case of the corresponding reset command below (default values see chapter 1.4 Object Library).Object 0x1010 Object 0x1011 Subindex /1AllSubindex /2CommunicationSubindex /3ApplicationSubindex /4ManufacturerCOB-ID SyncGuard Time X XLife Time Factor X XHeartbeat Timer X XTPDO COB-ID D XTPDO Trans Typ X XTPDA Inhibit Time X XTPDO Event Timer X XTPDO Mapping X XNMT Startup X XNode-ID X (TP1/TH1) X (TF1) BitRate X (TP1/TH1) X (TF1) Number of position markers (only TP1 / TH1) XCustom (only TP1 / TH1) X Operating Parameters X XLinear Encoder Measuring Step Settings X XPreset Value X XCAM Enable X XCAM Polarity X XCAM Low Limit X XCAM High Limit X XCAM Hysterese XWork Area Low Limit XWork Area High Limit XX: data saved or restoredD: data set to default value• Delete via SDO Object 0x1010:Additionally to the functionality defined in CiA standard DS-301, CANopen library offers the possibility to delete data inthe non-volatile memory. Del ete process is initiated by sending the signature “kill” (0x6C6C696B) to object 0x1010.• Manufacturing Mode Object 0x1010▪Only TM1 series:If the sensor is out of function and the signature “boot” 0x746F6F62 in object 0x1000 (device type) is active, the sensor is in manufacturing mode. This mode can be left by power off-on or via the operationalcommand.1.12 AbbreviationsCAN Controller Area Networkch channelCOB-ID Communication Object Identifierconst constant parameter, only readableDLC Data Length CodeDS Draft StandardEMCY Emergency ServiceNMT Network-ManagementPDO Process Data ObjectPos Position (value)ro read only, parameter can changerw read/writeRx Novotechnik sensor is consumer of the CAN data frameRTR Remote Transmission RequestSDO Service Data ObjectSYNC Synchronisation messageTPDO Transmit Process Data ObjectTx Novotechnik sensor is producer of the CAN data frame1.13 Document ChangesRevision Changes Date WhoV00 First edition 16.07.14 VM/mm V07 1.2.5 / 1.3.1 object 1801x2: event driven transmission deleted for TPDO2. 1.3.1 objects:TPDO1 and TPDO2: name modified. 1.3.object 1800/2 and 1801/2 comment: synchronous1...240 instead 1...239, TPDO off: 0 added01.04.20 VM/mmV08 1.3.1 object 1010/4 user parameter data instead of manufacturer defined parameters.1.3.1 1010/5 added (Manufacturer data parameter). 1.10. signature kill 6C6C696B insteadof 6B696C6C, comment regarding manufacturing mode added21.01.21 VM/mmV09 1.2 Support added, all further chapter numbers changed1.8.3 Textual modifications 07.09.2117.11.22VM/mm。

创建定制 Oracle® Solaris 11.2 安装映像文件号码 E537582014 年 7 月版权所有 © 2008, 2014, Oracle 和/或其附属公司。

保留所有权利。

本软件和相关文档是根据许可证协议提供的，该许可证协议中规定了关于使用和公开本软件和相关文档的各种限制，并受知识产权法的保护。

除非在许可证协议中明确许可或适用法律明确授权，否则不得以任何形式、任何方式使用、拷贝、复制、翻译、广播、修改、授权、传播、分发、展示、执行、发布或显示本软件和相关文档的任何部分。

除非法律要求实现互操作，否则严禁对本软件进行逆向工程设计、反汇编或反编译。

此文档所含信息可能随时被修改，恕不另行通知，我们不保证该信息没有错误。

如果贵方发现任何问题，请书面通知我们。

如果将本软件或相关文档交付给美国政府，或者交付给以美国政府名义获得许可证的任何机构，必须符合以下规定：U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.本软件或硬件是为了在各种信息管理应用领域内的一般使用而开发的。

LwIP配置文件opt.h和lwipopts.h初步分析其实对于在Stellaris上应用lwIP最难的局部是如何去配置协议栈，使我们设计出来的web效劳器或者串口转以太网及TFTP等等应用能够在lwIP协议栈的根底之上，既要保持稳定、快速地运行，又要占用最少的内存，正所谓：又要马儿跑，又要马儿不吃草。

能跑是第一步，这一步呢，StellarisWare的例程根本上把这一步做得非常完美，丰富的公开源码的例程是一个很好的借鉴，很多例程稍稍修改就能弄到自己的设计当中去，比方在enet_Lwip 这个例程中我们只需要通过makefsfilefile转化一下，或者直接把我们设计的网页index.htm 〔注意使用.html后缀有可能是访问不到的，具体原因以后分析〕放到SD卡的根目录下就能跑了，但是我们还必须要考虑第二步，你虽然是照猫画虎的跑起来来了，但是忽略了一个很重要的问题，那就是enet_lwIP例程的lwip的配置是按照这个例程量体裁衣的，这个例程的网页是TI的介绍，你实际设计的网页肯定与它的例程不同，如果是动态网页就更应该注意了。

这就是为什么有的人没有把例程分析清楚，就直接从中间卸掉一块放到自己的工程里边去之后，会出现的一大堆莫名奇妙的问题，什么翻开网页的速度很慢啊？什么丢包啊，什么死机啦，什么跑到无限循环里边去了，总之很多。

那主要你没有去修改正配置文件，没有为你的工程去量体裁衣。

就算第二步你侥幸躲过去了，也能够稳定的运行，就像借一双别人的鞋，虽然自己穿着大了点，但是呢，也能跑得很快，很稳当，不过有点浪费材料了。

所以第三步我们要考虑的问题是，如何去配置lwip，使它去适合不同大小的脚，这就是本贴的主题lwIP的配置问题。

尤其是内存的配置，配置多了浪费，配置少了跑不了或者不稳定。

研究如何占用内存少，正式我们学习和采用lwip中最关键的问题。

否那么你可以直接去使用TCPnet，可配置的不太多，可以把主要的精力放到应用层上面去。

DATASHEETModbus Master/SlaveCommunication ModuleMVI56E-MCM/MCMXTThe MVI56E Communication Module allows for Modbus Master and/or Slaveconnectivity from Rockwell Automation® ControlLogix® processors to ModbusRTU/ASCII devices. Each MVI56E port can be configured as a Master or Slave.The MVI56E-MCM and MVI56E-MCMXT act as input/output modules on theControlLogix backplane, making Modbus data appear as I/O data to the processor.Two independently configurable serial ports can operate on the same or differentModbus networks. The MVI56E-MCM is designed for standard processapplications and the MVI56E-MCMXT is designed for the Logix-XT™ controlplatform, allowing it to operate in extreme environments. It can tolerate higheroperating temperatures, and has conformal coating to protect it from harsh orcaustic conditions.Features BenefitsBackward Compatibility ♦All MVI56E products are backward-compatible with earlier MVI56 modules allowing directreplacement without the need to change existing controller programs10,000 Word Database ♦Allows you to gather more data from your devices, which improves operationalperformance♦Enjoy Enhanced features and flexibility without incurring expensive reprogramming costs Add-On Instruction ♦Module configuration stored within the RSLogix™ 5000 project (ACD file)♦No additional programming or configuration software is required♦Add-On Instruction for RSLogix 5000 version 16 or higher cuts development time andcostsCIPconnect® Enabled ♦Facilitates remote user access across the ControlLogix backplane through RockwellAutomation’s 1756-ENBT module♦Configure, diagnose, and analyze process data and communications status♦Bridge through multiple ENBT/CNBT links to connect to MVI56E-MCMs installed in remotechassis for configuration and diagnosticsAdd-On Profile ♦Simplifies adding the module in an RSLogix 5000 projectConfigurationThe module configuration is defined in the Add on Instruction. The AOI is fullycommented, and includes user-defined data types, ladder rungs and controller tags. TheAOI can be used without modification for most application.The MVI56E-MCM User Manual and sample configuration provide a quick and easyexample with step-by-step instructions on how to move data through the module fromthe Modbus network to the processor.General Specifications∙Backward-compatible with previous MVI56-MCM version∙Single Slot - 1756 ControlLogix® backplane compatible∙10/100 MB Ethernet port for network configuration and diagnostics with Auto Cable Crossover Detection∙User-definable module data memory mapping of up to 10,000 16-bit registers∙4-character, scrolling, alphanumeric LED display of status and diagnostic data in plain English∙ProSoft Discovery Service (PDS) software finds the module on the network and assigns a temporary IP address to facilitate module accessFunctional SpecificationsThe MVI56E-MCM will operate on a Local or Remote rack (For remote rack applications with smaller data packet size please refer to the MVI56E-MCMR product)∙Supports Enron version of Modbus protocol for floating-point data transactions∙PCB includes powerful Modbus network analyzer∙Special functions (command control, event commands, status, and so on) are supported by message transfer (unscheduled) using the MSG instruction∙Error codes, network error counters, and port status data available in user data memorySlave SpecificationsThe MVI56E-MCM module accepts Modbus function code commands of 1, 2, 3, 4, 5, 6, 8, 15, 16, 17, 22, and 23 from an attached Modbus Master unit. A port configured as a Modbus Slave permits a remote Master to interact with all data contained in the module. This data can be derived from other Modbus Slave devices on the network, through a Master port, or from the ControlLogix processor.Master SpecificationsA port configured as a virtual Modbus Master device on the MVI56E-MCM module actively issues Modbus commands to other nodes on the Modbus network. Up to 325 commands are supported on each port. Additionally, the Master ports have an optimized polling characteristic that polls Slaves with communication problems less frequently. The ControlLogix processor ladder logic can issues commands directly from ladder logic or actively select commands from the command list to execute under ladder logic control.ControlLogix™ Modbus IntegrationGeneral Modbus SpecificationsCommunication Parameters Baud Rate: 110 baud to 115.2 kbpsStop Bits: 1 or 2Data Size: 7 or 8 bitsParity: None, Even, OddRTS Timing delays: 0 to 65535 milliseconds Modbus Modes RTU mode (binary) with CRC-16ASCII mode with LRC error checkingFloating Point Data Floating point data movement supported, includingconfigurable support for Enron and DanielimplementationsModbus Function Codes 1: Read Coils Status2: Read Input Status3: Read Holding Registers4: Read Input Registers5: Force (Write) Single Coil6: Preset (Write) Single Register8: Diagnostics15: Force (Write) Multiple Coils16: Preset (Write) Multiple Data Registers17: Report Slave ID22: Mask Write 4x Register23: Read/Write 4x RegistersModbus Master SpecificationsCommand List Up to 325 commands per Master port, each fullyconfigurable for function code, slave address, registerto/from addressing and word/bit count.Optimized Polling Configuration options allow Master ports andcommands to be optimized to poll slaves withcommunication problems less frequently.Command Status/Error Monitoring Command Status or Error codes are generated for each command as it executes, allowing careful monitoring of communication health between the Master and its Slaves.Slave Polling Control Master Port maintains a Slave Status list of all networkSlaves. Polling of each Slave may be disabled andenabled using this list.Modbus Slave SpecificationsFull Memory Access A port configured as a Modbus Slave permits a remoteMaster to read from or write to any of the 10,000registers that make up the user memory database. Multi-source Slave Data Data presented at the Slave port can be derived fromother Modbus Slave devices on a different networkthroug h the module’s Master port or from the processortag database.Node Address 1 to 247 (software selectable)Status Data Slave port error codes, counters and statuses areavailable separately for each port when configured as aSlave® products areHardware SpecificationsGeneralSpecification DescriptionBackplane Current Load 800 mA @ 5 Vdc3 mA @ 24 VdcOperating Temperature 0°C to 60°C (32°F to 140°F) - MVI56E-MCM-25°C to 70°C (-13°F to 158°F) - MVI56E-MCMXT Storage Temperature -40°C to 85°C (-40°F to 185°F)Extreme/Harsh Environment MVI56E-MCMXT comes with conformal coating Shock 30 g operational50 g non-operationalVibration: 5 g from 10 to 150 HzRelative Humidity 5% to 95% (without condensation)LED Indicators Battery Status (ERR)Application Status (APP)Module Status (OK)4-Character, Scrolling, Alpha-Numeric LED Display Shows Module, Version, IP, Port Master/Slave Setting, Port Status, and Error InformationDebug/Configuration Ethernet port (E1 - Config)Ethernet Port 10/100 Base-T, RJ45 Connector, for CAT5 cableLink and Activity LED indicatorsAuto-crossover cable detectionSerial Application ports (P1 & P2)Full hardware handshaking control, providing radio, modem, and multi-drop supportSoftware configurable communication parameters Baud rate: 110 baud to 115.2 kbpsRS-232, 485 and 422Parity: none, odd or evenData bits: 5, 6, 7, or 8Stop bits: 1 or 2RTS on/off delay: 0 to 65535 millisecondsSerial Applications Ports (P1, P2) RJ45 (DB-9M with supplied adapter cable) Configurable RS-232 hardware handshaking500V Optical isolation from backplaneRS-232, RS-422, RS-485 jumper-select, each port RX (Receive) and TX (Transmit) LEDs, each portShipped with Unit RJ45 to DB-9M cables for each serial port5 foot Ethernet Straight-Thru Cable (Gray) Agency Approvals and CertificationsAgencyRoHSATEXCSACECSA CB SafetycULusGOST-RLloyds® offers a full。

© 2017 NXP B.V.SCM-i.MX 6 Series Yocto Linux User'sGuide1. IntroductionThe NXP SCM Linux BSP (Board Support Package) leverages the existing i.MX 6 Linux BSP release L4.1.15-2.0.0. The i.MX Linux BSP is a collection of binary files, source code, and support files that can be used to create a U-Boot bootloader, a Linux kernel image, and a root file system. The Yocto Project is the framework of choice to build the images described in this document, although other methods can be also used.The purpose of this document is to explain how to build an image and install the Linux BSP using the Yocto Project build environment on the SCM-i.MX 6Dual/Quad Quick Start (QWKS) board and the SCM-i.MX 6SoloX Evaluation Board (EVB). This release supports these SCM-i.MX 6 Series boards:• Quick Start Board for SCM-i.MX 6Dual/6Quad (QWKS-SCMIMX6DQ)• Evaluation Board for SCM-i.MX 6SoloX (EVB-SCMIMX6SX)NXP Semiconductors Document Number: SCMIMX6LRNUGUser's GuideRev. L4.1.15-2.0.0-ga , 04/2017Contents1. Introduction........................................................................ 1 1.1. Supporting documents ............................................ 22. Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloX .. 2 2.1. Host setup ............................................................... 2 2.2. Host packages ......................................................... 23.Building Linux OS for SCM i.MX platforms .................... 3 3.1. Setting up the Repo utility ...................................... 3 3.2. Installing Yocto Project layers ................................ 3 3.3. Building the Yocto image ....................................... 4 3.4. Choosing a graphical back end ............................... 4 4. Deploying the image .......................................................... 5 4.1. Flashing the SD card image .................................... 5 4.2. MFGTool (Manufacturing Tool) ............................ 6 5. Specifying displays ............................................................ 6 6. Reset and boot switch configuration .................................. 7 6.1. Boot switch settings for QWKS SCM-i.MX 6D/Q . 7 6.2. Boot switch settings for EVB SCM-i.MX 6SoloX . 8 7. SCM uboot and kernel repos .............................................. 8 8. References.......................................................................... 8 9.Revision history (9)Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloX1.1. Supporting documentsThese documents provide additional information and can be found at the NXP webpage (L4.1.15-2.0.0_LINUX_DOCS):•i.MX Linux® Release Notes—Provides the release information.•i.MX Linux® User's Guide—Contains the information on installing the U-Boot and Linux OS and using the i.MX-specific features.•i.MX Yocto Project User's Guide—Contains the instructions for setting up and building the Linux OS in the Yocto Project.•i.MX Linux®Reference Manual—Contains the information about the Linux drivers for i.MX.•i.MX BSP Porting Guide—Contains the instructions to port the BSP to a new board.These quick start guides contain basic information about the board and its setup:•QWKS board for SCM-i.MX 6D/Q Quick Start Guide•Evaluation board for SCM-i.MX 6SoloX Quick Start Guide2. Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloXThis section describes how to obtain the SCM-related build environment for Yocto. This assumes that you are familiar with the standard i.MX Yocto Linux OS BSP environment and build process. If you are not familiar with this process, see the NXP Yocto Project User’s Guide (available at L4.1.15-2.0.0_LINUX_DOCS).2.1. Host setupTo get the Yocto Project expected behavior on a Linux OS host machine, install the packages and utilities described below. The hard disk space required on the host machine is an important consideration. For example, when building on a machine running Ubuntu, the minimum hard disk space required is about 50 GB for the X11 backend. It is recommended that at least 120 GB is provided, which is enough to compile any backend.The minimum recommended Ubuntu version is 14.04, but the builds for dizzy work on 12.04 (or later). Earlier versions may cause the Yocto Project build setup to fail, because it requires python versions only available on Ubuntu 12.04 (or later). See the Yocto Project reference manual for more information.2.2. Host packagesThe Yocto Project build requires that the packages documented under the Yocto Project are installed for the build. Visit the Yocto Project Quick Start at /docs/current/yocto-project-qs/yocto-project-qs.html and check for the packages that must be installed on your build machine.The essential Yocto Project host packages are:$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-devThe i.MX layers’ host packages for the Ubuntu 12.04 (or 14.04) host setup are:$ sudo apt-get install libsdl1.2-dev xterm sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff curl lzop asciidocThe i.MX layers’ host packages for the Ubuntu 12.04 host setup are:$ sudo apt-get install uboot-mkimageThe i.MX layers’ host packages for the Ubuntu 14.04 host s etup are:$ sudo apt-get install u-boot-toolsThe configuration tool uses the default version of grep that is on your build machine. If there is a different version of grep in your path, it may cause the builds to fail. One workaround is to rename the special versi on to something not containing “grep”.3. Building Linux OS for SCM i.MX platforms3.1. Setting up the Repo utilityRepo is a tool built on top of GIT, which makes it easier to manage projects that contain multiple repositories that do not have to be on the same server. Repo complements the layered nature of the Yocto Project very well, making it easier for customers to add their own layers to the BSP.To install the Repo utility, perform these steps:1.Create a bin folder in the home directory.$ mkdir ~/bin (this step may not be needed if the bin folder already exists)$ curl /git-repo-downloads/repo > ~/bin/repo$ chmod a+x ~/bin/repo2.Add this line to the .bashrc file to ensure that the ~/bin folder is in your PATH variable:$ export PATH=~/bin:$PATH3.2. Installing Yocto Project layersAll the SCM-related changes are collected in the new meta-nxp-imx-scm layer, which is obtained through the Repo sync pointing to the corresponding scm-imx branch.Make sure that GIT is set up properly with these commands:$ git config --global "Your Name"$ git config --global user.email "Your Email"$ git config --listThe NXP Yocto Project BSP Release directory contains the sources directory, which contains the recipes used to build, one (or more) build directories, and a set of scripts used to set up the environment. The recipes used to build the project come from both the community and NXP. The Yocto Project layers are downloaded to the sources directory. This sets up the recipes that are used to build the project. The following code snippets show how to set up the SCM L4.1.15-2.0.0_ga Yocto environment for the SCM-i.MX 6 QWKS board and the evaluation board. In this example, a directory called fsl-arm-yocto-bsp is created for the project. Any name can be used instead of this.Building Linux OS for SCM i.MX platforms3.2.1. SCM-i.MX 6D/Q quick start board$ mkdir fsl-arm-yocto-bsp$ cd fsl-arm-yocto-bsp$ repo init -u git:///imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m scm-imx-4.1.15-2.0.0.xml$ repo sync3.2.2. SCM-i.MX 6SoloX evaluation board$ mkdir my-evb_6sxscm-yocto-bsp$ cd my-evb_6sxscm-yocto-bsp$ repo init -u git:///imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m scm-imx-4.1.15-2.0.0.xml$ repo sync3.3. Building the Yocto imageNote that the quick start board for SCM-i.MX 6D/Q and the evaluation board for SCM-i.MX 6SoloX are commercially available with a 1 GB LPDDR2 PoP memory configuration.This release supports the imx6dqscm-1gb-qwks, imx6dqscm-1gb-qwks-rev3, and imx6sxscm-1gb-evb. Set the machine configuration in MACHINE= in the following section.3.3.1. Choosing a machineChoose the machine configuration that matches your reference board.•imx6dqscm-1gb-qwks (QWKS board for SCM-i.MX 6DQ with 1 GB LPDDR2 PoP)•imx6dqscm-1gb-qwks-rev3 (QWKS board Rev C for SCM-i.MX 6DQ with 1GB LPDDR2 PoP) •imx6sxscm-1gb-evb (EVB for SCM-i.MX 6SX with 1 GB LPDDR2 PoP)3.4. Choosing a graphical back endBefore the setup, choose a graphical back end. The default is X11.Choose one of these graphical back ends:•X11•Wayland: using the Weston compositor•XWayland•FrameBufferSpecify the machine configuration for each graphical back end.The following are examples of building the Yocto image for each back end using the QWKS board for SCM-i.MX 6D/Q and the evaluation board for SCM-i.MX 6SoloX. Do not forget to replace the machine configuration with what matches your reference board.3.4.1. X11 image on QWKS board Rev C for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-x11 imx6dqscm-1gb-qwks-rev3 source fsl-setup-release.sh -b build-x11$ bitbake fsl-image-gui3.4.2. FrameBuffer image on evaluation board for SCM-i.MX 6SX$ DISTRO=fsl-imx-fb MACHINE=imx6sxscm-1gb-evb source fsl-setup-release.sh –b build-fb-evb_6sxscm$ bitbake fsl-image-qt53.4.3. XWayland image on QWKS board for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-xwayland MACHINE=imx6dqscm-1gb-qwks source fsl-setup-release.sh –b build-xwayland$ bitbake fsl-image-gui3.4.4. Wayland image on QWKS board for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-wayland MACHINE=imx6dqscm-1gb-qwks source fsl-setup-release.sh -b build-wayland$ bitbake fsl-image-qt5The fsl-setup-release script installs the meta-fsl-bsp-release layer and configures theDISTRO_FEATURES required to choose the graphical back end. The –b parameter specifies the build directory target. In this build directory, the conf directory that contains the local.conf file is created from the setup where the MACHINE and DISTRO_FEATURES are set. The meta-fslbsp-release layer is added into the bblayer.conf file in the conf directory under the build directory specified by the –e parameter.4. Deploying the imageAfter the build is complete, the created image resides in the <build directory>/tmp/deploy/images directory. The image is (for the most part) specific to the machine set in the environment setup. Each image build creates the U-Boot, kernel, and image type based on the IMAGE_FSTYPES defined in the machine configuration file. Most machine configurations provide the SD card image (.sdcard), ext4, and tar.bz2. The ext4 is the root file system only. The .sdcard image contains the U-Boot, kernel, and rootfs, completely set up for use on an SD card.4.1. Flashing the SD card imageThe SD card image provides the full system to boot with the U-Boot and kernel. To flash the SD card image, run this command:$ sudo dd if=<image name>.sdcard of=/dev/sd<partition> bs=1M && syncFor more information about flashing, see “P reparing an SD/MMC Card to Boot” in the i.MX Linux User's Guide (document IMXLUG).Specifying displays4.2. MFGTool (Manufacturing Tool)MFGTool is one of the ways to place the image on a device. To download the manufacturing tool for the SCM-i.MX 6D/Q and for details on how to use it, download the SCM-i.MX 6 Manufacturing Toolkit for Linux 4.1.15-2.0.0 under the "Downloads" tab from /qwks-scm-imx6dq. Similarly, download the manufacturing tool for the SCM-i.MX 6SoloX evaluation board under the "Downloads" tab from /evb-scm-imx6sx.5. Specifying displaysSpecify the display information on the Linux OS boot command line. It is not dependent on the source of the Linux OS image. If nothing is specified for the display, the settings in the device tree are used. Find the specific parameters in the i.MX 6 Release Notes L4.1.15-2.0.0 (available at L4.1.15-2.0.0_LINUX_DOCS). The examples are shown in the following subsections. Interrupt the auto-boot and enter the following commands.5.1.1. Display options for QWKS board for SCM-i.MX 6D/QHDMI displayU-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'U-Boot > run bootcmd5.1.2. Display options for EVB for SCM-i.MX 6SXNote that the SCM-i.MX 6SX EVB supports HDMI with a HDMI accessory card (MCIMXHDMICARD) that plugs into the LCD connector on the EVB.Accessory boards:•The LVDS connector pairs with the NXP MCIMX-LVDS1 LCD display board.•The LCD expansion connector (parallel, 24-bit) pairs with the NXP MCIMXHDMICARD adapter board.LVDS displayU-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} ${dmfc} video=mxcfb0:dev=ldb,1024x768M@60,if=RGB666 ldb=sep0'U-Boot > run bootcmdHDMI display (dual display for the HDMI as primary and the LVDS as secondary)U-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24video=mxcfb1:dev=ldb,LDBXGA,if=RGB666'U-Boot > run bootcmdLCD displayu-boot > setenv mmcargs 'setenv bootargs ${bootargs}root=${mmcroot} rootwait rw video=mxcfb0:dev=lcd,if=RGB565'u-boot> run bootcmd6. Reset and boot switch configuration6.1. Boot switch settings for QWKS SCM-i.MX 6D/QThere are two push-button switches on the QWKS-SCMIMX6DQ board. SW1 (SW3 for QWKS board Rev B) is the system reset that resets the PMIC. SW2 is the i.MX 6Dual/6Quad on/off button that is needed for Android.There are three boot options. The board can boot either from the internal SPI-NOR flash inside the SCM-i.MX6Dual/6Quad or from either of the two SD card slots. The following table shows the switch settings for the boot options.Table 1.Boot configuration switch settingsBoot from top SD slot (SD3)Boot from bottom SD slot (SD2)Boot from internal SPI NORDefault1.References6.2. Boot switch settings for EVB SCM-i.MX 6SoloXThis table shows the jumper configuration to boot the evaluation board from the SD card slot SD3.7. SCM uboot and kernel repositoriesThe kernel and uboot patches for both SCM-i.MX 6 QWKS board and evaluation board are integrated in specific git repositories. Below are the git repos for SCM-i.MX 6 uboot and kernel:uBoot repo: /git/cgit.cgi/imx/uboot-imx.gitSCM Branch: scm-imx_v2016.03_4.1.15_2.0.0_gakernel repo: /git/cgit.cgi/imx/linux-imx.gitSCM branch: scm-imx_4.1.15_2.0.0_ga8. References1.For details about setting up the Host and Yocto Project, see the NXP Yocto Project User’s Guide(document IMXLXYOCTOUG).2.For information about downloading images using U-Boot, see “Downloading images usingU-Boot” in the i.MX Linux User's Guide (document IMXLUG).3.For information about setting up the SD/MMC card, see “P reparing an SD/MMC card to boot” inthe i.MX Linux User's Guide (document IMXLUG).9. Revision historyDocument Number: SCMIMX6LRNUGRev. L4.1.15-2.0.0-ga04/2017How to Reach Us: Home Page: Web Support: /supportInformation in this document is provided solely to enable system and softwareimplementers to use NXP products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits based on the information in this document. NXP reserves the right to make changes without further notice to any products herein.NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does NXP assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequentia l or incidental damages. “Typical”parameters that may be provided in NXP data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including “typicals,” must be valida ted for each customer application by customer’s technical experts. NXP does not convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the following address: /SalesTermsandConditions .NXP, the NXP logo, NXP SECURE CONNECTIONS FOR A SMARTER WORLD, Freescale, and the Freescale logo are trademarks of NXP B.V. All other product or service names are the property of their respective owners.ARM, the ARM Powered logo, and Cortex are registered trademarks of ARM Limited (or its subsidiaries) in the EU and/or elsewhere. All rights reserved. © 2017 NXP B.V.。

SmartFusion2 and IGLOO2 Embedded Nonvolatile Memory (eNVM) SimulationSmartFusion2 and IGLOO2 Embedded Nonvolatile Memory (eNVM) Simulation Table of ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31NVM Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42eNVM Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 eNVM Internal Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 eNVM Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63eNVM Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Writing to the eNVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Reading from the eNVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Erasing the eNVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Product Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Customer Technical Support Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Contacting the Customer Technical Support Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 ITAR Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12IntroductionThe SmartFusion2 MSS has an on-chip embedded non-volatile memory (eNVM). You can access theeNVM using the eNVM controller. This controller is a slave of the MSS AHB Switch Matrix and canreceive commands from a master located either inside the MSS (i.e., Cortex M3) or a master located inthe fabric via the Fabric Interface Controllers (FIC_0 or FIC_1).This document describes the steps required to simulate eNVM operation.1 – NVM ConfigurationYou can configure the eNVM using the MSS eNVM configurator. Using the eNVM configurator, you can:•Add Serialization and Data Storage clients•Supply data files that will be used to initialize the eNVM block when you program your device For details, and to learn about the eNVM configurator options, refer to the SmartFusion2 MSS eNVMConfiguration Guide.2 – eNVM OrganizationThis chapter describes the internal organization of the eNVM, and how it is accessed by Masters in the MSS and the FPGA fabric.The eNVM is a nonvolatile (flash) memory that is divided into pages. Each page of the eNVM contains 128 bytes (accessible as 32 words).The total capacity of the eNVM varies with the SmartFusion2 or IGLOO2 device you are using. Table 2-1 provides a list of devices and eNVM capacities.Note:On the larger (M2S/M2GL090/150) devices, the eNVM is composed of two blocks (eNVM_0 andeNVM_1), which are accessed separatelyeNVM Internal OrganizationEach eNVM is divided into pages. One page is a 128-byte section of the eNVM. The eNVM is word-addressable. Table 2-2 and Table 2-3 list the ranges of the eNVM pages for different devices.Table 2-1 • eNVM Capacity by Device DeviceeNVM capacity (bytes)SmartFusion2M2S0051 x 128KB M2S010, M2S025, M2S050, M2S0601 x 256KB M2S090, M2S1502 x 256KB IGLOO2M2GL0051 x 128KB M2GL010, M2GL025, M2GL050, M2GL0601 x 256KB M2GL090, M2GL1502 x 256KBTable 2-2 • SmartFusion2 eNVM Page RangesDevice Capacity Total Pages (User + Reserved)Total Reserved Pages User Page Range (Available to User) Reserved Page Range(Unavailable to User)M2S005128KB1024160-10071008-1023M2S010, M2S025, M2S050256KB2048160-20312032-2047M2S050T_ES256KB2048330-20142015-2047Note:For IGLOO2, Reserved Pages are used by the HPMS to store Certificate/Digest and Peripheralconfiguration data for SERDES, FDDR and MDDR. For SmartFusion2, Reserved Pages are used by the MSS to store Certificate/Digest only. Reserved pages are for internal use only and not available to the user.eNVM AccessThe SmartFusion2 eNVM is part of the MSS. It is accessed via the eNVM Controller, which is a slave of the MSS AHB Switch Matrix (Figure 2-1). Masters of the AHB Switch Matrix (MSS Cortex-M3), a Fabric Master (via the FIC32_0/1 interfaces) can read from and write to the eNVM.•All eNVM accesses are performed using AHB read and write transactions•Irrespective of the master initiating the access, the procedure to read and write the eNVM remains the sameM2S060256KB 2048640-19831984-2047M2S090, M2S150512KB4096640-40314032-4095Table 2-2 • SmartFusion2 eNVM Page Ranges (continued)Device Capacity Total Pages (User + Reserved)Total Reserved Pages User Page Range (Available to User) Reserved Page Range(Unavailable to User)Table 2-3 • IGLOO2 eNVM Page RangesDevice Capacity Total Pages (User+Reserved)Total Reserved Pages User Page Range (Available to User) Reserved PageRange(Unavailable to User)M2GL005128KB 1024480-975976-1023M2GL010,M2GL025, M2GL050256KB 2048480-19992000-2047M2GL060256KB 2048960-19511952-2047M2GL090, M2GL150512KB4096960-39994000-4095Figure 2-1 • eNVM Access3 – eNVM SimulationThe eNVM simulation model fully models the commands and bus transactions required to access theeNVM on silicon.To access the eNVM, you must initiate AMBA transactions using either the Cortex-M3 Master or a FabricMaster (Using the FIC Slave Interface).Before accessing the eNVM, Microsemi recommends that you poll bit #0 of the eNVM status register(address: 0x60080120). If this bit is 0, the eNVM is busy. Wait until this bit becomes 1 to access theeNVM.Writing to the eNVMYou can simulate writing to eNVM from the following bus masters:•Cortex-M3 (SmartFusion2 only)•Fabric AHB Master (via FIC_0 or FIC_1)•Fabric APB Master (via FIC_0 or FIC_1)Writes to the eNVM are buffered. You must first write your data into the write data buffer (WDB) and thenuse a single command to commit (program) your data into one page of the eNVM.The sequence of transactions required to program the eNVM is:1.Request exclusive access to the eNVM control register set. This is necessary to ensure that noother Master can write to the eNVM at the same time, and is done by writing 0x1 to theREQACCESS register (address: 0x600801FC)The Master that is requesting exclusive access must then check that the request has beengranted by reading back from the REQACCESS register.–On read back, check bit #2 (counting up from 0). If it is 1, the request was successful.–If bit #2 is 0, the request for exclusive access was denied, and the eNVM cannot be written at this time.2.Write your data into the WDB; the WDB is a byte-addressable 1024-bit buffer. Its base address is:0x60080080 for eNVM_0 and at 0x600C0080 for eNVM_1.pute values of bits that will be written into the eNVM Command Register:–Bits 31-24 should be 0x80 (Hex) to specify the ProgramADS command code.–Bits [17:7] corresponds to the eNVM page address to be written–Bits [23:18] and [6:0] are not relevant for the ProgramADS command and can be written 0x0 (Hex)For details about what values to use, refer to Table 4-7 in the SmartFusion2 Microcontroller SubsystemUser's Guide.4.Write eNVM Command Register (address: 0x60080148) with the data computed in Step 3 aboveNote that the eNVM will not respond to further commands until the write is completeNote that on silicon, writing a page of the eNVM may take up to 8ms, but in simulation, this stepcompletes in a few clock cycles5.Release exclusive access to the eNVM control register set by writing 0x0 to the REQACCESSregister.The following is an example of a Cortex-M3 BFM script configured to write a block of data to eNVM0.Assume that you want to write two 32-bit words 0xaaaaaaaa and 0xbbbbbbbb into page 25 of the eNVM.#1. Wait for bit 0 of status register to become 1pollbit w 0x60080120 0x0 0 1#2. Request exclusive access to the eNVM control register setwrite w 0x600801fc 0x0 0x1#2b. Readcheck to see if access has been grantedreadcheck w 0x600801fc 0x0 0x5 (for MSS master)#The simulation will fail if access has not been granted#3. Write data to the WDBwrite w 0x60080080 0x0 0xaaaaaaaawrite w 0x60080080 0x4 0xbbbbbbbb#4. Compute the value of the command register: Bits[31-19]: '0000 1000 0000 0'#Bits[18-7]: '000 0000 1100 1' (25 in decimal)#Bits[6-0]: '000 0000'#Complete string: 0x08000c80#5. Write the command registerwrite w 0x60080148 0x0 0x08000c80#6. Release exclusive access to the eNVMwrite w 0x600801fc 0x0 0x0Refer to the SmartFusion2 FPGA Microcontroller Subsystem BFM Simulation Guide for generalguidelines on BFM simulations for SmartFusion2 designs.Reading from the eNVMThe eNVM can be read as a byte-addressable random access memory. The address range for reads isgiven in Table3-1.Table3-1 • eNVM Read Address RangesENVM0ENVM1Base Address0x600000000x60040000Max read address (005)0x6002FFFF N/AMax read address (010,025,050, 060)0x6003FFFF N/AMax read address (090,150)0x6003FFFF 0x6007FFFF The eNVM is accessible directly, similar to a random access memory. The address ranges of the eNVMsare given in Table3-1. To read any location in the eNVM, first compute the offset address as follows:Offset Address = (Page #) * 0x80 + (Address of Word in Page)The Base Address will be either 0x60000000 or 0x60040000, depending on whether you are accessingeNVM_0 or eNVM_1.The following is an example that demonstrates how to read data from eNVM_0. In the example above,two 32-bit words "0xaaaaaaaa" and "0xbbbbbbbb" were written into addresses 0x0 and 0x4 of Page# 25of eNVM_0. The example below shows an attempt to read the same two words back.#1. Wait for bit 0 of status register to become 1pollbit w 0x60080120 0x0 0 1#2 Read first word#2a Base Address = 0x60000000#2b Word in Page = 0x0 (first word). Page Number = 25.# Offset Address = 0x80 * 25 + 0x0 = 0xc80#2c Read and compare word to what was written in Fig. 2readcheck w 0x60000000 0xc80 0xaaaaaaaa#3 Read second word#3a Base Address = 0x60000000#3b Word in Page = 0x4 (second word). Page Number = 25.# Offset Address = 0x80 * 25 + 0x4 = 0xc84#3c Read and compare word to what was written in Fig. 2readcheck w 0x60000000 0xc84 0xbbbbbbbbErasing the eNVMYou can also erase the contents of the eNVM, one page at a time using the following steps:1.Request exclusive access to the eNVM control register set. This is necessary to ensure that noother Master can write to the eNVM at the same time. This is done by writing 0x1 to theREQACCESS register (address: 0x600801FC). The Master that is requesting exclusive accessmust then check that the request has been granted by reading back from the REQACCESSregister.–On read back, check bit #2 (counting up from 0). If it is 1, the request was successful.–If bit #2 is 0, the request for exclusive access was denied, and the eNVM cannot be written at this time.pute values of bits that will be written into the eNVM Command Register:–Bits 31-20: "0x020"–Bit19:0–Bits 18-7 corresponds to the number of the page to be written–Bits 6-0: “0x0"3.Write eNVM Command Register (address: 0x60080148) with the data computed in the previousstep.The eNVM will not respond to further commands until the erase is complete.Note that on silicon, erasing a page of the eNVM may take up to 8ms, but in simulation, this stepcompletes in a few clock cycles.4.Release exclusive access to the eNVM control register set by writing 0x0 to the REQACCESSregister.The example below shows a sequence of instructions to erase page #25 of eNVM_0.#1. Wait for bit 0 of status register to become '1'pollbit w 0x60080120 0x0 0 1#2. Request exclusive access to the eNVM control register setwrite w 0x600801fc 0x0 0x1#2c. Readcheck to see if access has been grantedreadcheck w 0x600801fc 0x0 0x5 (for MSS master)#The simulation will fail if access has not been granted#3. Compute the value of the command register: Bits[31-19]: '0000 0010 0000 0'#Bits[18-7]: '000 0000 1100 1' (25 in decimal)#Bits[6-0]: '000 0000'#Complete string: 0x02000c80#4. Write the command registerwrite w 0x60080148 0x0 0x02000c80#5. Release exclusive access to the eNVMwrite w 0x600801fc 0x0 0x04 – Product SupportMicrosemi SoC Products Group backs its products with various support services, including CustomerService, Customer Technical Support Center, a website, electronic mail, and worldwide sales offices.This appendix contains information about contacting Microsemi SoC Products Group and using thesesupport services.Customer ServiceContact Customer Service for non-technical product support, such as product pricing, product upgrades,update information, order status, and authorization.From North America, call 800.262.1060From the rest of the world, call 650.318.4460Fax, from anywhere in the world, 408.643.6913Customer Technical Support CenterMicrosemi SoC Products Group staffs its Customer Technical Support Center with highly skilledengineers who can help answer your hardware, software, and design questions about Microsemi SoCProducts. The Customer Technical Support Center spends a great deal of time creating applicationnotes, answers to common design cycle questions, documentation of known issues, and various FAQs.So, before you contact us, please visit our online resources. It is very likely we have already answeredyour questions.Technical SupportVisit the Customer Support website (/soc/support/search/default.aspx) for moreinformation and support. Many answers available on the searchable web resource include diagrams,illustrations, and links to other resources on the website.WebsiteYou can browse a variety of technical and non-technical information on the SoC home page, at/soc.Contacting the Customer Technical Support CenterHighly skilled engineers staff the Technical Support Center. The Technical Support Center can becontacted by email or through the Microsemi SoC Products Group website.EmailYou can communicate your technical questions to our email address and receive answers back by email,fax, or phone. Also, if you have design problems, you can email your design files to receive assistance.We constantly monitor the email account throughout the day. When sending your request to us, pleasebe sure to include your full name, company name, and your contact information for efficient processing ofyour request.The technical support email address is **********************.5-02-00498-2/07.15Microsemi makes no warranty, representation, or guarantee regarding the information contained herein or the suitability of its products and services for any particular purpose, nor does Microsemi assume any liability whatsoever arising out of the application or use of any product or circuit. The products sold hereunder and any other products sold by Microsemi have been subject to limited testing and should not be used in conjunction with mission-critical equipment or applications. Any performance specifications are believed to be reliable but are not verified, and Buyer must conduct and complete all performance and other testing of the products, alone and together with, or installed in, any end-products. Buyer shall not rely on any data and performance specifications or parameters provided by Microsemi. It is the Buyer's responsibility to independently determine suitability of any products and to test and verify the same. The information provided by Microsemi hereunder is provided "as is, where is" and with all faults, and the entire risk associated with such information is entirely with the Buyer. Microsemi does not grant, explicitly or implicitly, to any party any patent rights, licenses, or any other IP rights, whether with regard to such information itself or anything described by such information. Information provided in this document is proprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in this document or to any products and services at any time without notice.Microsemi Corporation (MSCC) offers a comprehensive portfolio of semiconductor and system solutions for communications, defense & security, aerospace, and industrial markets.Products include high-performance and radiation-hardened analog mixed-signal integrated circuits, FPGAs, SoCs, and ASICs; power management products; timing and synchronization devices and precise time solutions, setting the world's standard for time; voice processing devices; RF solutions; discrete components; security technologies and scalable anti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well as custom design capabilities and services. Microsemi is headquartered in Aliso Viejo, Calif. and has approximately 3,600 employees globally. Learn more at .Microsemi Corporate HeadquartersOne Enterprise, Aliso Viejo,CA 92656 USAWithin the USA: +1 (800) 713-4113Outside the USA: +1 (949) 380-6100Sales: +1 (949) 380-6136Fax: +1 (949) 215-4996E-mail:***************************©2015 Microsemi Corporation. All rightsreserved. Microsemi and the Microsemilogo are trademarks of MicrosemiCorporation. All other trademarks andservice marks are the property of theirrespective owners.My CasesMicrosemi SoC Products Group customers may submit and track technical cases online by going to My Cases .Outside the U.S.Customers needing assistance outside the US time zones can either contact technical support via email (**********************) or contact a local sales office. Sales office listings can be found at /soc/company/contact/default.aspx.ITAR Technical SupportFor technical support on RH and RT FPGAs that are regulated by International Traffic in Arms Regulations (ITAR), contact us via ***************************. Alternatively, within My Cases , select Yes in the ITAR drop-down list. For a complete list of ITAR-regulated Microsemi FPGAs, visit the I TAR web page.。

【转】VMwareCLI命令参考VMwareCLI命令参考基本命令范例123 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41vmware -v# 看你的esx版本VMware ESXi 5.0.0 build-469512esxcfg-info -a # 显⽰所有ESX相关信息esxcfg-info -w # 显⽰esx上硬件信息service mgmt-vmware restart # 重新启动vmware服务esxcfg-vmknic -l # 查看宿主机IP地址esxcli hardware cpu list # cpu信息 Brand，Core Speed，esxcli hardware cpu global get # cpu信息（CPU Cores）esxcli hardware memory get # 内存信息内存 Physical Memoryesxcli hardware platform get # 硬件型号，供应商等信息,主机型号,Product Name 供应商,Vendor Nameesxcli hardware clock get # 当前时间esxcli system version get # 查看ESXi主机版本号和build号esxcli system maintenanceMode set--enable yes# 将ESXi主机进⼊到维护模式esxcli system maintenanceMode set--enable no # 将ESXi主机退出维护模式esxcli system settings advanced list -d # 列出ESXi主机上被改动过的⾼级设定选项esxcli system settings kernel list -d # 列出ESXi主机上被变动过的kernel设定部分esxcli system snmp get | hash| set| test# 列出、测试和更改SNMP设定esxcli vm process list # 利⽤esxcli列出ESXi服务器上VMs的World I(运⾏状态的)esxcli vm process kill-t soft -w WorldI # 利⽤esxcli命令杀掉VMvim-cmd hostsvc/hostsummary# 查看宿主机摘要信息vim-cmd vmsvc/get.datastores # 查看宿主存储空间信息vim-cmd vmsvc/getallvms# 列出所有虚拟机vim-cmd vmsvc/power.getstate VMI # 查看指定VMI虚拟状态vim-cmd vmsvc/power.shutdown VMI # 关闭虚拟机vim-cmd vmsvc/power.off VMI # 如果虚拟机没有关闭，使⽤poweroff命令vim-cmd vmsvc/get.config VMI # 查看虚拟机配置信息esxcli software vib install-d /vmfs/volumes/datastore/patches/xxx.zip # 为ESXi主机安装更新补丁和驱动esxcli network nic list # 列出当前ESXi主机上所有NICs的状态esxcli network vm list # 列出虚拟机的⽹路信息esxcli storage nmp device list # 理出当前NMP管理下的设备satp和psp信息esxcli storage core device vaai status get # 列出注册到PS设备的VI状态esxcli storage nmp satp set--default-psp VMW_PSP_RR --satp xxxx # 利⽤esxcli命令将缺省psp改成Round Robinesxcli信息查询esxcli命令帮助信息ssh登录VMware ESX server控制台，⽤esxcli命令查询虚拟机信息，输出格式⽀持普通、xml、csv、keyvalue。

本指南将引导您完成使用Layer2(简称L2) 的方式连接设备.该文档为标准说明可能不适用特定的解决方案。

请访问我们的网站获取文档华为固件的最新版本：中文版本:1603目录介绍3本指南前提31.SiteManager设置 42.LinkManager客户端 5 Notices 8介绍使用Layer2的连接方法是针对于IP设备，在IP设备中使用的通信协议可能是TCP/IP或者是UDP，当设备使用UDP的通信协议时我们才需要使用Layer2的方式的方式。

在通常的情况下，我们连接一台IP的PLC或者HMI时，我们直接在SiteManager的GUI界面直接选择对应PLC或者HMI的品牌（在里面没有写有品牌的选通用），选择以太网然后填写IP设备就能添加成功，但是当我们使用LinkManager客户端连接这台设备时，却发现连接不上。

这时这台设备很大的可能是使用UDP的通信协议。

本指南前提本指南前提是:▪LinkManager客户端软件必须升级到6.0以上的版本；▪SiteManager升级到最新版本；▪仅支持硬件版的SiteManager，不支持嵌入版的SiteManager。

1. SiteManager设置打开SiteManager的GUI界面添加设备(GateManager>>>Agents)，给设备命一个名称，选择通用，选择Layer2，填写设备的IP地址。

如下图所示注意：当选择通用时，后面的一项没有Layer2 的这个选项时，请升级SiteManager,可以通过登陆Gatemanager服务器升级，点击对应要升级的SiteManager设备，在浏览器的中间会有一个升级的按钮，点击升级完成后设备将重启，重启连接到服务器后就可以选择了。

也可以通过到官网下载最新的SiteManager升级包，通过本地将SiteManager的DEV1口与电脑连接，进入到GUI界面后选择本地的升级包进行升级。

Fakeroot in ScratchboxTimo Savolatsavola@movial.fiFakeroot in Scratchboxby Timo SavolaCopyright©2004,2005NokiaRevision historyVersion:Author:Description:2005-02-06Savola Based on Device toolsTable of Contents1.Introduction to fakeroot (1)2.Fakeroot in Scratchbox (2)2.1.Known issues (2)3.Debugging (4)4.Building fakeroot (5)5.Implementation of network fakeroot (7)References (8)A.fakeroot1.2.3manual page (9)Chapter1.Introduction to fakerootFakeroot[1]is a utility that runs programs in an environment that looks as if they were run withsuper-user privileges.It is used primarily for settingfile ownerships and modes before packaging them.You can for example create device nodes and store them in a tarball while logged in as a normal user.Ofcourse,the programs run from a fakeroot session cannot really do privileged system calls;fakeroot keepsan in-memory database offile ownerships and such things.Fakeroot was developed by the Debian Project[2]to help in building Debian packages.The Debianpackaging system needs a root environment so that it would be as easy as possible to set up ownershipsand permissions.Fakeroot is released under the GNU General Public License version2[3].Chapter2.Fakeroot in ScratchboxScratchbox[4]introduces new requirements for fakeroot.During the development of Scratchbox anenhanced version of fakeroot was developed with the name fakeroot-net.It was later merged with theupstream project and nowadays Scratchbox uses the upstream codebase.Differences between the default and the Scratchbox version are:•When using sbrsh[5]to implement CPU-transparency in Scratchbox,the command execution canjump from host to target within a fakeroot session.Since both ends use the samefilesystems(via NFS),they must also use the same fakeroot session.This is not possible with the original design that usesSYSV IPC.The Scratchbox version uses TCP/IP sockets for its internal communication.(The TCPversion of the fakeroot command is also available in the Debian package with the name fakeroot-tcp.)Using TCP sockets in fakeroot is not enough to implement network-transparent fakeroot sessions.Thesbrsh server(sbrshd)is used tofilter the information passed between the remote fakeroot environmentand the fakeroot daemon(faked)that keeps the database.The reason for this is explained in Chapter5.•Fakeroot supports saving and loading its internal database in afile.The defaultfile format uses inodenumbers to identifyfiles.Scratchbox uses full path names instead of inodes so that it can reliablycheck the existence of thefiles when loading a database.(The Debian binary package does not shipthis version but the functionality is included in the source package.)Scratchbox provides the fakeroot command,the fakeroot daemon(faked)and a host version of thefakeroot library(libfakeroot).They are sufficient for running host tools in fakeroot,but a target versionof libfakeroot needs to be installed for each Scratchbox target in order to run target binaries in fakeroot.Installing Scratchbox[6]describes how to do that.Scratchbox’s fakeroot is compatible with thelibfakeroot provided by the Debian package,so you can use that aswell.Note:As described above,the fakeroot daemon provided by the Debian package does not use thesame database format as Scratchbox’s version.This should not be a problem though,since thanksto Scratchbox’s binary redirection feature the host version of the fakeroot command is normally usedeven when the target version is installed.Refer to fakeroot’s manual page(Appendix A)for usage instructions.2.1.Known issuesThe fakeroot environment is imposed upon a process by using the C-library’s LD_PRELOADenvironment variable.libfakeroot is preloaded by the dynamic linker whenever it loads a binary.ThisChapter2.Fakeroot in Scratchbox means that fakeroot does not work with statically linked binaries.There is also another side-effect.Since libfakeroot is loaded into the same process image with the “victim”program,they share the samefile descriptor table.Some programs(such as the configure scripts)use hard-coded descriptor numbers.libfakeroot needs onefile descriptor for its communication socket,and if the program starts to use the samefile descriptor,there will be trouble.fakeroot tries to monitor the status of its descriptor so that it can open a new socket if the descriptor has been changed.If you start seeing messages about hijackedfile descriptors,you can try to make fakeroot use some other file descriptor with the--fd-base option.Its default value is(descriptor_table_size-100).Chapter3.DebuggingThe fakeroot daemon can be launched with debug enabled and left running on the foreground:$faked--debug--foreground33366:5027Thefirst number is the TCP/IP port it listens to,and the second number is its process ID.Now,in anotherterminal,setup a fakeroot session manually that uses the daemon we started:$export FAKEROOTKEY=33366$export LD_PRELOAD=/scratchbox/tools/lib/libfakeroot-tcp.so.0Now you can run programs in the hand-made fakeroot session and see the daemon’s cryptic debug outputin the other terminal.This way you can also use a debugger to debug a program within a fakerootenvironment.Note:/scratchbox/tools/lib/libfakeroot-tcp.so.0is the host version.If you are runningtarget binaries,you should set LD_PRELOAD to/usr/lib/libfakeroot/libfakeroot-tcp.so.0.When using a remote fakeroot session,the communication can be traced using the sbrsh daemon’s debuglog.See Scratchbox Remote Shell[5]for instructions.Chapter4.Building fakerootThis chapter contains instructions for building fakeroot from source code using Scratchbox’sconfiguration options.You shouldn’t normally need to do that,since fakeroot is included in Scratchboxand all toolchains ship libfakeroot binaries for their target architectures.See Installing Scratchbox[6]and Scratchbox toolchains[7]for more information.Fakeroot should be cross-compiled inside Scratchbox.The fakeroot source package is available in the/scratchbox/packages directory in the Scratchbox installation,but you can also download it fromDebian[7].Here fakeroot is compiled for a preconfigured Scratchbox target:1.Extract the fakeroot source package:[sbox-HOST:~]>tar xfz/scratchbox/packages/fakeroot_1.2.3.tar.gz2.Select the target your wish to compile for:[sbox-HOST:~]>sb-conf select ARM3.Go to the source directory:[sbox-ARM:~]>cd fakeroot-1.2.34.Configure fakeroot using the options used by Scratchbox:[sbox-ARM:~/fakeroot-1.2.3]>./configure\--prefix=/usr--mandir=/usr/share/man--libdir=/usr/lib/libfakeroot\--program-suffix=-tcp--with-ipc=tcp--with-dbformat=pathNote:Fakeroot uses the/usr/lib/libfakeroot directory for its real libraries.A fake library isinstalled to/usr/lib to work around a bug in an old version of the dynamic linker.5.Build the real libfakeroot-tcp and install it along with the fakeroot-tcp command on the target:[sbox-ARM:~/fakeroot-1.2.3]>make[sbox-ARM:~/fakeroot-1.2.3]>make install6.Clean the configuration and go to the fake directory:[sbox-ARM:~/fakeroot-1.2.3]>make distclean[sbox-ARM:~/fakeroot-1.2.3]>cd fake7.Configure the fake fakeroot:Chapter4.Building fakeroot[sbox-ARM:~/fakeroot-1.2.3/fake]>../configure\--prefix=/usr--mandir=/usr/share/man\--program-suffix=-tcp8.Build and install the fake libfakeroot-tcp:[sbox-ARM:~/fakeroot-1.2.3/fake]>make[sbox-ARM:~/fakeroot-1.2.3/fake]>make install9.We won’t be building the non-TCP version so let’s link it to the TCP version:[sbox-ARM:~/fakeroot-1.2.3/fake]>ln-sf fakeroot-tcp/usr/bin/fakeroot10.If you are using the Debian devkit,you can also build a binary package for Debian:[sbox-ARM:~/fakeroot-1.2.3/fake]>make distclean[sbox-ARM:~/fakeroot-1.2.3/fake]>cd..[sbox-ARM:~/fakeroot-1.2.3]>dpkg-buildpackage-rfakeroot-b Note:It is important to note that the Debian package uses the non-TCP version as the defaultfakeroot command.Also,neither version is configured with the--with-dbformat=path option.Y ou can change the configure options by editing the debian/rulesfile.If you do that,youshould also change the package name and/or the package version to reflect the incompatibility with the standard Debian package.Note:The Debian package needs the“sharutils”package for running its tests.Scratchbox does not provide this package,so you mightfirst need to install it on the target:[sbox-ARM:~/fakeroot-1.2.3]>apt-get update[sbox-ARM:~/fakeroot-1.2.3]>apt-get install sharutilsChapter5.Implementation of network fakeroot faked maintains a list of entries based on their device and inode numbers of thefiles that have beenmodified during a fakeroot session.The entries contain a data structure that is essentially the same as theone used by the stat system call.The TCP version introduces an additional remotefield in the entry,which works like a“namespace”for the devices and inodes.Allfiles on the localfilesystems belog to thedefault namespace(remote is not set).When a remote command is run within a fakeroot session,sbrsh resolves the device numbers of the NFSfilesystems that are listed in its configfile for the used target.If they are not exported by the local hostbut some third host,it tries tofind out if the NFSfilesystems are mounted on the local host and use thedevice numbers of the mount points.sbrshd receives the list of mount entries andfinds out what their device numbers are on the target device.Then it creates a relay process that listens for connections from local fakeroot sessions.When it receivesone,it makes a corresponding connection to the faked running on the Scratchbox host.It maintains asmany connection pairs as there are processes running within the local fakeroot session.The relay copiesmessages from the local session to the remote daemon and responses from the daemon to the session,and translates the device numbers in the messages between the local and remote device number“spaces”.If the relayfinds an unlisted device number in one of the incoming messages,it does not translate it butsets the value of the remotefield to the IP address of the host it is running at.This way faked can serveunknownfilesystems without the danger of device number/inode collisions.References[1]fakeroot(/).[2]The Debian Project(/).[3]GNU General Public License(/copyleft/gpl.html).[4]Scratchbox website(/).[5]Scratchbox Remote Shell(/documentation/docbook/sbrsh.html),Timo Savola.[6]Installing Scratchbox(/documentation/docbook/installdoc.html),ValtteriRahkonen.[7]Scratchbox toolchains(/documentation/docbook/toolchain.html),RicardoKekki.[7]Debian—fakeroot(/fakeroot).Appendix A.fakeroot1.2.3manual pagefakeroot(1)Debian manual fakeroot(1)NAMEfakeroot-run a command in an environment faking root privileges forfile manipulationSYNOPSISfakeroot[-l|--lib library][--faked faked-binary][-i load-file][-ssave-file][-u|--unknown-is-real][-b|--fd-base][-h|--help][-v|--version][--][command]DESCRIPTIONfakeroot runs a command in an environment wherein it appears to haveroot privileges for file manipulation.This is useful for allowingusers to create archives(tar,ar,.deb etc.)with files in them withroot permissions/ownership.Without fakeroot one would need to haveroot privileges to create the constituent files of the archives withthe correct permissions and ownership,and then pack them up,or onewould have to construct the archives directly,without using thearchiver.fakeroot works by replacing the file manipulation library functions(chmod(2),stat(2)etc.)by ones that simulate the effect the reallibrary functions would have had,had the user really been root.Thesewrapper functions are in a shared library/usr/lib/libfakeroot.so*which is loaded through the LD_PRELOAD mechanism of the dynamic loader.(See ld.so(8))If you intend to build packages with fakeroot,please try building thefakeroot package first:the"debian/rules build"stage has a few tests(testing mostly for bugs in old fakeroot versions).If those tests fail(for example because you have certain libc5programs on your system),other packages you build with fakeroot will quite likely fail too,butpossibly in much more subtle ways.Also,note that it’s best not to do the building of the binaries them-selves under fakeroot.Especially configure and friends don’t like itwhen the system suddenly behaves differently from what they expect.(or,they randomly unset some environment variables,some of whichfakeroot needs).OPTIONS-l library,--lib librarySpecify an alternative wrapper library.--faked binarySpecify an alternative binary to use as faked.[--]commandAny command you want to be ran as e’--’if in thecommand you have other options that may confuse fakeroot’soption parsing.-s save-fileSave the fakeroot environment to save-file on exit.This filecan be used to restore the environment later using-i.However,this file will leak and fakeroot will behave in odd ways unlessyou leave the files touched inside the fakeroot alone when out-side the environment.Still,this can be useful.For example,itcan be used with rsync(1)to back up and restore whole directorytrees complete with user,group and device information withoutneeding to be root.See/usr/share/doc/fakeroot/README.savingfor more details.-i load-fileLoad a fakeroot environment previously saved using-s from load-file.Note that this does not implicitly save the file,use-sas well for that ing the same file for both-i and-s in a single fakeroot invocation is safe.-u,--unknown-is-realUse the real ownership of files previously unknown to fakerootinstead of pretending they are owned by root:root.-b fd Specify fd base(TCP mode only).fd is the minimum file descrip-tor number to use for TCP connections;this may be important toavoid conflicts with the file descriptors used by the programsbeing run under fakeroot.-h Display help.-v Display version.EXAMPLESHere is an example session with fakeroot.Notice that inside the fake root environment file manipulation that requires root privileges suc-ceeds,but is not really happening.$whoamijoost$fakeroot/bin/bash#whoamiroot#mknod hda3b31#ls-ld hda3brw-r--r--1root root3,1Jul222:58hda3#chown joost:root hda3#ls-ld hda3brw-r--r--1joost root3,1Jul222:58hda3#ls-ld/drwxr-xr-x20root root1024Jun1721:50/#chown joost:users/#chmod a+w/#ls-ld/drwxrwxrwx20joost users1024Jun1721:50/#exit$ls-ld/drwxr-xr-x20root root1024Jun1721:50//$ls-ld hda3-rw-r--r--1joost users0Jul222:58hda3Only the effects that user joost could do anyway happen for real.fakeroot was specifically written to enable users to create Debian GNU/Linux packages(in the deb(5)format)without giving them root privileges.This can be done by commands like dpkg-buildpackage -rfakeroot or debuild-rfakeroot(actually,-rfakeroot is default in debuild nowadays,so you don’t need that argument).SECURITY ASPECTSfakeroot is a regular,non-setuid program.It does not enhance a user’s privileges,or decrease the system’s security.FILES/usr/lib/libfakeroot/libfakeroot.so*The shared library containing the wrapper functions.ENVIRONMENTFAKEROOTKEYThe key used to communicate with the fakeroot daemon.Any pro-gram started with the right LD_PRELOAD and a FAKEROOTKEY of arunning daemon will automatically connect to that daemon,andhave the same"fake"view of the file system’s permissions/own-erships.(assuming the daemon and connecting program werestarted by the same user).LIMITATIONSLibrary versionsEvery command executed within fakeroot needs to be linked to thesame version of the C library as fakeroot itself.open()/create()fakeroot doesn’t wrap open(),create(),etc.So,if user joostdoes eithertouch foofakerootls-al fooor the other way around,fakeroottouch fools-al foofakeroot has no way of knowing that in the first case,the ownerof foo really should be joost while the second case it shouldhave been root.For the Debian packaging,defaulting to givingall"unknown"files uid=gid=0,is always OK.The real way aroundthis is to wrap open()and create(),but that creates otherproblems,as demonstrated by the libtricks package.This packagewrapped many more functions,and tried to do a lot more thanfakeroot.It turned out that a minor upgrade of libc(from onewhere the stat()function didn’t use open()to one with a stat()function that did(in some cases)use open()),would cause unex-plainable segfaults(that is,the libc6stat()called thewrapped open(),which would then call the libc6stat(),etc).Fixing them wasn’t all that easy,but once fixed,it was just amatter of time before another function started to use open(),never mind trying to port it to a different operating system.Thus I decided to keep the number of functions wrapped by fake-root as small as possible,to limit the likelihood of’colli-sions’.GNU configure(and other such programs)fakeroot,in effect,is changing the way the system behaves.Programs that probe the system like GNU configure may get con-fused by this(or if they don’t,they may stress fakeroot somuch that fakeroot itself becomes confused).So,it’s advisablenot to run"configure"from within fakeroot.As configure shouldbe called in the"debian/rules build"target,running"dpkg-buildpackage-rfakeroot"correctly takes care of this.BUGSIt doesn’t wrap open().This isn’t bad by itself,but if a program does open("file",O_WRONLY,000),writes to file"file",closes it,and then again tries to open to read the file,then that open fails,as the mode of the file will be000.The bug is that if root does the same,open() will succeed,as the file permissions aren’t checked at all for root.I choose not to wrap open(),as open()is used by many other functions in libc(also those that are already wrapped),thus creating loops(or possible future loops,when the implementation of various libc func-tions slightly change).COPYINGfakeroot is distributed under the GNU General Public License.(GPL 2.0 or greater).AUTHORSjoost witteveen<joostje@>Clint Adams<schizo@>Timo SavolaMANUAL PAGEmostly by J.H.M.Dassen<jdassen@>Rather a lot mods/addi-tions by joost and Clint.SEE ALSOfaked(1)dpkg-buildpackage(1),debuild(1)/usr/share/doc/fakeroot/DEBUG Debian Project6August2004fakeroot(1)。

Model: UM-1080CP-BPlease keep this manual for future reference.TABLE OF CONTENTSPAGE INTRODUCTION........................................................................................1COMPATIBILITY REQUIREMENTS......................................................................1DISPLAYLINK DRIVE INFORMATION................................................................1DISPLAYLINK DRIVER INSTALATION...............................................................2UNBOXING AND ASSEMBLY INSTRUCTIONS.................................................2WIRING AND CONNECTIONS.............................................................................5WINDOWS - CALIBRATION FOR TOUCH DISPLAYS..............................................5 WINDOWS 7.............................................................................................5 WINDOWS 10............................................................................................5IMPORTANT NOTES.............................................................................................6 WINDOWS UPDATES...............................................................................6 HDMI CAPTURE.......................................................................................6 EXTENDING USB CABLE. (6)Vue 10” HD Display HDMI Capture User’s ManualIntroductionDesigned to be a perfect conference room control interface, the Mimo Vue HD with HDMI capture UM-1080CP-B is the second generation of Mimo Monitors 10.1” monitor line. It features a modern zero bezel design, nearly 180-degree viewing angle from its bright, high contrast, IPS screen, and a resolution of 1280x800. The Mimo Vue HD includes a 10-point projected capacitive touch panel for developing an intuitive human interface.This capture device allows your USB 3.0 connected computer to stream high-quality HDMI® video, up to 1080p video at 60 frames per second. The capture device converts video and audio from your HDMI source device into standard UVC (USB Video Class) and UAC (USB Audio Class). The HDMI capture interface is integrated into the display and shares the USB connection to the host computer. This video data stream can be presented to other displays with video processing, sent over the internet to other online meeting participants, or many other options.Compatibility requirements:•Android - Requires DisplayLink Presenter application installed on Android device and a connection to a DisplayLink Universal Hub. Please review the information provided atDisplayLink for Android.•Mac - Requires DisplayLink driver. Please review the information provided at this page: DisplayLink for MacOS.•Windows - Requires DisplayLink driver. Please review the information provided at DisplayLink for Windows.•Ubuntu - Requires Intel-based x86 32 or 64-bit system running Ubuntu version 14 or later. Please review the information provided at DisplayLink - Ubuntu Driver Download.•Chromebox - No additional requirements. Please contact us if you experience issues during set up. Please review the information provided at DisplayLink - Native Chrome OS Support.DisplayLink Driver InformationIf noted above, DisplayLink driver must be installed on the computer. If you have Windows 10 or newer, the DisplayLink driver should be pre-installed on the computer. If Windows does not locate the driver locally, and if the computer is connected to the internet, Windows should automatically search online, download, and install the appropriate drivers. If necessary, please follow the instructions below to manually install the DisplayLink drivers.Please visit DisplayLink Support for important information such as: how to identify whether your operating is supported; how to identify operating system version, build, and system type; known issues and troubleshooting steps.DisplayLink Driver InstallationGo to . At the top left of the screen, you will find a button labeled DOWNLOAD DRIVERS, click on that button to download the necessary driver(s). The website will then prompt you to select the correct Supported Operating System. The website will then prompt you to select the correct version of the operating system you are running on the computer being set up.Note that while DisplayLink offers BETA versions for download, we recommend downloading the latest non-BETA released version.Unboxing and Assembly InstructionsUnbox the various components and ensure that nothing is missing. The following items should be included. See Figure 3 for component pictures and plankton assembly instructions.1. Mimo Vue HD Display (screen)2. Stand3. Hinge Cover4. Cable Cover5. HDMI Cable, green connectors6. USB 3.0 Cable, blue connectors, dual to single7. Power Cable, red connectors8. Stand9. Hinge Cover10. Cable Cover11. DC Power adapter with USB power output port12. Stand screws13. Cable cover screwsFigure 1: Components and Plankton Assembly InstructionsFigure 3: Wiring DiagramWiring and ConnectionsAs shown in Figure 4, all connectors are color-coded as are the connections on the back of the Mimo Vue. Simply match the connector style and color and insert. The red connector is for power and should be connected to the power adapter USB port and the display. The blue connector should be connected to the PC/NUC and the Mimo Vue. This cable is 3.0M long but can be extended using active cabling. See the Important Notes section on page 8 for details. The green connector is for HDMI capture, requires USB 3.0 capability, and should be connected to the Mimo Vue and any device that is trying to share its display.Windows - Calibration for Touch DisplaysWindows 7: If you are running Windows 7 the following steps for calibration still apply, however, you will need to install additional Mimo drivers. Please either call Mimo Monitors at 855-937-6466 or you may send an email request to *********************.Windows 10:Once all the components are properly connected and powered on, it is necessary to let the operating system know which of the displays in your configuration has touch capability. For example, if you’re using Windows 10, t ap the Windows Start button and select Settings. In the “Find a setting” box, at the top center of the screen, type “calibrate the screen for pen or touch input” and tap the Enter key. The Tablet PC Settings dialog window will pop up. Tap the Setup button as shown in Figure 2 below.Figure 1: Touch Screen SettingsOnce Setup is selected, all the connected screens will go white and one of the screens will display “Touch this screen to identify it as the touchscreen” and “If this is not the Tablet PC screen, press Enter to move to the next screen. To close the tool press Esc.” to move to the next display. So, if the screen with the above message is displayed, either tap the screen or tap the Enter key until the correct display is selected. Once selected click on Calibrate to be guided through the calibration process and complete the setup.Figure 2: Touch Screen SelectionAt this point, your system should be working and setup is complete.Important Notes1. Windows updates: Before updating Windows, uninstall any DisplayLink drivers thatmight already be installed. The latest DisplayLink drivers will be loaded by Windows. If you experience problems after updating Windows, you may need to manually install the drivers. Please refer to page 3 (above) for instructions and a link to DisplayLink drivers and resources.2. HDMI Capture: There must be an active HDMI signal for this feature to work. Pleasemake sure that the HMDI cable is connected to the PC.3. Extending USB Cable (Blue): If necessary, the USB cable can be extended usingactive cabling. Please read this related article on our website: USB extension and the UM-1080CP-B.。

frida脱壳原理及脱壳工具使用下载温馨提示：该文档是我店铺精心编制而成，希望大家下载以后，能够帮助大家解决实际的问题。

文档下载后可定制随意修改，请根据实际需要进行相应的调整和使用，谢谢!并且，本店铺为大家提供各种各样类型的实用资料，如教育随笔、日记赏析、句子摘抄、古诗大全、经典美文、话题作文、工作总结、词语解析、文案摘录、其他资料等等，如想了解不同资料格式和写法，敬请关注!Download tips: This document is carefully compiled by the editor. I hope that after you download them, they can help you solve practical problems. The document can be customized and modified after downloading, please adjust and use it according to actual needs, thank you!In addition, our shop provides you with various types of practical materials, such as educational essays, diary appreciation, sentence excerpts, ancient poems, classic articles, topic composition, work summary, word parsing, copy excerpts, other materials and so on, want to know different data formats and writing methods, please pay attention!Frida脱壳原理及脱壳工具使用1. 引言在移动应用程序的安全领域中，脱壳是一项关键任务。

Network Camera Firmware Version: V5.5.132Release Note(2020-04-20)Firmware Basic InformationFirmware Version:V5.5.132 build200312SDK Version:V6.1.0.5_build20190516 Play Library (PlayCtrl.dll) V7.3.6.82 iVMS-4200V2.6.17.2 build20190523Compatibility Update●Milestone:Milestone Coperate 2018R2 Device Pack/driver 10.2●Avigilon:Control Center: V6.14.4.6●Excaqvision:1. Version: V19.03.6.1528392. Protocol: HIKCGI, ONVIF●Intellect: V4.10.3●Digifort: V7.2.0.0●Tested NVRs:NVR VersionDS-7716NXI-I4/16P/4S V4.1.15 build190305iDS-9632NXI-I8/8F(B)V4.1.61 build190523iDS-9632NXI-I8/16S V4.1.25 Build181028iDS-9632NXI-I8/4F V4.1.25 Build181028iDS-96128NXI-I16V4.1.25 Build181028iDS-9632NXI-I8/16S(B)V4.1.25 Build181028DS-7632NXI-I2/4S V4.1.15 build190305●Tested Keyboard:DS-1600KI V2.0.0DS-1006KI V1.0Hikvision Firmware V5.5.132 Features*for G3 platform Cameras1.New Features●Newly release (D) models:DS-2CV2041G2-IDW(D)DS-2CV2026G0-IDW(D)DS-2CV2046G0-IDW(D)Wi-Fi camera with (D) model only support adding to Hik-Connect via wired network, not support adding to Hik-Connect via wireless network.●Support set Wi-Fi connection via mobile phone web browser, check the details of setting Wi-Ficonnection via mobile phone web browser on Quick Start Guide or Scan the QR code:●Fixed the known issue.●Device will be locked after resetting password three times.Customer Impact and Recommended ActionThis update refers to function/compatibility improvement and will take effect automatically after the Date of Change. We are very sorry for any inconvenience of use-habit changes caused by this action. For any questions and request for this firmware, please contact our local technical support team.Remarks:●Hikvision reserves the right to change, alter or withdraw the above notification without prior notice.●Product design and specifications are subject to change without prior notice.●The Hikvision firmware may contain defects or errors known as errata which may cause the product to deviate frompublished specifications. Current characterized errata are available on request.●Hikvision is not liable for any typing or printing errors.Hikvision Digital Technology CO., Ltd.No. 555 Qianmo Road, Binjiang District, Hangzhou 310051,ChinaTel: +86-571-8807-5998FAX: +86-571-8993-5635Email:*****************************Supported Product List (2XX1G2/2XX6G0 Series) Product Category Model Number Product Description Wi-Fi Bullet DS-2CV2041G2-IDW(D)4MP, IR, Wi-Fi AcuSense Wi-Fi Bullet DS-2CV2026G0-IDW(D)2MP, IR, Perimeter Protection, Wi-Fi AcuSense Wi-Fi Bullet DS-2CV2046G0-IDW(D)4MP, IR, Perimeter Protection, Wi-Fi。

layer-list中文字
`layer-list`中文字是指在 Android 开发中，`layer-list`的中文翻译。

`layer-list`是 Android 图形界面开发中的一个重要概念，它用于定义多层叠加的图形元素。

`layer-list`可以包含多个`item`，每个`item`都是一个单独的图形元素，可以是颜色、图片、形状等。

这些`item`按照从上到下的顺序叠加在一起，形成一个最终的图形效果。

通过使用`layer-list`，开发者可以创建复杂的图形界面，例如带有图标和文字的按钮、具有不同状态的进度条等。

`layer-list`提供了一种灵活的方式来组合和管理图形元素，以实现所需的视觉效果。

要使用`layer-list`，可以在 XML 资源文件中定义一个`layer-list`元素，并在其中添加`item`元素。

每个`item`元素可以设置自己的属性，例如颜色、透明度、图片资源等。

然后，可以在其他视图中使用`layer-list`作为背景或其他图形属性。

总之，`layer-list`中文字是指在 Android 开发中用于定义多层叠加图形元素的概念。

它提供了一种灵活的方式来创建复杂的图形界面，并允许开发者组合和管理不同的图形元素以实现所需的视觉效果。

Layer2学习模式文档编号RENIX版本作者修改时间修改版本3.1.0.828248 路浪2019.09.22 V1.0 RENIX-201909222目录Layer2学习模式 (3)如何配置Layer2学习模式 (4)添加和连接机箱 (4)预约端口 (5)添加流量 (6)流的二层学习 (8)启动二层学习 (9)配置说明 (11)启动二层学习的功能 (13)启动接收端口二层学习 (14)配置说明 (15)启动接收端口二层学习的功能 (18)接收端口的说明 (19)Layer2学习模式Layer2学习模式：RAW流的二层学习功能是为了实现在被测环境中共享流的MAC地址比如测试交换机的时候，启动二层学习，测试仪的发送端口会发出一定数量的报文（报文头部信息与流的报文头部信息一致），让交换机的MAC地址表中记录该MAC地址信息以便于转发如何配置Layer2学习模式接下来介绍如何配置RAW流为Layer2学习模式添加和连接机箱打开软件在软件的开始界面，点击“预约端口”，然后点击“新增机箱”添加机箱，在“机箱名或IP地址”处输入机箱IP地址，例如10.0.11.104（机箱的前面板液晶屏上会显示机箱IP地址），最后点击“确定”预约用作测试的端口，勾选相应的复选框，点击“确定”在测试端口Port1下建立一条发送给Port2的流量（Port1和Port2是自环的，没有接被测设备）选中测试端口Port1并展开，选择“流模板”，鼠标右键，选择“新建流”，弹出编辑流量的窗口，选择“常规”，将地址学习方式模式改为“L2 Learning”（默认是L3 Learning）点击“数据包/编辑”，将源MAC地址改为00:00:00:11:11:11，目的MAC改为00:00:00:22:22:22，点击“确定”，完成建流流的二层学习建立完流量之后，就可以启动二层学习/启动接收端口二层学习那这两种方式有什么区别呢？启动二层学习点击“启动二层学习”，可以看到测试仪Port1发送了4个报文抓取测试仪Port1发送的报文，内容如下：配置说明对于启动二层学习，可以通过“全局配置”界面的“二层学习”的参数来控制学习报文发送的速率、包数和报文内容速率（帧/秒）：设定学习报文的发送速率重复次数：设定学习包的个数。

安朗（Amnoon）宽带接入服务器用户手册Amnoon BRAS User′s Manual广州安朗通信科技有限公司Guangzhou Amnoon Communication Tech. Co. Ltd.2013-01版权声明安朗 AM BRAS宽带接入服务器用户手册(V4.0)修订日期：20130130本公司依据中华人民共和国著作权法，享有及保留一切著作之专属权力。

未经本公司书面同意，任何人不得对本用户手册的任何部分进行改编、翻印、抄袭、翻译或仿制，否则后果自负。

免责声明本出版物的内容将做定期性的变动，恕不另行通知。

更改的内容将会补充到新修订的手册,并会在本手册发行新版本时予以发布。

安朗公司在编写本手册时以尽最大努力保证其内容的准确、可靠，但安朗公司不对本手册中遗漏、不准确或者错误导致的损失承担责任。

商标使用说明Amnoon是广州安朗通信科技有限公司的注册商标，其它商标及注册商标均属于各其它所属公司。

一、总述AM BRAS宽带接入服务器是一款支持多种接入协议的宽带接入路由器。

设备支持PPPOE协议，可以实现以太网二层用户认证接入。

设备同时支持WebPortal,L2tp和专有客户端软件，可实现用户在三层网络环境的接入。

设备支持标准Radius协议，并支持多种厂家私有属性，可以对用户接入行为进行多种控制。

根据设备型号的不同，一台AM BRAS可以同时支持128～20000个用户在线连接。

1.1 软件概述：AM BRAS宽带接入服务器是一款可以跨三层网络的接入设备，它主要实现以下功能：用户认证（PPPOE,L2tp,Web和私有客户端）、DHCP（动态IP地址分配）、NAT（网络地址转换）、Radius协议支持、Web Portal功能、Filist报文过滤功能、用户控制、和Radius后台系统配合完成用户认证、计费等功能；同时，在原有的网络拓扑不做变动的情况下，使用桥接模式可以实现除NAT（网络地址转换）其它全部功能；您可以利用Console口或者Telnet方式，方便地对服务器进行配置，使其部分或全部实现上述功能要求。

HACMP的配置手册v1.0目录一．系统环境 (3)二．HACMP软件的安装 (3)三．修改系统参数及相关文件 (5)四．HACMP的配置 (5)4.1 设置两台主机IP地址 (5)4.2 修改两台主机系统的/etc/hosts文件 (6)4.3 创建启停脚本 (6)4.4 定义cluster (6)4.5 定义节点 (7)4.6 定义IP网络 (7)4.7 定义网络接口 (8)4.8 定义永久ip: (9)4.9 定义Service IP (10)4.10定义app server (11)4.11创建monitor (11)4.12创建资源组： (12)4.13创建磁盘心跳 (13)4.14同步HACMP (15)五．HACMP服务的启动和停止 (16)六．HACMP的接管测试 (16)本文档仅供研发内部使用，如需在生产环境使用，请先对指导书各步骤进行验证。

一．系统环境主机：两台Power550操作系统：AIX6.1 （61-03-06-1034）数据库：Oracle 10g （10.2.0.4）二．HACMP软件的安装安装以下系统文件集:bos.adt* （表示以bos.adt开头的文件集）pat.basic.hacmppat.clients.hacmpbos.data.*smitty install_latest->F4选择cd0 后回车，进入下面界面光标移动到SOFTWARE to install后，按F4键选择，在按/键，输入文件集的名字，选中后F7，选择，然后回车安装。

其他类似。

安装HACMP 6.1软件,并升级补丁.#smitty install_latestF4选择cd0注：安装前先进行preview安装，若成功，可以直接安装，若失败，则查看相关错误。

Preview成功后：直接安装更新补丁#smitty update_all/patch为存放补丁的文件系统，先preview，成功后再安装，安装选项如下：三．修改系统参数及相关文件此处在安装系统时按照配置手册配置即可。

layer子域名挖掘机用法
Layer子域名挖掘机是一个用于通过爬取网页和分析域名的工具，用于发现目标域名的子域名。

它主要用于进行信息收集和漏洞扫描等任务。

使用Layer子域名挖掘机的方法如下：
1. 安装Layer子域名挖掘机：可以从GitHub等代码托管平台下载并进行安装。

2. 配置API密钥：在Layer子域名挖掘机的配置文件中，输入您的API密钥。

Layer子域名挖掘机使用了许多第三方的API 来进行子域名的获取，所以您需要先注册并获取相关的API
密钥。

3. 设置目标域名：在配置文件中，设置要进行子域名挖掘的目标域名。

4. 运行子域名挖掘机：通过命令行或在终端中运行子域名挖掘机的脚本。

5. 分析结果：子域名挖掘机会输出挖掘到的子域名列表。

您可以进一步分析这些子域名，比如进行漏洞扫描或者进行其他安全测试。

需要注意的是，使用Layer子域名挖掘机需要遵守相关法律法
规和道德规范，只能用于合法的安全测试和授权的活动。

使用时请确保您有合法的授权，并遵守网络安全和隐私保护的原则。