USB004中文资料

ETRX2USB and ETRX2USB-PA USB STICKPRODUCT MANUALTelegesis™ is a trademark of Silicon Laboratories Inc.N o tRe co m m e nd edf or N e wDe si gnTable of Contents1 INTRODUCTION ................................................................................................................. 3 1.1 Supported Operating Systems .. (3)2 ABSOLUTE MAXIMUM RATINGS ..................................................................................... 3 3 OPERATING CONDITIONS (4)4 OTHER DATA ..................................................................................................................... 4 5 ETRX2 I/O CONNECTIVITY .. (5)6 FIRMWARE UPGRADES (5)7 DRIVER INSTALLATION AND OPERATION ..................................................................... 6 7.1 Windows 9x/XP/2k Driver Installation ............................................................................... 6 7.2 Macintosh and Linux drivers ............................................................................................. 9 8 CUSTOM FIRMWARE DEVELOPMENT ............................................................................ 9 9 ORDERING INFORMATION (10)N o tRe co m m e nd edf or N e wDe si gn1 IntroductionThe ETRX2USB wireless mesh networking USB Stick is effectively an RS232 to USB bridge connected to an ETRX2 ZigBee module. This allows connectivity to a computer’s USB port. The supplied drivers create a virtual COM Port, so that the command line of the ETRX2 can be accessed via any terminal software application.When using Windows ® 9x/XP/2000 the Telegesis Terminal application can be used as described in the Development Kit manual.1.1 Supported Operating Systems∙ Windows 98SE ∙ Windows XP ∙ Windows 2000 ∙ MAC OS-9 ∙ MAC OS-X ∙ Linux2 Absolute Maximum RatingsTable 1: Absolute Maximum RatingsThe absolute maximum ratings given above should under no circumstances be violated. Exceeding one or more of the limiting values may cause permanent damage to the device.N o tRe co m edf or N e wDe si gn3 Operating ConditionsTypical values at 5V 25°C.Table 2: Operating Conditions4 Other dataFor further technical information, including radio certification, see the ETRX2 or ETRX2PA Module Product Manual.If you purchase ETRX2USB sticks without printed markings on the case, you may be responsible for applying a marking appropriate to their geographical area of use, such as the FCC certification. For more information on ZigBee® compliance and the AT command interface firmware please refer to the latest AT command dictionary and the ETRX2 user guide.1 During USB suspend the current will drop by 25.6mA in all modes.2 Please note that the power consumption in various power modes is firmware and usage dependent.N o tRe co mm e nd en5 ETRX2 I/O ConnectivityThe I/Os of the built in ETRX2 are connected as follows:∙ I/O1 is connected to the LED (drive I/O1 low to sink LED).∙ I/O2 is the CTS input for the ETRX2. Make sure I/O2 is never defined as an output. ∙ I/O4 is the RTS input for the ETRX2.Important Note: The lines for hardware handshaking are connected, so even when not using hardware handshaking I/O2 should never be defined as an output as this would drive against the incoming CTS signal via a 1k Ω resistor and increase the current consumption.Note that if you use the command “AT&F” on the USB stick, I/O1 will revert to being an input and the LED will not light up. To restore its function as a pilot light, use the command “ATS0E=00FA” (with R2xx firmware) or “ATS17=00FA” (with R3xx) followed by a reset.6 Firmware upgradesThe firmware which is loaded onto the embedded ETRX2 Module can be upgraded over the air or via the virtual COM port as described in the Development Kit manual.Alternatively, access to the SIF programming interface is possible by opening the cover on the side of the ETRX2USB ZigBee USB stick.N o tRe co m m e nd edf or N e wDe si gn7 Driver Installation and OperationThe drivers provided will generate a virtual COM port allowing easy access to the serial port of the embedded ETRX2.To read more about the ETRX2 wireless mesh networking module and its command line interface please read the corresponding documentation which can be found at /telegesisdocuments .7.1 Windows 9x/XP/2k Driver InstallationThe driver package downloadable from the Support Software download page of /telegesissoftware should be unzipped into a local folder. When executing the file ‘TgVCPInstaller.exe ’ prior to plugging in the ETRX2USB stick an installer will guide you through the steps required for the driver installation. If prompted that the driver has not passed the W indows logo test simply press ‘Continue Anyway’.Figure 1: Found New Hardware WizardAfter insertion of the stick, Windows ® will prompt that new hardware has been found. If you have run the ‘TgVCPInstaller.exe ’ Windows will be able to install the driver by automatically as shown in Figure 2. If you have not run ‘TgVCPInstaller.exe ’ you will have to manually point to the directory into which you have unzipped the driver.N o tRe co m m e nd edf or N e wDe si gnFigure 2: Install software AutomaticallyFigure 3: Windows Logo TestPlease note that each ETRX2USB has a unique serial number which requires the installation procedure to be repeated with every new ETRX2USB being attached to the computer. This allows multiple ETRX2USB sticks to be used on the same computer at any one time.In order to find out the identity/number of the virtual com port the stick has been assigned to, please enter the Device Manager under the Windows Computer Management screen (see below) and click on the Ports (COM and LPT) section where you should find the new virtual COM port. By double clicking on the entry of the virtual COM port you can also change the number assigned to the virtual COM port when entering the advanced setup of the device.N o tRe co m m e nd edf or N e wDe si gnFigure 4. Device ManagerOnce the correct COM port has been selected, the Terminal software can be used to control the ETRX2USB stick as per the Development Kit Manual.Figure 5. Telegesis TerminalN o tRe co m m e nd edf or N e wDe si gn7.2 Macintosh and Linux driversA Virtual Com Port driver kit for Mac and Linux can be obtained by following the link on our website on the Support Software download page.In addition, one of our customers has written a Linux driver that will be included in the 2.6.25 kernel. It can be found at /pub/linux/kernel/people/gregkh/gregkh-2.6/patches/. (Note that this is for information only, and this software was developed entirely outside Telegesis.) Most Linux distributions now include suitable native drivers.8 Custom Firmware DevelopmentIf you intend to develop custom firmware to go onto the ETRX2USB you need to contact SiLabs to obtain access to their suite of development tools and their stack. The USB stick contains an ETRX2 module based on the SiLabs EM250 and a USB-to-serial bridge chip. The ETRX2 communicates via its serial port , so the user’s firmware must use the UART of Serial Controller 1. The nRTS and nCTS lines are connected to the USB bridge chip. The LED on the USB stick is driven from ETRX2 pad I/O1, which is EM250 pin GPIO14.In order to download custom firmware onto the ETRX2, the Ember bootloader can be used or alternatively the ETRX2USB can be directly connected to the Ember InSight Adapter for programming and real time debugging.N o tRe co m m e nd edf or N e wDe si gn9 Ordering InformationTable 11. Ordering InformationN o tRe c Silicon Laboratories Inc.400 West Cesar Chavez Austin, TX 78701USASmart.Connected.Energy-Friendly Products/products Quality /quality Support and Community Disclaimer Silicon Laboratories intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Laboratories products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Laboratories reserves the right to make changes without further notice and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Silicon Laboratories shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System without the specific written consent of Silicon Laboratories. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Laboratories products are not designed or authorized for military applications. Silicon Laboratories products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons.Trademark Information Silicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clockbuilder®, CMEMS®, DSPLL®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, ISOmodem®, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress® and others are trademarks or registered trademarks of Silicon Laborato-ries Inc. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand names mentioned herein are trademarks of their respective holders. N o t R e co m m e n d e d f o r N e w D e s i g n。

