USB Interface Adapter Evaluation Module User's Guide
|
|
- Rolf Haynes
- 7 years ago
- Views:
Transcription
1 USB Interface Adapter Evaluation Module User's Guide Literature Number: SLLU093 August 2006
2 2 SLLU093 August 2006
3 Contents Preface Introduction List of Hardware Items for Operation List of Software Items for Operation Step-by-Step Instructions for Operation and Troubleshooting Summary of Hardware Design Introduction Ribbon-Cable Connector J2 and Pinout Configuration of Pullup Resistors for Pins 8, 9, and EEPROM LED Indication of USB Attached Firmware Programming and Communications Protocol Firmware Features Summary Firmware Version Command and Response I 2 C Write Command and Response I 2 C Read Command and Response Read/Write Port 0 Command and Response EEPROM Program Command and Response EEPROM Read Command and Response Set Pullup Resistors Command and Response Set I 2 C-PMBUS-SMBUS Speed Command and Response Generic I 2 C Write Command and Response Generic I 2 C Read Command and Response Board Test Command and Response Other Commands for Different Applications Firmware Versioning Scheme Introduction Rules for Implementing Compliant Custom Firmware Compliant Versioning GUI and PC Libraries Windows XP Device Transport GUI Application Schematic, Bill of Materials, PCB Layout Schematic Bill of Materials (BOM) Printed Circuit Board (PCB) Layout A Lists of Communication Protocol A.1 Host PC to USB Interface Adapter Commands A.2 USB Interface Adapter to Host PC Response Commands B PMBUS/SMBUS Communications B.1 Overview SLLU093 August 2006 Contents 3
4 B.2 Basic SMBUS Transaction Types Supported B.3 Special Signals Used for PMBUS/SMBUS Communications B.4 Packet Error Checking (PEC) Implementation B.5 Communication Clock Speed and Clock Stretching B.6 Configuration of Pullup Resistors for ALERT, DATA, and CLOCK Lines B.7 Limitations B.8 List of Host PC to USB Interface Adapter Commands B.9 List of USB Interface Adapter to Host PC Response Commands B.10 Send Byte Command and Response B.11 Receive Byte Command and Response B.12 Write Byte Command and Response B.13 Write Word Command and Response B.14 Read Byte Command and Response B.15 Read Word Command and Response B.16 Process Call Command and Response B.17 Block Write Command and Response B.18 Block Read Command and Response B.19 Block Read Block Write Process Call Command and Response B.20 Group Command and Response B.21 Assert/Deassert CONTROL Lines Command and Response B.22 Poll PMBUS Signal Lines Command and Response B.23 Turn On/Off PEC Command and Response Contents SLLU093 August 2006
5 List of Figures 1-1 Connection of USB Interface Adapter, USB Cable, and Ribbon Cable Flow Chart for Determining Firmware Programing Interactions of Applications During Firmware Programming USB Adapter Software Architecture Sample GUI Application Schematic PCB Layout Top L1 (Copper Layer) Assembly TA PCB Layout Top S1 (Silkscreen Layer) PCB Layout Top L1 (Copper Layer) PCB Layout Bottom L2 (Copper Layer) List of Tables 2-1 Terminal Functions Configurable Options of Pullup Resistors for Pins 8, 9, and List of Pairs of Commands Needed for Firmware Versioning Three Bytes for Firmware Versioning Initial Family Codes Bill of Materials B-1 Host PC to USB Interface Adapter Commands B-2 USB Interface Adapter to Host PC Response Commands SLLU093 August 2006 List of Figures 5
6 All trademarks are the property of their respective owners. 6 List of Tables SLLU093 August 2006
7 Preface SLLU093 August 2006 Read This First About This Manual This user's guide describes the functions and operation of the USB Interface Adapter evaluation module, from different aspects of hardware design, firmware programming, communication protocols, GUI and PC libraries, etc. How to Use This Manual This document contains the following chapters: Chapter 1 Introduction Chapter 2 Summary of Hardware Design Chapter 3 Firmware Programming and Communications Protocol Chapter 4 Firmware Versioning Scheme Chapter 5 GUI and PC Libraries Chapter 6 Schematic, Bill of Materials, and PCB Layout Information About Cautions and Warnings CAUTION This EVM contains components that can potentially be damaged by electrostatic discharge. Always transport and store the EVM in its supplied ESD bag when not in use. Handle using an antistatic wristband. Operate on an antistatic work surface. For more information on proper handling, refer to SSYA008. WARNING By default, the I C data and clock lines are pulled up 2 internally to 3.3 V. If internal pullup resistors are not used and external ones are used instead, please make sure to pull up to 3.3 V only. Operation from 5 V is not specified and may permanently damage this USB Interface Adapter EVM. The information in a caution or a warning is provided for your protection. Please read each caution and warning carefully. SLLU093 August 2006 Read This First 7
8 FCC Warning FCC Warning This equipment is intended for use in a laboratory test environment only. It generates, uses, and can radiate radio frequency energy and has not been tested for compliance with the limits of computing devices pursuant to subpart J of part 15 of FCC rules, which are designed to provide reasonable protection against radio frequency interference. Operation of this equipment in other environments may cause interference with radio communications, in which case, the user, at his/her own expense, will be required to take whatever measures may be required to correct this interference. 8 Read This First SLLU093 August 2006
9 Chapter 1 SLLU093 August 2006 Introduction This EVM serves as an interface adapter or a bridge between a host PC (IBM compatible) and one or multiple slave devices via a standard type-a to mini-b USB cable. The communication between the USB interface adapter and the host PC is via USB, while the communication between the USB interface adapter and the slave device(s) is via an inter-integrated circuit (I 2 C) and/or general-purpose inputs/outputs GPIOs. The bridge converts communication transactions between the USB and I 2 C/GPIO. Note: For the USB interface adapter to communicate with multiple I 2 C slaves, build a special 10-pin ribbon cable with multiple connector(s), so that all the I 2 C slave devices can be daisy-chained together on the same ribbon cable. 1.1 List of Hardware Items for Operation In order to operate this USB interface adapter, the following items are required (see Figure 1-1): USB interface adapter in an enclosure Standard type-a to type-mini-b (5-pin) USB cable 10-pin ribbon cable with connectors on both ends USB Cable LED Indication of USB Attached 10-Pin Ribbon Cable Figure 1-1. Connection of USB Interface Adapter, USB Cable, and Ribbon Cable SLLU093 August 2006 Introduction 9
10 List of Software Items for Operation 1.2 List of Software Items for Operation In addition to the previously listed hardware items, the following software also is needed: I 2 C/GPIO/PMBUS/SMBUS transport layer DLL driver (PMBus Transport (USB HID).dll) created by TI Demo GUI software (USB SAA GUI.exe) for I 2 C/GPIO/PMBUS/SMBUS application Both can be downloaded from the TI website in the file "USB interface adapter GUI.zip", which also contains other accessory files. The USB interface adapter is recognized by a PC as a generic human interface device (HID), which is supported by the built-in USB/HID drivers of the Windows operating system. Therefore, it is plug and play and no proprietary USB driver is required. 1.3 Step-by-Step Instructions for Operation and Troubleshooting After you have downloaded and installed the transport DLL and the GUI demo software, follow these steps to operate the USB interface adapter: 1. Plug in the USB cable to both the PC and the USB interface adapter and wait for the green LED to illuminate. Troubleshooting: If the green LED does not illuminate after 30 s, check to ensure the USB cable is securely connected. If the connection is secure, try a different USB port. If a different USB port does not solve the problem, try to reboot the computer. If rebooting the computer does not fix the problem, try a different USB cable. If trying different USB cable does not solve the problem, contact TI technical support for help. 2. Plug in the 10-pin ribbon cable to both the USB interface adapter and an I 2 C slave board. Make sure that the notch on the ribbon-cable connector matches the keyhole of the socket in the enclosure. 3. Power up the I 2 C slave board. Note that the default I 2 C speed is set at 100 khz and the default pullups for I 2 C data and clock lines are set at 2.2 kω. 4. Run the DEMO GUI software and follow the instructions for the GUI. Troubleshooting: If the I 2 C slave board cannot talk with the USB interface adapter, first check to ensure the 10-pin ribbon cable has been securely connected. If the ribbon cable has been securely connected, check the I 2 C communication speed and the pullups for I 2 C data and clock lines suitable for the application. If not, modify the I 2 C communication speed and the pullups accordingly. If this still does not solve the problem, contact the manufacturer of the I 2 C slave board for help. 10 Introduction SLLU093 August 2006
11 Chapter 2 SLLU093 August 2006 Summary of Hardware Design This chapter describes the major features of hardware design for the USB interface adapter. See Chapter 6 for the schematic, bill of materials (BOM), and PCB layout information. 2.1 Introduction The hardware is based on a USB peripheral chip from TI (TUSB3210). The TUSB3210 has an 8052 core with enhanced performance. The PCB is a simple two-layer, top-side populated board (see the schematic in Chapter 6). The major features of the hardware design are detailed the in the following sections. 2.2 Ribbon-Cable Connector J2 and Pinout NAME This connector is used for communications and controls between the USB interface adapter and one more multiple I 2 C slave device(s). TERMINAL NO. I/O PMBCTRL5/GPIO7 1 I/O PMBCTRL4/GPIO6 2 I/O PMBCTRL3/GPIO5 3 I/O PMBCTRL2/GPIO4 4 I/O Table 2-1. Terminal Functions DESCRIPTION Used as either the 5th PMBUS CONTROL line (output) or as GPIO pin 7 (input/output, with internal pullup enabled) Used as either the 4th PMBUS CONTROL line (output) or as GPIO pin 6 (input/output, with internal pullup enabled) Used as either the 3rd PMBUS CONTROL line (output) or as GPIO pin 5 (input/output, with internal pullup enabled) Used as either the 2nd PMBUS CONTROL line (output) or as GPIO pin 4 (input/output, with internal pullup enabled) This pin can provide a 3.3-V output power supply at up to 100 ma. Any slave +3.3V 5 PWR device(s) can use this power supply as long as the total current consumption is less than 100 ma. Ground 6 GND Common ground for the entire evaluation board PMBCTRL1/GPIO3 7 I/O Used as either the 1st PMBUS CONTROL line (output) or as GPIO pin 3 (input/output, with internal pullup enabled) Used as either the ALERT line (input) for PMBUS or SMBUS communications, or as PMBALERT/SMBALERT/GPIO2 8 I/O GPIO pin 2 (input/output, with internal pullup disabled, and with an external programmable pullup) Used as either the CLOCK line (output) for PMBUS or SMBUS or I 2 C PMBC/SMBC/SCL/GPIO1 9 I/O communications, or as GPIO pin 1 (input/output, with internal pullup disabled, and with an external programmable pullup) Used as either the DATA line (input/output) for PMBUS or SMBUS or I 2 C PMBD/SMBD/SDA/GPIO0 10 I/O communications, or as GPIO pin 0 (input/output, with internal pullup disabled, and with an external programmable pullup) SLLU093 August 2006 Summary of Hardware Design 11
12 Configuration of Pullup Resistors for Pins 8, 9, and Configuration of Pullup Resistors for Pins 8, 9, and 10 The pullups for pins 8, 9, and 10 (see the schematic in Chapter 6) are configurable through communications with the embedded firmware in the TUSB3210 (see the command Set Pullup Resistors in Chapter 3). The default setting is for all these three pins to have pullups of 2.2 kω. Table 2-2 lists the possible options for each pin. Table 2-2. Configurable Options of Pullup Resistors for Pins 8, 9, and 10 PULLUP RESISTOR OPTION 1 OPTION 2 OPTION 3 OPTION 4 OPTION (BYTE VALUE) (0x00) (0x01) (DEFAULT) (0x02) (0x03) Pin 8 of J2: ALERT line No pullup (open) 2.2 kω N/A N/A Pin 9 of J2: CLOCK line No pullup (open) 2.2 kω 1 kω 688 Ω Pin 10 of J2: DATA line No pullup (open) 2.2 kω 1 kω 688 Ω 2.4 EEPROM The embedded firmware is stored in a 64-Kbits EEPROM (see U1 in the schematic in Chapter 6). The firmware is field programmable (see Chapter 5 for more information). Jumper shunt J1 is normally closed and is used for firmware development only. On power up, the TUSB3210 downloads the firmware image from the EEPROM to the internal static RAM and starts firmware execution (first with USB enumeration) from there. 2.5 LED Indication of USB Attached A green LED is mounted next to the USB connector on the evaluation board. Every time the USB interface adapter is attached to a PC via a USB cable, and if the host PC detects it and goes through USB enumeration successfully, the embedded firmware illuminates the green LED (D1) to indicate that; otherwise, the LED remains off. After unplugging the USB cable, the LED turns off immediately. 12 Summary of Hardware Design SLLU093 August 2006
13 Chapter 3 SLLU093 August 2006 Firmware Programming and Communications Protocol The following sections describe the embedded firmware, as well as the communications protocol supported in the USB interface adapter and how to use each command in the protocol. 3.1 Firmware Features Summary The embedded firmware in the TUSB3210 supports the following major features: Supports USB1.1 full speed at 12 Mbit/s. The USB interface adapter is recognized by the host as a generic human interface device (HID), so no proprietary USB or HID driver is needed. Therefore, the USB interface adapter can be treated as a USB plug-and-play device. Supports firmware programming in the external EEPROM so that firmware can be updated in the field. See the TI website ( for more detailed information on firmware programming. Configures different pullup resistors for ALERT, DATA, and CLOCK lines Supports flexible I 2 C read or write transactions. The USB interface adapter is used as the I 2 C master. Selects different clock speeds (either 100 khz or 400 khz) for I 2 C, PMBUS, or SMBUS communications Provides firmware version information (see Chapter 4 for details on firmware versioning scheme) 3.2 Firmware Version Command and Response COMMAND BYTE 0 Firmware Version 0x00 See Chapter 4 (Get Version) COMMAND BYTE 0 Response from Firmware 0x00 See Chapter 4 Version See Chapter 4 for a detailed explanation of how the Family Code, Major Version, and Minor Version bytes are assigned/interpreted. SLLU093 August 2006 Firmware Programming and Communications Protocol 13
14 I 2 C Write Command and Response 3.3 I 2 C Write Command and Response COMMAND BYTE 0 I 2 C Write 0x14 A B C C number of bytes (from 1 up to 60 bytes) to write COMMAND BYTE 0 Response from Success: 0 0x94 I 2 C Write Fail: 1 The following describes the detailed bit banking of this command: I 2 C Start write A (= slave address shifted left by 1 bit + write bit of 0) slave ACK write B (which is usually either a command byte or a register address byte) slave ACK repeat (write 1 byte slave ACK) for C number of times I 2 C stop. There is another more generic I 2 C Write transaction command in Section I 2 C Read Command and Response COMMAND BYTE 0 I 2 C Read 0x15 A B C D (from 1 to 62 bytes) COMMAND BYTE 0 Response from Success: 0 0x95 I 2 C Read Fail: 1 D number of bytes read The following describes the detailed bit banking of this command: I 2 C start write A (= slave address shifted left by 1 bit + write bit of 0) slave ACK write B (which is usually either a command byte or a register address byte) slave ACK repeated start write C (= slave address shifted left by 1 bit + read bit of 1) slave ACK read D number of bytes (with master ACKs in between) from a slave master NACK I 2 C stop. There is another more generic I 2 C Read transaction command in Section Firmware Programming and Communications Protocol SLLU093 August 2006
15 3.5 Read/Write Port 0 Command and Response Read/Write Port 0 Command and Response COMMAND BYTE 0 Read/Write Port 0 B does not A apply to port 0 (bit.x=1 for read. Each B 0x16 read/input, GPIO can be (byte to write) bit.x=0 for configured as write /output) input or output. COMMAND BYTE 0 Response from Read/Write Port 0 0x96 Success: 0 Byte read Fail: 1 from port 0 Each individual GPIO pin of the TUSB3210 port 0 can be configured as either an input or an output (see the schematic in Chapter 6). GPIO pins 3 to 7 are configured to have internal pullups turned on so no special external pullups are needed unless stronger I/O drives are necessary. GPIO pins 0, 1, and 2 are configured to be open-drain I/O ports. Use the software-configurable pullups to support I/O functions. When pin 0 or pin 1 is used as a GPIO, the I 2 C does not function properly anymore. Only after a power-on reset can the I 2 C function be used again without using pins 0 and 1 as GPIOs. Therefore, it is recommended that no more than six GPIO pins are used, reserve pins 0 and 1 exclusively for I 2 C applications. 3.6 EEPROM Program Command and Response COMMAND BYTE 0 EEPROM A = Starting B = Starting C (# of bytes Data to be programmed into EEPROM (up to 0x18 Program address MSB address LSB to program) 32 bytes) COMMAND BYTE 0 Response from EPROM Program 0x98 Success: 0 Fail: 1 This command is used for programming a firmware image to the EEPROM (U1 on schematic) of the EVM. It is recommended that the whole firmware image be split into multiple blocks of 32 bytes and call this command repeatedly until the programming is completed. SLLU093 August 2006 Firmware Programming and Communications Protocol 15
16 EEPROM Read Command and Response 3.7 EEPROM Read Command and Response COMMAND BYTE 0 A = Starting B = Starting C (# of bytes EEPROM Read 0x19 C 60 address MSB address LSB to read) COMMAND BYTE 0 Response from Success: 0 0x99 EEPROM Read Fail: 1 C number of bytes read back from EEPROM (up to 32 bytes) This command works with the EEPROM Program command to verify if the firmware image has been programmed into the EEPROM correctly. For the best efficiency, try to read a block of 32 bytes at a time by calling this command. 3.8 Set Pullup Resistors Command and Response COMMAND BYTE 0 0x00 for no pullups (switched off), 0x01 for 2.2 kω, 0x02 Set Pullup for 1 kω, 0x03 0x1A A (for SDA) B (for SCL) C (for ALERT) Resistors for 688 Ω. For ALERT, the option is either open (0x00) or 2.2 kω (0x01). COMMAND BYTE 0 Response from Pullups have Success: 0 Set Pullup 0x9A been Fail: 1 Resistors configured Byte A is for the DATA line for I 2 C, PMBUS, or SMBUS communications; byte B is for the CLOCK line for I 2 C, PMBUS, or SMBUS communications; byte C is for the ALERT line for PMBUS communications. If a slave device can provide one or multiple pullup resistors, switch off the pullups for DATA, SCL, or ALERT line accordingly. 16 Firmware Programming and Communications Protocol SLLU093 August 2006
17 3.9 Set I 2 C-PMBUS-SMBUS Speed Command and Response Set I 2 C-PMBUS-SMBUS Speed Command and Response COMMAND BYTE 0 0x1B Set I 2 C-PMBUS- SMBUS Speed A (0 for 100 khz, otherwise 400 khz) COMMAND BYTE 0 0x9B Response from Set I 2 C-PMBUS- SMBUS Speed Done with speed selection For I 2 C, PMBUS, or SMBUS communications, the clock speed can be set to either 100 khz or 400 khz. As an I 2 C, PMBUS, or SMBUS master, the USB interface adapter supports clock stretching (up to 25 ms per transaction). The firmware sets the default clock speed to 100 khz Generic I 2 C Write Command and Response COMMAND BYTE 0 Generic I 2 C Write 0x1C A A number of bytes (from 2 up to 62) to write The first byte of data to write is usually (device address < 1 + write bit of 0). COMMAND BYTE 0 Response from Generic I 2 C Write 0x9C Success: 0 Fail: 1 This is a generic I 2 C Write transaction command that can be applied to majority of I 2 C applications. The detailed bit-banking is as follows: I 2 C start repeat (write 1 data byte, slave ACK) for A number of times I 2 C stop. Basically, all the transaction bytes are placed one after another, such as address byte (7-bit slave address shifted left by 1 bit + write bit of 0), one or multiple command bytes, one or multiple data bytes into the A number of bytes buffer space, then the USB interface adapter carries out the bit banking. For maximum flexibility, this generic command for any I 2 C write transaction is recommended. SLLU093 August 2006 Firmware Programming and Communications Protocol 17
18 Generic I 2 C Read Command and Response 3.11 Generic I 2 C Read Command and Response USB USB USB USB USB COMMAND BYTE 0 PACKET PACKET PACKET PACKET PACKET DESCRIPTION COMMAND BYTES 6 63 BYTE 1 BYTE 2 BYTE 3 BYTE 4 BYTE 5 Generic I 2 C Read 0x1D A A number of bytes (2 to 60) to write Y = 1st X # of The 1st byte byte to bytes (1 of data to write + to 62) to write is usually read bit 1 read back (device USB USB address < 1 + byte 62 byte 63 write bit of 0). USB USB USB USB USB COMMAND BYTE 0 PACKET PACKET PACKET PACKET PACKET DESCRIPTION COMMAND BYTES 6-63 BYTE 1 BYTE 2 BYTE 3 BYTE 4 BYTE 5 Response from Success: 0 Generic I 2 C 0x9D X number of bytes (1 to 62) read back from slave Fail: 1 Read This is a generic I 2 C Read transaction command that can be applied to majority of I 2 C applications. The detailed bit-banking is as follows: I 2 C start repeat (write 1 data byte, slave ACK) for A number of times repeated start write Y slave ACK read X number of bytes (with master ACKs in between) from a slave master NACK I 2 C stop. Basically, all the transaction bytes are placed one after another, such as address byte (7-bit slave address shifted left by 1 bit + write bit of 0), one or multiple command bytes, then repeated start, write address byte Y (7-bit slave address shifted left by 1 bit + read bit of 1), and read back x number of bytes from the slave device being addressed. The USB interface adapter carries out the bit banking. For maximum flexibility, this generic command for any I 2 C read transactions is recommended Board Test Command and Response COMMAND DESCRIPTION Board Test USB PACKET USB USB USB USB USB USB BYTE 0 PACKET PACKET PACKET PACKET PACKET PACKET COMMAND BYTE 1 BYTE 2 BYTE 3 BYTE 4 BYTE 5 BYTES x7F Start toggling eight LEDs connected to the eight GPIO pins simultaneously for 5 s. COMMAND DESCRIPTION Response from Board Test USB PACKET USB USB USB USB USB USB BYTE 0 PACKET PACKET PACKET PACKET PACKET PACKET COMMAND BYTE 1 BYTE 2 BYTE 3 BYTE 4 BYTE 5 BYTES xFF Board test is done This command is for internal testing of USB interface adapter evaluation boards during production only. Do not use this command for any other application Other Commands for Different Applications For applications other than I 2 C/GPIO, such as PMBUS, SMBUS, HDQ, etc., see the corresponding literature for more details. 18 Firmware Programming and Communications Protocol SLLU093 August 2006
19 Chapter 4 SLLU093 August 2006 Firmware Versioning Scheme This chapter briefly describes the firmware versioning scheme for the USB interface adapter. Understanding the versioning scheme is critical for using the device in the preset configuration. This topic is important for those who would like to make a custom implementation of firmware or to understand how the firmware version is validated by the host client software. 4.1 Introduction The firmware can be no more than 8K bytes. This limits the amount of functionality that any single firmware image can have. All the functions needed for every application could not possibly be implemented in this space. In order to make the device extensible and to allow its use in many applications, it was designed in a way for a host application to reprogram the device with its own custom firmware whenever needed. For example, some end devices may require protocol X to send and receive data, but the standard firmware does not support protocol X. In this case, the programmer of the GUI software that supports this end device writes custom firmware that conforms to the rules in Section 4.2. At run time, the GUI software finds the USB interface adapter and retrieves its firmware version number. If the version number is not compatible with the protocols needed, the GUI software then reprograms the device with its own version of firmware so that it can use it. If all GUI software complies with this versioning system, then the same hardware can be reused for many applications without inhibiting other compliant software. This also ensures that all implementations will be backward compatible with older GUI software. SLLU093 August 2006 Firmware Versioning Scheme 19
20 Rules for Implementing Compliant Custom Firmware 4.2 Rules for Implementing Compliant Custom Firmware In order for custom firmware to be compatible with this versioning scheme, it must comply with the following rules: 1. The custom firmware must support pairs of commands listed in Table 4-1 (see Chapter 3 for the default implementation). Table 4-1. List of Pairs of Commands Needed for Firmware Versioning S (hex) DESCRIPTION INFORMATION 0x00 and 0x80 Firmware Version (Get Version) Required to communicate its unique identity to the GUI software 0x18 and 0x98 0x19 and 0x99 EEPROM Pro EEPROM Read Required for the GUI software to reprogram the firmware on the embedded EEPROM Required for the GUI software to validate the firmware image on the EEPROM 2. The custom firmware must have a unique, compliant version number that describes its functionality. Note: Together, these two rules describe an interface that all GUI software can expect to be implemented. If GUI software cannot call the Firmware Version command, it cannot identify the firmware and should not attempt to use it as the outcome is unpredictable. If GUI software needs to reprogram the USB interface adapter, it expects command 0x18 to be an EEPROM programming. Conforming to this standard ensures that the firmware does not break the validation and reprogramming cycle. 4.3 Compliant Versioning The versioning scheme uses three bytes to make up a unique identifier that the device can return (as the data part) in response to the Firmware Version command (see Chapter 3 for more details). The first byte is the Family Code and it describes who is responsible for the firmware. These codes are given out in blocks to various groups with TI. For instance, the Digital Power Group owns codes (or 0x01 0x10 in hex). Some Family Codes are reserved. Family codes (or 0xF0 0xFF in hex) have been set aside for custom implementations by end users or anyone wanting to make a compliant version of custom firmware for their own private use. This Family Code also denotes the permutations of protocols supported, such as Family Code 1 supports I 2 C, PMBus, and SMBus, while Family Code 2 might support I 2 C and Protocol X. The second byte is the Major Version and it describes a revision to the permutations of protocols. If the protocols supported need new functionality or have changes to the way that they are called (signature changed) then this byte denotes the change. The third byte is the Minor Version and it describes a revision to the permutations of protocols. If the firmware code has changed to fix a bug in the functions but no new public functions have been added and no changes have been made to the function signatures, this byte should be changed to denote the new version. Table 4-2 summarizes the significance of the three-byte code. Table 4-2. Three Bytes for Firmware Versioning BYTE ORDER MOST SIGNIFICANT BYTE MIDDLE BYTE LEAST SIGNIFICANT BYTE Byte Meaning Family Code Major Version Minor Version Example Value 01 = Major revision 01 = Owned by Digital Power 01 = Minor revision of the permutation of of the permutation of PMBus, SMBus, I 2 C supported protocols protocols 20 Firmware Versioning Scheme SLLU093 August 2006
21 Compliant Versioning To implement this versioning scheme properly, a Windows application calls a Firmware Version command that, along with some others, is reserved and must be present in each implementation of the device. If the Family Code does not match the code that the application is looking for, it should not assume anything about what protocols are supported. The Family Code should immediately attempt to reprogram the firmware with its own version (binary image distributed with the application). A Windows application that correlates Family Code and Major Version with the firmware implementation should then, theoretically, only have to check that the Minor Version is greater than or equal to its target Minor Version. A firmware programmer should be careful to never remove functionality from an implementation with the same Family Code/Major Version, or an older Windows application may attempt to make a malformed call to it when it attempts to communicate. In the case that such a drastic change is made, it is recommend that the firmware developer change the Family Code byte. FAMILY (DECIMAL) 00 Reserved Digital Power + POE Table 4-3. Initial Family Codes HPA Design Tools team Battery Management Unassigned GROUP/TEAM Open for custom implementations (user defined) SLLU093 August 2006 Firmware Versioning Scheme 21
22 Compliant Versioning GUI applications may use the flow chart in Figure 4-1 to determine whether or not to reprogram the firmware on the USB interface adapter. Start Call Get Version Comand Is first byte in response equal to the required family code? No Reprogram the USB Interface Adapter with required version Yes Is second byte in response equal to the required Major version code? No Yes Is third byte greater than or equal to the required Minor version code? No Yes Use the version that already on the board (Bugs have been fixed) End Figure 4-1. Flow Chart for Determining Firmware Programing 22 Firmware Versioning Scheme SLLU093 August 2006
23 Compliant Versioning Figure 4-2 shows an example of how the firmware programming into EEPROM should function between applications. Figure 4-2. Interactions of Applications During Firmware Programming SLLU093 August 2006 Firmware Versioning Scheme 23
24 Compliant Versioning 24 Firmware Versioning Scheme SLLU093 August 2006
25 Chapter 5 SLLU093 August 2006 GUI and PC Libraries The adapter solution includes a set of PC libraries and a GUI that can be used to allow PC applications access to the adapter and target devices that the adapter supports. The GUI and PC libraries are designed using the Microsoft.NET Framework, in order to leverage as many standard libraries as possible. As previously described in this document, the adapter presents itself as a USB HID to Windows. Because of this, no custom driver is required, and the application software on the PC can use the standard Microsoft Windows USB driver (usbhid.sys). Like the adapter, the Windows libraries support all the different types of device interfaces: I 2 C, SMBus, PMBus, and GPIO. In addition, the libraries support configuration and control of the adapter itself by allowing PC programs to update the EERPROM in the adapter, select switching in and out of resistors on data and clock lines, etc. Figure 5-1 represents the software architecture for the PC that is used. GUI Application: VB.NET solution that uses Device Transport (DLL) and.net framework No other dependencies Strictly managed code for Windows form control Device Transport:.NET DLL (managed code) that is also a VB.NET solution Interfaces with standard Windows USB HID driver (usbhid.sys) Allows abstraction of application level GUI from interface and can can be be re used reused in in any application using the adapter.net Framework: Standard installation of.net framework (version 1.1) Installed on all PCs shipping with Windows for last few years Standard libraries for application control Windows XP: Standard installation that ships with PCs.NET framework and application should also work with previous versions of of Windows as as well well USB HID Driver: Standard installation that ships with PCs Talks to USB hardware using Windows GUI Application Device.NET Framework Transport.NET Framework Windows XP USB HID Driver Sold and supported by Microsoft Figure 5-1. USB Adapter Software Architecture The major pieces of the software architecture are as follows: Windows XP.NET Framework Device transport GUI application SLLU093 August 2006 GUI and PC Libraries 25
26 Windows XP 5.1 Windows XP Windows XP provides the standard USB HID support to the application s libraries through a standard USB HID driver that comes with Microsoft Windows. The.NET Framework is a set of libraries that Microsoft provides that allows Windows applications a rich set of services to use. Functionality such as form and window management, memory management, and database are all supported by the.net Framework. Most recent applications written for Windows use the.net Framework. The.NET Framework is the only dependency that the device transport libraries and the GUI application have; there are no custom drivers required by this application. The.NET Framework is installed on all new PCs, so there should be nothing to do except unzip and run the GUI application that is delivered for the adapter Framework. The current version of the device transport libraries and GUI Application use version 1.1 of the Microsoft.NET Framework. Depending on the version of development tools used to generate GUI libraries and applications, an update to the.net Framework from Microsoft may be required. The URL to update the Microsoft.NET Framework on your PC may be found at the following URL: AAB15C5E04F5&displaylang=en 26 GUI and PC Libraries SLLU093 August 2006
27 Device Transport 5.2 Device Transport In order to enable new applications to be created with minimal effort by users of the adapter, a device transport library is provided. This library is a.net DLL that was generated using Microsoft Developer Studio 2003 and is basically a set of.net managed code. This library requires version 1.1 of the.net Framework to be present on the machine that uses it. This library is included in the sample GUI application that is provided with the adapter and is intended to be used by other applications, as well as to manage a target through the adapter. To use this library, simply include it in the project being developed as a dependency. This library provides the following functionality: Primitives that support all I/O types of the adapter I 2 C I 2 C read (variable length) I 2 C write (variable length) SMBus Receive byte Read byte Read word Block read Send byte Write byte Write word Block write Process call Block write block read process call PEC enable/disable PMBus Group command Assert/deassert CONTROL line Poll ALERT# signal GPIO (read/write) General functionality Reset adapter Get device version Select internal pullup resistors Update/read EEPROM contents Select 100-kHz/400-kHz bus speed SLLU093 August 2006 GUI and PC Libraries 27
28 GUI Application 5.3 GUI Application The sample application that is available with the adapter uses the device transport to communicate with the adapter, as well as the target devices behind the adapter. A screenshot is shown in Figure 5-2. Figure 5-2. Sample GUI Application From the main menu, update the firmware for the adapter, select the bus speed of the device (100 khz or 400 khz), and select whether PEC is enabled or disabled when communicating with the device. The main portion of the form is split into five sections: I 2 C, SMBus, PMBus, GPIO, and pullup resistors. From the I 2 C, SMBus, and PMBus group boxes, the user can select each of the available transaction types that the adapter supports. The result of the transaction to the device is also communicated here as an acknowledge (ACK) or not acknowledge (NACK). In the GPIO group box, each of the eight GPIO pins can be enabled and programmed as read or write. In addition, the state of the pin can be read or asserted to the desired value from this group box as well. Finally, the GUI allows users to select the values of the pullup resistors used for the SDA/SCL lines. The adapter and the GUI allow users to select from 668 Ω, 1.1 kω, 2.2 kω, or open drain. 28 GUI and PC Libraries SLLU093 August 2006
29 Chapter 6 SLLU093 August 2006 Schematic, Bill of Materials, PCB Layout This chapter contains information on schematic design, with related information on bill of materials (BOM) and printed circuit board (PCB) layout for the USB interface adapter. SLLU093 August 2006 Schematic, Bill of Materials, PCB Layout 29
30 Schematic 6.1 Schematic Figure 6-1. Schematic 30 Schematic, Bill of Materials, PCB Layout SLLU093 August 2006
31 6.2 Bill of Materials (BOM) Bill of Materials (BOM) Table 6-1. Bill of Materials REF QTY VALUE DESCRIPTION SIZE PART NUMBER MANUFACTURER DESIGNATOR C1, C5, C6, C8, Capacitor, Ceramic, 0.1 µf, 25 V, µf 0603 C1608X7R1E104KT TDK C10, C11 X7R, 10% Capacitor, Ceramic, 22 pf, 50 V, 2 C2, C3 22 pf 0603 C1608C0G1H220KT TDK C0G, 10% Capacitor, Ceramic, 1000 pf, 1 C pf 0805 Std Std 100 V, C0G, 5% Capacitor, Tantalum, 1 µf, 16 V, 1 C7 1 µf D105X0016A2T Vishay 20% Capacitor, Tantalum, 10 µf, 10 V, 2 C9, C12 10 µf D106X0010A2T Vishay 20% 1 D1 SSF-LXH305GD-TR Diode, LED, 2.6 V, 25 ma SSF-LXH305GD-TR Lumex 1 D2 MBRA130 Diode, Schottky, 1 A, 30 V SMA MBRA130 IR 1 D3 7.5 V Diode, Zener, 7.5 V, 3 W SMB 1SMB5922BT3 On Semi D4, D5, D6, D7, Diode, TVS diode, 8 D8, D9, D10, GL05T SOT23 GL05T General Low Capacitance D11 Header, 2-pin, 100 mil spacing, 1 J1 PTC36SAAN PTC36SAAN Sullins (36-pin strip) Connector, Male Right Angle 1 J AMP 2 5 pin, 100 mil spacing, 4 Wall Connector, Recpt, USB-B, Mini, 1 J3 UX60-MB-5ST UX60-MB-5ST Hirose 5-pins, SMT Transistor, NPN, High 1 Q1 MMBT2222A SOT-23 MMBT2222A Fairchild Performance, 500 ma Q2, Q3, Q4, MOSFET, Pch, 50 V, 0.13 A, 5 BSS84 SOT-23 BSS84 Fairchild Q5, Q6 10 Ω Resistor, Chip, 1.5 kω, 1/16 W, 3 R1, R2, R kω 0603 Std Std 5% Resistor, Chip, 2.2 kω, 1/16 W, 3 R17, R19, R kω 0603 Std Std 5% 2 R18, R20 1 kω Resistor, Chip, 1 kω, 1/16 W, 5% 0603 Std Std Resistor, Chip, 200 Ω, 1/16 W, 1 R Ω 0603 Std Std 5% 1 R3 1 MΩ Resistor, Chip, 1 MΩ, 1/16 W, 1% 0603 Std Std Resistor, Chip, 15 kω, 1/16 W, 2 R4, R28 15 kω 0603 Std Std 5% R5, R14, R15, Resistor, Chip, 100 kω, 1/16 W, kω 0603 Std Std R16, R30 5% R6, R7, R8, R9, R10, R11, R12, 14 R13, R21, R22, 33 Ω Resistor, Chip, 33 Ω, 1/16 W, 5% 0603 Std Std R23, R24, R26, R27, R32 IC, Serial EEPROM 64 kω, 1 U1 24LC64 SO8 24LC64 Microchip 1.8 V to 5.5 V, 400 khz Max IC, USB, General Purpose, 1 U2 TUSB3210PM TUSB3210PM TI Device Controller IC, Micro-Power 150 ma LDO 1 U3 TPS76333DBV SOT23-5 TPS76xxxDBV TI Regulator 1 Y1 12 MHz CY12BPSMD Crystek Ribbon Cable, Socket-to-Socket, 1 M3DDA-1018J-ND 18 M3DDA-1018J-ND 3M 10 pin 1 Shunt, 100 mil, Black M PCB, 1 HPA172E2 Any 3.12 in 1.6 in in SLLU093 August 2006 Schematic, Bill of Materials, PCB Layout 31
32 Bill of Materials (BOM) Note: These assemblies are ESD sensitive, so ESD precautions shall be observed. These assemblies must be clean and free from flux and all contaminants. Use of no clean flux is not acceptable. These assemblies must comply with workmanship standards IPC-A-610 Class 2. Ref designators marked with an asterisk ('**') cannot be substituted. All other components can be substituted with equivalent manufacturer's components. 32 Schematic, Bill of Materials, PCB Layout SLLU093 August 2006
33 6.3 Printed Circuit Board (PCB) Layout Figure 6-2 through Figure 6-5 show the PCB layout. Printed Circuit Board (PCB) Layout Figure 6-2. PCB Layout Top L1 (Copper Layer) Assembly TA SLLU093 August 2006 Schematic, Bill of Materials, PCB Layout 33
34 Printed Circuit Board (PCB) Layout Figure 6-3. PCB Layout Top S1 (Silkscreen Layer) 34 Schematic, Bill of Materials, PCB Layout SLLU093 August 2006
35 Printed Circuit Board (PCB) Layout Figure 6-4. PCB Layout Top L1 (Copper Layer) SLLU093 August 2006 Schematic, Bill of Materials, PCB Layout 35
36 Printed Circuit Board (PCB) Layout Figure 6-5. PCB Layout Bottom L2 (Copper Layer) 36 Schematic, Bill of Materials, PCB Layout SLLU093 August 2006
37 Appendix A SLLU093 August 2006 Lists of Communication Protocol This appendix contains a list of communication commands that can be sent from a host PC to the USB interface adapter, as well as a list of communication commands that can be sent from the USB interface adapter to the host PC. A.1 Host PC to USB Interface Adapter Commands USB PACKET USB USB USB USB USB COMMAND BYTE 0 PACKET PACKET PACKET PACKET PACKET DESCRIPTION BYTES 6-63 COMMAND BYTE 1 BYTE 2 BYTE 3 BYTE 4 BYTE 5 Firmware Version I 2 C Write I 2 C Read 0x00 See Chapter 4 0x14 A B C 0x15 A B C D (from 1 to 62 bytes) C number of bytes (from 1 up to 60 bytes) to write B does not A (bit.x=1 for apply to port 0 Read/Write read/input, B (byte to read. Each 0x16 Port 0 bit.x=0 for write) GPIO can be write/output) configured as input or output. EEPROM A = Starting B = Starting C (# of bytes Data to be programmed into EEPROM 0x18 Program address MSB address LSB to program) (up to 32 bytes) A = Starting B = Starting C (# of bytes EEPROM Read 0x19 C 60 address MSB address LSB to program) 0x00 for no pullups (switch off), 0x01 for 2.2 kω, 0x02 Set Pullup C (for for 1 kω, 0x03 0x1A A (for SDA) B (for SCL) Resistors ALERT) for 688 Ω. For ALERT, the option is either open (0x00) or 2.2 kω (0x01). Set I 2 C/PMBUS/SM BUS Speed Generic I 2 C Write Generic I 2 C Read 0x1B A (0 for 100 khz, otherwise 400 khz) The first byte of data to write is 0x1C A A number of bytes (from 2 up to 62) to write usually (device address << 1) + write bit 0. X # of Y = 1st bytes The first byte of byte to (1 to 62) data to write is write + 0x1D A A number of bytes (2 to 60) to write to read usually (device read bit 1 back address << 1) + USB USB write bit 0. Byte 62 Byte 63 SLLU093 August 2006 Lists of Communication Protocol 37
38 USB Interface Adapter to Host PC Response Commands USB PACKET USB USB USB USB USB COMMAND BYTE 0 PACKET PACKET PACKET PACKET PACKET DESCRIPTION BYTES 6-63 COMMAND BYTE 1 BYTE 2 BYTE 3 BYTE 4 BYTE 5 Start toggling eight LEDs connected to Board Test 0x1F the eight GPIO pins simultaneously for 5 s. Note: See Chapter 3 for detailed explanation of each command. A.2 USB Interface Adapter to Host PC Response Commands COMMAND BYTE 0 DESCRIPTION COMMAND BYTE 1 BYTE 2 BYTE 3 BYTE 4 BYTE 5 BYTES 6-63 Response from Family Firmware 0x80 number Version (0 to 255) Response from Success: 0 0x94 I 2 C Write Fail: 1 Response from Success: 0 0x95 I 2 C Read Fail: 1 Response from Read/Write Port 0 Response from EEPROM Program 0x96 0x98 Success: 0 Byte read Fail: 1 from port 0 Success: 0 Fail: 1 Response from Success: 0 0x99 EEPROM Read Fail: 1 Response from Set Pullup Resistors Response from Set I 2 C/PMBUS/SM BUS Speed Response from Generic I 2 C Write Response from Generic I 2 C Read Response from Board Test 0x9A 0x9B 0x9C 0x9D 0xFF Success: 0 Fail: 1 Success: 0 Fail: 1 Success: 0 Fail: 1 Main version Minor version (0 to 255) (0 to 255) D number of bytes read C number of bytes read back from EEPROM (up to 32 bytes) X number of bytes (1 to 62) read back from slave Pullups have been set. Done with speed selection. Board test is done. Note: See Chapter 3 for detailed explanation of each command. 38 Lists of Communication Protocol SLLU093 August 2006
39 Appendix B SLLU093 August 2006 PMBUS/SMBUS Communications This appendix describes the support for USB-to-PMBUS/SMBUS communications in the USB Interface Adapter and how to use it for your applications. B.1 Overview The default firmware for USB Interface Adapter provides support for USB to PMBUS (revision 1.0) and SMBUS (revision 2.0) communications. Similar to its I 2 C application, the USB Interface Adapter acts as a PMBUS/SMBUS master, which can talk with one or multiple PMBUS/SMBUS slave devices daisy-chained to a 10-pin ribbon cable. B.2 Basic SMBUS Transaction Types Supported Because PMBUS communication is derived from SMBUS communication, they share basic SMBUS transaction types in common. These basic SMBUS transaction types include: Send byte Receive byte Write byte Read byte Write word Read word Block write Block read Process call Block read block write process call In addition, PMBUS communication also supports Group command. All these commands are implemented in the USB Interface Adapter firmware. B.3 Special Signals Used for PMBUS/SMBUS Communications Refer to Table 2-2 for special signal lines used for PMBUS/SMBUS communications. Specifically, a slave device can assert an ALERT signal (by pulling it low) to report a fault or a warning condition to the USB Interface Adapter; the host PC can obtain the ALERT signal by polling the USB Interface Adapter. Note that the USB Interface Adapter does not support any Host Notify Protocol. This means that the USB Interface Adapter cannot become a PMBUS/SMBUS slave and, therefore, cannot support a slave to temporarily become a master and notify the host about the fault or the warning condition. For PMBUS communications, the USB Interface Adapter provides five CONTROL signals, each of which can be used to enable/disable the powering up of one or multiple slave device(s). Write Protect signal is not supported; neither is the RESET signal. SLLU093 August 2006 PMBUS/SMBUS Communications 39
40 Packet Error Checking (PEC) Implementation B.4 Packet Error Checking (PEC) Implementation By default, the USB Interface Adapter firmware implements PEC for all the different commands. However, the implementation of PEC byte is optional. There is a special host PC to USB Interface Adapter command that can be used to turn PEC on or off (see Section B.23). If PEC is on or enabled, the firmware in the USB Interface Adapter either appends a PEC byte to a command sent to one or multiple slave devices or checks the validity of a PEC byte received from a slave device. B.5 Communication Clock Speed and Clock Stretching The default clock speed is 100 khz, which is compatible with PMBUS 1.0 and SMBUS 2.0. For compatibility with future PMBUS specs, the clock speed can be increased to 400 khz (see Section 3.9). For each PMBUS/SMBUS transaction, the accumulative time of clock stretching cannot be more 25 ms. B.6 Configuration of Pullup Resistors for ALERT, DATA, and CLOCK Lines Refer to Section 3.8 for more details on this topic. B.7 Limitations Because of the limited capabilities of the TUSB3210 USB peripheral chip, the USB Interface Adapter has the following limitations: Extended Command is not supported. Only the first 256 commands are supported. For any block write or block read command, the number of data bytes is limited to 32 bytes only, even though the PMBUS specs support up to 256 bytes of data per transaction. Address Resolution Protocol (ARP) is not supported, so no multiple masters are allowed. Host Notify Protocol is not supported (see Section B.3). 40 PMBUS/SMBUS Communications SLLU093 August 2006
41 B.8 List of Host PC to USB Interface Adapter Commands List of Host PC to USB Interface Adapter Commands Table B-1. Host PC to USB Interface Adapter Commands COMMAND BYTE 0 Send Byte 0x01 A B Receive Byte 0x02 A Write Byte 0x03 A B C Write Word 0x04 A B C D Read Byte 0x05 A B C Read Word 0x06 A B C Process Call 0x07 A B C D E Block Write 0x08 A B C C number of bytes (from 1 to 32 bytes) to write Block Read 0x09 A B C Block Read Block Write 0x0A A B C D Process Call C number of bytes (from 1 to 31 bytes) to write Write 0 to D if Group D (0xFF for C number of bytes (from 1 to 0x0B A B C not for the last Command last packet) 32 bytes) to write packet Assert\Deassert Bit 0 for line 1, CONTROL 0x0C..., Lines bit 4 for line 5 Poll PMBUS Signal Lines Turn On/Off PEC 0x0F 0x11 0 for off, otherwise on Bit logic 1 for assert, bit logic 0 for deassert SLLU093 August 2006 PMBUS/SMBUS Communications 41
42 List of USB Interface Adapter to Host PC Response Commands B.9 List of USB Interface Adapter to Host PC Response Commands Table B-2. USB Interface Adapter to Host PC Response Commands COMMAND BYTE 0 Response from Success: 0 0x81 Send Byte Fail: 1 Response from Success: 0 Byte read 0x82 Receive Byte Fail: 1 from slave Response from Success: 0 0x83 Write Byte Fail: 1 Response from Success: 0 0x84 Write Word Fail: 1 Response from Success: 0 Byte read 0x85 Read Byte Fail: 1 from slave Low byte of High byte of Response from Success: 0 0x86 word read word read Read Word Fail: 1 from slave from slave Low byte of High byte of Response from Success: 0 0x87 word read word read Process Call Fail: 1 from slave from slave Response from Success: 0 0x88 Block Write Fail: 1 Response from Success: 0 0x89 X X number of bytes read from slave (up to 32 bytes) Block Read Fail: 1 Response from Block Read Success: 0 0x8A Block Write Fail: 1 X X number of bytes read from slave (up to 31 bytes) Process Call Response from Group Command 0x8B Success: 0 Fail: 1 Response from Assert/Deassert Success: 0 0x8C CONTROL Fail: 1 Lines Bit 0 for CONTROL 1,, Response from bit 4 for Logic high for Poll PMBUS 0x8F CONTROL 5, 1, logic low for Signal Lines bit 5 for 0 ALERT, bits 6 and 7 not used Response from Turn On/Off PEC 0x91 Success: 0 Fail: 1 See the following sections for detailed explanation of each command. 42 PMBUS/SMBUS Communications SLLU093 August 2006
MAX17061A Evaluation Kit/Evaluation System
19-4654; Rev 0; 5/09 MAX17061A Evaluation Kit/Evaluation System General Description The MAX17061A evaluation system (EV system) consists of the MAX17061A evaluation kit (EV kit) and the Maxim CMAXQUSB+
NB3H5150 I2C Programming Guide. I2C/SMBus Custom Configuration Application Note
NB3H550 I2C Programming Guide I2C/SMBus Custom Configuration Application Note 3/4/206 Table of Contents Introduction... 3 Overview Process of Configuring NB3H550 via I2C/SMBus... 3 Standard I2C Communication
The I2C Bus. NXP Semiconductors: UM10204 I2C-bus specification and user manual. 14.10.2010 HAW - Arduino 1
The I2C Bus Introduction The I2C-bus is a de facto world standard that is now implemented in over 1000 different ICs manufactured by more than 50 companies. Additionally, the versatile I2C-bus is used
Data Acquisition Module with I2C interface «I2C-FLEXEL» User s Guide
Data Acquisition Module with I2C interface «I2C-FLEXEL» User s Guide Sensors LCD Real Time Clock/ Calendar DC Motors Buzzer LED dimming Relay control I2C-FLEXEL PS2 Keyboards Servo Motors IR Remote Control
August 2001 PMP Low Power SLVU051
User s Guide August 2001 PMP Low Power SLVU051 IMPORTANT NOTICE Texas Instruments and its subsidiaries (TI) reserve the right to make changes to their products or to discontinue any product or service
Kvaser Mini PCI Express User s Guide
Kvaser Mini PCI Express User s Guide Copyright 2013-2014 Kvaser AB, Mölndal, Sweden http://www.kvaser.com Printed Sunday 28 th September, 2014 We believe that the information contained herein was accurate
MAX5417L Evaluation Kit/Evaluation System
19-3733; Rev 0; 6/05 MAX5417L Evaluation Kit/Evaluation System General Description The MAX5417L evaluation system (EV system) consists of a MAX5417L evaluation kit (EV kit) and a companion command module
Thumbus2300. User's Guide. 1 Introduction. 1.1 Features. 1.2 Kit Contents
User's Guide SLUU399A April 2010 Revised March 2011 Thumbus2300 This users guide describes the function and operation of the Thumbus2300 evaluation module. A complete description, as well as schematic
MAX6683 Evaluation System/Evaluation Kit
19-2343; Rev 1; 3/07 MAX6683 Evaluation System/Evaluation Kit General Description The MAX6683 evaluation system (EV system) consists of a MAX6683 evaluation kit (EV kit) and a companion Maxim CMODUSB board.
+Denotes lead-free and RoHS-compliant. C5 C10, C17, C18
19-0623; Rev 1; 3/08 Maxim MINIQUSB User Guide General Description The Maxim command module (MINIQUSB) receives commands from a PC through the USB to create an SPI or SMBus /I 2 C-compatible interface.
USB2.0 <=> I2C V4.4. Konverter Kabel und Box mit Galvanischetrennung
USB2.0 I2C V4.4 Konverter Kabel und Box mit Galvanischetrennung USB 2.0 I2C Konverter Kabel V4.4 (Prod. Nr. #210) USB Modul: Nach USB Spezifikation 2.0 & 1.1 Unterstützt automatisch "handshake
The Programming Interface
: In-System Programming Features Program any AVR MCU In-System Reprogram both data Flash and parameter EEPROM memories Eliminate sockets Simple -wire SPI programming interface Introduction In-System programming
ic-mq EVAL MQ1D EVALUATION BOARD DESCRIPTION
Rev A3, Page 1/7 ORDERING INFORMATION Type Order Designation Description and Options Evaluation Board ic-mq EVAL MQ1D ic-mq Evaluation Board ready to operate, accessible through GUI via PC adapter Software
Designing VM2 Application Boards
Designing VM2 Application Boards This document lists some things to consider when designing a custom application board for the VM2 embedded controller. It is intended to complement the VM2 Datasheet. A
Wireless Temperature
Wireless Temperature connected freedom and Humidity Sensor Using TELRAN Application note TZ1053AN-06 Oct 2011 Abstract Dr. C. Uche This application note describes the complete system design (hardware and
M68EVB908QL4 Development Board for Motorola MC68HC908QL4
M68EVB908QL4 Development Board for Motorola MC68HC908QL4! Axiom Manufacturing 2813 Industrial Lane Garland, TX 75041 Email: Sales@axman.com Web: http://www.axman.com! CONTENTS CAUTIONARY NOTES...3 TERMINOLOGY...3
Real Time Clock USB Evaluation Board V3.0
Real Time Clock USB Evaluation Board V.0 Application Note February 9, 008 RTC EVB Intersil RTC Devices Supported Introduction This evaluation board provides a platform for testing Intersil Real Time Clock
FM75 Low-Voltage Two-Wire Digital Temperature Sensor with Thermal Alarm
Low-Voltage Two-Wire Digital Temperature Sensor with Thermal Alarm Features User Configurable to 9, 10, 11 or 12-bit Resolution Precision Calibrated to ±1 C, 0 C to 100 C Typical Temperature Range: -40
EVAL-AD5390/91/92EB. Evaluation Board for 8-/16-Channel, 12-/14-Bit, Serial Input, Voltage-Output DACs
Evaluation Board for 8-/16-Channel, 12-/14-Bit, Serial Input, Voltage-Output DACs EVAL-AD5390/91/92EB FEATURES Full-featured evaluation board On-board reference On-board ADC for MON_OUT voltage readback
CHAPTER 11: Flip Flops
CHAPTER 11: Flip Flops In this chapter, you will be building the part of the circuit that controls the command sequencing. The required circuit must operate the counter and the memory chip. When the teach
Develop a Dallas 1-Wire Master Using the Z8F1680 Series of MCUs
Develop a Dallas 1-Wire Master Using the Z8F1680 Series of MCUs AN033101-0412 Abstract This describes how to interface the Dallas 1-Wire bus with Zilog s Z8F1680 Series of MCUs as master devices. The Z8F0880,
USB I/O CONTROL BOX 8 relays, 8 digital I/O lines and 8 HV inputs
USB I/O CONTROL BOX 8 relays, 8 digital I/O lines and 8 HV inputs The Big Deal USB HID device compatible with 32/64 Bit operating systems 8 TTL/LVTTL digital I/O channels, 8 High Voltage digital inputs
USB - FPGA MODULE (PRELIMINARY)
DLP-HS-FPGA LEAD-FREE USB - FPGA MODULE (PRELIMINARY) APPLICATIONS: - Rapid Prototyping - Educational Tool - Industrial / Process Control - Data Acquisition / Processing - Embedded Processor FEATURES:
Pmod peripheral modules are powered by the host via the interface s power and ground pins.
Digilent Pmod Interface Specification Revision: November 20, 2011 1300 NE Henley Court, Suite 3 Pullman, WA 99163 (509) 334 6306 Voice (509) 334 6300 Fax Introduction The Digilent Pmod interface is used
SMARTCARD XPRO. Preface. SMART ARM-based Microcontrollers USER GUIDE
SMART ARM-based Microcontrollers SMARTCARD XPRO USER GUIDE Preface Atmel SMARTCARD Xplained Pro is an extension board to the Atmel Xplained Pro evaluation platform. Atmel SMARTCARD Xplained Pro is designed
UPS PIco. to be used with. Raspberry Pi B+, A+, B, and A. HAT Compliant. Raspberry Pi is a trademark of the Raspberry Pi Foundation
UPS PIco Uninterruptible Power Supply with Peripherals and I 2 C control Interface to be used with Raspberry Pi B+, A+, B, and A HAT Compliant Raspberry Pi is a trademark of the Raspberry Pi Foundation
KTA-223 Arduino Compatible Relay Controller
8 Relay Outputs 5A 250VAC 4 Opto-Isolated Inputs 5-30VDC 3 Analog Inputs (10 bit) Connections via Pluggable Screw Terminals 0-5V or 0-20mA Analog Inputs, Jumper Selectable 5A Relay Switching Power Indicator
BrightSign Expander Hardware Guide
Hardware Guide PCBA: Rev C Version: 0.1 Saratoga, CA, USA 1 Table of Contents OVERVIEW... 3 EXPANDER BLOCK DIAGRAM... 4 PORTS... 6 POWER CONNECTOR... 6 OPTICAL SPDIF CONNECTOR... 6 DB25 SWITCH/LED CONNECTOR...
PolyBot Board. User's Guide V1.11 9/20/08
PolyBot Board User's Guide V1.11 9/20/08 PolyBot Board v1.1 16 pin LCD connector 4-pin SPI port (can be used as digital I/O) 10 Analog inputs +5V GND GND JP_PWR 3-pin logic power jumper (short top 2 pins
ARDUINO SEVERINO SERIAL SINGLE SIDED VERSION 3 S3v3 (REVISION 2) USER MANUAL
ARDUINO SEVERINO SERIAL SINGLE SIDED VERSION 3 S3v3 (REVISION 2) USER MANUAL X1: DE-9 serial connector Used to connect computer (or other devices) using RS-232 standard. Needs a serial cable, with at least
GPS/GLONASS SiRFstarV Evaluation Kit EVA5100-A
GPS/GLONASS SiRFstarV Evaluation Kit EVA5100-A A Description of the Evaluation Board for Maestro s GPS/GLONASS Receiver Module A5100-A User s Manual Version 0.1 Revision History Rev. Date Description 0.1
DK40 Datasheet & Hardware manual Version 2
DK40 Datasheet & Hardware manual Version 2 IPC@CHIP DK40 Evaluation module Beck IPC GmbH http://www.bcl.de page 1 of 11 Table of contents Table of contents... 2 Basic description... 3 Characteristics...
SKYEMODULE GEMINI DATASHEET VERSION 040913
SKYEMODULE GEMINI DATASHEET VERSION 040913 SkyeModule Gemini Datasheet Page 2 COPYRIGHT INFORMATION: Copyright 2013 SkyeTek, Inc., 1525 Market St. Suite 200, Denver, Colorado 80202, U.S.A. All rights reserved.
GTS-4E Hardware User Manual. Version: V1.1.0 Date: 2013-12-04
GTS-4E Hardware User Manual Version: V1.1.0 Date: 2013-12-04 Confidential Material This document contains information highly confidential to Fibocom Wireless Inc. (Fibocom). Fibocom offers this information
DS1721 2-Wire Digital Thermometer and Thermostat
www.dalsemi.com FEATURES Temperature measurements require no external components with ±1 C accuracy Measures temperatures from -55 C to +125 C; Fahrenheit equivalent is -67 F to +257 F Temperature resolution
UniPi technical documentation REV 1.1
technical documentation REV 1.1 Contents Overview... 2 Description... 3 GPIO port map... 4 Power Requirements... 5 Connecting Raspberry Pi to UniPi... 5 Building blocks... 5 Relays... 5 Digital Inputs...
Future Technology Devices International Ltd
Future Technology Devices International Ltd Datasheet UMFT200XD Breakout Modules 1 Introduction UMFT200XD is a USB to I 2 C breakout module The UMFT200XD breakout module utilizes FTDI s FT200XQ IC to convert
SRF08 Ultra sonic range finder Technical Specification
SRF08 Ultra sonic range finder Technical Specification Communication with the SRF08 ultrasonic rangefinder is via the I2C bus. This is available on popular controllers such as the OOPic and Stamp BS2p,
HDMI Switch USER MANUAL VS481A
HDMI Switch USER MANUAL VS481A FCC Information This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed
WICE-SPI Hardware Operation Manual
Contents 1.Hardware Instruction...1 2. Pin Definition Of WICE-SPI Connector...2 3. Peripheral Circuit Arrangements...3 4. On-Board Programming...4 5. Off-Line Programming...8 1.Hardware Instruction 1.WICE-SPI
RC2200DK Demonstration Kit User Manual
Demonstration Kit User Manual Table of contents TABLE OF CONTENTS... 1 QUICK INTRODUCTION... 2 INTRODUCTION... 3 DEMONSTRATION BOARD... 4 POWER SUPPLY SECTION... 5 RS-232 INTERFACE... 6 CONNECTORS... 7
PCAN-MicroMod Universal I/O Module with CAN Interface. User Manual. Document version 2.1.0 (2014-01-16)
PCAN-MicroMod Universal I/O Module with CAN Interface User Manual Document version 2.1.0 (2014-01-16) Products taken into account Product Name Part number Model PCAN-MicroMod IPEH-002080 with firmware
Adafruit MCP9808 Precision I2C Temperature Sensor Guide
Adafruit MCP9808 Precision I2C Temperature Sensor Guide Created by lady ada Last updated on 2014-04-22 03:01:18 PM EDT Guide Contents Guide Contents Overview Pinouts Power Pins I2C Data Pins Optional Pins
Table 1 below is a complete list of MPTH commands with descriptions. Table 1 : MPTH Commands. Command Name Code Setting Value Description
MPTH: Commands Table 1 below is a complete list of MPTH commands with descriptions. Note: Commands are three bytes long, Command Start Byte (default is 128), Command Code, Setting value. Table 1 : MPTH
Software User Guide UG-461
Software User Guide UG-461 One Technology Way P.O. Box 9106 Norwood, MA 02062-9106, U.S.A. Tel: 781.329.4700 Fax: 781.461.3113 www.analog.com ezlinx icoupler Isolated Interface Development Environment
PC2400 EEPROM PROGRAMMER INSTRUCTION MANUAL
PC2400 EEPROM PROGRAMMER INSTRUCTION MANUAL LAST UPDATE 23/09/09 LLOYD RESEARCH LTD., 7&7A BROOK LANE, WARSASH, SOUTHAMPTON, HANTS., SO31 9FH. Tel: +44 (0)1489 885515/574040 Fax: +44 (0)1489 885853 Internet:
NHD-0420D3Z-FL-GBW-V3
NHD-0420D3Z-FL-GBW-V3 Serial Liquid Crystal Display Module NHD- Newhaven Display 0420-4 Lines x 20 Characters D3Z- Model F- Transflective L- Yellow/Green LED Backlight G- STN-Gray B- 6:00 Optimal View
USBSPYDER08 Discovery Kit for Freescale MC9RS08KA, MC9S08QD and MC9S08QG Microcontrollers User s Manual
USBSPYDER08 Discovery Kit for Freescale MC9RS08KA, MC9S08QD and MC9S08QG Microcontrollers User s Manual Copyright 2007 SofTec Microsystems DC01197 We want your feedback! SofTec Microsystems is always on
The $25 Son of a cheap timer This is not suitable for a beginner. You must have soldering skills in order to build this kit.
The $25 Son of a cheap timer This is not suitable for a beginner. You must have soldering skills in order to build this kit. Micro Wizard has been manufacturing Pinewood Derby timers for over 10 years.
Switch board datasheet EB007-00-1
Switch board datasheet EB007-00-1 Contents 1. About this document... 2 2. General information... 3 3. Board layout... 4 4. Testing this product... 5 5. Circuit description... 6 Appendix 1 Circuit diagram
MODULE BOUSSOLE ÉLECTRONIQUE CMPS03 Référence : 0660-3
MODULE BOUSSOLE ÉLECTRONIQUE CMPS03 Référence : 0660-3 CMPS03 Magnetic Compass. Voltage : 5v only required Current : 20mA Typ. Resolution : 0.1 Degree Accuracy : 3-4 degrees approx. after calibration Output
DS1307ZN. 64 x 8 Serial Real-Time Clock
DS137 64 x 8 Serial Real-Time Clock www.maxim-ic.com FEATURES Real-time clock (RTC) counts seconds, minutes, hours, date of the month, month, day of the week, and year with leap-year compensation valid
8-Port HDMI Switch USER MANUAL VS0801H
8-Port HDMI Switch USER MANUAL VS0801H FCC Information This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits
DEMO MANUAL DC1338B LTC2990 I 2 C Temperature Voltage and Current Monitor DESCRIPTION
DEMO MANUAL DC8B LTC990 I C Temperature Voltage and Current Monitor DESCRIPTION Demonstration circuit 8B features the LTC 990, a high performance temperature, voltage and current monitor that uses I C
DS1621 Digital Thermometer and Thermostat
Digital Thermometer and Thermostat www.dalsemi.com FEATURES Temperature measurements require no external components Measures temperatures from 55 C to +125 C in 0.5 C increments. Fahrenheit equivalent
TCP/IP MODULE CA-ETHR-A INSTALLATION MANUAL
TCP/IP MODULE CA-ETHR-A INSTALLATION MANUAL w w w. c d v g r o u p. c o m CA-ETHR-A: TCP/IP Module Installation Manual Page Table of Contents Introduction...5 Hardware Components... 6 Technical Specifications...
Joule Thief 3.0 Kit. June 2012, Rev 1 1 http://www.easternvoltageresearch.com Joule Thief 3.0
Kit Instruction Manual Eastern Voltage Research, LLC June 2012, Rev 1 1 http://www.easternvoltageresearch.com HIGH BRIGHTNESS LED THIS KIT USES A 1W CREE, HIGH BRIGHTNESS LED. DO NOT STARE AT THIS (OR
[F/T] [5] [KHz] [AMP] [3] [V] 4 ) To set DC offset to -2.5V press the following keys [OFS] [+/-] [2] [.] [5] [V]
FG085 minidds Function Generator Manual of Operation Applicable Models: 08501, 08501K, 08502K, 08503, 08503K Applicable Firmware Version: 1 ) 113-08501-100 or later (for U5) 2 ) 113-08502-030 or later
MAX4399 Evaluation System/Evaluation Kit
19-3012; Rev 1; 2/07 MAX4399 Evaluation System/Evaluation Kit General Description The MAX4399 evaluation system (EV system) consists of a MAX4399 evaluation kit (EV kit) and a companion Maxim CMODUSB board.
AN601 I2C 2.8 Communication Protocol. SM130 SM130 - Mini APPLICATION NOTE
AN601 I2C 2.8 Communication Protocol SM130 SM130 - Mini APPLICATION NOTE 2 1. INTRODUCTION This application note explains I2C communication protocol with SM130 or SM130-Mini Mifare module based on the
Bluetooth HID Profile
RN-WIFLYCR-UM-.01 RN-HID-UM Bluetooth HID Profile 2012 Roving Networks. All rights reserved. Version 1.0r 1/17/2012 USER MANUAL www.rovingnetworks.com 1 OVERVIEW Roving Networks Bluetooth modules support
TI ARM Lab 7 Accelerometers
TI ARM Lab 7 Accelerometers National Science Foundation Funded in part, by a grant from the National Science Foundation DUE 1068182 Acknowledgements Developed by Craig Kief, Brian Zufelt, and Jacy Bitsoie
XPort Universal Demo Board User Guide
XPort Universal Demo Board User Guide Part Number 900-563 Revision A September 2009 Copyright and Trademark Contacts 2009 Lantronix. All rights reserved. No part of the contents of this book may be transmitted
ABB Drives. User s Manual HTL Encoder Interface FEN-31
ABB Drives User s Manual HTL Encoder Interface FEN-31 HTL Encoder Interface FEN-31 User s Manual 3AUA0000031044 Rev B EN EFFECTIVE: 2010-04-06 2010 ABB Oy. All Rights Reserved. 5 Safety instructions
EMBEDDED ACCESS CONTROL Hardware Installation Guide
EMBEDDED ACCESS CONTROL Hardware Installation Guide Lenel goentry Hardware Installation Guide, product version 1.00. This guide is item number DOC- ENHW-ENU, revision 1.003, April 2009 Copyright 2009 Lenel
HARDWARE MANUAL. BrightSign HD120, HD220, HD1020. BrightSign, LLC. 16795 Lark Ave., Suite 200 Los Gatos, CA 95032 408-852-9263 www.brightsign.
HARDWARE MANUAL BrightSign HD120, HD220, HD1020 BrightSign, LLC. 16795 Lark Ave., Suite 200 Los Gatos, CA 95032 408-852-9263 www.brightsign.biz TABLE OF CONTENTS OVERVIEW... 1 Block Diagram... 2 Ports...
User Manual. AS-Interface Programmer
AS-Interface Programmer Notice: RESTRICTIONS THE ZMD AS-INTERFACE PROGRAMMER HARDWARE AND ZMD AS-INTERFACE PROGRAMMER SOFTWARE IS DESIGNED FOR IC EVALUATION, LABORATORY SETUP AND MODULE DEVELOPMENT ONLY.
USB Plus+ RFID Reader Setup Guide
875-0042-03 RevA USB Plus+ RFID Reader Setup Guide 1 Government Limited Rights Notice: All documentation and manuals were developed at private expense and no part of it was developed using Government funds.
isppac-powr1220at8 I 2 C Hardware Verification Utility User s Guide
November 2005 Introduction Application Note AN6067 The isppac -POWR1220AT8 device from Lattice is a full-featured second-generation Power Manager chip. As part of its feature set, this device supports
- 35mA Standby, 60-100mA Speaking. - 30 pre-defined phrases with up to 1925 total characters.
Contents: 1) SPE030 speech synthesizer module 2) Programming adapter kit (pcb, 2 connectors, battery clip) Also required (for programming) : 4.5V battery pack AXE026 PICAXE download cable Specification:
The modular concept of the MPA-3 system is designed to enable easy accommodation to a huge variety of experimental requirements.
HARDWARE DESCRIPTION The modular concept of the MPA-3 system is designed to enable easy accommodation to a huge variety of experimental requirements. BASE MODULE GO LINE Digital I/O 8 Analog Out AUX 1
ALL-USB-RS422/485. User Manual. USB to Serial Converter RS422/485. ALLNET GmbH Computersysteme 2015 - Alle Rechte vorbehalten
ALL-USB-RS422/485 USB to Serial Converter RS422/485 User Manual ALL-USB-RS422/485 USB to RS-422/485 Plugin Adapter This mini ALL-USB-RS422/485 is a surge and static protected USB to RS-422/485 Plugin Adapter.
DS1621 Digital Thermometer and Thermostat
www.maxim-ic.com FEATURES Temperature measurements require no external components Measures temperatures from -55 C to +125 C in 0.5 C increments. Fahrenheit equivalent is -67 F to 257 F in 0.9 F increments
Internal Oscillator. I 2 C Interface. SPI Interface. Controller. Internal Registers Port Controller. Eight I/O Pins. Figure 1.
SPI TO I 2 C BRIDGE AND GPIO PORT EXPANDER Single Chip SPI to I 2 C Transfer Integrated clock; no external clock required On-Chip Voltage Monitor Slave Serial Peripheral Interface (SPI) Up to 1.0 Mbit/s
MX PIC24F Educational Module User Manual
MX PIC24F Educational Module User Manual Revision History Date Description Initial release. Table of Contents 1. Introduction... 3 1.1. Package Contents... 3 1.2. Key Hardware Features... 4 2. Hardware
In-System Programmer USER MANUAL RN-ISP-UM RN-WIFLYCR-UM-.01. www.rovingnetworks.com 1
RN-WIFLYCR-UM-.01 RN-ISP-UM In-System Programmer 2012 Roving Networks. All rights reserved. Version 1.1 1/19/2012 USER MANUAL www.rovingnetworks.com 1 OVERVIEW You use Roving Networks In-System-Programmer
Introducing AVR Dragon
Introducing AVR Dragon ' Front Side Back Side With the AVR Dragon, Atmel has set a new standard for low cost development tools. AVR Dragon supports all programming modes for the Atmel AVR device family.
Install the DeviceNet Module using the following procedure:
Installation INSTALLATION INSTRUCTIONS: MCD DEVICENET MODULE Order Code: 175G9002 1. Installation Install the DeviceNet Module using the following procedure: 1. Remove control power and mains supply from
Chapter 5 Real time clock by John Leung
Chapter 5 Real time clock 5.1 Philips PCF8563 Real time clock (RTC) Philips PCF8563 (U5) is an I 2 C compatible real time clock (RTC). Alternatively, this chip can be replaced by a software module like
GLOLAB Universal Telephone Hold
GLOLAB Universal Telephone Hold 1 UNIVERSAL HOLD CIRCUIT If you have touch tone telephone service, you can now put a call on hold from any phone in the house, even from cordless phones and phones without
DKWF121 WF121-A 802.11 B/G/N MODULE EVALUATION BOARD
DKWF121 WF121-A 802.11 B/G/N MODULE EVALUATION BOARD PRELIMINARY DATA SHEET Wednesday, 16 May 2012 Version 0.5 Copyright 2000-2012 Bluegiga Technologies All rights reserved. Bluegiga Technologies assumes
AN2680 Application note
Application note Fan speed controller based on STDS75 or STLM75 digital temperature sensor and ST72651AR6 MCU Introduction This application note describes the method of defining the system for regulating
FireWire 800 + Hi-Speed USB Combo Quick Installation Guide
FireWire 800 + Hi-Speed USB Combo Quick Installation Guide Introducing the FireWire 800 + Hi-Speed USB Combo The FireWire 800+Hi-Speed USB Combo features the latest technology in FireWire 800 and USB 2.0.
PACKAGE OUTLINE DALLAS DS2434 DS2434 GND. PR 35 PACKAGE See Mech. Drawings Section
PRELIMINARY DS2434 Battery Identification Chip FEATURES Provides unique ID number to battery packs PACKAGE OUTLINE Eliminates thermistors by sensing battery temperature on chip DALLAS DS2434 1 2 3 256
RIGtalk. Revision 5. Owner s Manual 2012.
RIGtalk Revision 5 Owner s Manual 2012 www.westmountainradio.com 1020 Spring City Drive Waukesha, WI 53186 262-522-6503 sales@westmountainradio.com 2012 West Mountain Radio, All rights reserved. All trademarks
NTE2053 Integrated Circuit 8 Bit MPU Compatible A/D Converter
NTE2053 Integrated Circuit 8 Bit MPU Compatible A/D Converter Description: The NTE2053 is a CMOS 8 bit successive approximation Analog to Digital converter in a 20 Lead DIP type package which uses a differential
SKP16C62P Tutorial 1 Software Development Process using HEW. Renesas Technology America Inc.
SKP16C62P Tutorial 1 Software Development Process using HEW Renesas Technology America Inc. 1 Overview The following tutorial is a brief introduction on how to develop and debug programs using HEW (Highperformance
Single channel data transceiver module WIZ2-434
Single channel data transceiver module WIZ2-434 Available models: WIZ2-434-RS: data input by RS232 (±12V) logic, 9-15V supply WIZ2-434-RSB: same as above, but in a plastic shell. The WIZ2-434-x modules
2.0 Command and Data Handling Subsystem
2.0 Command and Data Handling Subsystem The Command and Data Handling Subsystem is the brain of the whole autonomous CubeSat. The C&DH system consists of an Onboard Computer, OBC, which controls the operation
Programming Flash Microcontrollers through the Controller Area Network (CAN) Interface
Programming Flash Microcontrollers through the Controller Area Network (CAN) Interface Application te Programming Flash Microcontrollers through the Controller Area Network (CAN) Interface Abstract This
Bob Rathbone Computer Consultancy
Raspberry PI Stepper Motor Constructors Manual Bob Rathbone Computer Consultancy www.bobrathbone.com 20 th of December 2013 Bob Rathbone Raspberry PI Robotic Arm 1 Contents Introduction... 3 Raspberry
Quick Start Guide. MRB-KW01 Development Platform Radio Utility Application Demo MODULAR REFERENCE BOARD
Quick Start Guide MRB-KW01 Development Platform Radio Utility Application Demo MODULAR REFERENCE BOARD Quick Start Guide Get to Know the MRB-KW01x Module UART Selector ANT 1 RFIO (TX/RX) USB 2.0 Serial
MXL5007T TUNER RADIO
MXL5007T TUNER RADIO MxL5007T is a tuner IC designed mostly for digital signals (DVB-T, ATSC), but it can be used for analog reception too. It has a programmable IF output and it can receive anything from
150127-Microprocessor & Assembly Language
Chapter 3 Z80 Microprocessor Architecture The Z 80 is one of the most talented 8 bit microprocessors, and many microprocessor-based systems are designed around the Z80. The Z80 microprocessor needs an
How To Use A Watt Saver On A Microcontroller (Watt Saver) On A Cell Phone Or Mp3 Player
Watt Saver for a Cell Phone AC Adapter Reference Design Document Number: DRM130 Rev 1, 10/2013 2 Freescale Semiconductor, Inc. Contents Section number Title Page Chapter 1 Introduction 1.1 Overview...5
Dolphin In-Circuit programming Updating Firmware in the field
Dolphin In-Circuit programming Updating Firmware in the field 1 Introduction In systems e.g. gateways, where an external microcontroller is connected to a Dolphin based product like a TCM300 it might be
MicroTech II McQuay Maverick II Rooftop Unit Controller BACnet Communication Module (MS/TP)
Installation and Maintenance Manual IM 852 Group: Controls Part Number: IM 852 Date: June 2007 Supercedes: New MicroTech II McQuay Maverick II Rooftop Unit Controller BACnet Communication Module (MS/TP)
Review of. 4x IOcards (PCBs) Manufactured by Opencockpits
Review of 4x IOcards (PCBs) Manufactured by Opencockpits Intro We all know flight simulation hardware as yokes, pedals, throttle quadrant, various complete P&P modules etc. which certainly helps in creating
Perle Protocol Transparent Media Converter Modules
Perle Protocol Transparent Media Converter Modules Installation Guide C-4GPT-DSFP CM-4GPT-DSFP Part# 5500335-10 Overview This document contains instructions necessary for the installation and operation
+Denotes lead-free and RoHS-compliant.
19-4040; Rev 0; 2/08 MAX7474 Evaluation Kit General Description The MAX7474 evaluation kit (EV kit) is a fully assembled and tested printed-circuit board (PCB) that configures the MAX7474 IC for automatically