Cypress CY4672 - Manuals
Cypress CY4672 – Manual in PDF format online.
Manuals:
Manual Cypress CY4672
Summary
2 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Copyrights Copyrights © Cypress Semiconductor Corporation, 2007. The information contained herein is subject to change without notice. CypressSemiconductor Corporation assumes no responsibility for the use of any circuitry other than ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 3 Contents 1. Introduction 9 1.1 Scope...........................................................................................................................9 1.2 Chapter Overviews ......................................................
8 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Contents 7. Regulatory Testing Results 105 7.1 Introduction .............................................................................................................. 105 8. Power Considerations 107 8.1 RDK Keyboard..................
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 9 1. Introduction 1.1 Scope This document was written for firmware and hardware developers that want to understand and makemodifications to the PRoC™ LP KBM Reference Design Kit (RDK). This document provides a description of the hardwar...
10 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Introduction 1.4 Conventions The following are easily identifiable conventions used throughout this user guide. 1.4.1 Definitions The following are some definitions of words found in this document. There may be other meanings tothese...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 13 2. WirelessUSB™ Protocol 2.2 2.1 General Overview The WirelessUSB™ protocol 2.2 is designed to address 2-way Human Interface Devices (HID) aswell as general purpose devices; it provides reliable 2-way communication between a wireless...
14 CY4672 Reference Design Guide, Document # 001-16968 Revision ** WirelessUSB™ Protocol 2.2 accommodate hundreds of WirelessUSB devices in the same space. Each bridge/HID pair must usethe same PN code and channel in order to communicate with each other. 2.1.3 Chip Error Correction In the presence o...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 15 WirelessUSB™ Protocol 2.2 2.1.7 Channel Selection Algorithm The channel selection algorithm produces a subset containing 13 of the possible 78 channels. Thechannel selection algorithm is based on the network ID, with each channel in ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 17 WirelessUSB™ Protocol 2.2 2.2.2 Idle Mode (HID only) The HID enters this mode after a power on reset before it has had any communication with the RDKbridge. If the bridge’s MID is stored in non-volatile memory the HID retrieves the b...
18 CY4672 Reference Design Guide, Document # 001-16968 Revision ** WirelessUSB™ Protocol 2.2 2.2.5 Enhanced KISSBind™ KISSBind provides the ability to automatically bind out of the box without any intervention by theuser other than installing the batteries. KISSBind essentially is a bind process whi...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 19 WirelessUSB™ Protocol 2.2 Figure 2-4. KISSBind Transaction Sequence Master Slave KISSBind Request Ch N, PN 1 KISSBind Response Connection Request Auto ACK Auto ACK RX KISSBind Request Ch N + 1, PN 1 Master is in the connected state o...
20 CY4672 Reference Design Guide, Document # 001-16968 Revision ** WirelessUSB™ Protocol 2.2 2.2.6 Unbind An ‘unbind’ mechanism allows the bridge and HIDs to return to their default unbind mode as if theyhad never bound to any system before. The bridge dedicates a bind flag to each device type that ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 21 WirelessUSB™ Protocol 2.2 Figure 2-5. Back Channel Transaction Sequence Bridge Device 1 Device 2 BCD=1 Auto ACK Data CRC Seed = A,A CRC Seed = !A,A CRC Seed = A,A CRC Seed = !A,A BCD=1 CRC Seed = A,A CRC Seed = A,A CRC Seed = !A,A CR...
22 CY4672 Reference Design Guide, Document # 001-16968 Revision ** WirelessUSB™ Protocol 2.2 2.2.9 Dynamic Data Rate and Dynamic PA Dynamic data rate and dynamic PA provide the ability to improve the immunity to interference andreduce power consumption. Dynamic data rate is device behavior based and...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 23 WirelessUSB™ Protocol 2.2 2.3 Packet Structures The first byte of each packet is the Header byte. Some packets may consist only of the header bytewhile other packets may contain up to five bytes. Type[7:4]: The following packet types...
26 CY4672 Reference Design Guide, Document # 001-16968 Revision ** WirelessUSB™ Protocol 2.2 2.4 Bind and Reconnect Timing When the bind button on the bridge is pressed, the bridge goes into bind mode. In bind mode, thebridge uses the bind ID to communicate with any HIDs that want to bind to the sys...
28 CY4672 Reference Design Guide, Document # 001-16968 Revision ** WirelessUSB™ Protocol 2.2 Figure 2-7. Reconnect Timing Diagram 2.5 Signature Byte The PRoC LP RDK uses the Signature byte to determine if the HID has ever been bound to anybridge before. If the HID has never bound to a bridge, the no...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 29 WirelessUSB™ Protocol 2.2 2.6 Encryption WirelessUSB PRoC LP RDK supports Tiny Encryption Algorithm (TEA) and Advanced EncryptionStandard (AES) 128 to encrypt application data. Data packets may be encrypted for privacy. Allencrypted ...
30 CY4672 Reference Design Guide, Document # 001-16968 Revision ** WirelessUSB™ Protocol 2.2 Figure 2-8. TEA Encryption Key Management 2.6.2 AES Encryption AES_Encrypt requires the two variables tx_packet and AES_Key to be set prior to the call. Eachcontains a 16 byte (128 bit) value. At the complet...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 31 WirelessUSB™ Protocol 2.2 2.6.2.1 AES Key Management The encrypt key is stored on the keyboard and the decrypt key is stored on the bridge during compil-ing time. There is no dynamic encrypt key exchange in the running time. 2.6.3 En...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 33 3. Mouse 3.1 Introduction This section describes the design goals, architecture, firmware source code modules and configura-tion options for the PRoC™ LP mouse. It does not cover the details of the radio subsystem or theconfiguration...
34 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse Figure 3-1. Bottom View Bind Button and On-Off Switch Figure 3-1 shows the bottom of the mouse with the optics window, power switch, and Bind button. There are two screw holes above the label. The top of the mouse can be remove...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 35 Mouse 3.2.2 Hardware Block Diagram Figure 3-3. Mouse Hardware Block Diagram 3.2.3 Schematics All schematics for the optical wireless mouse are located in the following directory: <installationdirectory>\Hardware\Mouse. The sche...
36 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse test mode that is compatible with the Cypress Manufacturing Test Kit, use a shorting block and shorttogether pins 4 and 5 before power is applied. 3.2.4 Hardware Considerations The mouse design uses the SS12 schottky diode (D1)...
38 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse 3.3.2.1 Global Configuration Following is a description of the Global Resources that are configured for the CYRF69103 PRoC LP Programmable Radio on Chip. Care must be taken when modifying these values as they affectthe user mod...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 39 Mouse rupt API to this module is not used. See the SPI Module on page 40 for how this module is used to implement communication with multiple devices on the SPI bus. 3.3.2.3 Programmable Interval Timer User Module The Programmable In...
40 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse The mouse firmware is partitioned into two logical groups. The Common group is a collection of codemodules that provide the underlying support for the application. This group provides services suchas radio protocol, radio drive...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 41 Mouse In the PRoC RDK mouse design, the master SPI communicates with both the radio and optical sen-sor. Because the optical sensor does not supports 3-wire SPI mode, the 4-wire mode is employed. Inorder to save the GPIO pin, the IRQ...
42 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse since the microcontroller sleep feature is used. Also, when polling is enabled, it is performed as abackground task during the millisecond delay. This module also adjusts the tick advancement based upon the sleep resolution. Tu...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 43 Mouse which it returns to the idle state. If the mouse is unable to deliver a packet while in this state, it transi-tions to the disconnected state. In idle state the optical sensor is allowed to transition through its various rest m...
44 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse observing packet data on a Listener, a correlation can be made with a USB protocol analyzer. This isuseful for debugging data loss since the test mode guarantees packet delivery. Entry to this test mode can be changed by modify...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 45 Mouse When z-wheel motion is detected, the mouse module is notified for collection and reporting of thedata; see Mouse Module on page 42 . 3.3.5.7 Battery Module The battery monitor circuit is implemented using the Low Voltage Interr...
46 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse 3.3.6.5 MOUSE_CONNECT_ATTEMPT_TIMES This value sets the attempt times for the mouse trying to connect to the bridge before entering theBriefcase Mode. The default value is 20. 3.3.6.6 PLATFORM_H This configuration value identif...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 47 Mouse 3.3.6.14 KISS_BIND This configuration definition is used to selectively compile in the Enhanced KissBind feature. See Enhanced KISSBind™ on page 18 for a description of Enhanced KissBind. The mouse can be un-bound by holding th...
48 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse 3.3.9.1 Packet Format 1 When there is only X, Y delta data, the transmitted packet is two bytes. 3.3.9.2 Packet Format 2 When there is either z-wheel data or button data, then the transmitted packet is three bytes. In thecase w...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 49 Mouse The second portion is the time between the start of the ISR and the post of the event flag. For exam-ple, the motion interrupt takes 23 CPU clock cycles for this portion. Therefore, the Latency2 equalsto 1.917 µs for the 12 MHz...
50 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Mouse 3.4.2 Tips and Tricks A couple of ways for working with the kit are the following. 3.4.2.1 M8C Sleep When using the ICE-Cube, define the macro PSOC_ICE so that busy waits are used instead of thesleep instruction. Using the slee...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 51 4. Keyboard 4.1 Introduction This section covers the design goals, architecture, firmware source code modules and configurationoptions for the PRoC™ LP keyboard. It does not cover the details of the radio subsystem or the con-figurat...
52 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard 4.2.1 RDK Keyboard Assembly Figure 4-1. Keyboard Plastic Figure 4-1 shows the RDK keyboard plastic. Figure 4-2. Exploded Keyboard Figure 4-2 shows the keyboard with the top removed. The radio/enCoRe II LV board (PDC-9265) is...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 53 Keyboard Figure 4-3. Radio and PSoC Board (PDC-9265) Figure 4-3 shows the main controller board with the enCoRe II LV and WirelessUSB™ LP Radio. All of the components are on the top side of the board with the exception of the Bind bu...
54 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard Figure 4-5. Bind Button Figure 4-5 shows the Bind button. 4.2.2 Schematic All schematics for the PRoC LP RDK keyboard are located in the following directory: <installa- tion directory>\Hardware\Keyboard . The schematic...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 55 Keyboard 4.2.3 Keyboard Matrix The PRoC LP RDK keyboard matrix has 18 columns and 8 rows. Key presses generate a GPIOinterrupt when a column is connected (shorted) to a row. The keyboard then scans the matrix todetermine which keys h...
56 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard 4.3 Firmware Architecture There are two architectural views of the keyboard. The first is a microcontroller configuration view ofuser modules. This architecture and configuration is best viewed in the PSoC Designer™ applicat...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 57 Keyboard Figure 4-6. Microcontroller Device Architecture [+] Feedback
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 59 Keyboard V Reset This parameter is set to 2.6V. Watchdog Enable This parameter should be set to Enable, but may be set to Disable for debug purposes. 4.3.2.2 SPI Master User Module The SPI Master User Module is used to communicate wi...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 61 Keyboard 4.3.4.3 Protocol Module The protocol module defines and implements the layer used to deliver packets from the device to thebridge. It manages the binding of devices to a bridge as well as the connection and interferenceimmun...
62 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard In idle state the MCU and radio go to sleep to save power, and the keyboard application remainswaiting for input from the keys or Bind button. The timer is turned off to conserve power. This state ismaintained indefinitely u...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 63 Keyboard The first test mode is initiated by holding down the left Ctrl, left Alt, right Alt, right Ctrl, and F1 keys atthe same time. If PANGRAM_TEST_MODE is defined, the test sends the key up/down scan codesfor the test pangram: ”a...
64 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard 4.3.6.5 KEYBOARD_TEST_MODES This configuration definition is used to selectively compile code for keyboard test modes. If this valueis defined, then test modes are compiled into the executable image. If it is not defined, th...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 65 Keyboard manufacturing test code may be executed by holding the system sleep key and the Bind buttonwhen the batteries are inserted into the keyboard. 4.3.6.16 MFG_TX_MODES When the MFG_TEST_CODE is defined, the definition of this na...
66 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard The keyboard scan matrix is defined in kdefs.h and may need to be changed for different keyboards. Porting the code to another microprocessor architecture requires modification or leverage of theexisting code for processor s...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 67 Keyboard done to optimize the packet size based on the fact that the most common report has only one non-zero scan code without a modifier. The full Standard 101 Keys report format is shown in Table 4-5 . Example The following report...
68 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard 4.3.9.1.2 Multimedia Keys (Hot keys) Report An Application Report Header of 0xFF indicates that this report is a Multimedia Keys report. TheMultimedia Keys report format is shown in Table 4-10 . Example The following reports...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 69 Keyboard Example The following reports are sent if a user presses the Suspend/Sleep (Power Key 0) key on the key-board. The Suspend/Sleep down key packet sent from the keyboard to the bridge is shown in Table 4-14 . The up key packet...
70 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard Example of a Battery Voltage Level report with fully charged batteries is shown in Table 4-18 . Example of a Battery Voltage Level report with low batteries is shown in Table 4-19 . 4.3.10 Ghost Key Detection Ghost keys are ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 71 Keyboard The interrupt latency includes two portions. The first portion is the time between the assertion of anenabled interrupt and the start of its ISR, which can be calculated using the following equation: Latency1 = Time for curr...
72 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Keyboard 4.4 Modifying the Keyboard Matrix or Adding New Keys The current keyboard matrix with the USB scan codes are shown in Table 4-1 on page 55 . Custom- ers may modify the keyboard matrix or they may add new keys to their keyboa...
76 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge 5.2.1 Bridge Photographs Figure 5-1 shows the top side of the RDK bridge board. The side button on the board is the Bind but- ton. Figure 5-1. RDK Bridge Top Figure 5-2 shows the bottom side of the RDK bridge board. Figure 5-2...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 77 Bridge Figure 5-4 shows the PRoC LP RDK bridge connected with a USB adapter board to a PSoC Mini- Prog. Figure 5-4. RDK Bridge with USB Adapter and PSoC MiniProg 5.2.3 Schematics The PRoC LP RDK bridge schematics and Gerber files are...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 81 Bridge VReg This parameter is set to Disable, and the VReg will be enabled in the application code. V Keep-alive This parameter is set to Disable. Watchdog Enable This parameter should be set to Enable, but may be set to Disable for ...
82 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge 5.3.3 Model Figure 5-6. Firmware Architecture Model The bridge firmware is partitioned into two logical groups. The Common group is a collection of codemodules that provide the underlying support for the application. This grou...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 83 Bridge 5.3.4.1.2 USB HID Class Module ( USB_1_cls_hid.asm ) The additional user code provides support for the Battery Level and Link Quality software applica-tion. 5.3.4.1.3 1 Millisecond Interval Timer Interrupt Module ( MSTIMER.asm...
84 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge duration elapses with no change in report data (see the HID Specification for more information onthis topic). The check_usb_idle() function also checks the timeout for down key and ‘keep alive’ packet. A ‘keepalive’ packet is ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 87 Bridge 5.3.7 Platform and Architecture Portability The bridge firmware was designed to use the hardware features of the PRoC LP such as USB. Porting the code to another microprocessor architecture may require modification of the exis...
88 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge 5.3.12 Code Performance Analysis A keyboard report processing is used to analyze the code performance. A typical keyboard reportprocessing contains the following steps: ■ The bridge receives the keyboard report packet and proc...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 89 Bridge 5.4.1.1 Device/Config Descriptors Figure 5-7. USB Device/Config Descriptors 5.4.1.2 Keyboard HID Report Descriptor The keyboard HID report descriptor defines a Boot Protocol keyboard. This enables a PRoC LPRDK keyboard with th...
90 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge Figure 5-8. Keyboard HID Report Descriptor (Endpoint 1) 5.4.1.3 Mouse/Keyboard HID Report Descriptor The mouse/keyboard HID Report Descriptor uses report protocol format with a unique report ID foreach report. Mouse data uses ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 91 Bridge Figure 5-9. Mouse HID Report Descriptor (Report ID 1 – Endpoint 2) Keyboard multimedia keys use Report ID 2. Figure 5-10. Keyboard’s MM Keys HID Report Descriptor (Report ID 2 – Endpoint 2) [+] Feedback
92 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge Keyboard power keys use Report ID 3. Figure 5-11. Keyboard’s Power Keys HID Report Descriptor (Report ID 3 – Endpoint 2) Report ID 4 is used to send the mouse battery level and link quality report. Figure 5-12. Mouse’s Battery...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 93 Bridge Report ID 5 is used to send the keyboard battery level and link quality report. Figure 5-13. Keyboard’s Battery/Link Quality Report Descriptor (Report ID 5–Endpoint 2) 5.4.2 Keyboard Report Format The keyboard standard keys in...
94 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge Figure 5-14. Keyboard Report Format Figure 5-15. Multimedia and Power Keys Report Format Right GUI Right Alt Right Ctrl Right Shift Left Alt Left GUI LeftCtrl Left Shift Reserved Standard Key 1 Standard Key 2 Standard Key 3 St...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 95 Bridge 5.4.3 Mouse Report Format The mouse data is sent over the data endpoint 2 using Report ID 1. The format of the mouse reportis shown below: Figure 5-16. Mouse Report Format 5.4.4 Battery Level and Link Quality Reports The PRoC ...
96 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge The RadioParams Report is 8 bytes long and has the 6 data fields listed in Table 5-4 . 5.4.4.1 Requesting a New Battery Reading When the Bridge receives a control endpoint request from the host with the following parameters, i...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 99 Bridge Figure 5-19 shows the Sleep key being pressed. Note the power key reports are sent via endpoint 2 and Report ID 3. Figure 5-19. Example Keyboard CATC Trace (Power Key) Figure 5-20 below shows the Get_Report requests used to re...
100 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Bridge 5.5 Development and Debug Environment Information on the tools required and tips on using those tools are presented in this section. 5.5.1 Tools See the CY4672 Getting Started Guide for a list of tools required to build and d...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 101 6. Manufacturing Test Support, MTK 6.1 Introduction The Manufacturing Test Kit (MTK) provides production line test support in addition to providing FCCcertification tests. This section provides a description of the Tester serial pro...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 103 Manufacturing Test Support, MTK 6.4 MTK RF Protocol Command packets received by the Device-Under-Test (DUT) are ‘echoed’ with the addition of anadded byte that contains the count of invalid bits for the received packet. Extra bytes ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 105 7. Regulatory Testing Results 7.1 Introduction The PRoC™ LP RDK leverages the regulatory work done for the CY4636 RDK. The CY4636 LPmouse was tested in a certified lab and meets FCC part 15, Subpart B, Title 47 CFR–Unintentionalradi...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 107 8. Power Considerations 8.1 RDK Keyboard 8.1.1 Usage Model The following usage model are considered for the RDK keyboard. ■ 4 hours per day of 6 keystrokes per second, 5 days per week. ■ 24 hours per day with no activity, 2 days per...
108 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Power Considerations 8.1.3 Battery Life Calculations The following table shows the times spent in each state by the RDK keyboard usage model. By sub-stituting the current measurements in section Current Measurements on page 107 , th...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 109 Power Considerations 8.2.2 Current Measurements The following is the results of RDK mouse current measurement: 8.2.3 Battery Life Calculations The following table shows the times spent in each state by the RDK mouse usage model. By ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 111 9. Software Guide 9.1 Introduction This section describes the software source code modules used in order to communicate with thePRoC™ LP bridge HID device to obtain the current radio parameters for the attached Wire-lessUSB™ LP devi...
112 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Software Guide 9.2.1.1 CHidDevice Class Methods Table 9-1. CHidDeviceClass Methods Method Type Description OpenHidDevice() Public This method sets appropriate access rights, attempts to open a han-dle to the HID device, obtains the ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 113 Software Guide 9.2.1.2 CHidManager Class Methods Table 9-2. CHidManagerClass Methods Method Type Description Create() Public This method creates an invisible window and uses the returned win-dow handle to register for HID device not...
114 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Software Guide 9.2.2 System Tray Module The System Tray module defines the CCySysTray class which provides the interface to the systemtray for the application. This module is not expected to require any modification, however all sou...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 115 Software Guide 9.2.3 WirelessUSB System Tray Application Module The WirelessUSB System Tray module is the main system tray application. This module places theicon on the system tray bar, manages the HID devices, displays pop up mess...
116 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Software Guide 9.2.3.2 CMainFrame Class Methods The CMainFrame class is the Visual C++ generated file that is a derived frame-window class for thesystem tray application's main frame window. This class has been modified to also perf...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 117 Software Guide 9.2.3.3 CWirelessUSBStatusPropertyPage Class Methods The CWirelessUSBStatusPropertyPage class is the Visual C++ generated file that implements theWirelessUSB Device Status Property Page, a unique property page is crea...
118 CY4672 Reference Design Guide, Document # 001-16968 Revision ** Software Guide 9.2.3.5 CHidTrayDevice Class Methods The CHidTrayDevice class is derived from the CHidDevice class and is the class used to interfacewith WirelessUSB devices. 9.2.3.6 CHidTrayManager Class Methods The CHidTrayManager ...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 119 Appendix A. References CY4672 Getting Started PSoC Designer™ version 4.3 documentation CY3631 Manufacturing Test Kit Device Class Definition for Human Interface Devices (HID) ( http://www.usb.org/developers/hidpage ) Avago ADNS-3040...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 121 Index Numerics 1 millisecond interval timer user module 81 A acronyms 10advanced encryption standard 29 decrypt key 31encrypt key 31 AES See advanced encryption standard AES encryption 30application code 83architecture keyboard 51 A...
CY4672 Reference Design Guide, Document # 001-16968 Revision ** 125 Revision History Document Revision History Document Title: CY4672 Reference Design Kit Guide Document Number: Revision ECN# Issue Date Origin of Change Description of Change 1.0 10/3/06 ARI New document. The Beta copy of this manual...
Cypress Manuals
-
Cypress CY7C1363C
Manual
-
Cypress CY7C1307BV25
Manual
-
Cypress CY7C1471V25
Manual
-
Cypress CY7C1416AV18
Manual
-
Cypress CY7C1007B
Manual
-
Cypress CY7C1527AV18
Manual
-
Cypress CY7C1145V18
Manual
-
Cypress CY7C68301C
Manual
-
Cypress CY7C146
Manual
-
Cypress CY7C68023
Manual
-
Cypress CY7C1314BV18
Manual
-
Cypress CY62128E
Manual
-
Cypress CY7C1410JV18
Manual
-
Cypress CY8C23433
Manual
-
Cypress CY7C1372D
Manual
-
Cypress CY2309NZ
Manual
-
Cypress CY7C1387D
Manual
-
Cypress CY7C1350G
Manual
-
Cypress CY7C1380C
Manual
-
Cypress CY7C601xx
Manual