USB Mass Storage Support ..............................................................................................Section 1 Introduction...........................................................................................1-11.References................................................................................................1-12.Abbreviations............................................................................................1-13.Supported Controllers...............................................................................1-14.Introduction...............................................................................................1-15.Operating Systems....................................................................................1-16.LUN support..............................................................................................1-27.Minimum size under windows...................................................................1-2Section 2Memory Targets....................................................................................2-31.Memories Supported.................................................................................2-32.Dataflash card...........................................................................................2-3Section 3Frequently Asked Questions.................................................................3-51.How to use my USB Mass Storage Device under Windows 98SE ?........3-52.How can I disconnect my Mass Storage Device ?....................................3-53.I can't see the "Safe Disconnect" icon in the System Tray !.....................3-54.My device is enumerated but I can't see it under Linux !..........................3-65.Procedure for support 40 Invalid block per 1024 block.............................3-6Section 1Introduction1. References Universal Serial Bus Specification, revision2.0Universal Serial Bus Class Definition for Communication Devices, version 1.1USB Mass Storage Overview, revision 1.2USB Mass Storage Bulk Only, revision 1.02. Abbreviations USB: Universal Serial BusVID: Vendor IdentifierPID: Product IdentifierLUN: Logical Unit Number3. SupportedControllersAT89C5130/31A & AT8xC5122D4. Introduction The aim of this document is to support the developer for Mass Storage Application.5. OperatingSystems The following OSs support the USB Mass Storage Device class:•Linux: USB mass storage is available in kernel 2.4 or later •USB mass storage is available in Mac OS 9/X or later •Windows XP: native driver•Windows 2000: native driver•Windows Me: native driver•Windows 98SE: Vendor specific driver requiredIntroductionsupport In order to support multiple LUN, please verify that you have correctly intalled the latest 6. LUNservice pack of your OS. Multiple LUN will works on:•Windows XP SP1 or more•Windows 2000 SP4 or moresize7. MinimumThe minimum number of sectors to declare in order to be recognized by windows is 8.under windowsSection 2Memory Targets1. MemoriesSupported2. Dataflash cardDo not remove card during read/write action Because of the low write speed in dataflash, the Operating System can report an error when writing a file, but the file is correctly written. In case of failure, format the data flash using the Operating System tools.3. DataflashBecause of the low write speed in dataflash, the Operating System can report an error when writing a file, but the file is correctly written. In case of failure, format the data flash using the Operating System tools.SupplierRefTypeManuf, Dev Code (hex)Capacity (MB)Supported bydriver Samsung MT29F2G08AACWG Nand Flash 2C, DA 2561x2KB,2x2KB Samsung K9K1G08U0A Nand Flash EC, 79, xx, C01281x512B Atmel AT45DB642DataFlash -81x512B Atmel AT45DB321DataFlash -41x512BAtmelAT45DB002 AT45DB004 AT45DB008DataFlash Card-Section 3 Frequently Asked Questions1.How to use myUSB MassStorage Deviceunder Windows98SE ?There is no native driver to support USB Mass Storage in Windows 98SE. Atmel pro-vides drivers derivated from the SDK/DDK Microsoft example. For ATMEL products, we deliver this driver. The mass_storage_driver_for_Win98SE.zip file is in \Atmel\c5131-mass-storage-complete-x_x_x\doc folder.This driver is composed of 3 files:•atusbms.inf file•atusbms.sys file•atusbms.pdr fileThe atusbms.sys and atusbms.pdr files are the system drivers for Windows 98SE.The .inf file describes the driver to load for your application. The application is recog-nized using the Vendor ID (VID) and Product ID (PID). Because you will use your own VID/PID in the final application, you have to modify the .inf file with the corresponding VID/PID. After driver installation :atusbms.inf is located in C:\windows\inf\atusbms.sys is located in c:\windows\system32\drivers\atusbpdr.pdr is located in c:\windows\system\iosubsys\2. How can Idisconnect myMass StorageDevice ?Under Windows, each Mass Storage device appears in the System Tray. Click on the corresponding icon in order to safely disconnect your USB device.3. I can't see the"SafeDisconnect" iconin the SystemTray !There are 2 conditions for that:•be under Windows 2000 Professional, server•use a composite Mass Storage device (mass storage + mouse for example)In such situation, no icon will appear in the System Tray. It's a bug from Microsoft. Please refers to this page:/default.aspx?scid=kb;en-us;841880&Product=win2000Frequently Asked QuestionsTo solve this problem, use the Hotfix from Microsoft.4.My device isenumerated but I can't see it under Linux !Check with the USBview tool that your device is correctly enumerated.The Linux kernel requires a Master Boot Record (MBR) and a Partition Boot Record (PBR). In root mode ("su" command), launch the fdisk tool for your device "fdisk /dev/sdx" (x is the number of your device), erase all existing partitions, and create a new partition. By default, this partition will use a Linux file system. You can change it to a FAT12 or FAT16 in order to be recognized by every OS.$ su Password:# fdisk /dev/sdx Command : dnumber of the partition (1-4) : 1Command : dnumber of the partition (1-4) : 2Command : dnumber of the partition (1-4) : 3Command : dnumber of the partition (1-4) : 4Command : n e Extendedp Primary partition pFirst cylinder ():Last cylinder():Command: tNumber of the partition: 1Code Hex : 6Command: w5. Procedure for support 40 Invalid block per1024 block1) You must modify the number of free blocks in the file "nf_drv.h" :/* Number maximum of free block per zone */ #define NB_FREE_MAX (24+20)This variable increases the size of XDATA, and this one must be less than 2048 bytes.Change the MAX_FILE_FRAGMENT_NUMBER variable in "nf_drv.h" to reduce the xdata size.#define MAX_FILE_FRAGMENT_NUMBER ((Byte)140) /* The maximum number authorized2) if the Nand Flash has been used with a firmware generated with other NB_FREE_MAX value, you must reinitialize the NF : - modify in "config.h" the option format at TRUE :#define NF_FULL_CHIP_ERASE TRUEFrequently Asked Questions- include the new value of NB_FREE_MAX- compile, load and start the firmware- format the NF via the player menuAt this step the NF correct, and you can change this option to FALSE.3) You must format the NFDisclaimer: The information in this document is provided in connection with Atmel products. No license, express or implied, by estoppel or otherwise,to any intellectual property right is granted by this document or in connection with the sale of Atmel products. EXCEPT AS SET FORTH IN ATMEL’S TERMS AND CONDI-TIONS OF SALE LOCATED ON ATMEL’S WEB SITE, ATMEL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDEN-TAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF ATMEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Atmel makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Atmel does not make any commitment to update the information contained herein. Unless specifically providedot-herwise, Atmel products are not suitable for, and shall not be used in, automotive applications. Atmel’sAtmel’s products are not intended, authorized, or warranted for use as components in applications intended to support or sustain life.Atmel CorporationAtmel Operations2325 Orchard Parkway San Jose, CA 95131Tel: 1(408) 441-0311Fax: 1(408) 487-2600Regional HeadquartersEuropeAtmel SarlRoute des Arsenaux 41Case Postale 80CH-1705 Fribourg SwitzerlandTel: (41) 26-426-5555Fax: (41) 26-426-5500AsiaRoom 1219Chinachem Golden Plaza 77 Mody Road Tsimshatsui East Kowloon Hong KongTel: (852) 2721-9778Fax: (852) 2722-1369Japan9F, Tonetsu Shinkawa Bldg.1-24-8 ShinkawaChuo-ku, Tokyo 104-0033JapanTel: (81) 3-3523-3551Fax: (81) 3-3523-7581Memory2325 Orchard Parkway San Jose, CA 95131Tel: 1(408) 441-0311Fax: 1(408) 436-4314Microcontrollers2325 Orchard Parkway San Jose, CA 95131Tel: 1(408) 441-0311Fax: 1(408) 436-4314La Chantrerie BP 7060244306 Nantes Cedex 3, France Tel: (33) 2-40-18-18-18Fax: (33) 2-40-18-19-60ASIC/ASSP/Smart CardsZone Industrielle13106 Rousset Cedex, France Tel: (33) 4-42-53-60-00Fax: (33) 4-42-53-60-011150 East Cheyenne Mtn. Blvd.Colorado Springs, CO 80906Tel: 1(719) 576-3300Fax: 1(719) 540-1759Scottish Enterprise Technology Park Maxwell BuildingEast Kilbride G75 0QR, Scotland Tel: (44) 1355-803-000Fax: (44) 1355-242-743RF/AutomotiveTheresienstrasse 2Postfach 353574025 Heilbronn, Germany Tel: (49) 71-31-67-0Fax: (49) 71-31-67-23401150 East Cheyenne Mtn. Blvd.Colorado Springs, CO 80906Tel: 1(719) 576-3300Fax: 1(719) 540-1759Biometrics/Imaging/Hi-Rel MPU/High Speed Converters/RF DatacomAvenue de Rochepleine BP 12338521 Saint-Egreve Cedex, France Tel: (33) 4-76-58-30-00Fax: (33) 4-76-58-34-80e-mail********************Web Site© Atmel Corporation 2005. All rights reserved. Atmel ®, logo and combinations thereof, are registered trademarks, and Everywhere You Are ® are the trademarks of Atmel Corporation or its subsidiaries. Other terms and product names may be trademarks of others.。

标准修订记录表QJ 珠海格力电器股份有限公司标准QJ/GD 41.09.003代替 QJ/GD 41.09.002QJ/GD 41.09.007QJ/GD 41.09.009 QJ/GD 41.09.010电线电缆检验规范第八部分手机USB数据线2016-12-1发布2016-12-1实施珠海格力电器股份有限公司发布目录目录 (3)前言 (4)USB数据线 (5)1范围 (5)2规范性引用文件 (5)3技术要求 (5)4试验要求和方法 (5)4.1外观 (5)4.2规格尺寸 (6)4.3线芯排列 (7)4.4物理性能 (7)4.5VW-1燃烧试验 (8)4.6摇摆测试 (8)4.7吊重测试 (8)4.8插拨力测试 (8)4.9电气性能 (9)4.10火花试验 (9)4.11耐压测试 (9)4.12盐雾试验 (9)4.13有害物质含量 (9)5检验规则 (10)6标志、包装、运输和存贮 (10)6.1标志 (10)6.2包装 (11)6.3运输 (11)6.4存贮 (11)附录A （规范性附录）检验报告模板 (12)前言珠海格力电器股份有限公司技术标准是公司标准化技术委员会发布的标准，作为公司内部使用的技术法规性文件。

本部分标准与前一版本相比的主要变化如下：——4.1添加了外观判断图本部分标准由珠海格力电器股份有限公司提出。

本部分标准由珠海格力电器股份有限公司标准化技术委员会归口。

本部分标准由珠海格力电器股份有限公司标准管理部起草。

本部分主要起草人：蔡春晓（标管部）本部分标准本次修订人：蔡春晓（标管部）本部分标准于2016年6月首次发布(换版)。

·USB数据线1 范围本部分规定了USB线的技术要求、试验要求和方法、检验规则、标志、包装、运输和贮存。

本部分适用于USB线。

2 规范性引用文件下列文件对于本文件的应用是必不可少的。

凡是注日期的引用文件，仅注日期的版本适用于本标准。

凡是不注日期的引用文件，其最新版本（包括所有的修改单）适用于本文件。

PCIE 0404 数字音频系统
用户手册
版本：1.0
E-MU 0404 PCIE 声卡用户手册
目录 1、介绍 ………………………………………………………P3 2、安装 ………………………………………………………P4 3、PCIE 声卡和接口…………………………………………P9 4、PatchMix DSP Mixer……………………………………P12 5、特效………………………………………………………P36 技术特性……………………………………………………P61 网络参考信息………………………………………………P63
您会希望为您的 E-MU 数字音频系统保持最新的软件更新。您可以在以下网站找到全部这 些更新信息以及其他的帮助信息：
-3-
E-MU 0404 PCIE 声卡用户手册
旧型号的同步子卡 旧型号的同步子卡不适用于 0404 PCIe 声卡。同步子卡作为 0404PCI 声卡的配件可以提供字 时钟的输入与输出，SMPTE 的输入和输出，以及 MIDI 时间码的输出。
5、将0404 PCIE声卡对准插口并轻轻的压入到接口中，压紧。如图二 6、不要过于用力将声卡压入接口。在将声卡插入之前，确定声卡的金手指已经与主板上接 口对其。如果没有插好，轻轻的拔出再试一次。 7、确定插在接口的声卡使用了一个您稍早时取下的螺丝。 8、将模拟和数字连接线连接到0404声卡后面。 9、将您的音频线连接到连接线上。
关于Windows徽标测试的注意： 当您安装E-MU声卡驱动是，您会看到一个对话窗口提示您该硬件并未通过Windows硬件质量 实验室（WHQL）的认证，或者该硬件签名为Creative Labs，将询问您是否继续安装。 该声卡驱动没有通过WHQL的认证是由于该产品并不支持微软Windows徽标项目的要求的一些 特性，尤其是微软通用音频架构和数字版权管理方面的要求。 尽管如此，该声卡驱动已经按照WHQL的程序要求进行的严格测试，经过验证该驱动符合除了 微软通用音频架构和数字版权管理之外的其他项目的要求，包裹对驱动程序稳定性的检验。 因此，该驱动可以完全安全的安装到您的电脑中。